3 ms·
In my opinion, in not using JavaScript they are missing out on a really nice DX. This is the kind of app that could be highly optimized _despite_ using React or
by tills13 3y ago
In my opinion, in not using JavaScript they are missing out on a really nice DX. This is the kind of app that could be highly optimized _despite_ using React or something similar. Knee-capping your hiring to Make A Point (tm) is silly.
- james2doyle 3y agoNice DX at the cost of UX. The current state of web development has been ruined by putting developer experience over user experience. A great example that was shared on HN a few days ago: https://ericwbailey.website/published/modern-health-frameworks-performance-and-harm/ https://ericwbailey.website/published/modern-health-framewor... This person couldn't use the site. But at least the developer got to see red squiggles when they didn't format their object properly! If you see "not using JS as much" as knee-capping your hiring, then you are putting your personal preferences ahead of what is good for the users.
- callalex 3y agoServer side rendering in no way guarantees a bad DX. Such a statement is narrow-minded.
- austinjp 3y ago"Highly optimised" depends what you're optimising for.
- izoow 3y agoI have yet to see a website that felt better to use after switching to React or similar. To me it always feels like a straight downgrade in UX. A site that felt nice and snappy suddenly becomes heavy and sluggish.