Live data from Hacker News

The Frontend Treadmill

polotek.net

11–20 of 722 posts

Re: The Frontend Treadmill

#11

> But our current framework layer is working against the grain instead of embracing the platform. Said the person with this bullshit in their page code, which will not deactivate when JavaScript fails to run: body{visibility:hidden;opacity:0} Guess who just saw it happen.

That comes from the theme they’re using, and there’s a noscript directive immediately after it. https://github.com/Mitrichius/hugo-theme-anubis/blob/main/la...

Doesn't make it any less stupid or hypocritical. Dependencies you made a choice to use don't absolve you from responsibility.

Re: The Frontend Treadmill

#12
post #8
post #5

> Whatever framework you choose will be obsolete in 5 years. I've been writing React professionally for over a decade at this point. I don't know what this guy's on about.

Component lifecycle methods to hooks and HOCs, does that ring a bell?

Yeah, and I'm not anywhere near as distressed about it as this article implies I should be.

Re: The Frontend Treadmill

#13
post #5

> Whatever framework you choose will be obsolete in 5 years. I've been writing React professionally for over a decade at this point. I don't know what this guy's on about.

Didn't React deprecate itself entirely circa 2018?

Re: The Frontend Treadmill

#14
Giving up on that treadmill after investing 3 insanely intense years consuming everything about it was the best thing I ever did. Now I write elixir (phoenix liveview), sometimes I write javascript (phoenix hooks), sometimes that javascript uses Alpine. Zero pain.

I have never felt more vindicated understanding HTTP, Hypermedia, and HATEOAS than I have in the last three years.

Re: The Frontend Treadmill

#16
post #5

> Whatever framework you choose will be obsolete in 5 years. I've been writing React professionally for over a decade at this point. I don't know what this guy's on about.

Didn't React deprecate itself entirely circa 2018?

They just keep stirring his slop and he keeps eating it, that's all I'm reading here

Re: The Frontend Treadmill

#17

Earlier quoted context omitted.

That comes from the theme they’re using, and there’s a noscript directive immediately after it. https://github.com/Mitrichius/hugo-theme-anubis/blob/main/la...

Doesn't make it any less stupid or hypocritical. Dependencies you made a choice to use don't absolve you from responsibility.

Actually, it doesn't matter at all.

Re: The Frontend Treadmill

#18

> But our current framework layer is working against the grain instead of embracing the platform. Said the person with this bullshit in their page code, which will not deactivate when JavaScript fails to run: body{visibility:hidden;opacity:0} Guess who just saw it happen.

That comes from the theme they’re using, and there’s a noscript directive immediately after it. https://github.com/Mitrichius/hugo-theme-anubis/blob/main/la...

Which is now deprecated and no longer receiving updates! Haha, that’s hilarious in context of the post.

It’s also maddeningly frustrating as someone who regularly has to update things on awful frontend projects no one else is willing to touch. Frontend work is cursed.

Re: The Frontend Treadmill

#20
post #9

To jump off the treadmill is not using a fronted framework: at all, and not using a random one and not rewriting the code later. Server side rendering, JavaScript only when needed, no separation between backend and frontend folks in the company.

No separation between backend and front end is hard. I’m not good at front end, and we don’t have a designer. I’m miles better on backend though and other team members are more talented than me for front end design.
Post reply on HN