lime!

isn’t this basically the old F1 MGU-H system that they kept having issues with and eventually gave up on?

Edit: no, that system, confusingly, is an electric motor/generator connected to the turbocharger.

the driver is called AMDGPU PRO. it sits on top of the normal driver, and contains stuff specific to high performance compute and workstation workloads. i think it’s a requirement for properly fast ROCm but i’m not sure.

depends on whether matt mullenweg knows you exist

also i’ve only just realized why he named the company auto-matt-ic oh my god

yupyup, just send HTML over the wire. it’s fine.

the biggest speedup would probably come from using proper schemas that can be efficiently parsed. but we’ve made our bed out of ad-hoc protocols.

didn’t know donny was a forth programmer

anything that deserializes arbitrary json will put it into a hash table, right? it would definitely speed up the web.

I thought Jesus was the cross religion

ironically, if you stop doing pizza parties that’s really bad for morale, because everyone knows it’s cheap.

so it was! cool!

i will admit i’m not very well versed in rust, the only time i’ve used it was in like 2016, in an embedded context where there were hard restrictions on what could be used. no crates, no macros, no traits, no threading, and a very limited number of functions. procedural style, basically. someone else chose the wrong language and i just had to work within the system.

if the language is stable, i’m assuming the instability issues come from external crates? or are they just made up?

my take on the social media thing is that it basically amounts to creating an outside context problem. gathering the opinions of us plebs doesn’t really matter because the kernel isn’t developed by the masses, no matter what ESR thinks. the project is headed by Linus (and his “generals”) and what they say goes. so riling up a bunch of nobodies that aren’t fully aware of all the requirements there are on the kernel will amount to brigading no matter how well-meaning the mob is.

the LKML exists and is public specifically because they don’t want to deal with fielding questions from people on social media. they want to field questions from people who care enough to read it.

actually, they did try using social media for a while. unfortunately they chose google plus.

the linux kernel is over 30 million lines of code. it may not be there forever, but good luck phasing it out in a lifetime.

it’s a different technology and paradigm that the old guard would have to take considerable time to learn to be as productive as they are in C. it requires a different way of thinking about systems.

basically the rust-in-kernel-gang includes none of the “main” kernel team because they are busy building the kernel. this is an experiment to see if a second programming language can be successfully integrated into the kernel at all. if they try to force their way in, that’s going to cause problems for everyone.

it’s more niche than C, has less competency available, works very differently to C, and requires a whole new toolchain to be added to the already massive kernel compilation process. for it to be plain sailing adding it to the kernel some of the worlds’ foremost domain experts on operating systems would have to re-learn basically everything.

also since rust is just coming up on 15 years of existence without a 1.0 release, there’s no way to ensure that the code written today will be considered well-formed by the time 1.0 hits.

not really a good way to get the text out of a pdf though. then again, turns out neither is pandoc.

damn it, you’re right. should probably have checked that…

$ pandoc doc.pdf -o doc.txt

Edit: welp, pandoc can’t do that. pdftotext it is.

only time i’ve ever tried it was in a duolith consisting of over half a million lines of python, all of them critical.

it’s called the strangler pattern, where the new version is layered on top of the old and gradually replaces it.

it usually doesn’t work.

i’m still not entirely sold on them but since i’m currently using one that the company subscribes to i can give a quick opinion:

i had an idea for a code snippet that could save be some headache (a mock for primitives in lua, to be specific) but i foresaw some issues with commutativity (aka how to make sure that a + b == b + a). so i asked about this, and the llm created some boilerplate to test this code. i’ve been chatting with it for about half an hour and testing the code it produces, and had it expand the idea to all possible metamethods available on primitive types, together with about 50 test cases with descriptive assertions. i’ve now run into an issue where the __eq metamethod isn’t firing correctly when one of the operands is a primitive rather than a mock, and after having the llm link me to the relevant part of the docs, that seems to be a feature of the language rather than a bug.

so in 30 minutes i’ve gone from a loose idea to a well-documented proof-of-concept to a roadblock that can’t really be overcome. complete exploration and feasibility study, fully tested, in less than an hour.