News for hackers. Stuff that matters.
Re:Apple Introduces MacBook Neo by rbanffy on Wednesday March 04, 2026 @11:24AM (#47249804)
Let’s see… if the same problem happens under Safari, then it’s Microsoft fault. If the problem goes away when Safari runs the Azure admin portal, it’s a Google issue.

Developers should have laptops with 1366x768 screens, 4GB if RAM, and dual-core Intel Atom processors. We keep giving them server grade hardware and expect them to empathise with the muggles that run their software on potatoes.

Re:Apple Introduces MacBook Neo by epistasis on Wednesday March 04, 2026 @12:34PM (#47250930)
> Developers should have laptops with 1366x768 screens, 4GB if RAM, and dual-core Intel Atom processors.

I used to support federal laws towards this end. However, now I think the advocacy needs to be updated for the era of LLMs, as developers can just let the testing chug away and come back later. (Note: I did not actually support such laws.)

Re:Apple Introduces MacBook Neo by rbanffy on Saturday March 07, 2026 @12:32PM (#47289622)
For governments and services governments delegate to third parties, being usable by low-end machines is extremely important.

I always have to point out government services should not be designed to be efficient, but fair and universal. After they are fair and universal, THEN you can make them efficient, just as long as you don’t break fairness and universality.

Re:Apple Introduces MacBook Neo by hypercube33 on Wednesday March 04, 2026 @01:27PM (#47251701)
Make that 1 or 2gb of ram, a 32gb emmc drive and a single core 2 thread original Atom
Re:Apple Introduces MacBook Neo by rbanffy on Thursday March 05, 2026 @03:35AM (#47259160)
Or a single-core Raspberry Pi with 512MB and an SDCard ;-)
Re:Apple Introduces MacBook Neo by Geof25 on Thursday March 05, 2026 @02:13AM (#47258562)
Testing should be on such laptops. Development, especially in things like xcode or visual studio would be insane
Re:Apple Introduces MacBook Neo by rbanffy on Thursday March 05, 2026 @03:34AM (#47259151)
That would force vendors to make Visual Studio and Xcode same ;-)