Junk_Collector

both, really.

It could, but maybe not if your motto is, "Move Fast and Break Things."

Article is short on data instead referencing a bunch of aggregated IIHS studies.

It even goes so far as to call out the ones who were interfacing with AI as disadvantaged and manipulation of the advanced AI developed for the Chinese orphans led to the creation of the mouse army who were categorically trained to worship specific people as their leader which they otherwise had never known.

Can you build a CNC machine out of nothing but a computer and a CNC machine?

If you live in Austin proper, your local library may have repair meetups as part of the Austin Fix-it program.

From what's described in the article they are using it to write the process code. That is, control code for setting the states of the SOC under test and the test equipment, then recording the data that the test equipment would measure. It can be a pain to do because each SOC and piece of test equipment might have it's own control language, drivers, different data formats, etc. This usually all has to tie back in to a local (self hosting is the norm) cloud service for quality tracking and some 3rd party enterprise software from companies like Cadence. The test equipment would be something like a Keithley Parametric wafer tester, which is actually an entire rack of equipment glued together by 3rd party code with semi-open APIs. It's not uncommon to make thousands of measurements on an SOC during verification and then process engineers work to reduce the measurement count to just the critical ones for manufacturing.

That's a Nintendo Switch. The general purpose docking OS was what Win8 was supposed to be but it was flubbed horribly.

It's worth noting that this isn't new technology. This paper is specifically about how their new technique provides a small but statistically significant improvement on existing techniques.

The fact that they provide code and dataset is really praiseworthy.

Decades ago there was a huge push to green up cities by planting trees everywhere possible. A couple of decades after that there was a huge push to remove trees because of infrastructure and safety concerns. Now a few decade later we are back to putting the trees back in. I'm always for more trees but hopefully this time it's a little more long term this time.

This is as good as when the engineer from the Claude team said they load their website in such a way as to protect against hostile actions such as scraping.

Gotta love how they moved the "Create Email/meeting" buttons in Outlook mobile and stuck the Copilot button there so that you will hit it accidentally.

We have some special cases I can't go too much into that lend themselves well to rolling our own and stripping things down as much as possible.

It's an interesting case to me. The company I work for has been shipping systems on windows since the 90's despite pretty consistent requests from customers to ship hardware on Linux. 2 years ago we started creating our own Linux distribution and this year started shipping products on it. We still ship a lot of stuff on Windows 11, but that market share is starting to shift now. 10 years from now I could see us completely moved to our Linux distro. Now, what's actually interesting is that it wasn't customer requests or efficient capital allocation that drove this. Microsoft effectively forced us to do this against our will by a combination discontinued products and handling of Windows 11 and now that we've spent the capital we won't be going back.

Yup, a lot of scopes actually did this internally and some still do. It's part of why some scopes lose half their BW when you go from 2 ports to 4 ports (some go the other direction and run multiple ports on one very fast ADC), they split the digitizers. It's just very very difficult to keep it working external to the box mainly because of line drift.

If you are an absolute nutcase, you could characterize a set of line stretchers and a multiplexer on a high end VNA then offset the inputs of the 4 channels on that UXR with them, take a capture and finally rebuild a 1TSamp/s signal out of the 4 results.

You have to have the 240V model of the scope to run all four channels at full rate (110GHz) though.