ASP.NET could mean a bunch of programming languages and I'm assuming that a ASP.NET Server doesn't disclose that. It's probably safe to guess mostly C#, but that requires a different metric.

'Tis true. I used to know an absolute ton of big sites that were written in 100% VB.NET ASP.NET. I'd still be writing all my backend in VB.NET if it wasn't a second tier .Net language these days.

Doesn't Brave disable WebBluetooth by default via a flag?

Brave indeed does block WebBluetooth by default, but it can be turned on by the user using flags.

It's by no means a new feature, but the privacy concerns outlined in this post are still valid 10 years later: https://blog.lukaszolejnik.com/w3c-web-bluetooth-api-privacy...

For me it's a bottle opener, a corkscrew and a knife that's good enough.

More picnic less camping in the wild.

STM32 MCUs are 3V3, not 5V right?

Arduino really isn't great with naming, a Uno can be an AVR or ARM based board, now either 3V3 or 5V based and also a SBC rather than just a MCU.

I think to Arduino, Uno just means 'Uno form factor, with shield pins in the same place'

Which is kind of sad, since the Uno pinout is horrible for high-speed signals

FYI the new Q has two 'high speed connectors' on the bottom side, for signals like CSI, HDMI, USB 3.1, etc.

Haven't seen any examples of bottom 'high speed' shields yet, though. They said there would be some made available.

Well, if all the interesting signals are on the mezzanine, what's the point of the Arduino form factor and pinout? Just to claim that they're supporting a widely used platform? Engineers can see through it.

The more I look at it, the more it sounds like a platform designed by M&A team

Depends on the MCU, but generally STM32 is 1.7-3.6V

STM32 is 3v3 logic.

Not necessarily; see above (Or a datasheet)

Yes, but many (most?) of them are 5V-tolerant.

I'd like to argue that electric Rechauds are superior anyway. Fuel paste or gas always seems to run out just before you're finished, everything cools down while refilling and then you have to get the fluid up to temperature again. Safety around children or tipsy people is just the bonus on top.

Probably too small.

Also Switzerland is easy to bully, as can be seen by the current US tariff regime.

MAUI is supposed to use native ui components, AvaloniaUI just uses Skia. I think going with a non-native approach would kinda make Linux a clear second class platform, especially with all the native features that need to be rebuilt?

Is there any multiplatform ui framework that's actually "native" for all the different linux ui toolkits?

.NET LTS is on a 2-year cycle, isn't it?

I've worked in .NET shops with very niche WPF/WinForms applications where customers were years behind with our software/major .NET Framework releases.

I don't think it's a technical challenge, more a cultural one.

A shift in those cultural dynamics is that you can ship the current .NET LTS with your app (or even STS if you feel like making that sort of security support SLA with your own clients). You aren't relying on their Windows Update habits (or lack of them) or having to install a big .NET installer that might break their other apps.

They may still get left behind on an older version of your software because they want to be, but their relationship to Windows is no longer the big excuse/reason to skip updating to your latest that it used to be.

You are right that it’s on a 2 year cycle. Though there is support for 3 years, so you could safely put off an upgrade for up to a year if there are breaking changes one release.

I don't think that's a fair summary of Mozillas Position on the WebBluetooth/WebSerial/WebUSB specs. Interacting with arbitary devices has arbitrary consequences, mozilla seems to assume users are not able to understand these consequences and therefore cannot consent to it.

No improvment to the spec can fix users.

I've done the same thing for a few reasons.

- Certain things need good layouts - I think I can see a DC-DC Converter, you need to minimize certain loop areas, etc. You also need to ensure that you use the correct footprints for the chips. Way easier to just use a bunch of modules with a simple pcb.

- It reduces the components you need to aquire - you need to select a inductor with the correct specs for the dc-dc converter, a bunch of different resistors and capacitors for all sorts of uses or you just purchase a cheap module from china.

- It's easier to solder. Fancy chips with packages with no leads are not trivial to solder. LED's might be a bit sensitive to temperature and can get destroyed by a not-so-great solderer. Small pitches on IC make it easy to create solder bridges or bad connections.