10 ms·
The Web We Want
- jonstaab 7y agoI'll volunteer mine, in the hopes that it's been solved already: After transpilation, minification, and with flaky source map support in many places (e.g. rollbar downloads new source maps after the first error, and doesn't apply them retroacively to the stack trace), a lot of information about errors is lost. Combine this with ubiquitous async programming, and all you get is something like "a.x is undefined", which hardly actionable. I propose two solutions. First, instrumentation of functions (like rollbar does in python) where you can see the function's local variables and arguments alongside the stack trace. Second, async traces, which trace the scopes where a promise was created, fulfilled, rejected, and awaited. These are huge omissions in javascript tooling today.
- s_y_n_t_a_x 7y agoI haven't used rollbar, but both Sentry and BugSnag allow you to upload source maps on build. I've been satisfied with stack traces.
- Cthulhu_ 7y agoWhat I'd like to see is compiled JS with the equivalent of debug symbols; minified JS with source maps feels like a patchy solution at best, after all it's still JS which is represented and transferred as ASCII text; I feel like this could be accellerated by a lot. I wouldn't mind common libraries (jquery, react, etc) to be shipped by browsers (lazy loaded), with signature verification in the browsers themselves. CDNs / single code locations sorta help by increasing the change of a browser cache hit, but that too seems like a workaround.
- _verandaguy 7y agoHot take: the web technology toolchain is plenty powerful as it is, and expanding it will cause more problems through misuse of newer features than it would create solutions. Yes, web standards offer loads of tools that let developers and designers get _really_ creative with their work, but we've reached a point where many of us are spoiled for choice, and loads of the mainline options are used, abused, or otherwise ill-optimised to the point of making many websites heavy enough to turn many laptops into space heaters. Worse still, the "spoiled for choice" factor means that people keep finding radically new ways to use the toolchain; while this is arguably not a bad thing in isolation, it makes it _so_ difficult to keep up with what you're _supposed_ to use at any given time.
- drawkbox 7y agoTechnology and progress is great, but deciding on what to use is becoming like browsing for something to watch on Netflix (or other streaming services). Lots of the time we spend deciding, dealing with devtools and toolchains, and debugging magic helpers or abstractions on top of abstractions (and I love good abstraction), that takes time away from what we are building, the product. Simple is good, complexity is bad unless it is simple layers/parts but not too many you have to deal with, simplification is good, refactoring is necessary at this stage. In a way there is a choice technical debt. Move fast and break things, sometimes the 'break things' part of that is adhered to a little too much. Engineering/product development is taking complexity and simplifying it, are we doing that? Or are we adding complexity where it was simple? I am looking forward to the next great simplification wave.
- dfcmt 7y agoIt's in the interest of big corporations (like Google, Mozilla, and Microsoft) that making a browser is as complicated as possible so they face no competition.
- randomsearch 7y agoOne day the modern web will be sufficiently powerful and standardised to fully recreate the 1990s Java applet.
- tiborsaas 7y agoWelcome to now.
- drivingmenuts 7y agoNeeds to crash more. Lacks platform incompatibility. Needs more cheese. That wasn’t the dark ages of design. It was the bottom floor of a pit in the eye-tortuing prisons of the Inquisition in the dark ages of internet design.
- deleted 7y ago[deleted]
- randomsearch 7y agoCan’t tell which way around you’re talking. Modern web lacks cross platform - even cross browser - compatibility and is buggy as hell. I agree Java applets were pretty ugly. But that was 20 years ago...
- lijogdfljk 7y agoInteresting. I'd love to give feedback, but I don't think anything I want fits into the modern web. What I want are often problems with the modern nature of things, not so much with features lacking in the web as it stands. Eg; 1. I dislike how mutable information is. While I really value ephemerality, I think the "web" needs the ability to refer to content in an immutable way. Misinformation is big these days, and mutation only adds to confusion. It's why some information store stuff I'm writing is all content addressed; in my view information needs to be immutable. 2. Obviously tracking is a problem these days. I don't think this is a problem of the "web", but I do think it's a problem of the "web" that we have no easy way to distinguish between information sources, like an html page, vs applications with a user experience. I love big bloated web apps, but I think the user needs to be able to distinguish what type of application they're seeking. Information should not opt into complex application user experiences, aka JavaScript. The web keeps opting into more feature bloat as the default; this seems wrong. The opt-in, not feature bloat, to be clear. 3. The web as it stands also seems to embrace centralization over decentralization. This again is fine (imo) for user experience stuff; not everything needs to be decentralized. Yet, for information, especially immutable information, decentralization seems not only useful but vital. Ideally, stupid simple decentralization too. Connected hubs of peers are nice, but I don't think we should be required to run a process/server to view and manage something immutable. `git pull` a slice of the immutable information you want seems (to me) to be a critical lowest denominator here. Sharing, slicing up, distributing on flash drives, etc - the web as I'd like it should promote sharing of information in ways that fit as many people as possible; not just the ones permanently connected to the internet and so forth. I could go on, but I think ultimately what I end up describing is an alternate web. Something based around immutability and information, with opt-in full user experiences (aka javascript, wasm, etc) on top of that. What does this look like? Is this IPFS or DAT? No idea. All I know is I'm making an information store, likely very imperfect and full of flaws, with these ideals in mind. I love the model of Scuttlebutt and a compatibility of that and connected-distributed ideas like IPFS/DAT seem best to me currently. I hope we continue to embrace immutability.
- pfraze 7y agoThe immutability argument makes a lot more sense once you detach presentation from content (json, markdown, style-free html). A presentation-free Web is basically a DB with immutability acting as its versioning system. IPFS/Dat make that argument stronger my adding writability to end-users. A presentation-free Web also empowers the browser to set the presentation, which really helps with issues around accessibility, anti-tracking, end-user customization, and (I'd argue) decentralization of Web software overall.
- CM30 7y agoHmm, I really want to suggest that linked SVG files should be able to be styled like inline/embedded ones, but I partly feel this item on the site would probably cover that: https://webwewant.fyi/wants/13/ https://webwewant.fyi/wants/13/ Still, I guess outside of that, I want more customisation options and standardisation around the date/time picker interfaces on those custom fields. The fact every browser has its own version, and most of them are basically impossible to style is ridiculous. Also it's time we stopped treating form inputs like some immutable part of the OS UI and let developers customise those too. We should be able to fully style select fields/drop downs, radio buttons and checkboxes, etc.
- octosphere 7y agoThere's enough tooling as it stands. In-browser devtools are a veritable kitchen sink of possibilities to tap into. And even a cursory glance at some open source projects on Github yields a plethora of tools, modules and snippets of code to use in your project. In essence you can do anything you want with some JS, CSS, and HTML. This is the beauty of the web. We get lost when we ask for more tools and techniques to do things. It's like a massive collective hallucination that the current stack(s) for developing are unworthy or need to be drastically improved. Yes, progress is good, but we've reached a tipping point IMHO.
- qwerty456127 7y agoTrue, nevertheless the current stack(s) for developing needs to be drastically improved as long as it is meant to be a platform for building apps and not only for publishing documents. I recall how easy and fun it was to build apps with Delphi and alike IDEs and now the whole React&Friends stack scares the shit out of me.
- tru3_power 7y agoWhat scares you about it? React seems pretty easy to use?
- qwerty456127 7y agoWhen I make a WinForms app in VisualStudio I just drag-drop controls, click them and adjust properties the way I want, then click the controls and write the code which is going to execute in particular events. I have never had to learn this, I didn't need a single tutorial. Once upon a time I've just got a junior C# developer job (without knowing anything but basic C++ and SQL), were given a computer and a real task and implemented a reasonable good-looking (looking and feeling the way common to all the Windows apps) business app that went straight to production just in some hours. And I didn't need anything but intuition and the API reference. It felt exactly like playing Lego. Despite I also know basic HTML, CSS and JavaScript (I've learnt during the WindowsNT4 years) I have no bloody idea of what to do to get an approximately same result with today web-based front-end technologies. I've seen some React code and it seems pretty extraterrestrial. What scares me is the amount of what I need to learn before I can produce a useful application. And it seems (and feels the scariest) Photoshop and the art of visual design are on the list.
- tristanperry 7y agoIf this wasn't technology-specific, I'd submit an idea of: "The Web We Want... doesn't require you to accept a cookie notice, ignore an anti-ad-blocker warning and newsletter pop-up before circumventing a soft paywall in order to read a quick, shared article."
- buboard 7y agoWould you pay $0.2 to avoid that?
- short_sells_poo 7y agoYes. Or rather, I'd be happy to pay let's say $25-$50 a month for an overall "News Subscription". Then this amount would get distributed over the various news sources I visit, either based on how many articles I read from a certain source or some other "fair" mechanism.
- def_true_false 7y agoThere are block lists that deal with cookie popups and the like.
- OptionX 7y agoWhat a really want is not to have to browser tabs give triple AAA games a run for their money in resource use for little to no benefit in usability.
- katet 7y agoI know this isn't quite on topic, but this is not the web I want. I want open services to compete with the entrenched players of free-as-a-service, and I want more interop between these open services. I'm sure HN already gets the gist. I run as de-Googlified a stack as I can: Nextcloud, DAVdroid, LineageOS, exclusively Linux, a private cloud server, etc. This is for my personal usage - at work, we run the whole Google/Atlassian suite, and I'm (mostly) fine with that separation. But I positively pine for the ease of use and general UX of the closed services when I go back to my private, open-source stack. A quick case in point: the Conversations Android XMPP client I'm a Librem 5 backer, and I'm looking forward to the challenge of using it as a daily driver. So I'm looking to wean myself off WhatsApp in favour of something open. But Conversations isn't it. It's a great XMPP client, but it's not something I will ever convince the majority of my friends and family to use. It's couched in technical know-how, and while it's a great app for an open source project, it still manages to feel subpar to the closed-source, back-doorable, privacy-draining consumer offerings. Signal seems the closest so far. (I should add here that I am trying to do something about this: I contribute haphazardly to OSS I use and I evangelize it in my social circle, but it feels like an uphill battle) More anecdata: I run self-hosted GitLab, Nextcloud, and Wallabag. Hopefully Mastadon and Pixelfed soon. There is no freaking way to do SSO between all of these. Despite OAuth+OpenID being older than some of that software. Don't get me started on the fact that the quickest way to get a file from phone <-> PC is to Slack it to myself from my work account. The web I want will compete with closed-source ecosystems, instead of being a disparate collection of DIY server software that doesn't talk to each other in the slightest.
- yorwba 7y ago> the quickest way to get a file from phone <-> PC is to Slack it to myself from my work account. Assuming that phone and PC are on the same network, KDE Connect solves that scenario. You pair the devices once and afterwards you can not also share files, but also have access to a host of other features. The one I use most is clipboard synchronization.
- gregknicholson 7y agoI use Syncthing for this. I have a computer that I use to play podcasts, and the subscription list (a file) is synced to my main computer, so I can edit it from there. Syncthing is also on my Lineage OS phone (until my Librem 5 arrives) so I can have a shared Downloads folder. In the past, I used it to sync a subset of my music collection to my work computer. It's reasonably usable for a geek.
- z3t4 7y agoI was gonna write that I do not want any more tools to my web toolbox. Then it struck me, I'm working on developing ... a web tool. But I'm struggling to find "product-market-fit", who needs more/better tools ? And what do you need ?
- znpy 7y agoMeh. A lot of people say they want this and that, yet they keep using software and services from the known evil companies, and don't advocate against them. It's easy to just want things.
- pbhjpbhj 7y agoMost people perhaps don't know how to address the gap between what they want and what they use? Like me, I want federated social media so that users control their content. Probably that's only achievable legislatively, but the companies who don't want to have to break down their walled gardens - Facebook, Google, Microsoft (eg Skype) - can buy off ("lobby" you might euphemistically call it) the major political party in my country, I'm sure. Where does that leave me? If I stop using Facebook I just lose out from contact with various social circles (maybe that would be better for me, but that's an entirely separate question), I can use Matrix (say?) but I don't know of a bridge that will free my Facebook messages? Moreover most of the population probably don't know what they don't know and so aren't aware of the technical possibilities that are there, never mind how they might be put together as a tool they then can realise they want ... And that's not even to address things like companies finagling themselves into education or healthcare.
- znpy 7y ago> If I stop using Facebook I just lose out from contact with various social circles, I can use Matrix (say?) but I don't know of a bridge that will free my Facebook messages? My opinion is that this approach is wrong and less smart than it sounds. This approach suggests that it is possible to smoothly move from one close platform to another one, but it is not. Network effect is everything in social network, but if you stay on facebook you're keeping its network effect in place, effectively vanishing the need to even explore another social network, federated or not.
- davidy123 7y agoThis is the Web I want and am working on, in significant organizations that are also working on this web (connected to DLTs &c via DIDs), as a solution to everyday problems and a transformative way forward. https://ruben.verborgh.org/blog/2017/12/20/paradigm-shifts-for-the-decentralized-web/ https://ruben.verborgh.org/blog/2017/12/20/paradigm-shifts-f...
- wruza 7y agoBack in the 199x I was able to draw a design and pretty decent ui simply in CorelDraw. Stack some shapes, promote outlines, stretch textures, intersect/combine/diff/layer/group, place along few guides and that’s it. Now add some linear algebra on few points to make it resizable (including scroll and time axis) and everyone will create any app or site they need in hours. That’s what I did, working as a teenage ‘designer’ in a small typography producing promotional posters, business cards and info booklets (basically, almost all websites you can imagine, but on paper). Oh, and forms, lots of forms. I mean, finally throw away that html/css mindfuck, please, and provide some decent shaping and coordinate relationship system instead. So I could go back to that boring 20 projects a week routine.
- danso 7y agoI won’t argue that today’s web landscape isn’t bloated, but the designs you built in 199x had potential audiences several degrees of magnitude smaller and less diverse (in terms of users and devices) than what the average webdev has today. I don’t think it’s possible to have such breadth and size of userbase and use-cases without a non-trivial increase in build complexity.
- hedora 7y agoWhy should a layout designer care which device the document is rendered on? (Beyond form factor which is addressed by “ promotional posters, business cards and info booklets (basically, almost all websites you can imagine, but on paper)”) Similarly, how does CSS help me translate my document? (based on the court findings in the recent Dominos case, web accessibility technologies may as well not exist, even though that problem has also been solved for paper for a century).
- danso 7y agoHuh? Nothing is stopping you today from creating an image map or do table-based design, other than a client who wants a mobile-friendly design. I don't recall mentioning anything about translation. I don't know what hot-button issue you're going on about but I have a feeling it's tangential to the topic of web design.
- iratewizard 7y agoThis is turning into a great thread for developers to vent about browsers. "Accept/block Notifications?" have become the DHTML popups of late.
- emsy 7y agoI have this idea for quite some time, but it really manifested after I started using React. I'd like to hear the thoughts of fellow web developers on this. The whole browser facing side of the web is a mess. I think it's quite similar to C++'s situation. Because we require backwards compatibility, the standard is becoming an unmaintainable mess and the best plan would be to phase out the current browser technology while building something that applies the lessons learned from the current web and build something that is simple and powerful. I think WebGL and WASM would be a good way to start. That way we could build a new browser inside the old browser and once the new browser is stable, we can build the old browser inside the new browser and let it have it well deserved EOL. I'm usually in favour of fixing existing solutions than to start from scratch, but the current web is such a badly engineered mess that it warrants a rebuild.
- notduncansmith 7y agoWhat are some of the design choices you would make differently than existing browsers?
- emsy 7y agoDitch CSS and HTML completely and create a sensible layout engine. If you base everything on a low level rendering API, you can basically create your own framework (though you shouldn't need to). Databinding, event handling etc. should be as simple as in Desktop apps, so we don't need to create ham-fisted abstractions á la Angular or React. Make it so that 90% of the websites don't need any additional code (so that you can reasonably ask users for code execution permissions, similar to notifications). Maybe add the option for low level networking so you don't need to create interfaces so you can support mail protocols natively (I'm unsure about this). Make accessibility so simple it becomes the default. Performance should be a no brainer too. Make tracking as hard as possible from the get-go. Keep the specification lean and don't add stuff on corporate whims. Reduce the memory usage of browsers. Since it's based on WASM you can use any language you want. Hopefully this will encourage better programming practices. Because frankly, the current JavaScript framework/NPM/Yarn/Gulp/Bower/whatever environment is just ridiculous. Most technical issues can realistically be tackled. I doubt you could win against Google et al. on the tracking/code execution stuff.
- jascii 7y agoWouldn't it make more sense to have those discussions under the moniker of the WWW consortium rather then having yet another entity?
- bsaul 7y agoSomething i hadn’t considered before i started working with a historian friend is the duty we have as developper to provide searchable, durable, standard content for future generation. it is very likely the wide majority of today’s content won’t be searchable by historians 200 years from now, because of all the walls we put, of all types (sign up only content, native apps, disappearing companies trashing their database, etc.).
- hedora 7y agoI want tracking to be opt in, and content serving to be decentralized (at an organizational level — not one company with a decentralized network). I want the user agent to enforce this, and I want open standards so anyone can build a user agent. NNTP achieved these goals. The web has failed in all of these dimensions in practice.
- forgotmypw3 7y agoThe Web I Want: * Usable on a older devices and slower connections * Respect for accessibility, including no-JS and no-mouse * Markup that weighs less than 20x the content * No malware and adware * Respect for non-Chromefox users Edit: Just more respect for the user in general would be very nice. Pop-ups. Hostile TOSes. Making user jump through hoops. Spam. Unsubscribe that requires login. Text that's mixed with promotional links. Hostility to no-JS users. I've decided that this is not the Web I Want a while ago, and when I come across this type of crap, I just leave. And I don't click, e.g. medium.com, links anymore I am much happier now as far as browsig the Web goes, my stress levels are down. With the time I've saved, I've been able to find new, nice, quality websites, which I visit instead. And I realized something else: The quality of content I access has become higher as a result. Good quality content is apparently accessible. Crap quality comes with the above. TL;DR: Stop putting up with crap.
- judge2020 7y ago> Respect for accessibility, including no-JS and no-mouse How is JS directly related to accessibility?
- pjmorris 7y agoNot really an expert, but here goes: JS is for talking to computers, text is for talking to people. Accessibility, practically speaking, often means text-to-speech. At that point, JS is just gobbledygook in the way.
- forgotmypw3 7y agoAccessibility is not just about vision-impaired users. It is about making your website accessible -- to anyone. JS websites without fallback reduce accessibility for: * Users with slower devices * Users with dated devices and browser software * Devices with poor connectivity * Users who have JS disabled through no choice of their own. * Users who choose to disable JS. * Browsers which do not support JS. * Accessibility software. * Not to mention bots, scrapers, etc., who also have valid use cases. This is a non-comprehensive list I came up with in just a few minutes. I'm sure there are many more items that can be added to it.
- mfer 7y agoI find it interesting that for this site the "we" is web developers. It isn't web consumers or, for lack of a better term, typical users.
- ryu2k2 7y agoCan they help building a time machine to undo the iPhone?
- c-smile 7y agoI believe that most frustrations we've got is in the fact that we are trying to handle two distinct tasks by single tool. 1. Web as a source of information. Super Wikipedia as you wish. Mostly for us - readers. 2. Web as a functionality delivery tool - access and interaction with applications. As we know any universal tool is not that good for the particular task as specialized one. And that is the main problem I think. At early stages we had semistatic HTML(3.2)/CSS(2.1) that was quite adequate for task #1 (reading, consuming information). And we had Java applets for applications. These two were more or less orthogonal and could evolve independently so they still be specialized tools optimal for the tasks they serve. Hey, we had Android with Java UI... so technically things like VSCode or Google Docs could be just Java [or Kotlin or whatever] applications inside browser if someone really wants that ...
- _bxg1 7y agoThe problem with the web isn't its technology; that part is amazingly great now. The problem is with (a subset of) the people who make websites, and the business interests driving them.
- RenRav 7y agoWell that was a bad first impression. I don't want mobile websites asking to place their shortcut on my homepage.
- smithproxy 7y agoI want a Web in which we use different languages to describe a document and the UI for an app.
- revskill 7y agoYou often don't even know what you want until you build it, try it in PRODUCTION. I prefer a scientific method to discover what we really want here.
- zzo38computer 7y agoI want the user to be in full control and not the web site provider.
- godDLL 7y agoI threw this down the tubes, but put this here as well: What I'd like to see is an HTMLx that addresses the core needs of the Web-using entities, and an ecosystem of Web extensions that expand on the capabilities of it. So, something like what smartphones with their apps and markets are doing. Basic call and message capabilities, but then there's TrueCaller and WhatsApp and the like. Bear with me. Business, gaming, video and publishing would be the core interests. So this HTMLx would get forms and credit card processing and the like, accelerated sound and input and graphics and networking, two way streaming and en/decoding, and lastly, a responsive grid and symbolic styling. Everything else, all of it – client side tracking, syndication, advertisement, compulsory client-side computation of various forms like fonts and GPU or native kernels, even JS code and client storage and cookies – I think should be available through a market. If your website is using something like that, let it suggest an "app" module to the user to install and enable on this domain. "Please support our project by enabling advertising on this domain [OK] [Later] [Never]" "For Youtube Movies please install DRM/x264 package from the market [OK] [Later] [Never]" "You will need to enable storage, code, and gaming modules to use Itch [OK] [Later] [Never]" Because browser extensions suck. Browsers suck. Mobile browsers suck. The experience of the Web sucks, for anyone that knows better. Shopping, gaming, streaming, syndication and publishing all suck big time.
- SCLeo 7y agoThe second I saw this, I knew what I wanted: CSS transition to auto heights/widths.
- tambourine_man 7y agoHas anyone looked at the source code for this page? This is not the Web that I want.