IIRC, it’s still 100% privately held by the founders, who have no intention of selling up.
IIRC, it’s still 100% privately held by the founders, who have no intention of selling up.
Another recommendation for Mullvad. Solid privacy options and no marketing snake oil
I wonder what the proportion of bots to actual gamergate incel chuds who idolise Musk was.
4chan poster starter kit
I imagine the hate-clicks from GenXers and retro-game enthusiasts do wonders for Laughing Boy’s engagement
That looks like an Iain Banks non-sci-fi book jacket
That doesn’t sound like an unreasonable price for a missile interceptor; those things have to be fast and precise. If anything, it looks like they have reasonable economies of scale going for them.
There’s always a reason
The Latin name of the species is “phoca”, IIRC
Both of these services appear to be dependent on BlueSky. I.e., if BlueSky ceased existing, or cut them off from its API, they’d die.
One could theoretically make one’s own independent AT Protocol network, but not in a way that interoperates with BlueSky as a peer. You’re either a subsidiary part of its network or you don’t exist as far as it’s concerned, which is a much poorer value proposition than ActivityPub and related protocols.
No, because the AT Protocol is not designed for interoperability, but rather for entrenching the silo owned by the main node (BlueSky) whilst giving the illusion of being decentralised. It’s to decentralised social media what Microsoft’s OOXML file format (tl;dr: a memory dump of Microsoft Word’s internal data structures encoded in XML, and useless to anything that’s not Microsoft Word or a very precise emulation thereof) is to open document formats.
There’s also China, i.e. the Great Wall and some high-tech megacities, because the studios want a chance at that billion-viewer market.
Maybe the bad guys will also blow up Big Ben or the Eiffel Tower if the Europeans are lucky.
Oddly enough, they don’t seem to sell this in the EU or UK (though some Asian groceries near universities have a mix in similarly coloured packaging made for the Chinese market by House’s PRC subsidiary), though they sell other House and S&B curry mixes. I wonder if Vermont Curry might contain an ingredient that’s banned in the EU or something.
It’s possible though less than ideal. Drivers that connect to devices are part of the attack surface, and probably the part you’d least want implemented in C when the rest of the kernel is in Rust.
There’s a Pareto effect when it comes to them, in that you can cover a large proportion of use cases with a small amount of work, but the more special cases consume proportionately more effort. For a MVP, you could restrict support to standard USB and SATA devices, and get a device you can run headless, tethered to the network through a USB Ethernet adapter. For desktop support, you’d need to add video display support, and support for the wired/wireless networking capabilities of common chipsets would be useful. And assuming that you’re aiming only for current hardware (i.e. Intel/AMD boards and ARM/RISC-V SOCs), there are a lot of legacy drivers in Linux that you don’t need to bring along, from floppy drives to the framebuffers of old UNIX workstations. (I mean, if a hobbyist wants to get the kernel running on their vintage Sun SPARCstation, they can do so, but it won’t be a mainstream feature. A new Linux-compatible kernel can leave a lot of legacy devices behind and still be useful.)
Probably a reeducation-through-labour camp
Drew DeVault recently wrote a simple but functional UNIX kernel in a new systems programming language named Hare in about a month, which suggests that doing something similar in Rust would be equally feasible. One or two motivated individuals could get something up which is semi-useful (runs on a common x86 PC, has a console, a filesystem, functional if not necessarily high-performance scheduling and enough of the POSIX API to compile userspace programs for), upon which, what remained would be a lot of finishing work (device drivers, networking, and such), though not all of it necessary for all users. Doing this and keeping the goal of making it a drop-in replacement for the Linux kernel (as in, you can have both and select the one you boot into in your GRUB menu; eventually the new one will do enough well enough to replace Linux) sounds entirely feasible, and a new kernel codebase, implemented in a more structured, safer language sounds like it could deliver a good value proposition over the incumbent.
It’s not implausible that, among the enzymes in cat saliva, there are some which evolved to maintain the condition of the cat’s coat.
30 years on, that guy still had all those gadgets dangling from his belt, but now he’s the crazy old guy who lives in the junkyard