Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
Laravel
Laravel is a web application framework with expressive, elegant syntax. We’ve already laid the foundation for your next big idea — freeing you to create without sweating the small things.
-
ihp
🔥 The fastest way to build type safe web apps. IHP is a new batteries-included web framework optimized for longterm productivity and programmer happiness
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
I'm not looking for the overthrow of CRUD-through-MVC. Rather, Hobo and Hoodie seemed like advances---Hobo was sort of Rails for Rails, and Hoodie was an offline-first framework for something like what we now call Progressive Web Apps---when I tried them early in their life-cycle, but both seem to have withered away. And nobody else (that I can find) seems interested in improving graphical design (as in, "just use Material Design, or Carbon, or whatever"), cleaner parent/child relationships, automatically updating views and controllers to match changes to the models, and probably features that I don't know that I need.
Today, most of that mess is just how you threaten children to behave, because everybody else now has their equivalent to Rails. C#/VB.NET's ASP.NET, Elixir's Phoenix, Go's Beego, PHP's Laravel, Haskell's IHP, Java's Jakarta EE, JavaScript's Express, and literally dozens of others now have effective parity with Rails.
I'm not looking for the overthrow of CRUD-through-MVC. Rather, Hobo and Hoodie seemed like advances---Hobo was sort of Rails for Rails, and Hoodie was an offline-first framework for something like what we now call Progressive Web Apps---when I tried them early in their life-cycle, but both seem to have withered away. And nobody else (that I can find) seems interested in improving graphical design (as in, "just use Material Design, or Carbon, or whatever"), cleaner parent/child relationships, automatically updating views and controllers to match changes to the models, and probably features that I don't know that I need.
What I mean is that---apologies for the history lesson---once Ruby on Rails got its footing, it did enough that it changed how web development happen. Web applications in the 1990s was a nightmare, hacking everything together through CGI and session variables, which didn't substantially change until Rails.
Today, most of that mess is just how you threaten children to behave, because everybody else now has their equivalent to Rails. C#/VB.NET's ASP.NET, Elixir's Phoenix, Go's Beego, PHP's Laravel, Haskell's IHP, Java's Jakarta EE, JavaScript's Express, and literally dozens of others now have effective parity with Rails.
Today, most of that mess is just how you threaten children to behave, because everybody else now has their equivalent to Rails. C#/VB.NET's ASP.NET, Elixir's Phoenix, Go's Beego, PHP's Laravel, Haskell's IHP, Java's Jakarta EE, JavaScript's Express, and literally dozens of others now have effective parity with Rails.
Today, most of that mess is just how you threaten children to behave, because everybody else now has their equivalent to Rails. C#/VB.NET's ASP.NET, Elixir's Phoenix, Go's Beego, PHP's Laravel, Haskell's IHP, Java's Jakarta EE, JavaScript's Express, and literally dozens of others now have effective parity with Rails.
Today, most of that mess is just how you threaten children to behave, because everybody else now has their equivalent to Rails. C#/VB.NET's ASP.NET, Elixir's Phoenix, Go's Beego, PHP's Laravel, Haskell's IHP, Java's Jakarta EE, JavaScript's Express, and literally dozens of others now have effective parity with Rails.
I asked a similar question in a different community, and the closest they came up with was the niche Apache Beam and the obligatory vague hand-waving about no-code systems. So, maybe DEV seeming to skew younger and more deliberately technical might get a better view of things? Is anybody using a "Framework of the Future" that we should know about?