What do you think should not be in OTP?

[AstonJ]

@max-au

This surfaces so often that I think of writing an adapter for Erlang distribution to use protobuf/gRPC/Thrift/JSON format (+have a way to make binary_to_term use corresponding serialisation provider).

You should post a thread to explore this further Maxim

@Taure

I would say you could use Nova to build cutting edge apps. From creating app to deploy a release is very fast.

That’s awesome although what I had mind when I posted was something like OTPF, i.e something that sits in-between OTP (which Kenneth mentioned needs to avoid external dependencies) and frameworks like Nova. What exactly OTPF would include could depend on the conversations in this thread (and the other one: What do you think should be in OTP?) and whatever else the community thinks such a ‘framework’ needs (that could even be it including some of what, for instance, some web frameworks currently include - and then those web frameworks could slim down to only include their respective specialist parts). Again I refer to Dave Thomas’s ideas in his course, but I have no doubt there are many others with other ideas worth exploring too (which is why I’d love to see a book or course from people like @max-au - to see how successful teams go about putting together modern/massive apps like WhatsApp).

@Taure

Issue here it is some kind of ghosts that Erlang can’t be easy to use. And that syntax is bad and so on. And you gett all kind of magic from elixir that solves this for you.

If you’re referring to how this has impacted Nova adoption, I sympathise - because it’s not easy for web frameworks to take off as there is fierce competition in the space.

José and Chris (and their respective teams) made some very smart decisions when creating Elixir and Phoenix - there is very good reason (/value) with Elixir being Ruby-like and Phoenix Rails-like - because Ruby was one of the most loved languages around and Rails was one of the most prominent web frameworks around - I would even go as far as to say it was the industry standard due to how widely it was used and how it influenced so many other frameworks. Phoenix marketed itself as a better Rails, and with Ruby like syntax to boot it paid massively imo.

So in terms of Nova and general adoption you would need to ascertain what your USP is, why someone should use Nova over leading web frameworks and would those reasons be enough for someone to choose or move to Erlang because of it? (And if not, what could you do to make that more likely to happen? Highlight the benefits of Nova? Create some screencasts to show how easy it is to create apps in it (and so by extension that Erlang isn’t so hard after all)?) Only you can decide what path it takes and who you want it to appeal to