11 ms·
> Spotify, Slack, Discord, Facebook, Twitter, LinkedIn, all the annoying bloated websites, which I used to hate so much for the past months, now run like if the
by Apocryphon 6y ago
> Spotify, Slack, Discord, Facebook, Twitter, LinkedIn, all the annoying bloated websites, which I used to hate so much for the past months, now run like if they were the most optimized websites on the internet.
This is just going to encourage bloat and inefficiency, isn't it? Note: this has nothing to do with specifically Apple Silicon but just any computing improvements in general.
- 0xCMP 6y agoYes, but that's pretty much how it goes. Jonathan Blow had a rant on release of the M1 Macs saying it literally didn't matter because computers were already really fast and the problem has been, and will continue to be, that if the processor/system is faster then software will be written slower to hit the magical response time expected. Kind of a cynical take... but is he wrong?
- pushrax 6y agoCarmack famously also has declared "I would rather have magic software over magic hardware" - the context being that we're using current hardware to a small fraction of its potential. Still, I feel there's a lot of software I use that is hard to optimize or no longer developed, and I'm certainly happy to have it run faster given new hardware. As a programmer I also like being able to be lazier and still have usable software. Higher level languages, GC, less thinking about access patterns and debugging prefetch problems, etc.
- ATsch 6y agoGiven it's Jonathan Blow, I feel compelled to say yes. More seriously, while program overheads have undoubtedly gotten higher, that's always been in exchange for something else, even if non-technical, like a better developer experience and platform support. Nobody writes slow programs on purpose, but people are very willing to trade it off for things that are more important in the grand scheme of things. Low level programmers love to smugly pretend that those tradeoffs do not exist but they do.
- ChrisMarshallNY 6y ago> Nobody writes slow programs on purpose No, but we are in a place where most development projects are really "stitching" dependencies together, and those dependencies can get heavy. On the other hand, this may help apps written in things like Ionic to speed up like crazy, because WebKit is now insanely fast.
- ATsch 6y ago> we are in a place where most development projects are really "stitching" dependencies together Is there anything wrong with that, though? If there's any common thread in the history of computing, it's that progress happens when things become abstracted enough to allow for another layer of building blocks. That's not to say that those layers don't have a cost, or we don't need to learn how to do them well, but gluing together components is really all software development has ever been.
- ChrisMarshallNY 6y agoIt's both good and bad; depending on how much care is taken in selecting dependencies. It's hard to use a lot of dependencies, regardless of their quality, without introducing bloat. Lots of redundancies. For example, each dependency may have its own messaging or thread management system, or its own memory management system. Or it may include other dependencies that have their own "special sauce." For myself, I use lots of little packages; mostly written by Yours Troolie, and only occasionally use third-party dependencies. Each of my packages is usually crafted towards a certain discrete function, and has its own project lifecycle. I think that's a good thing about using dependencies. I believe that modules with encapsulated lifecycles are a good way to ensure quality (or not, if I "choose poorly," as the Knight Templar said in the Indiana Jones movie).
- zamfi 6y ago> Nobody writes slow programs on purpose, but people are very willing to trade it off for things that are more important in the grand scheme of things Wait, of course they write slow programs on purpose, because "premature optimization is the root of all evil," right? A developer might use Electron because it's "fast enough" and halves your development time, and "fast enough" is always a perceptual metric, and not a technical one. Faster hardware means even less optimization is needed before something is shippable -- great for developers! -- and a recipe for software continuing to feel just as slow as before, because we only optimize until it's "fast enough". And despite the M1, or any of the advances of the last decade, the perceptual line that is "fast enough" hasn't changed. EDIT: Yes of course Knuth was talking about optimizing noncritical paths, but the sprit he’s espousing lives on in system design: use electron, or something else that makes your product more maintainable and easier to understand (because you didn’t build your own bespoke cross-platform app scaffold, and electron is well-documented, etc.), until you’re sure you can’t anymore. Well, the bar for “can’t” is raised every time there’s more cpu to support rapid, maintainable, “nonoptimal” development, and here we are.
- will_pseudonym 6y agoThe software being written being slower is of course enabled by those hardware improvements, but 1) the slow software is due to those technical inefficiencies making software easier/less expensive to produce, and 2) we can still make fast software by not using those inefficient means. That said, there's something of a problem with that though, because by making 1) more and more prevalent, it makes 2) more expensive due to fewer people choosing to work in that manner. Similar to how consumer technology goods get much less expensive, but have many more defects and issues. That "race to the bottom" makes cheap things cheaper, but makes more expensive things more difficult to make. I don't know what that phenomenon is called specifically, but it's definitely something I've been frustrated by in nearly every industry and product category.
- Apocryphon 6y agoI think you're definitely onto something, and what you're describing is a reoccurring pattern of modern society chasing after quick gains and optimizing certain metrics (e.g. short-term profit) over other considerations. It's not that people or organizations were necessarily more considerate or contemplative in the past, it's just that the processes or technological improvements (e.g. better hardware) weren't there to allow those races to the bottom. And maybe the systems we were living under didn't reward that behavior as much.
- markstos 6y agoThere's also a counterculture of projects that are lightweight alternatives: Sway as a lightweight window manager (among many lightweight WMs), musl vs libc, libressl vs openssl, gemini vs http, Alpine Linux vs Ubuntu, Alacritty as a blazing fast terminal. This software culture is visible on Linux than macOS, but it's alive and thriving.
- zarkov99 6y agoA little wrong. It does matter that the thing is always cool to the touch and it can run all day, even under heavy load. That is pretty new to my knowledge.
- throw0101a 6y agoPerhaps x86 has been 'fast enough' for most people, but the M1 is as fast (or faster) using less power. Even if the M1 was 'only' as fast as other chips, then it's performance-per-watt would still be impressive. Further, as someone who deals with HPC at $WORK, our (medical) researchers always want faster.
- x3sphere 6y agoYeah, sorta wrong. Sure, computers are already really fast, but the big thing with the M1 Macs for me is that they've finally came out with a laptop that doesn't heat up like crazy when I'm using it for moderately demanding tasks. Also every laptop I've had prior, would get pretty hot or the fan would get quite loud when connected to an external display. This M1 is completely silent when doing that AND it doesn't throttle.
- pushrax 6y agoWe have had passively cooled high performance devices for a while. M1 Macs are a great step, but it's more useful to compare them with previous gen mobile devices (iPad Pro 2018 ran faster than the 13" MBP at the time). Bringing ARM SoCs to laptops is also not new (e.g. Surface Pro X from Oct 2019), but I agree it's worth noting that Apple is doing a great job of it. Best x86 translation out there.
- samatman 6y agoWe used to have a saying "Moore giveth, and Gates taketh away". But I see two reasons why the M1 is a big deal, even given the bloat tax. One is simple power efficiency. These chips run cool and fast, and Intel laptop chips don't. No amount of hyperefficient code is going to get you a real 18 hours of battery life on last year's MacBook Air. The other one is Apple's proven track record of integrating custom hardware and software, into something which is greater than the sum of its parts. Ever since I got an iPad Pro, I've been quietly frustrated with the user interface of MacBooks. It's just not physics-smooth, and the iPad just is. I just got one of the 16" MacBook Pros for work, and it's pretty loaded, and it's a good computer— by the standards previous to the M1. Battery life could be better; overheats sometimes with serious fan noise, for no good reason, although each update to Catalina appears to substantially reduce this. I figured I could get five years on this rig. No way. I might make it to 2022, but I know terminal gearlust when I see it. Whatever Apple sticks in the next release of the 16", I'm craving it already.
- computing 6y ago"What Andy giveth, Bill taketh away" (Andy Moore, Bill Gates) https://en.wikipedia.org/wiki/Andy_and_Bill%27s_law https://en.wikipedia.org/wiki/Andy_and_Bill%27s_law
- dreamcompiler 6y agoAndy Grove. Moore's first name is Gordon.
- computing 6y agoGrove, my bad.
- Betelgeuse90 6y agoWow man I'm really feeling that. I also have a great 16" and I'm experiencing similar issues with it. The new M1 MacBook Air is already as fast as my machine and costs less than half. It's bonkers. I use two external monitors however and the Air doesn't support that, so that's one thing keeping me away from the new M1. I imagine the new 16" MacBook Pros will support more than one external monitor, and I don't think I'd be able to stop myself from getting one.
- threeseed 6y agoNot really. They are cross-platform apps which still need to run well on the 95% of other computers which don't have the M1 chip.
- Apocryphon 6y agoNote: this has nothing to do with specifically Apple Silicon but just any [dramatic] computing improvements in general.
- threeseed 6y agoBut this is a dramatic computing improvement limited to 5% of the computing market. This isn't like with web browsers where it impacted everyone.
- TuringNYC 6y ago>> This is just going to encourage bloat and inefficiency, isn't it? Note: this has nothing to do with specifically Apple Silicon but just any computing improvements in general. If it does, Wintels are not going to be pleasant environments for users. Wintel laptops would need to up to 32gb/64gb RAM
- teabee89 6y agoYes, it's a variant of the Jevons paradox: https://en.wikipedia.org/wiki/Jevons_paradox https://en.wikipedia.org/wiki/Jevons_paradox
- Triv888 6y agobut that's not new, CPUs/etc have been getting faster since forever and games are already super-bloated
- raverbashing 6y agoYep I remember being shocked when I first read a game requiring 16MB of RAM (yes, 16MB, get off my lawn).
- whywhywhywhy 6y agoYou have to take into account of the capabilities and willingness to work on optimization of the average developer over time too.
- Apocryphon 6y agoNot to mention organizations' willingness to entertain those engineering initiatives, never mind prioritizing them.
- svachalek 6y agoBack in 1989 I ran an application called GeoWorks on my Commodore 64. It had a paint program and WYSIWYG word processor and both applications and documents ran in the C64's available RAM of... 38k? Roughly 1/100000 of what's on a low end computer today. On a CPU that ran at 1MHz and took many clock cycles per instruction. In other words, yes but that's nothing new.
- deleted 6y ago[deleted]
- Wowfunhappy 6y agoOf course, the programs couldn't render as many pixels or colors at once, couldn't insert photographs, videos, or complex tables and charts, couldn't load complex fonts or otherwise handle nuanced typography, etc etc. There's a heck of a lot of pointless bloat. But at least some of the extra power has gone to useful features! Today feels different. If Slack really have any significant features that couldn't be done on computers 15 years ago?
- pvg 6y agoIt's worth thinking about what happens when you touch your phone's screen or reach for your trackpad/mouse and scroll a bit, at 60fps. That's a basic gesture that involves a gazillion C64s of everything.
- Dylan16807 6y agoI'm thinking about it. Processing the touches into events should take 1 C64 of power or less. Scrolling shouldn't significantly more difficult. 1 C64 for this. The screen is much higher resolution, so we need the power to render that, but that's offloaded to the GPU and the GPU doesn't even need to leave idle frequencies. 60fps, well what was the C64? Whatever, multiply the resources by 10. We've now accounted for... 20 C64s of power.
- pvg 6y agobut that's offloaded to the GPU It's a little odd to exclude the supercomputer your computer comes with to help with scrolling.
- s1k3s 6y agoI've enjoyed high level programming so far (think Java, Swift). But for the sake of argument, I'm gonna say this: high level languages (& their runtime environments) take control over the code that the programmer writes. Speaking of "computing environments", I'm unease with the fact that I don't really know that my Swift program is doing in the background, and more so, the fact that the vendor (Oracle, Google, Apple etc) tries so hard to prevent me from finding out.
- zepto 6y agoSwift really isn’t doing anything “in the background”. There is no virtual machine, and nothing is happening other than your code and the libraries you use. It’s only high level from the point of view of the type system.
- rsynnott 6y ago> I'm unease with the fact that I don't really know that my Swift program is doing in the background, and more so, the fact that the vendor (Oracle, Google, Apple etc) tries so hard to prevent me from finding out. Eh? Apple's fairly clear about what Swift is doing in the background (which isn't much, really; boring ol' reference counting). This might apply more to Java, mind you. There are no secrets, but most people probably aren't going to investigate exactly what the JIT or GC are doing.
- Wowfunhappy 6y ago> and the fact that the vendor (Oracle, Google, Apple etc) tries so hard to prevent me from finding out. Are there any specific instances you’re thinking of here? Java, Go, and even Swift all are open source.
- matthewmacleod 6y agoI'm unease with the fact that I don't really know that my Swift program is doing in the background I don’t really understand your complaint here. The Swift runtime library is pretty limited - basically just allocation and reflection. The compiler spits out machine code that you can look at. Where is the “background” you are thinking of?
- mortenjorck 6y agoIf, in a year or two, everyone at a tech company is building and testing on Apple Silicon machines, it could very well lead to major performance blindspots. While you can profile performance in any web inspector, I think a good product team should keep a base-spec Windows laptop on hand to see how it all comes together for users who may not have the kind of hardware they design and develop on.
- Eric_WVGG 6y ago> Visual Studio Code is now optimized for Apple Silicon… and it works and it's snappy. I hated that app on my last laptop, it was very slow and bloated I was thinking the same thing as I read this bit. I’m still on an Intel Mac and recently switched from VSC to Panic’s Nova editor, highly polished and 100% native. If bloated code runs fast on an M1, imagine how native code performs? I’m trying very hard to excise as much Electron garbage from my life as possible.
- zimpenfish 6y ago> If bloated code runs fast on an M1, imagine how native code performs? As an example, Minecraft on the 16GB M1 Pro running under Rosetta 2 runs much better (near-constant 60fps with everything on default, no fans, imperceptible heat) than on the 32GB i9 Pro (peaks about 40fps with everything turned down, full fans, will burn you unless you disable Turbo Boost). I'm looking forward to a native JVM and seeing if it gets even better.
- rsynnott 6y agoKnock yourself out: https://www.azul.com/downloads/zulu-community/?package=jdk https://www.azul.com/downloads/zulu-community/?package=jdk (I assume you can sub in your own JDK with Minecraft? Never used it)
- selectodude 6y agoI'm pretty sure it just calls Java. Whichever interpreter pops up it'll use.
- zimpenfish 6y agoFound https://gist.github.com/tanmayb123/d55b16c493326945385e815453de411a https://gist.github.com/tanmayb123/d55b16c493326945385e81545... which uses Zulu to run Minecraft - was a lot of faff to get running, no sound, decent perf, definitely more heat than normal MC running on R2 though.
- Nextgrid 6y ago
- basicneo 6y agoOne person's "bloat and inefficiency" is another person's "features at low cost". We simply wouldn't have the services we have today at their low price if our hardware didn't offer them more breathing room. As inefficiency tips more towards degradation in machines, more emphasis will be given to efficiency.
- throw0101a 6y ago> This is just going to encourage bloat and inefficiency, isn't it? Same as it ever was: > Wirth's law is an adage on computer performance which states that software is getting slower more rapidly than hardware is becoming faster. > The adage is named after Niklaus Wirth, who discussed it in his 1995 article "A Plea for Lean Software".[1][2] […] > Other common forms use the names of the leading hardware and software companies of the 1990s, Intel and Microsoft, or their CEOs, Andy Grove and Bill Gates, for example "What Intel giveth, Microsoft taketh away"[7] and Andy and Bill's law: "What Andy giveth, Bill taketh away".[8] * https://en.wikipedia.org/wiki/Wirth%27s_law https://en.wikipedia.org/wiki/Wirth%27s_law * https://en.wikipedia.org/wiki/Andy_and_Bill%27s_law https://en.wikipedia.org/wiki/Andy_and_Bill%27s_law
- heavyset_go 6y agoSimilar to how taser training for law enforcement involves being tased themselves, I think Electron developers should have to use old computers for an extended period of time as their Electron development machines, just so they get an idea of what it feels like to be a user of their apps.
- mhh__ 6y agoAlthough it's a complete pain to standardize the results, you can have benchmarks as part of your CI (It's a bit easier if you can use some kind of normalised measurement like cache misses per loop iteration, but rdpmc generally isn't allowed - or even available from the OS). Latency from the user perspective is a bit harder, although I guess for a webpage you could run it headless into a video recording then time how long to go from a blank screen to showing information?
- jschwartzi 6y agoSure but the fact that you need benchmarks and big performance optimizations in a chat app is a sign that your approach is very inefficient and slow. Especially considering the same feature set was available 30 years ago in computers that were less capable than my wrist watch.
- deleted 6y ago[deleted]
- hnick 6y agoI really like the idea behind Facebook's 2G Tuesdays, but I'm not sure if it helped achieve anything apart from PR, or if it's still going.
- an_opabinia 6y agoAd networks are strongly incentivized to perform well on slow devices, since they are paid per impression. In contrast the most valuable clicks almost always occur on the most expensive devices.
- 6y ago
- yumraj 6y agoMost likely yes, but if x86 keeps on lagging behind then hopefully not since the developers of these will need to make sure these work ok on x86 also.
- psadri 6y agoThe sad part is that most developers will be using these faster machines and to them their software will seem super snappy. But the poor folks with non-state of the art machines will experience much slower experiences. It creates a dynamic where other users are forced to upgrade just to use basic software. In the past, I developed on old hardware (or at least tested on old hardware). If the software was performant on my old machine, it was bound to be fine for most others.
- honzajavorek 6y agoIt's already the case with JavaScript bloat, which destroys performance and network efficiency of the internet in many countries.
- megablast 6y agoHaving slower noisier computers didn’t stop the bloat.
- ReactiveJelly 6y agoAnd when confronted with "Faster CPUs will cause slower software!" the only actionable is what? Purposely build slower CPUs? That consumers won't want to buy? If I ever meet the king of software I could ask him to make faster software, but I haven't found him in the phonebook yet.
- sorokod 6y agoMany producer consumer systems really; roads-traffic, predator-prey. It a very common emergent behavior.