3 ms·
I dunno, I think most people will still err on the side of x86. Most developers aren't deploying to ARM, so it's a pretty difficult value proposition to sell so
by smoldesu 5y ago
I dunno, I think most people will still err on the side of x86. Most developers aren't deploying to ARM, so it's a pretty difficult value proposition to sell someone a computer where they can't even natively debug their program. Maybe my workflow constitutes that "five percent" you're talking about, but part of me also knows that most developers will probably be pretty disappointed with just 8 gigs of ram and 256 gigs of storage. Especially if you install XCode, one of the most asinine and largest programs I've ever seen.
- epmaybe 5y agoI'm not the most "organized" or "sophisticated" developer (I mainly code for fun or basic research related experiments), and I mainly do everything from my m1 MacBook Air. If I need to test something that will need more hardware, I fire up my desktop. Edit: Also, the M1 has a lot of surprising performance. I can run two 4k 30fps cameras off of it, display to a 4k monitor, and stream the video to another computer. My 2017 MBP struggled with this much.
- smoldesu 5y agoHave you gotten two displays to connect to it yet? That's my biggest bottleneck right now.
- jamesgeck0 5y agoYeah, I used a $40 DisplayLink adapter.
- epmaybe 5y agoWhat the other commenter said, displaylink works, but it’s not ideal and adds additional overhead like using up precious usb bandwidth for my work. I have learned to live with only two displays, plus an iPad for airplay. I’d wait for the next generation if multi display is necessary.
- indymike 5y agoIt is remarkable how much space xcode + Android studio eat of 256gb. Especially given that a 1TB SSD costs what, $100 at consumer prices?
- eyelidlessness 5y agoI’d be curious what proportion of developers build to a specific ISA at all, versus simply caring that their tools are available for the one they’re developing for.
- scoopertrooper 5y agoMost popular modern languages aren't low level enough for developers to care about architectural differences unless they are trying to squeeze every last ounce of performance. However, the x86 chip in your laptop and the x86 chip running on your deployment target, probably aren't similar enough to help you reach that goal. Also worth noting that ARM is becoming increasingly popular in the cloud services space, so that x86 advantage will deplete significantly with time. I have a M1 Macbook Pro with 8GB ram and 256 GB storage. I bought it mainly to play with, but I've found it surprisingly capable and I've used it for some moderate development workloads and even some gaming (Metro Exodus)! I've found it pretty fantastic for the most part, but I have to constantly make difficult decisions about exactly what I want to have running and stored on the device. For instance, running Docker rapidly consumes both memory and storage resources. I'd definitely recommend buying the Mac SKUs with 16GB memory and more storage, if you want to make it your primary workstation. I think 16GB is probably enough for most development workloads though, that's generally what I'm given for a work laptop an it's worked out okay.
- eptcyka 5y ago>However, the x86 chip in your laptop and the x86 chip running on your deployment target, probably aren't similar enough to help you reach that goal. Cross-compiling is still very buggy, code built for ARM on x86 can still just _not work_ correctly when deployed on ARM. In such cases, it really does help that my laptop is running x86. I hope running arm stuff will be similar.
- scoopertrooper 5y agoThere is no theoretical limitation on the ability to cross-compile between architectures. There may be bugs in individual compilers or mistakes made in configuring them, but those sorts of problems are solvable. However, how often do you locally compile the binary you deploy? Every company for which I've worked has delegated that activity to a build server.
- smoldesu 5y ago