Does it work well as a daily driver? Would you recommend it as the best choice amidst a sea of bad (Windows) options?

It would be perfectly fine as a daily - I use it for SQL Server on-prem infra that I also RDP to for SSMS 8 hours a day.

It’s clear to me it’s the best of the worst if you need to use Windows.

I daily macOS Sequoia - you don’t want my unfiltered thoughts on Tahoe.

Sign me up for this beautiful alternate reality.

"Data processing by advertising providers including personalised advertising with profiling - Consent required for free use"

Fuck no.

https://archive.ph/MZuVl

But why? (Real question)

Easy to create different skins and behavior

> Easy to create different skins and behavior

Kids those days. Fvwm.

Which printers did they use?

Helicopter pilots have trouble with them as well.

> Both agents uncovered two novel zero-day vulnerabilities and produced exploits worth $3,694, with GPT-5 doing so at an API cost of $3,476

Its a risky PR move to have this line on the top of article. To be more realistic the cost of dev effort should be included as well

Anyone know if there's anything like this for the Dell Precision M6600?

(Or upgrade suggestions for someone who loved that laptop? Framework? Thinkpad?)

> upgrade suggestions for someone who loved that laptop?

The repair-friendly [0] StarBook and StarFighter line might interest you. They generally seem good value for money and ship worldwide. Here's a 96g DDR5 + Intel Core Ultra 7 configuration at ~$2200: https://starlabs.systems/products/starbook-ultra?variant=552...

Their funder/backer is a mystery (to me) though.

[0] https://support.starlabs.systems/what-is-the-star-labs-limit...

Seconded. Coreboot and lvfs firmware upgrades and completely repairable with inventory parts.

Get an x1 carbon gen 13 (lunar lake version) for a general usable laptop. For clunkers/workstations that use desktop style CPUs, Dell still makes them and so does Lenovo. The Lenovo version is P16 Gen 3.

i'm also curious. i used that thing until last year.

Ok, but if you distrust the library so much it needs to go in a VM, what the hell are you doing shipping it to your customers?

Once upon a time I would download the source code of a library, unzip it, and personally vet the code before adding it to my project.

With some package managers these days I don't even know how to do that (and I'm not necessarily talking about Node, specifically). How do you figure out what the install process does to your computer, without becoming an expert on the manifest syntax? For those of us who care about what goes on under the hood, it is definitely not easier than the days of following well-formed (or even semi-formed) documentation by hand.