News for hackers. Stuff that matters.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @02:20PM (#25239752)
I'm a developer as well and don't use apps like VSCode, or Java/Gradle... but instead develop open source projects running Python, and Rust.

1. For my open source projects, running tests has sped up so much that I find it more of a joy to work on this projects now. Test suites that take ~60 seconds on my 2017 MacBook Pro i7, now take just ~15 seconds. That's a HUGE win in the edit, run test suite cycle.

2. My Rust projects now compile in WAY less time. Something that used to take 3 minutes to compile + link for a debug build is now down to 40 seconds. Once again, this has increased my productivity in the edit, compile, test cycle.

For other projects like node/npm the speedups are also massive and running various pipelines to go from source code to final deployable object is also much faster.

I use vim to develop, and it runs on Rosetta just fine, so I can continue to use all my existing plugins. I don't extensively use docker containers, but for those I connect to the cloud instead of running them locally, which is a move I was already making even on my Intel based MacBook Pro.

I got the 16GB 13" MacBook Pro. I, like the blog author, was thinking of this as a secondary laptop, something fun to have around, but I have hardly touched my old 15" MacBook Pro because this one does everything I already need. And does it faster.

I've been living with 16GB of RAM forever, so maybe I am used to fitting in that memory space... I avoid Electron based apps like the plague, and with being able to run iPad/iOS apps on the M1, I've been able to cut down even further since things like Authy are way faster to launch when they aren't large Chrome based hogs.

I am looking forward to the 16" MacBook Pro's with Apple Silicon based processors, but only because I do miss the additional screen real-estate, and prefer the larger size. But the 13" MacBook Pro M1 has been absolutely fantastic so far.

Re:Apple Silicon M1: A Developer's Perspective by spideymans on Saturday November 28, 2020 @02:54PM (#25239990)
>I've been living with 16GB of RAM forever, so maybe I am used to fitting in that memory space... I avoid Electron based apps like the plague, and with being able to run iPad/iOS apps on the M1, I've been able to cut down even further since things like Authy are way faster to launch when they aren't large Chrome based hogs.

iOS apps on the Mac are a game changer for me. The UX isn't 100% perfect, but it sure is better than web apps, which are very often slow, resource intensive and kill your battery. I haven't touched the Twitter web app since I've installed the iOS/Catalyst app on my Mac. Even with its iOS-optimized user interface, the better performance of the iOS app makes it so much more enjoyable than the web version.

I'm very much looking forward to seeing other iOS apps arrive on the Mac, to replace their web variants.

There's really something to be said about how web developers have been killing the performance of their websites with their bloated frameworks or whatever. I know web apps will always be at a performance disadvantage compared to native apps, but the performance regression has gotten absurd. Using Reddit via the Apollo iOS app is a quick and buttery smooth experience, meanwhile the redesigned Reddit webpage is a laggy stuttering mess on my MacBook Pro.

Re:Apple Silicon M1: A Developer's Perspective by kitsunesoba on Saturday November 28, 2020 @04:04PM (#25240524)
> iOS apps on the Mac are a game changer for me. The UX isn't 100% perfect, but it sure is better than web apps, which are very often slow, resource intensive and kill your battery. I haven't touched the Twitter web app since I've installed the iOS/Catalyst app on my Mac. Even with its iOS-optimized user interface, the better performance of the iOS app makes it so much more enjoyable than the web version.

Totally agree, particularly for small utility apps and the like. Most good iOS apps launch instantly and sip power even on comparatively limited iPhone and iPad batteries, so the impact they have on a Macbook battery should be close to nothing. Night and day compared to electron stuff.

Re:Apple Silicon M1: A Developer's Perspective by lstamour on Saturday November 28, 2020 @03:43PM (#25240380)
Similarly, it’s a joy to use the Jira app for macOS which uses Catalyst to port their iPad app to macOS. Compared to how long it takes to load and use Jira on the web, it’s just a bit snappier and nice. The dark mode support is also appreciated, though aesthetics could still improve to be a bit more mac-native... and because of Jira’s design, it’s possible the app will always lag in functionality compared to the website. But still— progress! :)
Re:Apple Silicon M1: A Developer's Perspective by nicoburns on Saturday November 28, 2020 @08:56PM (#25242310)
Are you serious? The JIRA app is by far the worst native mac app I've ever used. If their website is anything to go by then it's not the underlying technologies fault, but I found the JIRA mac app to be just as slow as the website.
Re:Apple Silicon M1: A Developer's Perspective by lstamour on Sunday November 29, 2020 @01:20AM (#25243314)
I'm serious, yes, it's better. I'm not going to say it's as good as other apps. I mean, if you're keeping a to-do list, better to do that in Apple Reminders -- especially now that they've added that new shared list feature and assigning todos. But if you have to put up with Jira, then yes, I personally find the Jira app to be faster than the website. It reminds me why I like apps as much (or more) than websites.

