15,015 karma · joined April 15, 2013
twitter: @jcdickinson element: @jonathan:dickinson.id email: similar to element
While PC likely has the most exclusives by a ridiculously large margin, it probably has the fewest AAA exclusives.
NVIDIA, Intel, AMD, and OpenAI are all already engaging in this type of behavior.
> Just install
Not on Debian? Have fun with that. You'll also need the Azure SDK. And what about openssl-dev? Oh no, you installed dotnet on Windows instead of within WSL? Start again.
No, you don't "just install" the SDK. There is a lot that the IDEs set up for you.
> Local nuget.config
I don't see how adding a nuget config improves anything. You have completely omitted what you place inside of it to make it build and use a local clone of the package source.
Look at all this nonsense that people have resorted to: https://stackoverflow.com/questions/32482746/how-to-temporar...
I personally won't be using it, given the choice, again. I don't like exceptions, but can live with them. I don't like null, but can live with it. Nuget is complete and utter garbage. You still have to resort to all forms of unreliable hacks in order to redirect it to a locally clone (and if you do use a feed to avoid that, good luck with getting the local cache to not be completely moronic).
(Look, it certainly didn't help that the project itself was heavily enterprisey because the developers hadn't kicked those habits)
Then there is the series bits x R resistors. The output of each 2R resistor is connected in-between the two resistors that straddle its bit position. So:
Out
|
R
+-2R-bit0
R
+-2R-bit1
...
R
+-2R-bitN
And that's it (apart from pull-up/down resistors)! Due to the way that resistors in series and parallel work, each input step in the ladder provides twice the voltage of the previous if powered: it's base 2 enshrined in a physical object.These are relatively uncommon because they are highly sensitive to the resistor (and trace) tolerance, but this circuit is my Euler's identity of electronics: it very literally bridges the digital and analog worlds.
> Oh Christ. Is somebody seriously working on BE support in 2025?
Followed by Eric:
> And as someone who works on optimized crypto and CRC code, the arm64 big endian kernel support has always been really problematic. It's rarely tested, and code that produces incorrect outputs on arm64 big endian regularly gets committed and released. It sometimes gets fixed, but not always; currently the arm64 SM3 and SM4 code produces incorrect outputs on big endian in mainline
BE support is unambiguously best-effort (which is none in some cases).
No, the Kernel does not take BE seriously. Not sure why I have to quote from the mailing list when the URL was a significant portion of my comment text - it directly contradicts your assertion on multiple fronts.
As for the grand parent comment, yeah, I guess the UI situation sucks - but I did everything through home-manager anyway.
[1]: https://lore.kernel.org/lkml/CAHk-%3DwgYcOiFvsJzFb%2BHfB4n6W...
Furthermore, with modern MBAs at the helm, the concern is only pumping figures for the next quarter - five years be damned.
It's also completely possible to do agile with QA. One place I worked had 1 QA per 3 devs, and they were able to maintain a single (2 week) sprint behind cadence.
Scrum was always how Agile was sold to behemoths. It necessarily makes several compromises that deeply undermine it.
Zigbee's issue was that anyone could make devices and modify the protocol. Tons of devices are vendor-locked to their first-party hub. Philips attempted to do this recently with a firmware update and only backed off due to extremely bad PR.
Z-Wave has the same "problem" as Matter. You have to pay the consortium per product. Part of that what that pays for is testing, and cross-vendor compatibility is mandatory. As a consumer you are guaranteed that a Z-Wave device will work with any hub (and therefore Home Assistant/completely locally). You own Z-Wave devices.
I ran both in my old home, and used Zigbee devices where possible (Z-Wave devices are often more expensive).
I would much rather have it the way of Z-Wave and Matter. It is the lesser of two evils.
I forked out for SmartWings blinds. You can choose between either Zigbee/Matter or Z-Wave (or neither I think?). The first-party hub is completely optional (that's important to look out for with Zigbee, which can be vendor-locked). They are drastically simpler than the average motorized blinds I've seen around, so I haven't had any of the mechanical failure nightmares. Pretty happy overall; though I haven't had them for 10 years.
I do use them as a kind of alarm clock as I am absolutely horrific with mornings, so manual ones wouldn't really work out for me.
I strongly doubt the stuff is good for your skin, so I've only done this a few times.
So that excludes you from the "someone who hasn't seen/used a RSS reader" demographic mentioned in the comment you are replying to.