3 ms·
"it’s not developer ready yet." Hey, what if we just... kept it that way? Kiss all that speed goodbye once software developers get their hands on this. And th
by jerf 6y ago
"it’s not developer ready yet."
Hey, what if we just... kept it that way?
Kiss all that speed goodbye once software developers get their hands on this. And then the low end current-gen models will be even slower when running "the code that runs ok on the M1 hardware, I guess, ship it."
- smnrchrds 6y agoFor cross-platform software like Chrome and Electron apps, this will never happen, as the main target and market will still be Windows and x86-64.
- ultrarunner 6y agoIt’s unclear to me how reduced availability of developer tooling will result in a faster software experience for M1 owners.
- Shish2k 6y agoIf developers are forced to use slow machines to develop, then they’re less likely to build bloaty slow software that depends on fast machines
- ultrarunner 6y agoMaybe, but also If developers are forced to use slow machines to develop, then they’re less likely to build. Full stop. I'm actually in this situation right now. I develop a web application for event management. In some cases it's being used on older Chromebooks, where speed is, well, not there. While I'm testing on Chromebooks, I'm definitely not building my front end bundle on one. The faster machine I'm on, the faster I can iterate on building fast data tables, making intelligent choices about asset loading, etc. So yeah, I think something like the Network Conditioner prefpane should exist to simulate a slow CPU for testing (does something like this exist?). But I very much enjoy my fast dev machine and I think it'll have the best overall outcome.
- donmcronald 6y agoGive the executives slow ass old computers imo. Problem solved. Or just tell the devs the ceo has a core 2 duo.