4,765 karma · joined August 17, 2012
Unfortunately there isn't a magic bullet to code bloat.
Which makes sense IMO, then the designer can take on as many clients as they have bandwidth for.
I assume they are just standard ML.
Not really sure why this was submitted or what makes it interesting.
Code size has not grown as fast as memory and storage capacity has. One is constrained by manufacturing progress, the other is constrained by programmer output.
Deno is sub 50MB
For any non trivial app, your assets and working set data will likely dwarf the code size itself.
EDIT: Was looking at an old bug, deno is closer to 100MB. Starting to feel a bit large but still.
Not to mention no internal and communications are cited in the article.
Just. Brutal.
What does the science tell you about the risks to vaccinated individuals when exposed to other vaccinated individuals or to non vaccinated individuals?
A group of people in a room all vaccinated is safer than a group of people half vaccinated.
The vaccine is not a boolean on off switch, it's a percentage wise improvement over nothing, and it compounds when those around are also vaccinated.
It needs to be thoughtful, but the firefox position appears to be that web apps have no business accessing bluetooth or usb. Which as I explained earlier leads to user installing clunky native apps to interact with their bluetooth/usb gadgets, or the gadgets being deployed with phone home functionality so that user can still access them through a web portal.
If firefox wishes to remain relevant they're going to have to implement the things that developers and users want. Nobody wants a dumb document browser anymore, that ship has sailed. Browsers are a ubiquitous application platform.
Don't leave thoughts unfinished, if you have something interesting to add you should share with the rest of the class.
Then I read their makefile on github and they're still using pandoc...
https://github.com/chrisman/chrisman.github.io/blob/a2a949f3...
What? That's the whole purpose of search algorithms isn't it? I'm not sure I understand your complaint.
The stick will grow as IPv4 addresses get more and more expensive.
Firefox abandoned FirefoxOS, Apple is focused on the App Store.
What's the last interesting API proposed by someone other than Google?
Sure I can make a native app that extends Safari with the APIs I need, and I can also do that again for Android, and again for Windows and again for macOS. Or the browsers could implement features developers like me want and I only have to invest once.
Replacing native apps with web apps IS innovative.
Sure the app's functionality is the same as those before it, but the delivery and interaction paradigm is so much improved for users. Being able to invite a friend to participate on what I'm doing without them having to install a native app IS a step forward in user experience.
If I can unlock your computer with your password or with the word "hello" and you have no intention of removing the "hello" feature, would you not agree that we might as well remove the password entirely?
How do we increase the attack surface of service workers by adding background sync, when we can get nearly identical behaviour using push?
If you goal is purely to not increase the attack surface, you might as well never add any new APIs ever.
From the perspective of users of existing software that seems to break with no reason I agree. It's stupid how heavyweight imgur has become when it used to just be a fast simple website that worked everywhere.
Maybe you're content with the functionality your system has now and need no more, but I am still on the quest for new things I can do digitally, and easier way to do things I already can.
Take Figma for example, I'm not even a designer but even I enjoy having access to a collaborative drawing app that is trivial to share with other collaborators. If browsers had not agreed to implement Canvas and all rolled it out, Figma would likely not exist. Perhaps they could have created a packaged native application for all major operating systems, but in reality that's a ton more work, and a huge impediment for users to convince collaborators to buy/install some native app so they can work on a drawing together.
What other software are we missing out on because the barrier for interacting with USB/NFC/Bluetooth/Notifications/Background-Sync is too high.
In a world with native apps only, only the big players can afford to target all platforms, and only the big enough use cases can justify the expense.