11 ms·
Give Mac software a few years to "catch up" and everything will feel just as slow as usual (and I'm not even joking, so far, software was always excellent at un
by flohofwoe 6y ago
Give Mac software a few years to "catch up" and everything will feel just as slow as usual (and I'm not even joking, so far, software was always excellent at undoing any advancements in hardware very quickly).
- mojo982 6y agoYou are right. And I hate it.
- nemo1618 6y agoEven today the M1 still feels slow occasionally -- hanging for a second or two, browser taking multiple seconds to launch, etc. Granted, that could be due to I/O or power management, but in any case it's clear that software is not making proper use of hardware.
- pentae 6y agoWhat you just described only happens for me with Chrome on my M1 MBA. Try loading Safari, its instant.
- SSLy 6y agoThis is called "What Andy giveth, Bill taketh away."
- homarp 6y agoand this is now called Electron trading speed of development with 'hardware optimization'. Mac being a small market, some users are still opiniated/loud enough to reward nicer/native UI vs cross-ish platform lowest common denominator UI. Maybe there is hope Arm mac stays fast.
- mixmastamyk 6y ago+ Mac OS checking every binary you run over the internet.
- walterbell 6y agoPihole and others can block those Apple queries.
- bonestamp2 6y agoWhat happens if you block them.. do they eventually stop working if they haven't been validated in a long time?
- Klonoar 6y agoIt's slightly more nuanced than that - you can of course just block it from doing so, and there's certainly an argument for it being updated to not need a network call each time, but phrasing it like this makes it sound worse than it actually is. I'll just quote Jeff Johnson, who's looked into this and written about it - his comment[1] on this is post is quite useful: https://eclecticlight.co/2020/11/25/macos-has-checked-app-signatures-online-for-over-2-years/ https://eclecticlight.co/2020/11/25/macos-has-checked-app-si... >The request to http://crl.apple.com/root.crl http://crl.apple.com/root.crl is simply checking the revocation status of Apple’s own Developer ID Certification Authority intermediate signing certificate. If you examine the cert in the System Roots keychain, you can see that URL under CRL Distribution Points. This request contains no information specific to third-party developers or apps. In contrast, there’s no CRL for third-party Developer ID leaf certs signed by Apple’s intermediate cert. Their status is only available via OCSP. Notably, this: >This request contains no information specific to third-party developers or apps. https://eclecticlight.co/2020/11/25/macos-has-checked-app-signatures-online-for-over-2-years/#comment-53659 https://eclecticlight.co/2020/11/25/macos-has-checked-app-si...
- mixmastamyk 6y agoYou added detail, yet didn't refute the statement. That it isn't easy to simply and specifically turn off is not acceptable.
- Klonoar 6y agoNo, I'm fairly certain I refuted it. The parent comment is incorrectly stating that each request to Apple is checking a binary, and it's not. This has been well documented both here on HN and across the web.
- whatever1 6y agoI would say that 90% of my pc resources are consumed to execute JavaScript code. If we need dedicated hardware to execute this more efficiently so be it. We do it anyway for so many other domains. Video, graphics, encryption etc.
- deleted 6y ago[deleted]
- Jetrel 6y agoOne of the big deals with electron-et-al is that we're not married to JavaScript, really; we're married to "the DOM and css" as our gui, and things like FF/Chrome/Safari devtools to develop that gui. Most javascript developers are already using babel-et-al pipelines to build electron apps, which are already transpiling between major variants of javascript, and I wouldn't at all surprised to see a thing where it gets compiled into WebAssembly rather than interpreting javascript. I also think there's a thing, right now, where it's possible to build electron apps with Rust+WebASM; I'm not sure, but I think the main thrust here is it definitely would eliminate a huge chunk of the slowdown. I guess the main takeaway is just that the development revolution that's happened recently is mainly about how insanely good browser dev tools have become, and not about javascript - javascript was just along for the ride. As an aside - I recently saw a video of someone demoing one of the old Symbolics LISP workstations, and I was shocked to realize how much they had in common with a modern browser console - specifically of being able to inspect all of your gui components, live, and look at all the properties set on them. It's provided a hell of a way for me to explain what the deal was with all the old gurus in the 80s "AI Winter" diaspora who were pretty butthurt about having to move from programming in that environment, to having to write C on DOS (or whatever else paid the bills at the time).
- xvilka 6y agoWebAssembly is just another JVM which is notoriously slow for GUI compared to the native alternatives like Qt.
- rmorey 6y agoThere basically already is in the M1: https://www.anandtech.com/show/16226/apple-silicon-m1-a14-deep-dive/2 https://www.anandtech.com/show/16226/apple-silicon-m1-a14-de... tl;dr it has really sick floating point double performance which directly translates to JS performance
- imwillofficial 6y agoYep, see the success of the Nova editor.
- Hamuko 6y agoIt's a success?
- imwillofficial 6y agoYes
- 1123581321 6y agoI don't know what qualifies as a success, but I saw in Git Tower's developer survey that it has about 5% share. The share of the whole developer industry should be lower, because Tower's audience is interested in premium tools, but I expected it to be struggling to break 1%. https://www.git-tower.com/blog/mac-dev-survey-2021-results https://www.git-tower.com/blog/mac-dev-survey-2021-results
- homarp 6y agodiscussion of Nova Editor: https://news.ycombinator.com/item?id=24495330 https://news.ycombinator.com/item?id=24495330
- realityking 6y agoFunnily enough, I dropped it after the trial expired because the plug-ins - which I belobe are written in JavaScript - were incredibly unstable.
- Klonoar 6y agoIf you don’t run Electron apps, even an older Mac will fly. My 2015 is still astoundingly fast, it just doesn’t have Chrome bogging it down.
- coliveira 6y agoExactly, I have a 2015 MacBook that works perfectly, unless I try to use electron-based apps.
- mrweasel 6y agoYou can even go back to 2013 and not notice that you’re using a 7-8 year old machine. A MacBook Pro from late 2013 runs Big Sur and performs fine for most everyday use use case and any development work that doesn’t require an IDE. You just can’t run Chrome all the well, which should tell you more about Chrome than Macs.
- hugi 6y agoI do all my work (java/postgres etc) on a 2012 i7 Mac Mini. It used to be my home media server but I started using it as a "temporary machine" last year after killing my 2018 15" MBP by spilling water over it. I was planning to replace it with an Apple Silicon machine once they became available, but it's performing so well I'm more than happy to keep using it while waiting for a 15" or 16" M1x/M2. Amazing little machines.
- vladvasiliu 6y ago> and any development work that doesn’t require an IDE Probably depends on the IDE and the language. My impression is that newer computers (especially in the "consumer" / "general public" market) have especially improved efficiency. They're not much faster, but they last longer on smaller batteries. My late 2013 15" (2.3 GHz / 16 GB RAM) works great with Pycharm for moderately sized projects. It's even usable for personal Rust projects (with the intellij-rust plugin). For Rust it's somewhat slower than my i5-8500 desktop but not by much. For incremental compiles, I don't feel like I'm waiting around more. The i5 mainly wins when it can use all six cores. It's however quite a bit faster than my work HP ProBook with an i5-8250U which is a much newer machine (2018 I'd say). Aside from battery life, which is somewhat lesser, all in all the mac is a much, much better machine than the HP, especially for "creature comforts": gorgeous screen, no misaligned panels rubbing against my wrists, great trackpad, no random coil whine, inaudible fans unless it starts compiling for a while, no background noise on the headphone out, integrated optical output when I want to use my home stereo.
- AceJohnny2 6y agoIs there an equivalent to Parkinson's Law ("Work expands to fill the available schedule"), where software expands to fit the available performance?
- flohofwoe 6y ago"Software is a gas; it expands to fill its container." - Nathan Myhrvold PS: apparently the quote is from 1997, go figure.
- jml7c5 6y agohttps://en.wikipedia.org/wiki/Wirth's_law https://en.wikipedia.org/wiki/Wirth's_law
- RachelF 6y agoAn old joke: c - the speed of light, independent of the speed of the observer. w - the speed of Windows, independent of the speed of the hardware.
- coliveira 6y agoWe don't even need to wait for that. Right now web developers are creating the new generation of web-based apps that will consume everything that M1 can give and more. In fact these apps already existed, they were just largely ignored because they're so power-hungry (just look at electron and similar stuff).
- mrweasel 6y agoEven worse: Developers will get an M-series Mac, write Electron apps that performs okay. They will then ship them as cross platform app, that will absolutely suck on any other platform.
- imtringued 6y agoWhere is that inefficiency supposed to come from though? I mean there are four big inefficiencies that came with JS. 1. Garbage collection and minimum runtime Garbage collection decreases memory efficiency, browsers need a certain minimum amount of resources to render a page, no matter how complicated leading to 500MB RAM text editors like Atom and worse once you open files. Similar problems plague Eclipse and IntelliJ which both often consume 1GB of RAM. The JVM often needs 150MB for an empty or perfectly optimized app. 2. Everything is an object with pointers This is especially bad in Javascript where every object is basically a hashmap. This causes performance slowdowns because even something as simple as looking up a field is a pointer chase through several layers now. Raw numerical data may consume a lot of memory if you are not using typed arrays. Especially bad with ArrayList<Integer> in Java. 3. JIT JIT compilers can only spend a certain amount of time on optimizations, which means JIT languages tend to either suffer from slow start up times or faster start up but less optimizations. 4. GUI complexity Things like having animations and constantly recomputing layouts. If you designed your processors for these things and made them fast at this, the only further source of slowdown is a lack of caring because you have already exhausted the unavoidable technical reasons. E.g. your processor is so fast, you write a naive algorithm that takes 5 seconds on the fastest computer available but then takes 20 seconds on an old computer.
- josho 6y agoI think the next layer is cross platform bridges. Look at multi-platform products like ms office and how slow they run on a Mac. I suspect because there is a translation layer to bridge win32 calls to Mac equivalents. And that seems like it would be point 5 on your list.
- ogre_codes 6y agoMaybe for some low hangers, but compiling code will still be faster, XCode and VSCode will be a bit snappier, Safari and Messages will be a bit better. These base things need to work on a broad range of products. The fact that Apple writes much of their software for iOS and MacOS at the same time means much of it is designed to run on fairly light hardware. I know we’re all stuck with bloated stuff like Slack and some of us with MS Office, but just go native where you can it reap the benefits of the platform.
- flohofwoe 6y ago> but compiling code will still be faster I don't know about that, LLVM is getting slower with each new release too [1]. Same for Xcode: startup is very noticeably slower than a few years ago on the same machine. Starting into a debugging session for the first time is much slower (it used to be instant, now it's multiple seconds). The new build system in Xcode is most definitely slower than the old one, at least for projects with more than a handful compile targets. Etc etc etc... new software is only optimized to a point where performance doesn't hurt too much on the developer's machine. [1] https://www.npopov.com/2020/05/10/Make-LLVM-fast-again.html https://www.npopov.com/2020/05/10/Make-LLVM-fast-again.html
- nicoburns 6y agoThe work off the back of that article has mostly halted that I think.
- ogre_codes 6y agoI suppose that’s a fair comment. The whole build system and IDE slow down when working with Swift. It’s possible Swift wouldn’t exist if it weren’t for faster processors. One nice thing is Swift is slow to build but quick at runtime.
- jrockway 6y agoI feel like things have felt pretty good in the PC world since NVMe SSDs and approximately Sandy Bridge. But, I do agree that there is a lot of jank in software that we write these days. Over the weekend I started writing an application that uses glfx + dear imgui, running on a 360Hz monitor. The lack of latency was incredible. I think it's something that people don't even know is possible, so they don't even attempt to get it. But once you know, everything else feels kind of shitty. This comment box in a web browser just feels ... off.
- disgruntledphd2 6y agoEmacs has given me this feeling for a while. Even over a remote connection that is super slow, I am supremely confident in every keystroke getting to the server and doing what I want. (Except for lsp/company which occasionally just messes up everything).
- legulere 6y agoThere are some hard usability limits that feel like the performance has stagnated or getting worse: when resizing Relayouting needs to be faster than the time for one frame (16ms usually). On Windows seemingly no software manages to do that.
- jkestner 6y agoSpeed is a feature, said well: https://craigmod.com/essays/fast_software/ https://craigmod.com/essays/fast_software/
- bscphil 6y ago> I feel like things have felt pretty good in the PC world since NVMe SSDs and approximately Sandy Bridge. Agree, and I would add that devs on some platforms have not been as thorough about using (or abusing?) all that new power. I've been able to continue use a Sandy Bridge laptop from 2011 - it'll turn 10 years old in a couple of months - because most apps on Linux still have so little complexity that you could run them on a computer from 2006. Electron-based stuff is not the norm. Adding an SSD a few years ago has been my only significant hardware upgrade. Meanwhile, Macbook Pros that came out two years after my laptop was built can't even be updated to the latest version of macOS, before you even get to the issue of software jank.
- arthur_sav 6y agoNo need to wait, just use Chrome to get a taste of the "future".
- granshaw 6y agoCould be even worse – web devs writing shitty webapps that are fast on their Macs but dog slow on non-Macs
- happymellon 6y agoNah, don't worry they are using electron apps to build them as well.
- crazygringo 6y agoBut since so much software these days is cross-platform, apps/sites will still have to work performantly on Intel chips. E.g. Google can't slow down Chrome to take advantage of Mac speed increases, because it would become unusable on Windows. So I actually think that Mac software will hold the performance edge for a long, long time.
- nexuist 6y agoIt logically makes sense for Windows to move to ARM as well at this point. They already ported it with Windows RT, and now all they have to do is provide a translation layer like Rosetta and release the full Windows experience (instead of the locked down version RT was).
- crazygringo 6y agoBut there's no M1 chip equivalent for PC's. It's fine to have an ARM version of Windows but there's no equivalently high-performance ARM chip to run it on. Unless you're talking about Bootcamp on Macs.
- floatboth 6y agoMicrosoft went with Qualcomm, but indeed it's not-that-high performance. (Even the "new" 8cx gen2, also rebranded as Microsoft SQ2, is still basically an 855… The situation will improve somewhat with an 888 based chip.)
- _carbyau_ 6y agoAny reason why Intel and AMD can't do an ARM chip? I have a vague tickle in my memory that both Intel and AMD have dabbled in ARM before. Even if they don't assign large production volumes to it now, they could still have a design team working on it for a contingency plan.
- kalleboo 6y agoAMD was developing an ARM core "K12" in parallel with the Zen core. K12 was delayed in order to prioritize Zen, Zen turned out to be a massive hit, so K12 got delayed indefinitely. https://en.wikipedia.org/wiki/AMD_K12 https://en.wikipedia.org/wiki/AMD_K12 https://en.wikipedia.org/wiki/Zen_(first_generation_microarchitecture)#History_and_development https://en.wikipedia.org/wiki/Zen_(first_generation_microarc... Once Apple released M1, rumors of AMD ARM development started again https://www.techspot.com/news/87851-amd-rumored-working-arm-based-apple-m1-rival.html https://www.techspot.com/news/87851-amd-rumored-working-arm-...
- mullingitover 6y agoSoftware is a gas that expands to fill its container. It's just science.
- crossroadsguy 6y agoThis is so true. My work kept providing latest Macs at excellent configurations and those Macs kept getting slow very fast :) Also, Apple’s buggy releases (which is tradition now[0]) didn’t really help. 0. Apple essentially stopped fixing bugs and they just release another buggy OS in a year or so with a new name and changes that break everything.