151–160 of 161 posts
Earlier quoted context omitted.
Robust performance, error handling that's not stuck in 1982, and cross platform would be my guesses, but agree the OP could be more spicific as there are more benefits.
I hate Go as much as anyone, but it has incredible cross platform support. There's built in cross compilation for building a static binary across window/mac/linux. It's the number 1 feature in Go, lol.
Earlier quoted context omitted.
Progressive enhancement is about accommodating JS being disabled. You have missed, in your description of what users care about, anything about disabling JS. Having JS disabled is a preference observable among Opinion Havers which crawl out of the woodwork on HN, but not observable among your target audience, even when your target audience is mostly HN.
Progressive enhancement isn't about supporting the minority of users that disable JavaScript. It's about sound engineering and building a robust system that is tolerant to errors. A system that can fail gracefully. There's nothing wrong with using JavaScript. There's nothing wrong with depending on JavaScript for specific functionality. However, I don't think it's acceptable to completely break down if that JavaScrip…
Earlier quoted context omitted.
I hate Go as much as anyone, but it has incredible cross platform support. There's built in cross compilation for building a static binary across window/mac/linux. It's the number 1 feature in Go, lol.
So does C#, python, node and a variety of other languages.
Earlier quoted context omitted.
Progressive enhancement isn't about supporting the minority of users that disable JavaScript. It's about sound engineering and building a robust system that is tolerant to errors. A system that can fail gracefully. There's nothing wrong with using JavaScript. There's nothing wrong with depending on JavaScript for specific functionality. However, I don't think it's acceptable to completely break down if that JavaScrip…
Have you ever given an iota of thought to how your website looks when the CSS doesn't load? Contemplated arranging elements into ` `s to preserve some semblance of formatting, crammed some truly necessary styling into `style=`? If not, then the users that disable JS are the primary driver of thinking about how your website looks when the JS doesn't load; any two given files are about equally likely to not load, JS is…
I think you may be overthinking the appearance aspect of a failure state. The application doesn't need to look the same when CSS fails to load. However, the application should be functional.
This thinking carries over to the backend as well. My application server doesn't require all services to be up and running. Instead, it's able to query and tell what is working and what isn't. That information is then bubbled down to the UI in one way or another. That may mean certain functionality is unavailable (ex, if solr isn't reachable then search is disabled).
Earlier quoted context omitted.
This comment implies you've not used Go. It really isn't equivalent to the NPM and dependency hell that's node. Or picking the number of workers in Gunicorn. Or.. C#?
[flagged]
Earlier quoted context omitted.
Thank you for doing this. Is it possible to follow the work somewhere?
Not right now. CSP in a Datastar context is mostly a red herring. If an enterprise wants it to check a box then please reach out.
Earlier quoted context omitted.
I hate Go as much as anyone, but it has incredible cross platform support. There's built in cross compilation for building a static binary across window/mac/linux. It's the number 1 feature in Go, lol.
So does C#, python, node and a variety of other languages.