4 ms·

I really don't think that people have been coming up with new frameworks because you can add [1] to 5 and get nonsense. Javascript cycles through technologies

I really don't think that people have been coming up with new frameworks because you can add [1] to 5 and get nonsense. Javascript cycles through technologies quickly because web developers cycle through technologies quickly, and they do that because they get to work on greenfield projects with minimal expectation for them to be around in 5 years a lot. Check out all the different server side frameworks and infrastructure components that have been in vogue with web developers over the last decade. In comparison, people who aren't writing consumer-facing websites and webapps tend to have much more clearly-defined goals, longer lifespans of their apps, and don't often get the choice to use anything but industry standard technology. Because of the slower cycle, there's less opportunity to redesign frameworks and core technologies even when it's allowed.

crdoconnor 10y ago
>I really don't think that people have been coming up with new frameworks because you can add [1] to 5 and get nonsense. There's plenty more nonsense where that came from. That's just an easy to understand, concrete and obviously stupid example. >Check out all the different server side frameworks and infrastructure components that have been in vogue with web developers over the last decade. In python it's mainly been django and flask for a decade. In Ruby it's mainly been Rails. Why do they have sticking power? It's partly cultural but it's largely because they were built on far more stable foundations.
- vertex-four 10y ago
  In web frameworks, over the past decade, we've had various PHP frameworks, Zope, Ruby on Rails, Django, a variety of microframeworks in various scripting languages, Play, node.js+express in a handful of configurations (though generally MVC-ish), and Phoenix. There's very likely more that I'm forgetting. In deployment, we've gone from SFTP scripts to Fabric-like software to PaaS to configuration management software to Docker, and then it seems every 6 months there's a different preferred way to make Docker do something useful. And of course there's the eternal argument over whether to deploy to VPSes, cloud platforms, or bare-metal hardware. The "hip" web companies at any given moment - the ones who need the latest and greatest components to impress investors and attract "rockstar" "10x" developers - aren't tied to any specific language. They'll pick whatever was the most popular at the time they needed to pick something. Hence, right now, you have a whole lot of companies building on Golang and node.js, where they'd've been building on RoR five years ago.
  - nickpsecurity 10y ago
    Great comment illustrating the big picture of a few years. Now we just have to figure out which of those is the best for arbitrary, use cases with easy maintenance, unlimited scaling, and high availability. Whoever figures that out will finally be "Right." ;)

crdoconnor 10y ago

>I really don't think that people have been coming up with new frameworks because you can add [1] to 5 and get nonsense. There's plenty more nonsense where that came from. That's just an easy to understand, concrete and obviously stupid example. >Check out all the different server side frameworks and infrastructure components that have been in vogue with web developers over the last decade. In python it's mainly been django and flask for a decade. In Ruby it's mainly been Rails. Why do they have sticking power? It's partly cultural but it's largely because they were built on far more stable foundations.

vertex-four 10y ago
In web frameworks, over the past decade, we've had various PHP frameworks, Zope, Ruby on Rails, Django, a variety of microframeworks in various scripting languages, Play, node.js+express in a handful of configurations (though generally MVC-ish), and Phoenix. There's very likely more that I'm forgetting. In deployment, we've gone from SFTP scripts to Fabric-like software to PaaS to configuration management software to Docker, and then it seems every 6 months there's a different preferred way to make Docker do something useful. And of course there's the eternal argument over whether to deploy to VPSes, cloud platforms, or bare-metal hardware. The "hip" web companies at any given moment - the ones who need the latest and greatest components to impress investors and attract "rockstar" "10x" developers - aren't tied to any specific language. They'll pick whatever was the most popular at the time they needed to pick something. Hence, right now, you have a whole lot of companies building on Golang and node.js, where they'd've been building on RoR five years ago.
- nickpsecurity 10y ago
  Great comment illustrating the big picture of a few years. Now we just have to figure out which of those is the best for arbitrary, use cases with easy maintenance, unlimited scaling, and high availability. Whoever figures that out will finally be "Right." ;)