81–90 of 180 posts
http://lite.cnn.io/en https://text.npr.org/ Every site should have a plain html option. Or create their html so that it works fine without js or cnn.
I'm trying to assemble a list: https://sjmulder.nl/en/textonly.html but so far there aren't many sites like this that I found useful.
Earlier quoted context omitted.
It does make development easier, and at some point it just doesn't make sense to support any longer. If the number of people who visit your site with JavaScript disabled is less than the number of people who visit using the Opera browser, does it really make sense to add [number of supported browsers] x [JS on | JS off] permutations to your testing workload? Is spending the time and resources on creating a non-JS sit…
> If the number of people who visit your site with JavaScript disabled is less than the number of people who visit using the Opera browser, does it really make sense to add [number of supported browsers] x [JS on | JS off] permutations to your testing workload? If your site doesn't work for people with JS disabled, you're unlikely to see significant traffic from people with JS disabled.
It is VERY much an alpha and a lot of things aren’t working, just the bare minimum.
I'm glad he can code his brochureware site with minimal impact when JS is disabled. It is 2018 and every site is driven by JS, not just DOM events. If you disable JS, you know what you're getting into. Do we need to develop for those that decide to block CSS? Insist on deprecated browsers? You develop for your audience.
Earlier quoted context omitted.
English obviously. It is quite far fetched, but I'm just tired of seeing countless hours wasted because the numbers aren't localized properly or RTL breaks layout. It's superfluous, people should have their native tongue and should learn English as means of international communication. Also imagine encoding problems which are also great PITA going away with ascii-only technologies.
I'd prefer to take your comment as a push for a common language across the planet. In other words, remove the need for i18n before removing i18n.
Earlier quoted context omitted.
>It made web app development so much easier I aim to develop web UIs using (mostly) progressive enhancement. I adopted several practices and developed some libraries supporting this process. As a result: 1. When I need to create something, I know exactly which data structures to use. This is determined by what is available in modern browsers. 2. I can quickly prototype solutions using plain HTML focusing on logic rat…
This is also my approach, when I am allowed to set the rules. Server side rendering with vanilaJS for the snippets that actually matter.
Earlier quoted context omitted.
English obviously. It is quite far fetched, but I'm just tired of seeing countless hours wasted because the numbers aren't localized properly or RTL breaks layout. It's superfluous, people should have their native tongue and should learn English as means of international communication. Also imagine encoding problems which are also great PITA going away with ascii-only technologies.
This is some of the most self-centered reasoning I've seen on HN. Everyone should learn English to reduce your workload. It's almost a caricature of the stereotypical redneck who has never left the country and gets mad when they overhear someone speaking Spanish at Fiesta, muttering "but this is America " under their breath.
It IS a caricature.
Back in 2006/7 I remember we'd use "progressive enhancement" to make a site work without JavaScript and then add JavaScript enhancements for those who had JS enabled. At some point (maybe after the popularity of Google Maps?) nobody wanted progressive enhancement and it was totally cool to just ignore users who had JS turned off. It made web app development so much easier, but probably less user friendly. It feels li…
With that mandate, the site (about 300 pages) ended up almost completely js-free. I think there was only one page that had js, and that was for a calculating widget.
js is great for certain things, but certainly not necessary for all the things it's used for.
http://lite.cnn.io/en https://text.npr.org/ Every site should have a plain html option. Or create their html so that it works fine without js or cnn.
I'm trying to assemble a list: https://sjmulder.nl/en/textonly.html but so far there aren't many sites like this that I found useful.
Earlier quoted context omitted.
This is some of the most self-centered reasoning I've seen on HN. Everyone should learn English to reduce your workload. It's almost a caricature of the stereotypical redneck who has never left the country and gets mad when they overhear someone speaking Spanish at Fiesta, muttering "but this is America " under their breath.
Maybe some see it as self-centered, but I find it resonates with me strongly. Now that we're a global civilization, life would be much simpler of global-scale things get standardized. Like, if metric system was adopted everywhere. If people used ISO 8601[0] instead of whatever is their random way of writing time down. If people used one well-defined number format. Etc. IMO what's really being self-centered is - when…