I have a 1.5GHz TDS7154B in addition to my 200MHz SDS1204 specifically to measure power rail noise with a low noise probe.

You just can’t characterise power rail noise well with less than 500MHz of bandwidth.

I recently did something similar with a TDS7154B. Rather than going with an IDE/PATA drive I was able to use the SATA Gen1 ports on the motherboard and a molex-sata power adapter to use a modern SSD.

Using SATA gen 1 would be ideal, but the TDS7104 motherboard is old enough not to have that: it doesn't support booting from a USB stick.

The government loan changes the calculus. Allows for short term thinking and a long term benefit.

It feels like LEGO for a while have been dumbing-down their education products.

I saw it with computer science education as a whole during my schooling. Instead of focusing on fundamentals there was more and more layers of abstraction added, lying to you about what you were actually learning.

There is also another competitive event that will be affected by this: RoboCup Junior.

This competition was my first experience with programming, but from what I can see RoboCup Junior is still thriving - just with different products controlling the robots now.

LEGO are fundamentally toy company. You cant really compare it to a school.

You buy the physical rack and install it in your data centre. It is your property.

So you are telling me that the cloud is not actually made of water-vapor?

$1k per year if you run an action 24/7. How many minutes per month do you actually use? How does that compare to the cost of the machines being used as runners?

The real mistake was GH not charging anything for self-hosted runners in the first place, setting an expectation.

Is there a technical reason it only supports x86_64, riscv64, and not arm64?

There were a bunch of ports, like arm64, but with several bugs. So the maintainer removed all but x86_64, and then another group added risc64. From there arm64 can be tried again

XML? how is this not just XML with a schema?

Does XML allow you to define for-loops inside <bracketed> items then reference the loop variables inside {{template vars}}? https://youtu.be/b9WDcFsKixo?t=223

I guess it doesn't prevent you from doing such things, but... well... there's some eyebrow-raising shoehorning in this one.

Yes it does. Apache ant did that... many many years ago.

Creating a new language that looks like XML but is not XML is... kind of unforgivable. I'd go as far and call it amateur-like. We already have good configuration languages (such as dhall-lang) and when more power is needed, then just use a real language and provide a DSL inside of it.

It's from Microsoft. They always cook up their own incompatible shit instead of using existing standards.

Maybe it's not fully XML compliant.

Anyway quite an interesting project, XML's a better fit for "programmable" data.

It has self-closing tags, which you can see in the repo screenshot, so you're correct.

But why... standards are good, eveyone should have one, I guess.

XML, for those born after 1990, you could have well said COBOL or FORTRAN, something gramps used to mention.

Yes, but you aren't wasting time early on negotiating compensation.

Have a look at Ethercat. Based on the same physical layer as Ethernet but allows daisy-chaining devices.

Similarly, PROFINET, the confusingly named EtherNet/IP (IP here stands for Industrial Protocol not Internet Protocol), POWERLINK, and others - all based on Ethernet but with a custom protocol layer replacing IP. "We need something that is high speed but also supports rapid deterministic communication" is pretty much a solved problem in the industrial space.

I wonder what Tesla's game is here: is it really just reinventing the wheel, or are they perhaps using higher speed Ethernet as industrial Ethernet tends to still be limited to 100Mbit? Or perhaps it's tightly linked with the proposal to communicate over 48V lines?

Industrial Ethernet uses 100Mb speeds because (and when) those are sufficient for their use cases. There is no technical limitation there. 1000base-T1 (and even 2.5, 5 & 10G SPE¹) show where this is going.

¹ Single Pair Ethernet

Huh, I didn't know single pair ethernet went up that fast - neat! We're still living in the 100Mbit world at my company - and, yeah, it's fast enough for pretty much everything we need.