6 ms·

It's an odd way to judge the success of a project based on number of recent blog posts or whatever. In general Elixir is a bit more quiet that way, but that do

It's an odd way to judge the success of a project based on number of recent blog posts or whatever. In general Elixir is a bit more quiet that way, but that doesn't go to say its not nice to use.

jstummbillig 4y ago
I questioned neither success nor usability. (Apparent) activity of a project relative to how active the overall space is seems like a decent metric to look at.
- threatofrain 4y ago
  I would also look at https://trends.google.com/trends/explore?date=today%205-y&geo=US&q=%2Fm%2F0pl075p https://trends.google.com/trends/explore?date=today%205-y&ge...
- andy_ppp 4y ago
  Ther weirdest thing about Elixir projects like Phoenix is that they don’t rewrite them changing things needlessly every generation, instead something about the language and decisions made causes things to be very stable. You might see this as a lack of activity but they really have worked on great new features with every release. Phoenix is really lovely, I’ve been using Absinthe the GraphQL add on and it’s been awesome and for the first time I’m starting to play with channels and web sockets which are really so well done and so scalable. The only thing I’d really like is types and better introspection support in my editor but pattern matching often can be used to simulate runtime duck typing to a certain extent protecting you even if your program will still compile. Maybe worth trying it out as Elixir and Phoenix are quite simple compared to a lot of magic you’ll see in OOP programming languages.
  - namaria 4y ago
    >something about the language and decisions made causes things to be very stable We should never underestimate the value of building on solid foundations. This may not be as intuitive with software as with, say, buildings. But it's just as true. Start with a language slapped together quickly and you end up with tonnes of unnecessary headaches down the line. Start with one built around the main problem it's trying to solve, with a lot of foresight and early improvements built in, and you eliminate whole classes of problems.
  - signaleleven 4y ago
    LiveView, which of course isn’t exactly Phoenix but is closely related, changed a great deal late last year. These were welcome changes but they were significant.
  - ramchip 4y ago
    Reminds me of this twitter thread from Jose yesterday: > I keep reading the false dichotomy that languages/frameworks either evolve (and therefore break code) or stagnate (and are stable) while there is plenty of evidence in both old (C#, Erlang, etc) and new (Rust, Go, Elixir, etc) that you can evolve without breaking code. [1/4] https://twitter.com/josevalim/status/1560552538004389890 https://twitter.com/josevalim/status/1560552538004389890
    - BuckRogers 4y ago
      Linus Torvalds has a simple demand: don’t break userspace. It’s hard work, but breaking changes should be rare. As a happy C# dev, very rarely is anything broken over here. Some obscure changes were made for the upgrade to 4.8 and .NET 5.0 but there are significant benefits.
- conradfr 4y ago
  I think LiveView has taken a lot of effort off the main Phoenix project.

It's an odd way to judge the success of a project based on number of recent blog posts or whatever. In general Elixir is a bit more quiet that way, but that doesn't go to say its not nice to use.

jstummbillig 4y ago

I questioned neither success nor usability. (Apparent) activity of a project relative to how active the overall space is seems like a decent metric to look at.

threatofrain 4y ago
I would also look at https://trends.google.com/trends/explore?date=today%205-y&geo=US&q=%2Fm%2F0pl075p https://trends.google.com/trends/explore?date=today%205-y&ge...
andy_ppp 4y ago
Ther weirdest thing about Elixir projects like Phoenix is that they don’t rewrite them changing things needlessly every generation, instead something about the language and decisions made causes things to be very stable. You might see this as a lack of activity but they really have worked on great new features with every release. Phoenix is really lovely, I’ve been using Absinthe the GraphQL add on and it’s been awesome and for the first time I’m starting to play with channels and web sockets which are really so well done and so scalable. The only thing I’d really like is types and better introspection support in my editor but pattern matching often can be used to simulate runtime duck typing to a certain extent protecting you even if your program will still compile. Maybe worth trying it out as Elixir and Phoenix are quite simple compared to a lot of magic you’ll see in OOP programming languages.
- namaria 4y ago
  >something about the language and decisions made causes things to be very stable We should never underestimate the value of building on solid foundations. This may not be as intuitive with software as with, say, buildings. But it's just as true. Start with a language slapped together quickly and you end up with tonnes of unnecessary headaches down the line. Start with one built around the main problem it's trying to solve, with a lot of foresight and early improvements built in, and you eliminate whole classes of problems.
- signaleleven 4y ago
  LiveView, which of course isn’t exactly Phoenix but is closely related, changed a great deal late last year. These were welcome changes but they were significant.
- ramchip 4y ago
  Reminds me of this twitter thread from Jose yesterday: > I keep reading the false dichotomy that languages/frameworks either evolve (and therefore break code) or stagnate (and are stable) while there is plenty of evidence in both old (C#, Erlang, etc) and new (Rust, Go, Elixir, etc) that you can evolve without breaking code. [1/4] https://twitter.com/josevalim/status/1560552538004389890 https://twitter.com/josevalim/status/1560552538004389890
  - BuckRogers 4y ago
    Linus Torvalds has a simple demand: don’t break userspace. It’s hard work, but breaking changes should be rare. As a happy C# dev, very rarely is anything broken over here. Some obscure changes were made for the upgrade to 4.8 and .NET 5.0 but there are significant benefits.
conradfr 4y ago
I think LiveView has taken a lot of effort off the main Phoenix project.