News for hackers. Stuff that matters.
Re:JavaScript hydration is a workaround, not a solution by michaelchisari on Thursday September 01, 2022 @11:54AM (#32678247)
Simplicity is almost always best, but the hardest part is pushing back on management and product that often only care whether feature requests are possible and aren't as concerned with what goes on under the hood.
Re:JavaScript hydration is a workaround, not a solution by jeffy90 on Thursday September 01, 2022 @12:58PM (#32679366)
Speed and uptime are also features. If customers like speed/uptime (they do) we need to make sure management prioritizes them and understands how certain features will work against speed/uptime.
Re:JavaScript hydration is a workaround, not a solution by jozzy-james on Thursday September 01, 2022 @02:36PM (#32680961)
been a juggling act for me for some time, and always comes down to - they'd rather take a performance hit vs. harm the branding/interactivity. tho we're in a very niche market that doesn't seem to mind (i do my best to make it as efficient as can be)
Re:JavaScript hydration is a workaround, not a solution by epolanski on Thursday September 01, 2022 @06:53PM (#32684435)
This.

We have a very slow eshop, worst than any competitor, yet the priority is always new features that will make the life of users even worse.

Re:JavaScript hydration is a workaround, not a solution by galaxyLogic on Thursday September 01, 2022 @03:16PM (#32681583)
Cool-looking things appeal to customers, and also to developers.

It's a bit like your car. It takes you from place to place and could drive much faster than speed-limits or traffic-jams allow. But getting from place to place is not all you want. You want to pay extra for the coolest looking fastest wheels you can afford.

When you work with an app or app-development tool that looks cool your self-image improves. You are a cool dude because you work with a cool-looking application. Seriously, it does have an effect on me.