245 upvotes, 9 direct replies (showing 9)
View submission: Is modern Front-End development overengineered?
I find everything is OK until about 6 months later and everything within the framework has changed. And now whenever I search for things I get a mismatch of old and current ways of doing it and the build system needs a total overhaul. Like with Android development I spend more time administrating projects than actually creating useful code.
Comment by the_jaysaurus at 19/12/2024 at 23:47 UTC
22 upvotes, 3 direct replies
That's always been the way with front end though
Comment by big-papito at 20/12/2024 at 11:22 UTC
11 upvotes, 0 direct replies
This is why my personal project never moved for years - every time I go back, total overhaul. So I said, "I have no time for this bullshit, I am going to use HTMX". I did more stuff in two weeks than I did in five years.
Comment by SneakyDeaky123 at 19/12/2024 at 23:42 UTC
10 upvotes, 0 direct replies
Angular moment
Comment by BitchinCapybara at 20/12/2024 at 06:48 UTC
7 upvotes, 1 direct replies
What? Are you saying you don’t just love to be afraid of falling asleep and waking up to 10 new frameworks that are now the minimum requirement to get a job?
Comment by rom_romeo at 20/12/2024 at 07:52 UTC
2 upvotes, 0 direct replies
It's almost impossible not to mention Next.js here, followed by my "favorite" feature - API routing. It was ridiculously designed, then changed, but it's still ridiculously designed, and I bet they will change it again.
Comment by Buckwheat469 at 20/12/2024 at 05:40 UTC
1 upvotes, 1 direct replies
Build system? When I started with React we installed the packages by hand, then CRA came out and gave us a nice little command that included tools like Typescript, but now that's deprecated. Now we use NextJS, but wait people don't like that for some reason and Vite is the new kid in town.
I just set up a new component library a few days ago and one of the other developers laughed that I tried to use CRA because I didn't know it was deprecated. Silly me.
Comment by terserterseness at 20/12/2024 at 13:22 UTC
1 upvotes, 0 direct replies
nice thing is that in the olden days, the unspoken deal between devs was that you don't break stuff on minor updates of a library, now i update some left-pad package from 2.4.5.0.3 in npm to 2.4.5.0.4 and everything stops working because they changed, for no reason at all, all interfaces. of course this happens automatically due to some deploy or something in a container.
Comment by TScottFitzgerald at 20/12/2024 at 07:37 UTC
0 upvotes, 0 direct replies
Angular needs to rebrand itself at this point.
Comment by MardiFoufs at 20/12/2024 at 14:41 UTC
0 upvotes, 0 direct replies
At least react does not seem to have that problem.