otp VS Phoenix

Modern type system over BEAM sounds great but unfortunately OTP is still not 100% supported https://github.com/gleam-lang/otp?tab=readme-ov-file#limitat...

They seem to have rewritten/wrapped OTP, but it's not production ready. https://github.com/gleam-lang/otp

YMMV, but a BEAM language without OTP severely limits its appeal and usability.

Looks like it is an external library[^1]. Readme states it is experimental and lists some limitations.

[^1]: https://github.com/gleam-lang/otp

We have a fully type safe and OTP compatible implementation of actors and supervisors here https://github.com/gleam-lang/otp

No primitives as it's not possible to have them when compiling to JavaScript, but we do have them as types and functions in the OTP library https://github.com/gleam-lang/otp

On the advice of u/WrongJudgment6 I'm reading the Gleam OTP tests. But I can't compile, and hence can't test, the code. (I'd like to do that so I can tweak the tests to do my own experiments.) Whenever I try I get an error like this:

And docs at https://hexdocs.pm/gleam_otp/

We have a fully type safe and Erlang compatible OTP library! It is used in production today.

https://github.com/gleam-lang/otp

It is not a wrapper around gen_server etc, but instead it is a full implementation from the ground up using a very small core. This was done because:

a) Erlang OTP cannot be typed, we need different abstractions are designed with types in mind

b) We want to be confident that our abstractions are powerful enough to build something like OTP, rather than cheating by relying on type casts.

I'm very happy with how Gleam OTP is going, but it is not the focus now that an initial version is out. Tooling and documentation is more important at the moment.

A standard Phoenix app contains a priv/repo/seeds.exs script file, which populates a database when it is run, so that developers can work with a conveniently prepared environment.

There was one in the Phoenix Framework (Elixir) about issuing certificates with an invalid end date: https://github.com/phoenixframework/phoenix/issues/5737

Interestingly, Azure had this bug some years ago too leading to an outage. https://azure.microsoft.com/en-us/blog/summary-of-windows-az...

Official website: https://www.phoenixframework.org/

Since you mention Rails, have you seen https://www.phoenixframework.org/

Thus, we set out to build a desktop application using a LiveView from the Phoenix Framework in Elixir. For the uninitiated, a LiveView is a process that receives events, updates its state, and renders updates to a page as diffs. The LiveView programming model is declarative: instead of saying “once event X happens, change Y on the page”, events in LiveView are regular messages which may cause changes to its state.

It seems though like Phoenix is similar like Blazor Server (using web socket), but Phoenix is: SEO friendly (first render is plain html) Light weight, scales well and concurrency is first class Easy to develop (runs a local server so you see live updates) Compiled With auth out of the box https://www.phoenixframework.org/

Sorry to hear this. Phoenix v1.7 changed how it structures files in disk and that broke quite some of the getting started material. However, the guides are always kept up to date, so you can give it a try: https://hexdocs.pm/phoenix/overview.html

You can also see the resources on this page listed by year: https://github.com/phoenixframework/phoenix/blob/main/guides... - the recent launched ones are most likely up to date.

Yes! I love Elixir :) [Phoenix LiveView](https://www.phoenixframework.org/) is really amazing. I feel so fast working in it. I got hooked after watching Chris McCord's ['Build a real-time Twitter clone in 15 minutes'](https://www.youtube.com/watch?v=MZvmYaFkNJI&embeds_referring...), and things have improved a lot since then.

I still work on a lot of Java projects. As of JDK 17 Java has most of "ML the good parts" and has the same scalable, reliable and high-performance threading Java is famous for. JAX-RS provides a Sinatra style framework that makes it easy to write JSON API back ends. JDK 21 is just about to come out as a long term supported version and it will be even better.

I do my side projects in Python with aiohttp and think it is a lot of fun even though people tell me it is suicide (I guess if you block the thread you are in trouble)

I think "Next.js" really wants a node.js backend which has the big advantage that you can share code with the front end and back end. It's basically single-threaded but I know people who are happy with it.

The system I'd most like to try is

https://www.phoenixframework.org/

which is just great if you want to do stuff with websockets that is more interactive than what most people are doing.