Steve Jobs Said This Kind of Apple Device Would Be ‘Terrible.’ 16 Years Later, Apple Seems Set to Release It

The MacBook Pro could be getting a controversial new feature.

We haven't written up this one. Inc. has the full story — the link below goes straight to it.

More in Tech

Google cleared 300 hectares of Finnish forest for a data center, and regulators want answers

Google was apparently so eager to build its new data center infrastructure in Finland that it began bulldozing large swaths of forest before the required environmental review of the full plan was…

2h ago ·techspot.com

GitHub Slams the Brakes on Private Vulnerability Reports

Drowning in AI-generated bug reports? GitHub has a radical answer: Stop accounts from reporting them. GitHub’s new limits on bug reports aren’t a solution to the AI bug-report flood. Anything but!

2h ago ·devops.com

Apple One subscribers in Europe hit with a price increase

Apple One subscribers face higher monthly bills in 12 European countries following another round of Apple One Family and Apple One Premier price increases.

2h ago ·appleinsider.com

The last stall in the market never sells, unless?

AI is adding a new layer to a world where software has been packaged and sold as a commodity for a long time. The old-school players have formed a complex ecosystem with deep distribution networks and…

Last market stall never sells unless idea is uncloneable
Author's free resume builder faces saturated market
Google refuses to index site, limiting reach

2h ago ·dev.to

Node.js API Approach for Moderating Uploaded Images, User Captions, and Compression Gates

Short answer: put byte validation and one review-sized derivative before publication, then defer the full compression matrix until approval.

Node.js API enforces explicit moderation workflow with state transitions
API validates uploads via durable object address, idempotency key, and decoded bytes
Review path simplifies by treating missing derivatives as build state

2h ago ·dev.to

6 Practical Ways to Fix Flaky Tests in Your CI Pipeline

A flaky test passes sometimes and fails sometimes, with no change to the code. One flaky test is an annoyance. Twenty of them destroy trust in your pipeline: developers start clicking "re-run" by…

Identify flaky tests by running suite multiple times and tracking results
Replace fixed sleep with explicit waits for user interface/API interactions
Ensure tests are independent by creating isolated data and cleanup after each test

2h ago ·dev.to