fjksksvdjsjd

Didn’t apple just ADD support for external, discrete GPUs? It’s certainly disheartening to see them drop support; I understand the latency demands, but the platform tie in is unnecessary.

At least there’s linux! :)

Hopeful, eh?

Well, that’s an argument they should have made! I think it’s extremely charitable to assume this is why, though, when every indication points to code-audit fearmongering.

But, you’re also forgetting that these virus scanners can also be vulnerabilities and exploits in themselves; i seem to remember one virus exploited a flaw in the compression code of a virus scanner to establish some type of malware. Just because something is a trade secret doesn’t exactly lessen the risk of it existing.

It is for many cases of computation! I can do my bill paying, writing, and much of my coding work from a raspberry pi; for those things, it’s a suitable replacement. These days you can get an entire phone that outputs to your tv that is hackable, cheap, and has access to relatively quality proprietary software.

And yea, a DVD is in the dame league, but it’s a format that deteriorates with age. Not exactly an investment format like vinyl. At least you can back up MP3s and play them with any software you like.

But, it’s really not that terrible. Intel has plenty of competition; if you just need “a computer” you can get a rpi for $25.

Realistically there’s no way to buy digital video without also fucking yourself into a walled garden that restricts your use of your own licensed content. There is no real competition there for the experience people want—video they can play on whatever they want to, whenever.

Anti competitive or not, it’s terrible for consumers.

Or inbox/gmail. All mailto links are hardwired to the shitty built-in imap client.

Yikes, that killed my interest with a bullet. Do people only game with it?

I haven’t played too much with VSTs beyond a proof of concept for logic tools. However I have been doing plenty of realtime processing! It’s great: it integrates seamlessly with the C ABI—I wrote my own core audio binding (though there is already on on crates) to get to know the API, and I was far more restricted by the poor documentation than the FFI itself.

But, rust has everything you need: find-grained control over memory and ownership, inline assembly and intrinsics (I haven’t attempted autovectorization yet), bindings to common audio formats, and excellent parallelization. The datastructures are extremely expressive, especially if you come from a C background; so far I really just want better VLA support, which is mostly annoying to work around (you have to manually poke the values into memory at the correct offset in an unsafe block).

I did find that tokio-rs wasn’t suitable as I had hoped for realtime work with an async/future api and fell back onto ringbufs locked with mutexes. The good news is you can wrap that in futures itself and have a great async api that does its work eith shared memory, minimizing the viable races.

Rust will definitely be a player in the audio workstation world; right now you’ll be implementing the bindings yourself, but you can go out and write plugins today so long as the ABI is C.

It’s good.

Net/http is still less mature, but this an absolutey massive golang ecosystem. You can certainly write http clients and servers today.

Unicode, string processing, regex—all of these have performant, stable implementations, either in std or in crates. Recently i’ve been doing audio processing in rust; the code there is at least as good as the equivalent in go. Overall I’d say I haven’t had issues finding a package for something in a couple years, though the quality varies from “has a full support community” to “DIY if you need something”.

However, rust really shines with datastructures. Heap? Btree? Doubly linked lists? It’s all high quality, performant, and type-safe code (though the internals are unsafe as hell), which was my major pain point in go. Doing anything with a typed datastructure feels a lot like copy/paste coding in go, though apparently templates formalize this.