I've also run Jira on a server before, and if you optimize the Java runtime's settings and over-provision, you can get a pretty fast Jira instance going. It's just most folks rarely touch the default configurations, which are terrible, or don't shell out for SSDs when running it. And the cloud version ... well, it seems a bit under-provisioned if you ask me. Jira doesn't appear to be written well enough to take full advantage of the cloud, yet.

Re:Apple Silicon M1: A Developer's Perspective by girvo on Saturday November 28, 2020 @06:29PM (#25241480)
I wonder how it compares to the existing Mac native Jira app?
Re:Apple Silicon M1: A Developer's Perspective by lstamour on Sunday November 29, 2020 @12:56AM (#25243234)
The Jira Cloud iPad app does not appear in the App Store. Apps can opt out from the macOS App Store, and this is especially useful if there already is a macOS version. Why? Generally, any macOS version of an app -- even one like Jira which is nearly a straight port of the iOS app -- is 10x better than the iOS version. Running iOS apps on the M1 is a lot rougher around the edges compared to running Intel apps on the M1. I expect Apple will polish up how iOS apps run on macOS in future releases, if they maintain the feature in its current form.
Re:Apple Silicon M1: A Developer's Perspective by someperson on Saturday November 28, 2020 @02:59PM (#25240037)
I think a lot of the performance gain is due to switching from an aging 2017 Intel processor to a modern processor on a recent TSMC node (5nm in Apple's case).

Had Apple switched to AMD Ryzen processors on TSMC's 7nm node the performance improvement will have been similarly stark.

Re:Apple Silicon M1: A Developer's Perspective by dreamcompiler on Saturday November 28, 2020 @11:04PM (#25242846)
I think the most important performance benefit of the M1 is having all RAM within a few millimeters of the CPU. Can you do that with a Ryzen?
Re:Apple Silicon M1: A Developer's Perspective by Rillen on Sunday November 29, 2020 @09:39AM (#25245327)
Huh? Is there anything to support your assumption?
Re:Apple Silicon M1: A Developer's Perspective by dreamcompiler on Sunday November 29, 2020 @11:12AM (#25245993)
The speed of light is a huge limiting factor on modern processors.

https://arstechnica.com/science/2014/08/are-processors-pushi...

Light travels about a foot in 1 nanosecond so moving RAM from a foot away to touching the CPU saves 2 ns in round-trip latency. That's a big win on modern systems.

In reality it's a bigger effect since electric signals travel slower than light. And the effect is yet bigger because off-package memory must be accessed through buses with several levels of synchronization and buffer and gate delays.

Apple gets away with "unified memory" in the M1 because having the memory on-package means a good deal of the bus and sync and contention logic becomes unnecessary. So everything that touches RAM gets a lot faster. And almost everything touches RAM.

https://www.theregister.com/2020/11/19/apple_m1_high_bandwid...

https://www.macworld.com/article/3597569/m1-macs-memory-isnt...

Re:Apple Silicon M1: A Developer's Perspective by wulfklaue on Sunday November 29, 2020 @09:02PM (#25250037)
Plenty move advantages then just round trip latency. The fact that its a single SOC, what in turn reduces traces on the MB. Freeing up real-estate.

We are finally moving to the conversion point between smartphone's and PCs. It has been in the making for a while.

Now, if that is a good thing for the consumers ( losing upgradability ) is another thing? But given how PC's have become less and less flexible anyway.

We used to have slots for everything ( GPU, Network, Audio, ...). Now we have ATX boards where you maximally put in a GPU. SATA is going the way of the dodo with m.2 becoming the new standard for anything data. I mean, what do we even change anymore on PC's... CPU, Memory, GPU.

GPU's will become a external device with USB4. Mass storage has been moving to NAS more and more or USB3 devices. The people that need 4+ HDD's are more exceptions. And you can get away with USB3 HUB's + external enclosures.

I questioned for a long time, why we still have Chipset, that artificially segment MB's when the difference has become very small between them anyway. You can easily move that last bit of IO into the CPU SOC.

The days that we buy AMD or Intel SOC's with some default CPU+RAM+IO is probably closer then what most think.

Separate hardware is probably going to become a Server / Workstation Pro only feature ( with big $$$ prices ).

The reality is that hardware has reached a point, that most people did not even upgrade for years anymore. And its more a smaller group / minority that really needs ultra fast hardware.

Flexibility is moved from big MB's to external devices, connected over high speed connections.

Sorry if i have gone a bit off topic but when you mentioned the onboard memory, it got me thinking about how we really are moving to a SOC/NUC/... future for even powerful hardware.

Re:Apple Silicon M1: A Developer's Perspective by read_if_gay_ on Saturday November 28, 2020 @03:01PM (#25240046)
But not the battery life.
Re:Apple Silicon M1: A Developer's Perspective by nightski on Saturday November 28, 2020 @03:38PM (#25240334)
That's not entirely true. My Ryzen 4900hs laptop gets great battery life with integrated graphics. Not as good as the m1, but it's a zen 2 chip and we have yet to see what zen 3 mobile will do.

Apple clearly has a huge advantage here with a cutting edge process and for all practical purposes unlimited money to throw at this. Their cash on hand is more than AMD s full market cap.

Re:Apple Silicon M1: A Developer's Perspective by threeseed on Saturday November 28, 2020 @05:13PM (#25240993)
Can you clarify what you mean by "great" i.e. in hours.

From all benchmarks the Apple M1 laptops are around 1.8-2x more battery life than anything from AMD/Intel.

Re:Apple Silicon M1: A Developer's Perspective by neogodless on Saturday November 28, 2020 @08:35PM (#25242205)
My friend sent me a screen shot from `powercfg /batteryreport` on his Asus Zephyrus G14 (Ryzen 9 4900HS) and it had consumed 16,704 Wh of battery in 1:47:27 of active use. That tracks to about 8.5 hours (capacity showed just under 80 Wh).
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Sunday November 29, 2020 @01:15AM (#25243296)
I've been averaging about ~15 hours per charge on my 13" MacBook Pro M1 so far.

That includes compiling/running tests/and not just web browsing/checking mail.

Re:Apple Silicon M1: A Developer's Perspective by dr_zoidberg on Sunday November 29, 2020 @08:04AM (#25244915)
Going by TSMCs claim of 30% better power consumption at iso-speed would put the battery of the G14 at 11-12 hours. So that places the Apple system on a 25-36% better battery range, instead of 80-100%.

And still, there are more catches: Apple is probably driving the screen at 60Hz instead of 120Hz for the G14, and the screen tends to be one of the main drivers of battery life.

What I'm trying to say is that the talks revolve around the M1 vs x86 for battery consumption, but the big savings can probably come from other components in the system.

Re:Apple Silicon M1: A Developer's Perspective by Rillen on Sunday November 29, 2020 @09:45AM (#25245352)
Its such a hard comparision though.

You are running the newest of the newest.

My Lenovo Thinkpad X390 which i'm sitting on right now for a while, still has ~8h left to go.

Chrome with 30 tabs, intellij etc. open and running.

I do assume the M1 is doing a great job, don't get me wrong, but i would like to see a more objective comparison.

Personally speaking, the most interesting thing for me to see is that Apple now put a very strong SoC on all its models. From Air to Pro, with a relative good price point (as long as you don't upgrade anything...)

Re:Apple Silicon M1: A Developer's Perspective by meditative on Sunday November 29, 2020 @03:37AM (#25243831)
mWh? Otherwise that's one hell of a battery.
Re:Apple Silicon M1: A Developer's Perspective by neogodless on Sunday November 29, 2020 @06:20AM (#25244477)
Oops I missed my edit window! That'd also be some insane power consumption! Let's pretend I'm not from the U.S.A. and the comma is used as a decimal.
Re:Apple Silicon M1: A Developer's Perspective by totalZero on Saturday November 28, 2020 @03:35PM (#25240319)
Power efficiency is indeed one of the benefits of smaller process nodes, so it has a direct impact on battery life.
Re:Apple Silicon M1: A Developer's Perspective by tbrock on Saturday November 28, 2020 @11:46PM (#25242973)
Or the coolness (lack of heat).

I bought a laptop with an AMD chip once, never again. Thing was a fire hazard.

Re:Apple Silicon M1: A Developer's Perspective by adar on Sunday November 29, 2020 @03:32AM (#25243809)
Gotta be more specific when you say AMD chip. Was it a newer Zen chip or one of the old ones pre-Ryzen?
Re:Apple Silicon M1: A Developer's Perspective by chii on Saturday November 28, 2020 @07:03PM (#25241706)
> Test suites that take ~60 seconds on my 2017 MacBook Pro i7, now take just ~15 seconds.

wow, a 5x improvement without you doing anything but changing hardware!? That's an excellent upgrade imho.

I wish apple would be able to sell the M1 as a generic processor to which other machines can use.

Re:Apple Silicon M1: A Developer's Perspective by atq2119 on Sunday November 29, 2020 @03:45AM (#25243864)
Oh they're able to sell the M1 however they want. They just don't want to.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:34PM (#25241878)
Yeah, it is absolutely insane for my workloads.
Re:Apple Silicon M1: A Developer's Perspective by runeks on Saturday November 28, 2020 @04:24PM (#25240689)
> Test suites that take ~60 seconds on my 2017 MacBook Pro i7, now take just ~15 seconds.

Interesting! Are you compiling to arm64 or emulating x86?

Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:29PM (#25241850)
This is Python 3.6 -> 3.9 compiled to Intel running under Rosetta 2.

For Rust I am running the ARM toolchain that was recently released, so no Rosetta involved at all.

Re:Apple Silicon M1: A Developer's Perspective by dr_zoidberg on Sunday November 29, 2020 @07:32AM (#25244787)
Do you think moving from python 3.6 to 3.6 had any impact whatsoever? I'm surprised by such a large improvement in performance as other reports I read indicated similar-to-slightly-worse python performance of M1 vs x86.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Sunday November 29, 2020 @12:51PM (#25246669)
I run test suite across those Python's. So Python 3.6, 3.7, 3.8, and 3.9 using tox to drive the automation to test against all of those versions to validate compatibility and that nothing breaks.

So there is no moving anything. Python compiled using pyenv for the Intel platform.

Which reports are you reading? Are they using C libraries or doing heavy math computation that is not CPU bound because there's no optimized ARM version yet?

Re:Apple Silicon M1: A Developer's Perspective by dr_zoidberg on Sunday November 29, 2020 @06:20PM (#25249048)
Okay, I'm not finding any benchmark that supports the idea of a slowdown, so probably I remembered some rumour I read on twitter or reddit.

What I am finding now is that python is working more than fine on M1, be it through rosetta or native code, which is consistent with your experience.

Also to clear things a bit, I parsed your "3.6 -> 3.9" as meaning that you had moved from Py36 on intel to Py39 on apple, which is why I asked if maybe there were speedups or differences from moving to 3.9.

Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Sunday November 29, 2020 @11:26PM (#25250733)
Ah, my apologies for not making that more clear. Currently all are running under Rosetta.

I was unable to get all the versions I needed compiled natively, which means for now I will use the non-native versions.

I have tested Py3.9 compiled for arm64, and one particular test suite went from 9 seconds to 6 seconds. Other test suites were not as dramatic, especially larger ones, where it might go down from 40 seconds to 36 seconds.

Still a speed improvement, but not as dramatic as the 2017 MacBook Pro i7 -> 2020 MacBook Pro M1.

Re:Apple Silicon M1: A Developer's Perspective by kossTKR on Sunday November 29, 2020 @02:37AM (#25243605)
When do people think the 16" with a M chip will be available?

I'm honestly for the first time in a decade a bit excited about an upcoming computer, pretty great.

Still running on a 2014 MBP that honestly is still great so can wait a bit.

Re:Apple Silicon M1: A Developer's Perspective by wulfklaue on Sunday November 29, 2020 @09:07PM (#25250060)
> I'm honestly for the first time in a decade a bit excited about an upcoming computer,

I think we are more excited about a shake up in the whole computer world, that may mean the dead of ATX/MB's/etc as we know it. And a more profound move to eGPU/NUC/Laptop like powerful devices with a low power usage.

This feels a bit like a wakeup call to the industry. Like how the first (commercial) successful smartphone, the iPhone 1 fueled a entire industry for over 10 years to massive evolve. What is kind of funny because i felt like the smartphone evolution was starting to loos steam. The conversion between PC/Laptop/Smarthones will begin now.

Re:Apple Silicon M1: A Developer's Perspective by thejohnconway on Sunday November 29, 2020 @08:00AM (#25244895)
I don’t think this transition will take two years, the transition to Intel took less time than they said last time. Maybe for the Mac Pro.

The MacRumours buyers guide has the MacBook Pro 16” as due an update right now: https://buyersguide.macrumors.com/#MacBook_Pro_16

Honestly, I’d be surprised if we don’t get an M1x (or whatever it’s called) within six months.

Re:Apple Silicon M1: A Developer's Perspective by pfranz on Sunday November 29, 2020 @02:50AM (#25243655)
Nobody actually knows, but I remember Apple saying something like a 2 year transition (which includes new Intel products). So if you're not in a rush that's likely the longest you'll wait.
Re:Apple Silicon M1: A Developer's Perspective by alwillis on Sunday November 29, 2020 @04:18PM (#25248164)
I use vim to develop, and it runs on Rosetta just fine, so I can continue to use all my existing plugins.

Don't forget—Vim comes as a Universal binary, so it already runs natively on the M1.

    /usr/bin/vim: Mach-O universal binary with 2 architectures
    [x86_64:Mach-O 64-bit executable x86_64] [arm64e]
    /usr/bin/vim (for architecture x86_64): Mach-O 64-bit executable x86_64
    /usr/bin/vim (for architecture arm64e): Mach-O 64-bit executable arm64e
Re:Apple Silicon M1: A Developer's Perspective by raverbashing on Saturday November 28, 2020 @02:31PM (#25239833)
Good to know

I'm glad Vim is running fine on Rosetta, still, if you wanted to compile it from source, it really shouldn't be too hard.

(Rust is a harder problem, so I wouldn't worry too much, still, once the dependencies are downloaded and compiled it's usually fine)

Re:Apple Silicon M1: A Developer's Perspective by saagarjha on Saturday November 28, 2020 @02:40PM (#25239893)
No need to use Rosetta:

  $ file `which vim`
  /usr/bin/vim: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e]
  /usr/bin/vim (for architecture x86_64): Mach-O 64-bit executable x86_64
  /usr/bin/vim (for architecture arm64e): Mach-O 64-bit executable arm64e
Re:Apple Silicon M1: A Developer's Perspective by lmedinas on Saturday November 28, 2020 @03:06PM (#25240091)
vim 8.2 included in MacOS is native, neovim is not yet ported :(
Re:Apple Silicon M1: A Developer's Perspective by mlindner on Saturday November 28, 2020 @11:02PM (#25242836)
NeoVIM works fine after adding a compilation target. See: https://github.com/neovim/neovim/pull/12624

It hasn't been merged yet as some of the dependencies aren't available, one of them apparently being LuaJIT, but if you build it yourself without that it shouldn't be a problem.

Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:31PM (#25241864)
I install from Homebrew, specifically MacVim. The system version is usually behind on patch levels/plugins that can be loaded.
Re:Apple Silicon M1: A Developer's Perspective by mlindner on Saturday November 28, 2020 @11:03PM (#25242841)
Gluing yourself at the hip to homebrew is a bad idea IMO. It's trivial to install things yourself. It's just a matter of `./configure && make && make install` and you're done.
Re:Apple Silicon M1: A Developer's Perspective by ibraheemdev on Saturday November 28, 2020 @11:39PM (#25242953)
Why do a `git clone pkg && cd pkg && ./configure && make && make install` instead of just a `brew install`? The whole point of a package manager is to make installations and upgrades easier.
Re:Apple Silicon M1: A Developer's Perspective by mlindner on Sunday November 29, 2020 @02:36AM (#25243599)
Homebrew never was a package manager until recently. It was in the name, it was designed for building packages from source on your local machine.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Sunday November 29, 2020 @02:43AM (#25243627)
Now your are just quibbling over what ultimately is a minor difference.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Sunday November 29, 2020 @01:17AM (#25243303)
"just"

Also need to track down and install all of the dependencies, and the dependencies dependencies and all the way down, and figure out the right configure flags to pass, and what environment variables it needs and where it expects to look for header files and the like.

Doing all of that from scratch takes hours and hours. Homebrew lets me not worry about that, and instead be productive.

Re:Apple Silicon M1: A Developer's Perspective by ant6n on Sunday November 29, 2020 @08:44AM (#25245064)
It also takes care of updates
Re:Apple Silicon M1: A Developer's Perspective by arcticbull on Saturday November 28, 2020 @05:00PM (#25240924)
I'm doing my Rust development in a Docker container deployed on AWS w/Fargate and EFS to store my source, via VSCode Remote on my M1 MacBook Pro :) Thin client, arbitrarily fat server. VSCode Remote makes it a very pleasant experience. I'll document my experience once I've smoothed out the kinks.

The nice thing is I can just wait out the compatibility issues re: arm migration, especially with some of the third party crates my rust projects depend on currently failing to build.

Re:Apple Silicon M1: A Developer's Perspective by aledalgrande on Saturday November 28, 2020 @07:01PM (#25241692)
What is the monthly expense to run your dev on Fargate?
Re:Apple Silicon M1: A Developer's Perspective by arcticbull on Sunday November 29, 2020 @07:50PM (#25249646)
Just got it set up a few days ago, but happy to report back. I'll also write up a quick medium post or something.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:30PM (#25241859)
Being able to easily install it using homebrew is really where that need came from. I can use the existing bottles and the recommendation for right now is to not mix and match both Intel/Arm binaries.

Also, the ARM version of Homebrew is not yet ready for primetime, there is a ton of software that doesn't compile for ARM yet (Including MacVim).

Re:Apple Silicon M1: A Developer's Perspective by kzrdude on Saturday November 28, 2020 @07:29PM (#25241848)
How is Rust support for the platform?
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:34PM (#25241877)
It's Tier 2... and I've been using the ARM toolchain that was just released.

So far all the crates that were not working have been getting updates to work on the new platform, so far I haven't found any issues!

Re:Apple Silicon M1: A Developer's Perspective by steveklabnik on Saturday November 28, 2020 @07:32PM (#25241867)
Re:Apple Silicon M1: A Developer's Perspective by throwaway201103 on Saturday November 28, 2020 @09:01PM (#25242340)
> Something that used to take 3 minutes to compile + link for a debug build is now down to 40 seconds.

1990s me laughs remembering edit/compile/test cycles measured in hours.

Re:Apple Silicon M1: A Developer's Perspective by zeroonetwothree on Saturday November 28, 2020 @09:34PM (#25242510)
Well it still can be hours. Really depends what you work on.
Re:Apple Silicon M1: A Developer's Perspective by Aeolun on Sunday November 29, 2020 @04:56AM (#25244110)
At that point, wouldn’t you buy a double Threadripper machine to speed it up? If you sit around for a few hours that is a lot of time wasted.
Re:Apple Silicon M1: A Developer's Perspective by harrygeez on Saturday November 28, 2020 @10:18PM (#25242676)
Well it still could be, depending on what you do
Re:Apple Silicon M1: A Developer's Perspective by selestify on Saturday November 28, 2020 @10:53PM (#25242811)
What were you compiling back then?
Re:Apple Silicon M1: A Developer's Perspective by in3d on Saturday November 28, 2020 @04:12PM (#25240592)
Why are you using a laptop for development in the first place unless you have to be on the move? Why not take advantage of even faster CPUs or GPUs, more RAM, many times more screen space, more disk space, ergonomic keyboard and mouse, or even real speakers if you work from home?
Re:Apple Silicon M1: A Developer's Perspective by samb1729 on Saturday November 28, 2020 @06:42PM (#25241571)
In a similar vein: "Why are you using a Mac for development in the first place unless you have to develop software for Apple devices? Why not run Linux if everything you write runs on Linux servers?"

Your post reads less like a sincere question and more like "you should be doing it this way unless you can defend your position". Maybe--just maybe--people weigh up tradeoffs differently than you do personally.

FWIW 'on the move' can mean going into a meeting room or even just walking over to a coworker's desk with your computer. Desktops kinda suck when you work around humans who don't just stare at their screens with cans on all day.

Re:Apple Silicon M1: A Developer's Perspective by coward8675309 on Saturday November 28, 2020 @07:05PM (#25241714)
You've touched on something that irks me to no end — the tendency of many Elite Coder Bros to say things like, "Didn't you see my enormous headphones on?! Can't you see I'm coding — don't you realize I think for a living?!"

Yeah, dude, we're all thinking. As a hands-on programmer-manager I can report that creating slides for the fundraising deck that'll raise money to pay you or writing that email about you taking bags of beef jerky home for your post-workout recovery meal can take as much sustained concentration as you spinning in your `while 1 { copy_compiler_error(); stack_overflow_it(); paste_code(); }` infinite loop.

Re:Apple Silicon M1: A Developer's Perspective by spacedcowboy on Saturday November 28, 2020 @10:13PM (#25242661)
I tend to get given large projects to do. I'm fairly senior, and once we've got past the brainstorming stage, the ideas have flowed forth, and the direction is, if not clear, then at least aspirational, I often get given the job of breaking ground.

Here's how I think.

I model interaction between distinct parts. I have a mental model of how X fits with Y, how X can affect Y, and how Y can in turn affect X. I'm not doing it with just X and Y, I painstakingly build this mental model[1] over as much of the problem space as I can, and having done this for many years now, I can cover a fair amount of ground before the complexity gets beyond my ability to model. It takes a while to create this, and then when some middle-management type wanders along, taps me on the shoulder and disturbs the concentration, and it all comes crashing down around me, I am less than best-pleased. Bonus points if it's just to "touch base" or "remember we have a meeting in 2 hours time", or ... you get the picture.

Why do I expend this enormous mental effort to gain such a fragile and ephemeral state ? Because I can mentally throw boundary conditions at it and "see" how things will react. It's how I deal with inherent complexity of large systems, and a couple of hours of mental effort can prevent me spending a week coding down a dead-end path. It's happened often enough now that even my line management understand it's worth the time - there's been plenty-a-meeting where I go in and say "yeah, I know we wanted to do <insert X> but I think there's a problem when Y and Z come into play under conditions A, B and C. I think <insert option gamma> is a better route even though we didn't think so at first".

Sometimes you really do just need to be able to be left alone and think. As someone who used to own the company before he sold it, and who's done pitches to VC's and other investors, I can quite categorically state that (for me), the slides, presentations, and client management is nowhere near the level of mental investment. Nowhere near.

Just my $0.02

---

[1] It's not visual, I have aphantasia, it's more firing-condition-based.

Re:Apple Silicon M1: A Developer's Perspective by waheoo on Saturday November 28, 2020 @07:45PM (#25241924)
My wife and I discus this all the time. Not all jobs require the same level of thought. Her work involves a lot of mechanical movement, practice, skill, talent, and some thinking. But most of her day to day can be done listening to a podcast like she's driving.

I can't do that.

So no,

We're not "all thinking", some tasks require deep thought and long periods of uninterrupted concentration.

The problem is working in a team requires communication, and management of interruption, it is not useful to be like this dick with the headphones on, that creates barriers (the attitude, not the headphones) to communication.

Re:Apple Silicon M1: A Developer's Perspective by in3d on Saturday November 28, 2020 @09:13PM (#25242408)
I do think it makes little sense and it’s a message board, sometimes things will be said directly. If a preference is not rational and has negative consequences then it’s worth challenging. Who knows, maybe somebody will realize that squinting at the text on a 13-in screen while looking down and having their hands in unnatural positions for many hours each day is not great for them. I never said that you can’t have a laptop to take with you. I’m talking about development like the OP was - where things like compile times matter and where you can very likely remotely access your desktop if you want to show things to others.
Re:Apple Silicon M1: A Developer's Perspective by mypalmike on Sunday November 29, 2020 @01:18AM (#25243307)
Much of the development world has moved to laptops, docks for ergonomic desktop use, and cloud compute for when beefier hardware is needed. As a developer, I haven't used a desktop machine either at work or at home in well over a decade.

This is all off topic in any event.

Re:Apple Silicon M1: A Developer's Perspective by in3d on Sunday November 29, 2020 @02:48AM (#25243653)
Sorry to hear that. I tried to use a top-of-the-line 2019 MacBook Pro for some development while on the road and it doesn’t come close to a desktop, even when it’s augmented with external monitors, etc.

“Compared to the desktop (sitting), tablet and laptop use resulted in increased neck flexion (mean difference tablet 16.92°, 95% CI 12.79-21.04; laptop 10.92, 7.86-13.97, P < 0.001) and shoulder elevation (right; tablet 10.29, 5.27-15.11; laptop 7.36, 3.72-11.01, P < 0.001).”

“These findings suggest that using a tablet or laptop may increase neck flexion, potentially increasing posture strain.”

https://pubmed.ncbi.nlm.nih.gov/30373975/

And it is on-topic enough for both the link and the OP.

Re:Apple Silicon M1: A Developer's Perspective by mypalmike on Sunday November 29, 2020 @10:19AM (#25245582)
You seemingly don't know what a docking station actually is.
Re:Apple Silicon M1: A Developer's Perspective by woah on Saturday November 28, 2020 @10:15PM (#25242665)
Ever want to code on the couch? Not everyone wants to spend all day sitting on a gaming chair in the man cave illuminated by the light of their LED desktop enclosure
Re:Apple Silicon M1: A Developer's Perspective by in3d on Sunday November 29, 2020 @12:25AM (#25243126)
See my other response. Remote login.
Re:Apple Silicon M1: A Developer's Perspective by joshmanders on Saturday November 28, 2020 @04:16PM (#25240629)
Literally everyone who chooses a laptop as their main driver is doing it purely for the portability... We don't choose it because it's small, we choose it because while most of the time we're stationary, the time we do need to be portable, its easier to just undock and walk away than to make sure your laptop and desktop are synced.
Re:Apple Silicon M1: A Developer's Perspective by macintux on Saturday November 28, 2020 @04:27PM (#25240705)
I was considering picking up a new Mini so I could drive two displays, but then I remembered another laptop advantage: TouchID. I would really miss that.
Re:Apple Silicon M1: A Developer's Perspective by joshmanders on Saturday November 28, 2020 @04:36PM (#25240763)
I drive two 27-inch 4K displays at 3840x2160 on my 2019 16-inch MacBook pro.
Re:Apple Silicon M1: A Developer's Perspective by macintux on Saturday November 28, 2020 @04:40PM (#25240792)
Ditto, but the M1 laptops officially only can do one display. People have hacked around it but I’d rather wait.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:37PM (#25241888)
I have it driving a 49" UltraWide Curved Monitor... which replaced my two 27" monitors.

Might not be for everyone, but I only need it to drive a single external monitor.

Re:Apple Silicon M1: A Developer's Perspective by waheoo on Saturday November 28, 2020 @07:49PM (#25241939)
At what res/rate?
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:59PM (#25242006)
5120 by 1440 at 60 hertz.
Re:Apple Silicon M1: A Developer's Perspective by threeseed on Saturday November 28, 2020 @06:27PM (#25241469)
You can use DisplayLink to get around it.

I wouldn't class it as a hack since it is pretty standard in enterprise environments. Downside is that it does consume CPU which depending on your workload may/may not be noticeable.

Re:Apple Silicon M1: A Developer's Perspective by joshmanders on Saturday November 28, 2020 @05:29PM (#25241094)
Ah I didn't know that.
Re:Apple Silicon M1: A Developer's Perspective by in3d on Saturday November 28, 2020 @09:17PM (#25242430)
You can get it up to 3 4k monitors and the original laptop screen running together with this MacBook Pro. But it becomes laggy.
Re:Apple Silicon M1: A Developer's Perspective by st3fan on Sunday November 29, 2020 @05:32PM (#25248712)
The Mini also unlocks with your Apple Watch :-)
Re:Apple Silicon M1: A Developer's Perspective by macintux on Monday November 30, 2020 @10:15AM (#25254561)
Good point. I don’t think it handles all of my use cases (e.g., passwords and credit card info in Safari) but I’d forgotten that there are several instances where my finger and my watch are in competition to see who unlocks something first.
Re:Apple Silicon M1: A Developer's Perspective by in3d on Saturday November 28, 2020 @04:43PM (#25240812)
You can remotely access your desktop if you’re spending most of the time stationary.
Re:Apple Silicon M1: A Developer's Perspective by joshmanders on Saturday November 28, 2020 @05:30PM (#25241096)
Or just get a laptop...
Re:Apple Silicon M1: A Developer's Perspective by pkage on Saturday November 28, 2020 @04:19PM (#25240643)
Not the original commentor, but it's nice to be able to pick up my laptop from my desk and move to sit in the kitchen, or the couch, or outside, or (in better days) a café. I really only barely use my desktop nowadays, and half the time it's over mosh.
Re:Apple Silicon M1: A Developer's Perspective by coin on Saturday November 28, 2020 @05:46PM (#25241209)
Every tech company that I’ve worked for in the last 10 years issues laptops to their SW engineers
Re:Apple Silicon M1: A Developer's Perspective by waheoo on Saturday November 28, 2020 @07:50PM (#25241950)
I bet you'll find a lot of Devs hate it.

I had a seriously nice mac mini taken off me once, got given a "new Mac Pro". Was huge downgrade, was not happy.

Re:Apple Silicon M1: A Developer's Perspective by war1025 on Saturday November 28, 2020 @10:02PM (#25242624)
I have a ~10 year old desktop and a ~5 year old laptop (I think we're due for another upgrade cycle here soon).

We got docking stations for the laptops but I just couldn't get used to it, and my desktop was just sitting there still functioning happy as could be.

So I still use my desktop for actual work and my laptop is basically a very over-powered video conferencing machine.

Re:Apple Silicon M1: A Developer's Perspective by throwaway45349 on Saturday November 28, 2020 @09:18PM (#25242434)
Don't most companies also provide workstations at desks for engineers? I know many who only use their laptop for meetings (until WFH) and it always seemed like a huge waste.
Re:Apple Silicon M1: A Developer's Perspective by in3d on Saturday November 28, 2020 @09:22PM (#25242450)
Right. I bet many of them also love open-floor plans despite research showing that they reduce the number of meaningful interactions by 70%.
Re:Apple Silicon M1: A Developer's Perspective by X-Istence on Saturday November 28, 2020 @07:33PM (#25241873)
Because I enjoy working from my home office hooked up to my 49" UltraWide, but I also enjoy working from a coffee shop, or from my couch, or from my bed, or when I go spend time with friends and do amateur photography I like having my laptop with me to do on the fly editing/reviewing of images before finishing a shoot...

Portability.

Re:Apple Silicon M1: A Developer's Perspective by waheoo on Saturday November 28, 2020 @07:47PM (#25241932)
I wish I could do this but my laptops would always struggle to run well driving dual 4k monitors.

I think next go round I'm going to get a desktop replacer style laptop and see if I can get best of both worlds.

I don't really care about portability and thus use a desktop but I do want to sit outside or work from the couch sometimes.

Re:Apple Silicon M1: A Developer's Perspective by charrondev on Sunday November 29, 2020 @11:16AM (#25246031)
The MacBook pros have been able to drive 2 4K displays at 60hz since at least 2016 (when they became thunderbolt 3).

I don’t recall if that worked on the smaller models, but it worked on my 15” model. I’ve been using 2 Dell P2715Qs since then and they work great.

Re:Apple Silicon M1: A Developer's Perspective by Rillen on Sunday November 29, 2020 @09:48AM (#25245371)
Working from home on a friday is probably the biggest reason for a lot of people i guess.

Meetings, is another one.

Doing presentations.

Also for me at least: On-Call.

I would prefer a workstation at home and a lightweight laptop with company network access but hey my companie prefers to buy me a Laptop for 3k over a desktop for 1k and a light laptop for 1k.

What can i do? yeah nothing :)

Re:Apple Silicon M1: A Developer's Perspective by sally1620 on Monday November 30, 2020 @02:04AM (#25251371)
In most companies, a laptop is a standard issue. In my company, you are given a laptop on 1st day, but you have to put in a request for a desktop.

It also greatly simplifies working from home. Not just for portability.