Hacker News new | past | comments | ask | show | jobs | submit login

> 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:

    <style>body{visibility:hidden;opacity:0}</style>
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.


If they weren't in that morass they'd be writing about how happy they are with Common Lisp or Pony or something.


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.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: