9 ms·
Add limits to amount of JavaScript that can be loaded by a website
- lurker458 8y agothe ability to restrict cpu and memory consumption per page would make more sense
- lmilcin 8y agoUh... this is wrong on so many levels. What is going to be the limit? Who is going to be setting it? How is it going to be calculated? Is it the amount of loaded files? What if the page is small but then loads more dynamically later? How I, as a developer, make sure my website works everywhere? What with sites that use a lot of code but still work fast? The amount of code does not directly translate to slowness. You can have little code and slow website or a lot of code and fast website. As an example, single page applications tend to load all of its code but still manage to be responsive.
- kbenson 8y agoIf I was responsible for setting the agenda... > What is going to be the limit? Whatever the user wants it to be. > Who is going to be setting it? A default from the browser, which can be overridden by the user. > How is it going to be calculated? Is it the amount of loaded files? What if the page is small but then loads more dynamically later? Preferably by a total per-site and per page (with page being a higher amount than site). When a site/page hits its limit, halt running with a popup asking for a temporary larger limit (and a checkbox to remember the limit for this site). > How I, as a developer, make sure my website works everywhere? The same way you, as a developer, make sure it works everywhere with Javascript features. You find a sane maximum by the lowest of all the browsers that support it. If you figure out what IE, Chrome, Firefox and Safari (and their mobile equivalents) have as limits, you've basically solved the problem. > What with sites that use a lot of code but still work fast? The amount of code does not directly translate to slowness. Depending on your connection, it really does. Bad mobile connections (even if only in certain locations, like supermarkets that are constructed like Faraday cages) mean that an increase in the size of the JS loaded required to use the page directly translates into extremely slow websites, and in a lot of contexts, the first page is the only page visited, so the idea that a SPA will be quick after that first load (to stave off that future point) doesn't really solve the problem.
- throwawayy1001 8y ago> What is going to be the limit? He suggests 1mb, personally I still think it is too much. > How I, as a developer, make sure my website works everywhere? 1mb for a single page isn't enough? > What with sites that use a lot of code but still work fast? It's fast if the resources are near your device (CDN), most websites don't do that at all.
- nicoburns 8y ago> 1mb for a single page isn't enough? What about single-page apps where the whole app is "a single page". With this proposal, even lazily loading the extra bits would hit the limit.
- krapp 8y agoI strongly suspect the true purpose of this would be to make javascript unusable for all but the most trivial cases, and to train end users to fear it like a virus, or find its presence annoying, making it an anti-feature. Killing SPAs would probably be a feature in that case.
- apalmer 8y agoI think we already do this. Its built into the fabric of the web. Not sure why we are proposing arbitrary limits and additional user opt in for this. Wether a website wants to be inefficient or has a good reason for having a lot of resources it impacts the speed with which the site loads. The slower the site loads the more users are going to abandon the site. Stats say by 2 seconds most users have abandoned a slow loading site. Caveat that if the user feels the site is really worth the wait, they will wait longer. So seems everything in this proposal is already addressed...
- yuchi 8y agoI don’t know who the author of this proposal is, but I believe this should not be pursued and that his idea is uninformed. Content blockers try their best do block and remove specific parts of the web page, surgically identifying them. You can’t just randomly block stuff and therefore break an insane amount of websites and call it a day. What about web apps? Should there be a «this application wants to exceed the xMB quota» confirmation messages? Oh please no.
- irq11 8y agoYou should be making your pages work without javascript. Progressive enhancement has been a best-practice for years. I routinely use the fast JS switcher extension to turn off javascript on any site that does any number of irritating things (popups, autoplay videos, etc.) If those sites don’t work any more, then I just never visit them again. Their loss.
- humblebee 8y ago> What about web apps? I think it's important to make this distinction. A lot of websites don't need the JavaScript they ship with to present the material the users want. I agree those websites should work without JavaScript. However, you can't expect actual web applications to do this. Examples - https://www.draw.io/ https://www.draw.io/ - https://www.audiotool.com/app/ https://www.audiotool.com/app/ (sign in required; demo https://www.youtube.com/watch?v=gvIu_R8bmdA https://www.youtube.com/watch?v=gvIu_R8bmdA) - https://human.biodigital.com/signin.html https://human.biodigital.com/signin.html (sign in required; demo https://www.youtube.com/watch?v=dW4JSMlBhWQ https://www.youtube.com/watch?v=dW4JSMlBhWQ) - https://pixlr.com/x/ https://pixlr.com/x/ Other more commonly know examples - Most of Google Drive offerings - Google Analytics control panel - Twitch I see this confusion a lot when this topic is discussed on HackerNews.
- irq11 8y agoWebapps can be implemented just fine without Javascript; I’ve been doing it for years. React is a luxury, not a requirement, and progressive enhancement is a thing in all but the most demanding apps. The point is, I currently exist in a world where I randomly shut off all javascript on websites, and it’s a happy world. Personally, I’d be tickled pink if it was a built-in browser feature (and if it forced web devs to be more responsible? Bonus!)
- anontechworker 8y ago> Today's JavaScript developer is acting like they have a 100 GHz CPU with terabytes of memory. And being lazy and uninspired as a result. Not sure how I feel about a statement this broad. I work mostly with front end code and I try neat things and tricks to reduce resource use all the time. I also always push for the lightest way of doing things in PRs. I’m certain I’m not the only engineer who thinks like this.
- kstrauser 8y agoI agree. I don't do frontend stuff, but I sit next to the team that does. They take a lot of pride in making fast-loading pages that render quickly and respond instantly. That's not compatible with writing giant, bloated, inefficient code.
- vezycash 8y ago>They take a lot of pride in making fast-loading pages that render quickly and respond instantly. Maybe in your company. My experience browsing modern front-end SPA design however begs to differ. They pride themselves in loading megabytes of uncompressed images, layers of invisible background images, frameworks to load frameworks, auto-download/auto-playing 4k videos...
- seattle_spring 8y agoNo one prides themselves on any of those things.
- chris_wot 8y agoAnd yet they still do it.
- choochootrain 8y agoi agree with you but you have to keep in mind that pages which load fast on a fiber connection and render and respond quickly on the latest macbook don't guarantee the same for the average user. giving devs 4 year old laptops would help but when shiny startup is offering new macbooks how can you compete?
- troutwine 8y ago> I think it's time we start looking at the problem differently. It's resource abuse that's the root cause, so why aren't there limits on those resources? This is a flawed assumption, I think. Sure, maybe _some_ people are blocking ads because all that JS and network IO eats up battery but I bet more people block ads either because they dislike advertisements generally or they dislike advertisements based on surveillance. Whether you manage to cram your ad serving code into 1Mb or 1Kb is irrelevant for the later two groups of people.
- headcanon 8y agoAuthor's premise includes a lot of personal opinion and simple gripe against JS. not a fan of this. Whats the limit going to be? 1MB? 5? why is it the browsers job to police that? I run adblock primarily because I don't want to see ads and get tracked by sketchy sources. Resource usage is a minor bonus. If that hurts peoples pockets then so be it, most ads are out of hand and need to be tempered. Most people who run adblock aren't going to click on the ads anyway. With that said, I do hope we're able to figure out how to treat web "sites" and web "apps" differently - for the former, I want as little JS as possible since that just gets in the way of content, but for the latter, the JS is necessary to get the app running, and I don't mind if its a few megabytes in size.
- mrweasel 8y agoWhile I'm not a huge fan of JavaScript heavy sites, I do think it's a little disingenuous to drag content blocking in as part of the argument. Ads have little to do with his basic argument, it just there to make the sales pitch go down a little easier. It's also not very effective as an ad-blocker or anti-tracking tool.
- deleted 8y ago[deleted]
- gruez 8y agoWhat's stopping a site from loading javascript using a side-channel (encoded inside a png, for example), and then eval-ing the payload? I guess you can prevent this by limiting the amount characters you can send to eval, but I'd imagine it'd break a lot of sites. Plus you can probably bypass the eval limit by rolling your own eval (basically writing a javascript interpreter in javascript)
- sneakernets 8y agoSimple: stop loading those PNGs or strip them of all not-image content. The fact that you can inject code into an image sounds like a security flaw waiting to happen.
- DCoder 8y agoCan you define "not-image content"? Steganography begs to differ.
- sneakernets 8y agoSimple: Any content that isn't required to generate the image.
- Technetium_Hat 8y agoIn this case, the JavaScript is the image. It's all just bytes, they can be decided as pixels or code.
- IggleSniggle 8y agoAnything medium can be encoded and decoded. You transpile your code into pixels, CSS, whatever medium is considered "ok." Images just happen to be large and so can be used to hold a lot of information. You can't just inherently know what is and isn't encoded information and strip out "the bad stuff." Those pixels do not execute themselves (or cookies, or headers, or whatever we are still allowing). They still need an interpreter. Interpreters are indeed security flaws. Pushing people away from scannable code and towards hiding their code in other filetypes will cause a proliferation of interpreters, and a proliferation of security flaws.
- smacktoward 8y ago> A simple dialog would put the user in control of the situation: > "The site example.com uses 5 MB of scripting. Allow it?" Oh God, no. Please don't do this. 1) We know that users presented with these kinds of dialogs don't read them. They just blindly click "OK" to get the dialog to go away. So now you're just annoying people to no good purpose. 2) Even if the user does read this dialog, how is she supposed to know how much JavaScript is too much? There's no context to tell her whether 5MB is a lot, or how it compares to payloads delivered by similar sites. ("The site example.com wants to load more code than 99.99% of other sites you visit" would be slightly more helpful, but only slightly.) It just expects her to have a strong opinion on a subject that nobody who isn't a coder[1] themselves would have an opinion about. 3) If the problem we're trying to solve here is that code makes sites load slowly, making people click through a dialog isn't going to make the site load any faster. In fact it will almost certainly take the user more time to find and click the "OK" button than it would to just load the code. 4) It's measuring the wrong thing. 1 kilobyte of badly written code can do as much or more harm to the user experience than 1 megabyte of well written code will. [1] With the possible exception of people on strictly capped data plans, but now we're solving a different problem.
- kbenson 8y ago> We know that users presented with these kinds of dialogs don't read them. They just blindly click "OK" to get the dialog to go away. So now you're just annoying people to no good purpose. I would say you're annoying some people so others have the ability to make that choice, and the site developers will definitely see the friction of that dialog as something to be avoided. It incentivizes good behavior. > It's measuring the wrong thing. 1 kilobyte of badly written code can do as much or more harm to the user experience than 1 megabyte of well written code will. That depends entirely on your connection, keeping in mind your connection might be from your phone, when you have very poor reception. The fact that people are immediately assuming it only matters for execution time after loading illustrates part of the problem, which is that developers often forget about entire classes of access and thus don't consider the problems they create for them.
- kodablah 8y ago
- holoduke 8y agoThis Author got to have some personal hate against javascript. Otherwise, it just does not make sense.
- naaaaak 8y agoDisable Javascript by default and make turning it on the exception. The web would be a much better place.
- crazygringo 8y agoThis particular solution seems wrong for all the obvious reasons listed in other comments... But on the other hand, I love the idea of resource-limiting tabs by default, along all of: - CPU usage (allow an initial burst, but after a few seconds dial down to max ~0.5% of CPU, with additional bursts allowed after any user interaction like click or keyboard) - Number of HTTP requests (again, initial bursts allowed and in response to user interaction, but radically delay/queue requests for the sites that try to load a new ad every second even after the page has been loaded for 10 minutes) - Memory usage (probably the hardest one to get right though) I mean, every so often I've caught things like a Gmail tab in Chrome stuck at using 100% CPU indefinitely because it must be stuck in some infinite JavaScript loop due to a bug, as well as the occasional other random blog that uses constant 50% CPU for no discernable reason... and it would be nicer if this didn't suck up two hours of my laptop's remaining battery time before I discovered it. If the browser had soft resource limits that just gradually slowed down code execution and HTTP requests to extreme levels, with a discreet pop-up warning in the corner "this site is attempting to use higher than normal resources, click here to allow temporarily/permanently" for the times you're opening a WebGL demo... ...it seems like it would be a big win for users.
- crdrost 8y agoRight, you definitely want something that is somewhat more adaptive if you want to solve this problem. Something to the effect of "as you use more resources you slow down those resources." What's more interesting to me is the broader economic question. Do users end up flocking to those browsers because it makes the browser more snappy for the other web sites and contexts? Or do they ditch them because they are necessarily slower than browsers that don't? Is this sort of decision, in other words, a sort of suicidal option for browsers?
- acqq 8y agoThe need for the user-friendly resource limitations in browsers is real. E.g. https://www.coindesk.com/firefox-announces-move-to-block-cryptomining-scripts https://www.coindesk.com/firefox-announces-move-to-block-cry... I know that solution presented in the article didn't work (neither in Firefox nor in Opera), and I know that from a person close to me who is not "technical" but wants to access some sites which slowed down the person's computer (the sites indeed managed to use exactly 100% of the CPU, that means, to use all cores at once, and to contact regularly some other sites with the "coin" in the name). Then, I've shown the person that the JavaScript can be blocked and that the computer is that way completely responsive... and you know the result: even the non-technical persons do what's rational, once they know that they have a choice.
- jakeogh 8y agoSurf (a suckless webkit2 frontend) can be configured to disable JS by default, if you really need it, hit ctrl-alt-s and volla the junk gets executed. Browsing without js is wonderful. https://surf.suckless.org/ https://surf.suckless.org/
- duxup 8y agoThis whole thing seems like adding an arbitrary knob for arbitrary reasoning, considering that it would impact sites that have nothing to do with the author's problems with js.
- robbrown451 8y agoI 100% agree with this: "But there's a downside to this content blocking: it's hurting many smaller sites that rely on advertising to keep the lights on. More and more of these sites are pleading to disable content blockers" The solution proposed is unworkable for all the reasons others propose. But there really is a baby/bathwater situation with ad blockers that attempt to kill all advertisements. I don't know what the solution is, but I think it is an important problem and deserving of a more sophisticated solution than ad blockers or ones like the solution proposed. People here are smart, I hope people can do more than just state reasons why we can't do better than what we are doing.
- burkaman 8y agoMost people block ads because they don't want to see ads, not because they want less javascript. The solution is to find a better business model, not make smaller ads.
- robbrown451 8y agoI think it is a small subset of people that see things that black and white. I agree it is not simply "wanting less javascript", but I think a large number of people would not mind small ads that have minimal bandwidth requirements, minimal cpu usage, minimal slowing down the page, that don't pop up in your face, are not visually distracting, and are relevant to the material on the site. I don't think "get a different business model" is a reasonable option for many web sites, unless the whole point of the site is to support a product (for instance Adobe's Photoshop web page, or whatever).
- bostik 8y agoLong, long time ago I wrote down my set of rules for acceptable ads: https://news.ycombinator.com/item?id=10521930 https://news.ycombinator.com/item?id=10521930 Really, we block ads because they are intrusive, disruptive, invasive and bloated pieces of malware. Simple as that.
- zzzcpan 8y agoI think it's incorrect to assume that small websites rely on advertising to keep the lights on. They are the ones who definitely can't make enough on ads to sustain and are always funded primarily some other way. But at the same time running ads they let advertising companies to profit from all of them in aggregate. Given that, I don't see any point trying anything that somehow keeps ads around. Intrusive online advertising doesn't really need to exist.
- osrec 8y agoHmm, not sure I like this idea. I'm a very pro-PWA/webapp sort of person, so anything that restricts flexibility on the webapp side annoys me. Especially given the number native apps that are equally as bloated and virtually never share or reuse code between apps (think of the 10mb native note taking apps out there). Perhaps we just let quality rise to the top? If your website is full of ads and slow, then someone else with better, less annoying execution will eventually win more users.
- Zecar 8y agoI use Super Stop and I'm in a habit of hitting shift+escape on basically every website I visit. It kills all AJAX calls and content loading. 9/10 websites load perfectly in the first second and stopping them after that just prevents popups, tracking, etc. It would be nice to have a plugin that automatically stops websites after some preset interval.
- xg15 8y agoPlease disable your adblocker! Do you accept our cookies, tracking and privacy policy? Would you like to subscribe to our newsletter? Please give us access to your location! This site is way better if your download our app! Please allow us to load another 30MB of JavaScript!
- davb 8y agoI really hope interest based advertising dies. I'm not convinced it works and every time it's brought up, someone links to some study suggesting it's not particularly effective. I actually don't mind ads all that much, if they're static, don't track me and are rendered server side (no javascript). Base it on the content of the page, not the person visiting. I've never clicked on a retargrted ad for sneakers that follows me to a tech site, but an ad for (for example) DataGrip on an article about SQL tooling might actually interest me!
- pornel 8y agoThere exists a less blunt proposal to add resource limits to web pages: https://www.igvita.com/2016/03/01/control-groups-cgroups-for-the-web/ https://www.igvita.com/2016/03/01/control-groups-cgroups-for... It's aimed at limiting resource usage of 3rd parties (ads), and pages voluntary limiting their usage, but presumably browser extensions could add the limits too.
- 8bitsrule 8y agosmaller sites are collateral damage in a larger battle. Smaller sites could avoid farming their content out to 2 or 20 locations on the cloud. The user can already add limits. Try using uBlock Origin with scripts open to inline and first-party scripts and images everywhere ... and nothing else. If the page comes up blank, bye-bye. Don't visit it any more. They made their choices, let them live with it.
- j4kp07 8y agoI imagine Jim Carey (Liar, Liar) screaming....STOP RUNNING CLIENT SIDE ADVERTS ASSHOLE!
- andrewmcwatters 8y agoSo it's totally okay when we block advertisers but when developers are the ones under scrutiny, suddenly the user-centric argument is out the window. I think this is a great idea. It puts pressure on developers and makes experiences better for users. The average American Internet speed is sub-100 Mbps, but average LTE speeds are closer to 12 Mbps, with websites opting usually to use responsive layouts over separate mobile sites. This means you're downloading the full resources of a desktop site, and the mobile device is adjusting to media queries. 5 MB / 12 Mbps is over 3 seconds. That's bullshit. Put pressure on developers, make a better web.
- tanilama 8y agoI am not sure the proposal is solving the right problem: > The situation I'm envisioning is that a site can show me any advertising they want as long as they keep the overall size under a fixed amount, say one megabyte per page. With minification/compression, I don't see how 1MB could work...
- deadmetheny 8y agoI came to these comments to see if it was mostly webshit programmers complaining about the horror that would be unleashed if JS had limits, and I was not disappointed. A lot of people use their phones to access the Internet and have hard data caps, and webpages don't need to load several MB of JS to display 55k of text. There's certainly use cases for JS that justify that amount of script to load, but shoving ads, trackers, and widgets aren't those uses.
- mattlondon 8y ago"640k ought to be enough for everyone." Setting some arbitrary hard-limit is counter-productive and shortsighted. That quote is infamous for exactly the same reasons that this claim is flawed. Lots of unanswered questions here, e.g. what happens if a 500byte javascript file then does a load of XHR requests that download more JS: what happens then? does the connection just get closed as soon as you pass 5mb? That will break the internet for lots of users. Plus what happens if I down load a couple of kilobytes of javascript that ends up allocating many gigabytes of memory? Is that ok because it was under 5mb of over-the-wire-bytes? I can easily imagine a 5mb+ web application. Sure you might not like that, but it does not make that a bad situation. If you don't like javascript, then the answer is simple: disable it. If you want to use javascript but feel like a particular website is using too much resources, then the answer is simple: dont visit it. You have choice.
- mcphage 8y ago> If you want to use javascript but feel like a particular website is using too much resources, then the answer is simple: dont visit it. You have choice. You don't know how many resources it's going to use until you've already visited it.
- tenebrisalietum 8y agoI can imagine a 5mb+ web application too, but there should be some way of communicating something needs a lot of resources before it is casually downloaded. It's impolite for an installer to not tell you it's copying 50GB of data to your hard drive before it starts. "640K ought to be enough for everyone" is shortsighted, but "Web applications should not assume the user wants to dedicate all system resources to them without knowledge/permission" is not. It won't matter much longer. Websites are giving way to phone apps. Where no visibility into behavior or resource consumption is normal, standard, and expected.
- zelon88 8y agoJust thinking about this problem and the proposed solution is making me flustered. Remember those popups in IE "Do you want to continue running scripts on this page?" Nobody knew what they were, where they came from, or what they were talking about. Even wose than that was the fact that nobody knew what the Yes/No button was for and if you clicked "Yes" sometimes it would just keep popping up over and over again. They got rid of that for a good reason (although its still alive and well in MSHTA.exe). It sucked and offered nothing of value to most users. On the other hand, the New York Times's website has 5 external scripts that total over 1mb of just text. They've got their CMS, 4 DIFFERENT ad agencies, analytics, and some other crap the site problably never "needed" before 2010. That's disgusting. And that's what you get from a $300m+ company that RELIES on technology to stay in business. Missing a feature? Fuck it, just have the client pull down another 400kb of js from a sixth CDN. Nevermind the actual CONTENT that attracted the user in the first place is measured in bytes. So while I think this is horribly misguided, I do agree that something needs to be done to deincentivize lazy Javascript programmers pasting all their problems away. Perhaps the lock icon in the address bar should also turn yellow or red to reflect external script resources? Or maybe whenever multiple frameworks are combined or multiple ad networks used? Almost every page of my WP website has just 8 internal resources and a page size of <310kb. There's no reason NYT can't stay in that ball park with their deep pockets. Megabytes of tracking and bullshit for basically a white page with text is disingenuous.
- k__ 8y agolol, good luck getting this through in Safari with the current state of Apples websites.
- dijit 8y agoSo. I figured you were probably right so I went and checked Apples websites for their largest products to see how bad it was. The largest sum of JavaScript was on the Mac Pro (2013) page with just under 200kb. That’s a lot less than 1MB
- k__ 8y agoSure, their sales pages are in shape. But the developer stuff in the walled garden not so much. The App Store Connect login/start page has 2MB JS and the App page has >3MB. Overall the whole Apple Dev experience is sluggish.
- Wowfunhappy 8y ago> Content blockers [...] prevent abuse by ad networks and many people are realizing the benefits of that with increased performance and better battery life. But there's a downside to this content blocking: it's hurting many smaller sites that rely on advertising to keep the lights on. [...] In effect, these smaller sites are collateral damage in a larger battle. And that's a big problem for the long-term health of independent content on the web. I've got another way to solve this problem. Content blockers should operate on a blacklist instead of a whitelist. Advertisements appear by default, but if a given site annoys you enough, you can go into your ad blocker's preferences and add it to your blacklist, and then you'll never see any ads on that site again. Why is this not even an option in any of the major adblockers? I know it's possible in Ublock Origin via tweaking advanced settings[1], but it should be a built-in, user friendly feature. [1] https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-turn-off-uBlock-everywhere-except https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-tu...
- hungryfoolish 8y ago>Advertisements appear by default, but if a given site annoys you enough, you can go into your ad blocker's preferences and add it to your blacklist, and then you'll never see any ads on that site again. Thats literally what ABP has. Ads which have meet the acceptable ads criteria appear by default, and the rest are blocked by default. Users can however go and disable that setting so that all ads are hidden by default.
- Wowfunhappy 8y agoA built in whitelist ≠ a user created blacklist
- hungryfoolish 8y agoEasylist would be a user created blacklist, right? Very ad blocker I know of uses that.
- Wowfunhappy 8y ago
- mbell 8y agoIMO the critical thing needed to stop JS bloat is a decent standard library. The _vast_ majority of code on an average site tends to be the same thing implemented 45 times because the stdlib in Javascript is anemic. The current process of adding a function at a time to the language spec is rather pointless at solving this issue since it's often years after the function is added before anyone can realistically rely on it existing. In the mean time we have to keep loading polyfills just in case. Also at the current rate of functionality additions it'll be decades before the stdlib is decent. What I really want to see happen is WHATWG start a standard lib project. In my mind it would look something like this: * Open source project that implements the standard library in Javascript only and holds the canonical test suite. Something akin to core-js but the 'official' version of it and with features outside the language spec. * Every browser agrees to preload / cache all recent versions of the standard library (or most recent version for each major release assuming semver). This allows all programmers to load the version they need without concern for the performance hit. * User loads the standard library via a script tag with src something like: https://ecmascript.org/stdlb/v1/lib.js https://ecmascript.org/stdlb/v1/lib.js. Doesn't really matter what it is, just some recognized url the browser knows about that encodes the version. * Each browser can provide a native implementation of anything in the stdlib so long as it passes the spec. Browsers could even optimize which pieces of the stdlib it parses / loads based on this. e.g. If the browser has a native Promise implementation then it doesn't need to load the Promise code from the stdlib. * Be reasonable but aggressive about adding to the stdlib. It's scope should be wide and cover common use cases. e.g. I shouldn't have to write a URL parsing class or a throttle function every time I start a new project (which is where we are today). There are plenty of projects to look at for learning what people need (lodash, etc). Obviously this would not cover everything; it's not going to add `await` to browsers that don't support it. But I think we're at the point where what we are most in need of is not language features (and mostly these are transpilable anyway), but stdlib functionality.
- maccam94 8y agoWe're in a kind of interesting economic situation when it comes to consumer compute and bandwidth resources. There's no "billing" for compute time on the server side nor on the client side. Bandwidth costs are also negligible on most connections. This means there are no pressures to efficiently utilize them beyond user annoyance (which usually isn't a strong enough motivating factor to modify behavior). Is the solution some sort of bidirectional billing scheme? "This page will cost $0.02 to retrieve. Pay by running 20FLOPs of code?" "OK" "This page will cost $0.05 to retrieve. Pay by running 500FLOPs of code?" "No, pay via $fiat_transfer_method"
- demarq 8y agoMore done, with less bytes is a virtue and a great show of skill among software developers. Outside that infinitesimal small bubble however... users could barely give a damn. Also I fear that a lot of this is javascript phobia formed by the mindset that the web is supposed to be documents not full blown applications, after all why complain about 2 megs of js when the page has a 10mb banner image and an autoplaying 40mb HD video?
- Veedrac 8y agoOne thing I would love personally is the ability to restrict JS usage to a CPU limit, which increases in response to certain events and gradually reduces to 0 if unused. This could be * A number of seconds on page load, * a fraction of a second in response to network activity (eg. image loads), * a small number of frames in response to significant user interaction (mouse clicks, typing), * one frame after less-significant user interaction (mouse movement), limited only to local operations (no network activity). The vast majority of sites should need nothing more than this, so opt-in to unlimited usage should be fine. Sites where the user has enabled extra permissions like notifications should be allowed extra time for those.
- amiga-workbench 8y agoLove it, I believe Chrome mobile already completely kills JS on GPRS connections.
- waste_monk 8y agoExample.com does not use any scripting, let alone 5mb worth. In fact, it only transfers 1.24kb of plain CSS/HTML. Whoever wrote that comment was a liar and a peddler of nonsense.
- shanehoban 8y agoI believe a huge saving across the web could be something much more simple considering even the ubiquity of jQuery. A build tool that scans your JS code, and includes only the jQuery functions that it has found to be using; or equivalent library etc.
- Technetium_Hat 8y agoThis exists already. Modern JS build tools are actually pretty sophisticated.