• 10 Posts
  • 890 Comments
Joined 2 years ago
cake
Cake day: January 16th, 2024

help-circle





  • EDIT:

    I’m removing the image (keeping the original text for posterity), but I just completely got had by someone straight up lying.

    It’s quite embarrasing, I should’ve been way more skeptical of someone posting an image without sourcing the original paper. Turns out not only is it not a recent paper at all (published June 2025), not only is that table not saying what he claims it’s saying, but the authors have since removed that table altogether from revised versions of the paper!

    That’s what you get from reposting someone who has “The Finance Newsletter” in his fucking username, couldn’t have gone well for me.

    original post

    From https://bsky.app/profile/thefinancenewsletter.com/post/3mek7wsqgkk26

    Microsoft released a study showing the 40 jobs most at risk by AI:

    Tag the most ridiculous entry, I am curious of your choices.

    To me it has to be fucking historians. Arriving at new conclusions by looking at available evidence and/or finding obscure references that are not well known to the public – CLASSIC THING LLMS ARE GOOD AT.













  • I wonder what actual experts in compilers think of this.

    Anthropic doesn’t pay me and I’m not going to look over their pile of garbage for free, but just looking at the structure and READMEs it looks like a reasonable submission for an advanced student in a compiler’s course: lowering to IR, SSA representation, dominators, phi elimination, some passes like strength reduction. The register allocator is very bad though, I’d expect at least something based on colouring.

    The READMEs are also really annoying to read. They are overlong and they don’t really explain what is going on in the module. There’s no high-level overview of the architecture of the compiler. A lot of it is just redundant. Like, what is this:

    Ye dude, of course it doesn’t depend on the IR, because this is before IR is constructed. Are you just pretending to know how a compiler works? Wait, right, you are, you’re a bot. The last sentence is also hilarious, my brother in christ, what, why is this in the README.

    Now this evaluation only makes sense if the compiler actually works - which it doesn’t. Looking at the filed issues there are glaring disqualifying problems (#177, #172, #171, #167, etc. etc. etc.). Like, those are not “oops, forgot something”, those are “the code responsible for this is broken”. Some of them look truly baffling, like how do you manage to get so many issues of the type “silently does something unexpected on error” when the code is IN RUST, which is explicitly designed to make those errors as hard as possible? Like I’m sorry, but the ones below? These are just “you did not even attempt to fulfill the assignment”.

    It’s also not tested, it has no integration tests (even though the README says it does), which is plain unacceptable. And the unit tests that are there fail so lol, lmao.

    It’s worse than existing industry compilers and it doesn’t offer anything interesting in terms of the implementation. If you’re introducing your own IR and passes you have to have a good enough reason to not just target LLVM. Cranelift is… not great, but they at least have interesting design choices and offer quick unoptimized compilation. This? The only reason you’d write this is you were indeed a student learning compilers, in which case it’d be a very good experience. You’d probably learn why testing is important for the rest of your life at least.