perbu

fwiw; I've prototyped some USB gadgets using Raspberry Pi Zeroes and Composite USB in the Linux Kernel. At least storage and serial devices were pretty easy to get going.

You'll need something like a shell script on the Raspberry to initialize the composite kernel module and you'll find the boildplate in the kernel docs.

You can do that today with the closed source wifi driver. This is not something limited by the wifi performance.

Note that neither the framerate not resolution would be something to write home about. We're talking abot an aging MCU here.

Most generative AI will struggle when given a task that requires something more less exact. They're probably pretty good at making something "chessish".

I have this 300 line Go application which manages git tags for me. I asked it to implement a -dry-run function. It failed twice. First time it just mangled the file. Second time it just made code that didn't do anything.

I asked it to rename a global variable. It broke the application and failed to understand scoping rules.

Perhaps it is bad luck, or perhaps my Go code is weird, but I don't understand how y'all wanna trust this.

I worked on unikernels for a number of years and this (serverless functions) was our long-term use-case we worked against.

What made me stop believing in this was WASM/WASI. When it matures it will have similar performance, far better start-up times (microseconds) and a superior transport in/out of the application - WASI is a lot more convenient compared to serial ports and ethernet, which are how a unikernel normally talks to the world.

I still think unikernels are a good idea, but, imo, serverless functions isn't a valid use-case anymore.

Gross negligence and willfull misconduct cannot be waved away like this, in certain legislations, at least.

I'm wondering if it be better if an iota would assign random, unique numbers at compile time, just to make it clear that these are not entirely safe identifiers inbetween compilations.

*citation needed.

That is a really good question.

Instead of freeing it you can just keep zero it out and keep it. That way you don't have to allocate memory for the next HTTP request. IIRC this was how Varnish managed the per thread worker memory.

There is also the issue where you have a pointer in the arena pointing to something on the heap. The GC will gladly kill the object on the heap as it has no idea something is still pointing to it.

Why don't you point them out, please. We already know about testcontainers not using the shell, but rather talking to the HTTP API.

Making comments like "this is wrong, but I'm not gonna explain why" has no place here, imho.

fwiw, Simula67 had coroutines. Not the first to do so, but IIRC it was the first major language to do so.

I assume you mean main() and not main.go.

main() is the only place where you can't return an error. In order to keep as much of the code as idiomatic as possible you just call something like run() where you can do so.

In addition there is the testing aspect. You can't invoke main() from your tests.

I've started doing the same but with oapigen; github.com/deepmap/oapi-codegen

I thougt it would be boring writing the spec, but it was not nearly as bad as I thought. Also, a spec is needed, so might as well write it up front.

A tiny insignificant part which owns the commerical part.

Most outlets should let you draw 10A without issue, unless the electrical system is from the 70s or earlier.

Fwiw; Europe did standardize on 230V back in 1992. 220V hasn't been used in a generation or so.

The chip itself is fine.

If you have the wrong board it will be bad. You need to pay attention to the power supply on the board.

I've got a weather display (epaper, refreshes every hour) that I need to charge every 18 months or so. If you find the right board they're pretty much perfect.

yes. I ran ssh clients on the Original Palm pilots in the late 90s. This was way before ssh v2, which increased complexity a fair bit, but the processor here should be more than powerful enough for ssh.

Likely it isn’t criminal code, so the legal process is typically very slow.

It still sounds like future.

According to this researched I heard an interview with about 15-20% of the population has some level of intolerance for histamines. Having high histamine levels affect sleep.

I find it interesting that it is never addressed in these common list of what to try to improve sleep. It's not rocket science managing it, just a matter of avoiding high histamine food after 5pm or so. Good sleep might be worth it.

This is very typical. If you know a lot of about anxiety, you'll have an anxiety bias and will try to explain everything as anxiety. Psychologists will also perceive LC to be psychological. Immunologists tend to think it is immune related, gastrologs think it is gut-related, etc.

Out of all these it's quite simple to dismiss the psychological explanations of LC. There are obvious physical changes found in various tissue and blood in LC patients. Changes that we can be reasonably certain aren't caused by mental issues.

The video is still compressed, but the colors are RAW. Sort of.

It's also quite fast.

I remember we had a similar use-case. This was for collecting live statistics from a sizable Varnish Cache cluster. We wrote a in memory database to store the data. It's been chugging away for about 10 years now and last I heard the zmq traffic alone was about 3Gbps with zero issues.

As a long term MySQL user I think getting acquired by Oracle pretty good for the product. The old, hard issues that MySQL never had the engineering to tackle themselves finally got resolved.

If the skies are clear and the phone falls of the car it shouldn't have any problem reaching a satellite.

Copilot certainly has expanded what I feel comfortable tackling. Now, writing a simple SPA with some modern framework, is within reach for a person with very limited knowledge in JS, CSS, HTML and React.

I've got a bunch of video on a harddrive that I put in storage 20 years ago. Tried to spin it up again and it just makes funny noises.

So, yeah, spinning rust might rust.

Tape drives will, when writing, re-read the data as it is written to make sure no errors are written and will transparently correct any errors. In addition, quite a bit of error correcting code is written, making it possible to correct simple errors.

So perhaps not 100% immune, but partial immunity to bit-rot is a pretty important part of the LTO spec.