(A couple of decades ago I worked for a company that was a tenant at a datacenter that used these instead of batteries; it's not new or particularly exotic technology.)
(As an aside, the linked blog series is great, but if you're interested in new Go features, I've found it really helpful to also subscribe to https://go.dev/issue/33502 to get the weekly proposal updates straight from the source. Reading the debates on some of these proposals provides a huge level of insight into the evolution of Go.)
I have to wonder if we need, say, a special "secret data" type (or modifier) that has the semantics of both crypto/subtle and runtime/secret. That is to say, comparison operators are always constant-time, functions holding the data zero it out immediately, GC immediately zeroes and deallocs secret heap allocations, etc.
I mean, if you're worried about ensuring data gets zeroed out, you probably also don't want to leak it via side channels, either.
I recently logged onto LinkedIn for the first time in a while, and found an old job posting from when I was hiring at a startup ~2 decades ago. It's amazing how much it sounds like LLM output—I would have absolutely flagged it as AI-generated if I saw it today.
My first car (hand-me-down from my Dad) was a 1980s Datsun, that I managed to total within a few weeks of getting my license, much to the consternation of my younger brother and sister who expected it to eventually be handed down to them as well.
I also totalled my first Nissan. I'm sorry everyone, that was 100% my bad. I'm glad Nissan made a lot of them.
That car had the digital "Heads Up Display" on the windscreen that a lot of modern cars are getting back now. I wonder why it fell out of fashion for three decades?
I daily-drove a 1981 280ZX Turbo for three glorious, infuriating years. The L28ET would boost like a freight train one minute and then randomly cut out because the AFM flap got sticky or the injector harness decided it was allergic to moisture. Fuel pump relay? Shot. Turbo coolant lines? Weeping. ECU temp sensor? Lies constantly. Every single ground in the engine bay needed cleaning twice a year or it would just die at traffic lights for fun. But man, when it ran (which was most of the time) that long hood, perfect 50/50 weight, and the way the turbo spooled with that glorious whistle made every commute feel like a low-budget 80s action movie chase scene. It leaked, it overheated, it ate alternators, and I still miss it every single day. Cars were allowed to have personality back then, even if that personality was “occasionally tries to strand you on the motorway lol
If you're in the U.S., you might check if your local fire department has a CERT[0] training course. (I did it many years ago in San Francisco; they call it NERT for some reason.)
It'll give you a chance to practice putting out an actual fire, refresh first aid skills, learn the incident command system, learn basic search and rescue, and other preparedness skills to help yourself, your family, and neighbors in an emergency (in that order).
The first step in filing a libel lawsuit is demanding a retraction from the publisher. I would imagine Google's lawyers respond pretty quickly to those, which is why SafeBrowsing hasn't been similarly challenged.
I had this same problem with my self-hosted Home Assistant deployment, where Google marked the entire domain as phishing because it contains a login page that looks like other self-hosted Home Assistant deployments.
Fortunately, I expose it to the internet on its own domain despite running through the same reverse proxy as other projects. It would have sucked if this had happened to a domain used for anything else, since the appeal process is completely opaque.
My work laptop is Windows, and the only native applications I run on it are a web browser, Zoom, and the company's VPN software. Everything else runs inside WSL.
I greatly prefer Debian to Homebrew, so if I can't run actual Linux, this is (to me) superior to trying to develop on a Mac.
I agree that Debian beats Homebrew. But wouldn’t a persistent Debian container on Mac be better? WSL is nothing more than a container on the system, no?
The Mac hardware is vastly superior to most Windows laptops, especially enterprise Windows laptops.
> The Mac hardware is vastly superior to most Windows laptops, especially enterprise Windows laptops.
Man alive, what you mean is normie "Apple-style" Windows laptops with a bit of an "enterprise" makeover. Mobile enterprise workhorses (e. g. Panasonic, Getac)? Apple has no hardware in this segment. Detachables with extended five-year warranties plus certified dual-OS support? Nothing. Some of you fruit afficionados need to get out more.
With Windows 11, WSL has X and Wayland support, so you can run graphical applications as if they're native (e.g. share the same cut-and-paste buffer, switch between windows using alt+tab, and so on). It's also much easier to attach USB devices like Yubikeys to an already-running container than the last time I tried to do the same with Parallels. (That was quite a few years ago, so maybe it's gotten better.) You can also launch Windows applications from Linux, which is makes it trivial to control my (Windows-native) browser from within WSL.
I strongly disagree about Mac hardware vs. Thinkpads or Framework, but to each their own.
Related: Go is looking to add SIMD intrinsics, which should provide a more elegant way to use SIMD instructions from Go code: https://go.dev/issue/73787
reply