Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Interview with Senior JavaScript Developer 2024 [video]

youtube.com

Post reply on HN
Print view View original

11–20 of 75 posts

Re: Interview with Senior JavaScript Developer 2024 [video]

#11

Post by dimal »

I couldn’t make it through. It’s funny but also stressed me out.

I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be.

Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that people were using React to build websites, when React wasn’t designed for that problem. It was designed for SPAs. And so with server components and Nextjs they’ve reinvented PHP. It’s like, we could have skipped a five year step and used PHP/Rails/whatever.

Re: Interview with Senior JavaScript Developer 2024 [video]

#12

Post by ramesh31 »

dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

>And so with server components and Nextjs they’ve reinvented PHP.

Except worse. There will be PHP-7 monoliths out there running on Apache until the heat death of the universe. Try updating a Node project that hasn't been touched in two years.

Re: Interview with Senior JavaScript Developer 2024 [video]

#13

Post by egeozcan »

nextworddev wrote: post #9
hu3 wrote: post #8

Earlier quoted context omitted.

The future is already here. As a tech lead, consulting for one of my clients, I have to oversee the maintenance of three JS-heavy projects (backend too) that are imploding under their own weight of technical debt. And a good part of that are dependencies.

It’s like dealing with the old Angular 1 and Meteor projects from 2015

Those are actually easy. The ones using the first versions of React with custom state management and weird conventions however, are a different story.

Those, and debugging jQuery UI problems.

I digress but in my career of using every technology possible, the pain I had debugging a huge (HUGE) jQuery UI project could perhaps only be matched by trying to make NHibernate (Hibernate ORM but for .NET) behave in some complicated (but CRUD after all) data-heavy projects.

Re: Interview with Senior JavaScript Developer 2024 [video]

#14

Post by triyambakam »

dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

I think the editing style is stressful. It could be funnier if it were slower paced.

Re: Interview with Senior JavaScript Developer 2024 [video]

#17

Post by whoknowsidont »

dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

>that people were using React to build websites, when React wasn’t designed for that problem. It was designed for SPAs.

React generated HTML on the server from the very start with Node.js. You always had some form of hydration, even before there was an explicit API and process for it.

It was built by Facebook... to build a highly utilized and extremely popular website. React had pretty popular examples and integration with RoR and Python, and of course PHP.

Why are you just making up history to fit preconceived notions?

Re: Interview with Senior JavaScript Developer 2024 [video]

#18

Post by beepbooptheory »

whoknowsidont wrote: post #17
dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

>that people were using React to build websites, when React wasn’t designed for that problem. It was designed for SPAs. React generated HTML on the server from the very start with Node.js. You always had some form of hydration, even before there was an explicit API and process for it. It was built by Facebook... to build a highly utilized and extremely popular website. React had pretty popular examples and integratio…

Idk if this is charitable. To gp's point: isn't the website of Facebook a SPA? The overall point isn't that React et al have no place, its just that they became so prominent from the changing face and market of the web itself, that somewhere a long the way we forgot it could be any way else. To the point that it is now molding js development in general.

Re: Interview with Senior JavaScript Developer 2024 [video]

#19

Post by egeozcan »

holoduke wrote: post #7
gjsman-1000 wrote: post #5

Who here wants to work on a minimally-maintained PHP project from 2011? Nobody? In 10 years from now, this JavaScript crap will be just like that PHP project is perceived today. Except it will be much worse , because the PHP project didn’t have dependency hell like this. At least the PHP project wasn’t also your phone app.

I like to work on old legacy systems from the 00s. They are all relatively simple without too many dependancies. Code is often spaghetti, but its often also not having 20 layers of abstraction. Nowadays code is so damn abstract with layers of enheritance, delegates, messaging etc. Very difficult to understand apart from the makers. Give me old code. I like it.

Let me introduce you to JSF and the magic templates. Not all old code is equal, and not all JS-heavy projects are bloated.

Re: Interview with Senior JavaScript Developer 2024 [video]

#20

Post by whoknowsidont »

beepbooptheory wrote: post #18
whoknowsidont wrote: post #17

Earlier quoted context omitted.

>that people were using React to build websites, when React wasn’t designed for that problem. It was designed for SPAs. React generated HTML on the server from the very start with Node.js. You always had some form of hydration, even before there was an explicit API and process for it. It was built by Facebook... to build a highly utilized and extremely popular website. React had pretty popular examples and integratio…

Idk if this is charitable. To gp's point: isn't the website of Facebook a SPA? The overall point isn't that React et al have no place, its just that they became so prominent from the changing face and market of the web itself, that somewhere a long the way we forgot it could be any way else. To the point that it is now molding js development in general.

>Idk if this is charitable.

It's responding concisely to the point OP was trying to make. Their "point" or perspective is not accurate and it's certainly disingenuous.

>To the point that it is now molding js development in general.

I'm not following this statement. Can you expound on this?

Post reply on HN