11 ms·
Personally, I think the web/browsers has churned far too much, and if that stopped happening, perhaps we would get more accessible sites and browser diversity a
by userbinator 5y ago
Personally, I think the web/browsers has churned far too much, and if that stopped happening, perhaps we would get more accessible sites and browser diversity as people "stop looking for new dogs and start teaching new tricks to the old ones." Of course, Google would try its hardest to never let that happen, since change is its weapon of monopoly.
Related: Stop Pushing the Web Forward (2015) https://news.ycombinator.com/item?id=9961613 https://news.ycombinator.com/item?id=9961613
- rapind 5y agoIt would be great to slow down on features and focus on securing the platform (browser) so it didn’t leak like a sieve.
- judge2020 5y agoAll the problems with security seem to come from JavaScript exploits intrinsic to the engine, not any of the new features (misty because the new features are strictly typed and have the power of hindsight with modern design principles), so it’s not like new features are strictly an antigen to security.
- thefr0g 5y ago> All the problems with security seem to come from JavaScript exploits intrinsic to the engine Yes the classic memory-related bugs come from the engine, but the comment explicitely mentioned leaks and I don't think that was about the memory ones. Many of the new "features" turned out to leak sensitive or at least identification-enabling information. Imo having remote code execution without a big red warning that this is stupid and you should not do it that users can't click away without being forced to think about it just isn't a good idea, even if it is sandboxed. At the very least we should have a permission-based system where users need to authorize every single Javascript API, for every single connection/file/database/whatever and be unable to ignore it without disabling the APIs. That would imo be the best compromise since web-devs would be forced to think about what they are doing to users computers¹ while still allowing applications to be built. ¹ My hope being that they wouldn't include [bullshit fontend framework] except when absolutely necessary
- adrianN 5y agoI think you underestimate the number of users who would either blanket-approve everything or switch to a browser that doesn't nag so much. Most people care very little about their privacy online.
- Sohcahtoa82 5y agoRelevant: https://twitter.com/JimMcKeeth/status/692596120464150528/photo/1 https://twitter.com/JimMcKeeth/status/692596120464150528/pho... Indeed, users don't read error messages, and will just click whatever they think they need to click to move on.
- no_way 5y agoIronically Chrome is the most secure(not talking privacy) browser, because of site isolation and sandbox architecture. Firefox is somewhere second.
- goohle 5y agoI was hacked by IE (viruses on Windows), Firefox, and Chrome. Few years ago, at revolution, Chrome told us about MITM attack and refused to connect to Google servers, while Firefox noticed nothing. Few years later, attackers used my Chromium, which I used for work, to spy on my Firefox window, which I use for private browsing, by capturing of whole screen when Chromium sit unused. (I have it recorded on video).
- LAC-Tech 5y agoMay be risking a lot of downvotes, but I really want to work for somewhere that cares about a11y for very selfish reasons - I want to use semantic html and not have to do stupid shit like using a package that re-implements the select element with divs
- atoav 5y agoWell that is what html should be used for. I do freakishly experimental webdesign at times (like for designer portfolios, where freakishly experimental webdesign is kinda part of the thing), but for everything where it is much more about the info and the content I will bend over backwards to use semantic html (and even with those freakish sites I will try). If you never looked at your website via lynx or used a screenreader I highly encourage it. It will give you a different perspective on things.
- petepete 5y agoI work with the GOV.UK Design System and everything's geared towards making services accessible. Your government (or health service) might have their own. https://design-system.service.gov.uk/ https://design-system.service.gov.uk/
- dmitriid 5y agoYou guys are the best people. I can't express the depth of respect for you and the work you're doing.
- petepete 5y agoI don't want to take credit for the work the Design System team does (they're awesome and supremely dedicated), I stand on their shoulders.
- rablackburn 5y agoAustralia just cancelled our equivalent :( It’s been open-sourced and forked here if people would like to help keep it alive: https://designsystemau.org/ https://designsystemau.org/
- 1vuio0pswjnm7 5y agoThe recurring calls for a "faster web" or a "safer web" are responses to problems for users that web developers, "tech" companies and their advertiser customers have themselves created. Users did not create these problems and yet, unless I am mistaken, these marketing campaigns for "pushing the web forward" are directed at users. As a user, I want those problems fixed but I am under no illusions about where they come from. It stands to reason that a user-controlled web would be much faster and much safer.
- achairapart 5y agoIt's also worth reading from the same author the update on the same matter: Breaking the web forward[0] [0]: https://www.quirksmode.org/blog/archives/2021/08/breaking_the_we.html https://www.quirksmode.org/blog/archives/2021/08/breaking_th...
- musicale 5y ago> change is its weapon of monopoly I think it's OK for Google to make Chrome into an OS and cram whatever they want into it as fast as they can. Regular web browsers don't necessarily need to be on the same feature treadmill/death march (assuming they could keep up.) We seem to be trying really hard to reinvent the applet systems of the 1990s, but in a way that brings systems with 10-100x the memory and CPU resources to their knees and requires huge armies of programmers to implement. I guess JavaScript/webasm is better than Java in some ways.
- dmitriid 5y ago> it's OK for Google to make Chrome into an OS > Regular web browsers Chrome is a "regular web browser". It holds a 70% market share among web browsers. > Regular web browsers don't necessarily need to be on the same feature treadmill/death march (assuming they could keep up.) They either don't need to be on the same death march, or keep up. You can't have both. Currently, it's a major problem, because Chrome churns out 40-70 new web APIs with every release which happens every two months or so [1] So, no, it's not OK for Google to convert Chrome into an OS. [1] https://web-confluence.appspot.com/#!/ https://web-confluence.appspot.com/#!/
- musicale 5y ago> Currently, it's a major problem It certainly is an insane amount of feature churn. But the right perspective might be to look at the impact on end users. The issue for end users seems to be that they occasionally encounter "web sites" (really web apps) that only work properly with Chrome. This is sort of a bummer for iOS users, but for the most part they seem to get by just fine. Perhaps there will be a tipping point where the "web" becomes unusable from iOS, but it hasn't happened yet. I consider this a comparable problem to encountering web sites that only worked with Internet Explorer, or Flash, or Silverlight, or Java. Certainly annoying, but not really catastrophic.
- onion2k 5y agoI can't think of many new browser features I've used in the past few years. There's the permissions API and the fileReader API that are part of apps I've built (and they're very useful), and I've played with a few things like sharedArrayBuffers and WebGL2 but not in anything that's been deployed. Browsers do move fast, but not that fast, and most of the new features are super niche things that the majority of developers don't really need. If you're prioritizing looking at new things over accessibility and cross-browser support then you are making that choice; browser vendors are not forcing it upon you.
- travisd 5y agoThe one feature I want more than anything in the world (and seems to be stalled in Chrome land, which means it’s stalled overall since chrome tends to drive the standards) is the streams API (aka websockets with backpressure). There’s no easy way for clients to signal to servers that they’re overwhelmed, and the result is either saturating the network or the CPU since the message handlers are synchronous.
- AshamedCaptain 5y agoAnd yet try the popular websites on browsers from a couple years ago. Like a tablet stuck in 2015.
- onion2k 5y agoYes, and this is what really bothers me. Feature detection is a thing in browsers. There's things like @supports in CSS, "if (<property> in <API>)" in JS, and there are even whole libraries like Modernizr to make it trivial to detect whether something is available. Web developers don't bother though, and then they complain that "browsers broke their code". Browser vendors do a lot to make it possible to write robust code that doesn't break in the future. Maybe they could do more, but if web devs are failing to leverage the features that are there already then why would they? A whole lot of the responsibility for the broken ass nature of the web is not due to browsers.
- 5y ago
- forgotmypw17 5y agoI agree with you, and I think it can be done today, by taking matters into your own hands. I've done it by testing with historic browsers alongside modern, and challenging myself to make it work with all of them, JS and noJS, without errors, reliably. In the process, I found a set of "lowest common denominator tags which work across almost anything. I use these to build the "base" HTML. Then, I add JS with feature-checks to allow older browsers with JS enabled to still run it, though it doesn't do much at the moment. I think it's a worthwhile exercise to learn where the roots of the web are, and how it evolved, and allows you to write much more resilient code in general. The reason for this is that the longer a technique or syntax has been in use, the longer it's likely to continue to be used. Lindy effect is the name of the trend.
- thealig 5y agoI'm curious, what kind of tools and processes do you use to test that the webapps/website work on so many platforms?
- forgotmypw17 5y agoFor the time being, I mostly use manual testing. Most of the older browsers are covered by three VMs: Windows 95, Windows ME, and Windows NT 4.0. Most Windows Netscape can run in Wine, so I can use symlinked .wine directories to switch versions. I also do occasional testing at Best Buy or Walmart (many thanks to those places) at a cross-section of their available devices -- a couple of desktops, a couple of phones and tablets of each flavor, etc. I also often ask people if I can test out my website with their device (or if they want to participate in a 5-minute user study) For difficult things like Mac IE, I just have a couple of devices e.g. G4 Macs and iOS 7 iPad. Of course, there are text-mode browsers, which I usually install with apt or whatever. I also use online emulator services like BrowserStack, they have a pretty good slice in their free tier, and a couple of minutes is enough for smoke testing. Also, I sometimes come across public devices, such as desktops in survival center, library, hotel, or public community space, and I test on those. With my own devices, I test across various public wifi locations, so that I can provide workarounds for e.g. content blockers or inadequate proxying. I use Charles Proxy locally to simulate low-bandwidth connections and other common issues. I have also asked rare use-case users, such as visually impaired, to test using a script, usually through topical Facebook groups. That's about all I can think of for now, there's probably more.
- FractalHQ 5y agoAs long as it doesn’t break or give up backwards compatibility, I don’t want the web to stop improving. It’s one of the most important platforms in history. I thought we can’t teach the old web new tricks because of backwards compatibility?
- redsparrow 5y ago> Google's weapon of monopoly. This reminds me of Spolsky's blog post about Fire and Motion. [0] He gives the example of Microsoft creating an endless stream of new technologies which kept their competition busy (eg: ODBC, RDO, DAO, ADO, OLEDB, ADO.NET, ...). Get the competition to spend their resources keeping up rather than competing. 0: https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/
- brundolf 5y ago"Start teaching new tricks to the old ones" on the web usually means shipping a bunch of extra JavaScript. Which is fine when a new pattern or paradigm is being felt out, but once everybody is using this one library to do this thing the exact same way, you reach a point where it makes more sense to enshrine it in a native API. See jQuery (both Ajax and selection), Moment/Temporal, etc