| ▲ | Narew 9 hours ago |
| I'm not a front end dev and only use JS stuff time to time for small personal project.
There is so much JS framework out there that appear and disappear so fast. I don't know if we can call it innovation. I have the impression they just reinvent the wheel with so little value added.
I prefer to keep on React at least it will not disappear the next time I will do some change on my project. |
|
| ▲ | ixxie 8 hours ago | parent | next [-] |
| It's really hard to be sure, but my pet theory is that frontend tech has been rapidly evolving since it had to solve some real problems that are relatively new at scale: - Work with reactive variables - Combine three different languages - Write modular code - Enable highly response designs The target platform (the web) doesn't natively support all of these things elegantly, and maybe for good reasons. I've got the feeling that frontend frameworks are starting to converge to some consensus on some of these things (e.g. signals), and I hope the next decade will be more stable than the last. |
| |
| ▲ | agos 2 hours ago | parent [-] | | That is my feeling/hope as well. Modules were a big win, even if the advantage was felt mostly in bundlers and it’s just now arriving in browsers and node. Hopefully signals will be a smoother thing |
|
|
| ▲ | lopatin 8 hours ago | parent | prev | next [-] |
| grug say ok to react |
| |
|
| ▲ | uoaei 9 hours ago | parent | prev [-] |
| My pet theory is that frontend devs have so little on the critical path, and are usually overqualified for the kind of work they do, that they keep reinventing these interesting paradigms for managing state in GUIs basically just so they can keep themselves entertained. |
| |
| ▲ | whstl 9 hours ago | parent | next [-] | | I suspect it’s bimodal. There’s lots of people able to work anywhere on the stack but choose to work on the frontend because they feel super-productive compared to others. They can switch between frameworks and even come up with new ideas. On the other side, there’s way too many frontend engineers that can barely write tests, have extremely little ability with the visual part, have never setup a new project, but are still getting super small things done. | |
| ▲ | meh3749823 5 hours ago | parent | prev | next [-] | | You are giving most front end devs way too much credit. Most just use React because that's what they were taught and see it as an end rather than as a means to an end as if it is an accomplishment. Computers have become faster while websites have become slower. You can go on a random webpage and usually see 100s of MBs of memory being used while we had computers in the 90s running 3D games with around 1/100 of that. LLMs have partly become popular because people don't want to enter the current wasteland of web pages who couldn't care less what framework you used and just want to get what they are looking for and to get out. You will see people write things like "powered by React" as if React is doing any thing except running more JS. You are not getting any closer to the CPU or any of your hardware that actually runs your machine. At best some of these front-end devs want to appear as if their job is far more complicated and sophisticated than it is. | | | |
| ▲ | robofanatic 8 hours ago | parent | prev | next [-] | | > My pet theory is that frontend devs have so little on the critical path. Given that the frontend is the first thing users interact with, doesn’t that make it one of the most critical parts of the entire product experience? | |
| ▲ | satellite2 8 hours ago | parent | prev [-] | | Could it be possible your pet theory is pretty generalisable? My pet theory is that innovation happens when you look at https://xkcd.com/1205/ and estimates it's not worth it and do it anyway. |
|
