3 ms·

Coldfusion may have been one of the granddaddies, which java's JSP copied shamelessly. So many web revolutions touted as "don't use Java and all that big stack

Coldfusion may have been one of the granddaddies, which java's JSP copied shamelessly. So many web revolutions touted as "don't use Java and all that big stack, instead use our SUPER SIMPLE stack called:" Rails: wow did rails eventually encompass a massive stack of dizzying extensions options and frameworks. React: I laughed when I saw basically a full rewrite of various Java unit testing frameworks in javascript. But HTMX seems to get love that angular/react/etc never got from a HN front page perspective. I take a dim view of AI so far, but one thing it could be fantastic for is "take this basic HTML application and write it in framework X" so I can finally see a good comparision. The web framework landscape has needed a "reference web app" since the year 2000 where frameworks could demonstrate their way of doing rendering, layout, validation, forms, routing, error handling, data binding / data retrieval, tables/grids, media. As in your web framework isn't even close to prime time unless you can show WHY it is novel or useful.

Dylan16807 3y ago
> React: I laughed when I saw basically a full rewrite of various Java unit testing frameworks in javascript. Why? Can't run java in a browser. (And don't bring up applets.) I suppose you could keep most of a testing framework as Java code, and adapt the rest for testing javascript, but that seems fussy enough for a rewrite to makes sense. Edit: Okay, if people are going to downvote, then I'll elaborate. I understand amusement in people moving from one server language to another, only to recreate the same things they already had, because they could have just stuck with the original. But you can't just stick with a server language when you're writing an interactive web page. Trying to port the tools you like is making the best of the situation, not creating work out of nothing.
- AtlasBarfed 3y ago
  Mostly because React was yet another "we're so much simpler/uncomplicated than all that enterprisey Java" sale job (just like Rails was) and lo and behold, React went full enterprisely in like less than 12 months (at least it took Rails something like 3-4 years to get to full complexity, and Rails/Ruby contributed huge amounts of groundbreaking frameworks and idioms along the way).

Dylan16807 3y ago

> React: I laughed when I saw basically a full rewrite of various Java unit testing frameworks in javascript. Why? Can't run java in a browser. (And don't bring up applets.) I suppose you could keep most of a testing framework as Java code, and adapt the rest for testing javascript, but that seems fussy enough for a rewrite to makes sense. Edit: Okay, if people are going to downvote, then I'll elaborate. I understand amusement in people moving from one server language to another, only to recreate the same things they already had, because they could have just stuck with the original. But you can't just stick with a server language when you're writing an interactive web page. Trying to port the tools you like is making the best of the situation, not creating work out of nothing.

AtlasBarfed 3y ago
Mostly because React was yet another "we're so much simpler/uncomplicated than all that enterprisey Java" sale job (just like Rails was) and lo and behold, React went full enterprisely in like less than 12 months (at least it took Rails something like 3-4 years to get to full complexity, and Rails/Ruby contributed huge amounts of groundbreaking frameworks and idioms along the way).