lime!

i’m saying i don’t understand the reply in the context of what i wrote. it may be a difference in terminology, but when i said “balance reactions” i was talking purely about on paper. we got a bunch of formulas and were to fill in the result like a multiplication table. i don’t know if i’ve ever had to do that in practice. labs were always just “n moles of chemical a, n moles of chemical b, observe the precipitation” over and over again. it was only years after school that i realized that precipitation occurs when a solution is saturated.

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.

my first chemistry lab (like actual chemistry, rather than as part of the “sciences” subject) involved us mixing three components we were not given the names of in a test tube, then we would go out to the school yard and while we were holding the test tubes with tongs the teacher shoved a match into each of them to show the efficacy of the black powder we had just unknowingly made. there was so much glass everywhere.

like, it was cool, but i don’t think anybody learned anything from that other than how to make black powder, which i imagine most people with a dad learn at one point or another.

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.

i don’t understand this reply.

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.

i was thinking of that as well, like surely land would still have value. don’t know if it’s ever addressed though.

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

nope, big things are built with “industrial replicators”. the only thing they can’t make is a material called latinum, which is sought after by the ferengi precisely because it’s the only scarce thing left.

also, there’s a distinction to be made between “private” and “personal” property. people still own things, but it’s for sentimental reasons. like, you wouldn’t have a toolbox or a statue or a mansion unless it was your “lucky” toolbox or “antique” statue or a “family” mansion. things only have sentimental value, not monetary value.

but you’re right in that an economy exists, because the federation still needs to do outside trade and freight. it’s just more of a bartering system.

also, people on DS9 tend to carry latinum around due to the ferengi presence. the bar in ds9 just has the same replicators that all the rooms do, but it’s like a custom to buy a drink at the bar and gamble.

i may just have had bad teachers but i to this day have no idea what chemistry at pre-university level were supposed to teach. the labs were all about watching things change, with no explanation as to why. and the theory parts were all about balancing reactions. none of it connected.

here’s a cure

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 mean they came out in 2002 and were for schools, so yes.

we had them in school in europe in like 2003.

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.