• 1 Post
  • 297 Comments
Joined 6 months ago
cake
Cake day: August 21st, 2024

help-circle






  • 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.




  • 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’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.


  • his take on the petition was uneducated and seemed to stem mostly from a pro-industry perspective. it was like he misunderstood how government petitions in europe works and based all his criticism on that misunderstanding.

    basically the point he missed is that these petitions don’t become laws as written, but are put up for discussion. highlighting a problem in a niche where it is easy to understand usually ends up highlighting a broader issue.

    Thor took this flawed understanding and applied his substantial industry knowledge to it, which led him to the conclusion that games would be impossible to make if this petition won out because it would force companies to keep the servers up forever, which is not at all what the petition is about.

    he then refused to back down from this position when people tried to explain it better.