• 0 Posts
  • 16 Comments
Joined 2 months ago
cake
Cake day: June 8th, 2025

help-circle

  • Meh, burning CDs… ever had to worry whether you’d parked your hard drive’s heads before moving it, child…?

    (To be fair, neither did I, probably; my earliest hard drive was already IDE, I believe, and those seem to have already had autopark, but the old lore was that you parked your hard drives before moving them, or the heads would scratch the surface, so park them we did.)





  • They’ll never be able to learn, though.

    A LLM is merely a statistical model of its training material. Very well indexed but extremely lossy compression.

    It will always be outdated. It can never become familiar with your codebase and coding practices. And it’ll always be extremely unreliable, because it’s just a text generator without any semblance of comprehension about what the texts it generates actually mean.

    All it’ll ever be able to do is reproduce the standards as they were when its training model was captured.

    If we are to compare it to a junior developer, it’d be someone who suffered a traumatic brain injury just after leaving college, which prevents them from ever learning anything new, makes them unaware that they can’t learn, and incapable of realising when they don’t know something, makes them unable to reason or comprehend what they are saying, and causes them to suffer from verbal diarrhoea and excessive sycophancy.

    Now, such a tragically brain damaged individual might look like the ideal worker to the average CEO, but I definitely wouldn’t want them anywhere near my code.




  • DISCLAIMER: I’m just speculating, I haven’t touched c in decades and have no idea how Linux code works.

    Generic headers here could refer to headers declaring common functions whose specific implementation might differ based on CPU architecture.

    That is, the .h files would declare certain functions that other parts of the code can call to do CPU related stuff, and when compiling for a certain architecture you’d use different .c files implementing said functions for that specific architecture.

    Obviously, since these headers will be common to multiple specific implementations, it’d be very important to have a standard or at least a consensus in regards to which functions they should declare, what they should return, and which parameters they should take.

    From Linus’ quote there, I assume the Google “devs” (probably Gemini) must have included RISC-V specific stuff in the headers, which would be an extremely big no-no as it could break other implementations or the code calling these functions.





  • Yeah, maybe it’s because I learned git from the graph, but I find it really helpful when figuring out why a certain piece of code ended up looking like it does (the ability to see the changes made in every commit and open versions of the files at any point in history without checking out the commit is also very useful).

    And yeah, if you need or want the command line it always lets you open a git prompt for you to do whatever you want, which is nice.

    Also, again maybe because it’s what I’ve gotten used to, but I find the way it handles merge or rebase conflicts more useable (or rather less unusable) than any other I’ve tried…