Earlier quoted context omitted.
Go on, I’ll bite: why?
They miss the 2 hours procrastination time. It's a version of "code's compiling" :)
The foam swords are collecting dust.
Tracking developer build times to decide if the M3 MacBook is worth upgrading
111–120 of 432 posts
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#112I wonder why they didn't include Linux since the project they're building is Go? Most CI tools, I believe, are going to be Linux. Sure, you can explicitly select macOS in Github CI but Linux seems like it would be the better generic option?
*EDIT* I guess if you needed a macOS specific build with Go you would us macOS but I would have thought you'd use Linux too. Can you build a Go project in Linux and have it run on macOS? I suppose architecture would be an issue building on Linux x86 would not run on macOS Apple Silicon but the reverse is true too a build on Apple Silicon would not work on Linux x86 maybe not even Linux Arm.
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#113As a scientist, I'm interested how computer programmers work with data. * They drew beautiful graphs! * They used chatgpt to automate their analysis super-fast! * ChatGPT punched out a reasonably sensible t test! But: * They had variation across memory and chip type, but they never thought of using a linear regression. * They drew histograms, which are hard to compare. They could have supplemented them with simple me…
I think it's partly because the audiences are often not familiar with those statistics details either.
Most people hates nuances when reading data report.
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#114As a scientist, I'm interested how computer programmers work with data. * They drew beautiful graphs! * They used chatgpt to automate their analysis super-fast! * ChatGPT punched out a reasonably sensible t test! But: * They had variation across memory and chip type, but they never thought of using a linear regression. * They drew histograms, which are hard to compare. They could have supplemented them with simple me…
Yeah, I was looking at the histograms too, having trouble comparing them and thinking they were a strange choice for showing differences.
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#115Does anyone have any anecdoctal evidence around the snappiness of VsCode with Apple Silicon? I very begrudgingly switched over from SublimeText this year (after using it as my daily driver for ~10yrs). I have a beefy 2018 MBP but VScode just drags. This is the only thing pushing me to upgrade my machine right now but I'd be bummed if there's still not a significant improvement with an m3 pro.
VSCode is noticeably laggy on my 2019 MBP 16in to the point that I dislike using it. Discrete GPU helps, but it still feels dog slow.
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#116My personal research for iOS development, taking the cost into consideration, concluded: - M2 Pro is nice, but the improvement over 10 core (8 perf cores) M1 Pro is not that large (136 vs 120 s in Xcode benchmark: https://github.com/devMEremenko/XcodeBenchmark ) - M3 Pro is nerfed (only 6 perf cores) to better distinguish and sell M3 Max, basically on par with M2 Pro So, in the end, I got a slightly used 10 core M1 P…
The M3 Pro being nerfed has been parroted on the Internet since the announcement. Practically it’s a great choice. It’s much more efficient than the M2 Pro at slightly better performance. That’s what I am looking for in a laptop. I don’t really have a usecase for the memory bandwidth…
I don’t really have a usecase for even more battery life, so I’d rather have it run faster
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#1171. If, and only if, you are doing ML or multimedia, get a 128GB system and because of the cost of that RAM, it would be foolish not to go M3 Max SoC (notwithstanding the 192GB M2 Ultra SoC). Full Stop. (Note: This is also a good option for people with more money than brains.) 2. If you are doing traditional heavyweight software development, or are concerned with perception in an interview, promotional context or just…
Good to know I have commercial options for overcoming my laptop shame at interviews. /s
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#118Author here, thanks for posting! Lots of stuff in this from profiling Go compilations, building a hot-reloader, using AI to analyse the build dataset, etc. We concluded that it was worth upgrading the M1s to an M3 Pro (the max didn’t make much of a difference in our tests) but the M2s are pretty close to the M3s, so not (for us) worth upgrading. Happy to answer any questions if people have them.
Hi, Thanks for the interesting comparison. What I would like to see added would be a build on a 8GB memory machine (if you have one available).
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#119> Application error: a client-side exception has occurred (see the browser console for more information).
When I open the page.
Re: Tracking developer build times to decide if the M3 MacBook is worth upgrading
#120My personal research for iOS development, taking the cost into consideration, concluded: - M2 Pro is nice, but the improvement over 10 core (8 perf cores) M1 Pro is not that large (136 vs 120 s in Xcode benchmark: https://github.com/devMEremenko/XcodeBenchmark ) - M3 Pro is nerfed (only 6 perf cores) to better distinguish and sell M3 Max, basically on par with M2 Pro So, in the end, I got a slightly used 10 core M1 P…
I also made this calculation recently and ended up getting an M1 Pro with maxed out memory and disk. It was a solid deal and it is an amazing computer.