No, it can do whatever it wants. Just don't leak resources!

Don't worry. Once IT Security discovers that they miss their trusty endpoint security products on your Mac, they'll add it and you'll be in the same ballpark as the Windows machine. Been there, received that, and learnt that Microsoft Defender exists for macOS, too.

They have all the endpoint protection stuff on this machine. It just seems to run better. Or it could just be that the M5 is doing laps around the Windows workstations but I didn’t think they were that far off looking at the spec sheets. They didn’t cheap out on the Windows side.

Either way enjoying this machine.

That's why you gotta have your work laptop, and your "work" laptop. Give them something to secure. It makes them feel important.

Gosh, the last sentence is the most terrifying thing I’ve read today.

"USB data blocker" on AliExpress yields you very small adapters that enable you to run USB-PD, but block the data lines.

I tried to read this, and what the tool works, but this is so much text with little context. Looks like AI fluff. It sounds pretty straight-forward, so this should be a single page with a few paragraphs only.

Interfaces are persistent in Windows, that's why they get assigned such silly names as "LAN interface (42)".

If the mapping between the logical and physical interfaces changes, that probably means that your NICs lack proper IDs to differentiate them or the bus topology is somehow not stably sorted. I wouldn't blame the OS for this.

Don't want to go too far off topic; but the interface in question was a uniquely named internal network interface for a Hyper-V VM. Considering it's MS all the way down, I'd expect them to get it right.

The trick about documentation is depth, not prose. You need context and understanding to write documentation "like in the old days". No amount of LLM trickery will free you from that. Once you have that source material, it's easy to re-shape it into an 80's/90's/00's doc format.

Negative example: I was looking into the German manual of my Canon EOS R5 II, and it is just fluff. Hundreds of pages, full of white space, telling me about features without actually explaining what they mean. Awful automatic translations. Their manuals used to be good (looking at my EOS 6D). But these days: oh boy.

My tooth brusher: Take the <Brand Name Product Name> and turn on <THE SUPERAWESOME MEGE POWER INNOVATIVE BEST IN THE WORLD> feature to experience <Brand Name Product Name> unique...

At that moment I felt sorry for this company, very sorry. How can you have so much disrespect for your customers? Does anyone in the physical world talk like this or do you marketing guys want to be talked to in such terms?

Brutal.

In that example they probably do view the median customer as a random peon, or not far from it…

And unless you are above the 99th percentile of the customerbase… that’d probably be a correct guess?

Heck they could directly write “You Peons!” and still probably retain most of their customer base… if the price to performance ratio was sufficiently better than the next best competitor.

Most people care so little about the refinement of anything else nowadays.

I doubt you have to be above 100 IQ to roll your eyes at obvious bullshit.

IQ isn’t the differentiator, more like willingness to swallow BS and pull out the wallet anyways.

Author here. Another trick, I would argue, is consistency, hence the focus on style.

I also wrote on what I think makes docs beautiful, by the way! https://passo.uno/what-makes-docs-beautiful/

That is canon for ya, should have used INSERT_OTHER_MANUFACTURER_HERE$ /s

But if you look how much manuals get ignored by the customer, it doesn’t make sense to put work into them.

It is much better to let a YouTuber do it, by lending them the product and throw small amount of money against them.

Manuals are just there for legal or certifications requirements these days.

Yet they keep getting larger and less useful. It’s a matter of writing quality more than effort.

When was the last time you met a good technical writer? It’s a vanishing profession.

I dunno, depends on the subject/topic it seems to me. Most of the musical gear I buy nowadays come with manuals that are hundreds of pages long, including schematics, when to use what, tips and tricks, why things are the way they are and more. Even simple instruments like an analog mono bass comes with well-written schematics and lots of explanations. Even the manual for my mixer is 36 pages long, even though almost everything is self-explanatory, and besides that, it even has jokes and stuff in it too!

It's sad to see Xtensa go. Their architecture was a clean design, a treat to read the assembly code. I get it, RISC-V comes without licensing costs, but that's one of the few positive things about it. For a fresh start, it is just already in this "we pile stuff on stuff on stuff" state that you expect of an architecture after 10-20 years of productive use.

The inevitable result of Risc-v trying to be everything to everyone, so everything is half-baked.

Well, salt may be less volume than brine. But the demand for table salt is pretty limited. Thus: Why pay for its disposal when you can discharge brine for free?

Great! Brings a bit more dynamic into the market. So far, I'm happy with DxO, but I also don't need to manage a library.

I don't know, does Resolve have lens corrections for 100+ lenses built-in? That's the thing that DxO does really well: Lens corrections, matching your camera's color rendering, denoising. Unfortunately, they still struggle with HDR output.

I imagine the tools in Resolve save you much time, due to automation. Probably handy if you shoot a lot. Yet, the biggest difference is that in photography, you're not necessarily limited by throughput. You can and do actually put a lot of effort into single images.