Aus stock was cheap a couple of weeks ago, it's caught up though. I'd snatch it up if you need it.

> Upgrading gets harder the longer you put it off.

This is only true if you install dependencies that break backwards compatibility.

Personally, I avoid this as much as possible.

They'll use AI to do it and it will be no better than what we have today. You will pay for it anyway.

So don't say 100%? Not hard.

Human speech is not mathematical formalism. What would even "open-source" mean in case of hardware, is there a consensus on it to begin with? Is it only 'every firmware is open-source and available', or would you want the whole floorplan of the chip?

So given that the word doesn't really apply to hardware, I believe they used it correctly (100% means the set of things where it makes sense to be used) and are not misleading. In fact I strongly dislike some of the "open-hardware" marketing of some previously mentioned devices, when that is obviously false and misleading.

"Not needing binary blobs" would be a start, wouldn't it?

I don't know, depends on a lot of stuff. If you are interested in this property from a security perspective, then no -- it's trivial to have hardware backdoors without any binary blobs.

This likely would also mean that it can't be flashed, so if you care about future maintainability, this is also a negative -- it can not be updated/fixed in the future, which may or may not make sense depending on what part we are talking about.

But if there are some kind of signature validation then it gets even more complicated (like e.g. iphone screens knowing if they are from apple or not).

> I don't know, depends on a lot of stuff. If you are interested in this property from a security perspective, then no -- it's trivial to have hardware backdoors without any binary blobs.

This is a "necessary but not sufficient" thing.

This is why I don't use dependencies that break backwards compatibility.

If you break my code I'm not wasting time fixing what you broke, I'm fixing the root cause of the bug: finding your replacement.

A list please

Just putting out that statement is kind of “ok and now”?

Precisely this. Lots of superior options. (I say this as someone who has AirPods but didn’t know any better.)

Which ones do you prefer?

Both the Bose and Sony offerings are, in my opinion, better sound quality and better noise cancellation than AirPods.

Many people are gifted a pair.

> much better

Citation needed

I want it. They just need to figure out the ux. Chat ain't it. I'd love voice chat to access the web.

Opting not to over engineer the solution with abstractions nobody asked for until you came along is the definition of best practice. something not being designed for any and all use cases doesn't make something bad practice. Reading and writing from a filesystem you always expect to available is more than reasonable. Modular code for the sake of modularity is a recipe for fizz buzz enterprise edition.

> along is the definition of best practice

Not disagreeing or agreeing, but "best practice" is probably one of the concepts together with "clean code", that has as many definitions as there are programmers.

Most of the time, it depends, on context, on what else is going on in life, where the priorities lie and so on. Don't think anyone can claim for others what is or isn't "best practice" because we simply don't have enough context to know what they're basing their decisions on nor what they plan for the future.

Slow news day? The economy is about to fall off a cliff.

Unless you’re heavy weighted in stocks.

All time highs!

When you sail into a maelstrom, the boat will also pick up steam…

git push prod

Until you have more users than dollars that's all you need.