Skip Navigation

Posts
11
Comments
937
Joined
3 yr. ago

  • and that's a different problem entirely

  • It really isn't. A line by line translation doesn't introduce new logic and doesn't change the system architecture. Saying it carries the same tech debt as brand new code is just not true.

  • was the study funded by Chobani?

  • you can't compare the tech debt because it's essentially a line by line translation from an existing codebase, not 1M brand new lines of code

  • the faster you burn them the sooner you burnout

  • yes, but when you make a port from one language to another, usually you want to rewrite it as a translation first, then refactor later with the features that language provides. A port that refactors everything in the first release is too risky.

    The fact the translation has unsafe blocks only demonstrates the Zig version is not really safe as per Rust standards.

  • do you replicate your CI environment locally with something like act (for GitHub Actions)

    this is what does it for me most times; but I usually also have a CI .env file act can use and use just to abstract recipes e.g. when running just test, either CI or local will run depending if the CI env var is set. It's the same battery of tests, only different env files.

  • Zig is not as strict as Rust for memory management

  • for anyone like me who could not understand that stupid title

    "Call a spade a spade" is a figurative expression. It refers to calling something "as it is"[1]—that is, by its right or proper name, without "beating about the bush", but rather speaking truthfully, frankly, and directly about a topic;

    "Blow smoke" - to speak idly, misleadingly, or boastfully

  • Fwiw it works on the desktop's alexandrite ui and on the thunder app

  • that crushed ear lobe lol

  • that's still massive, an animated webm will probably be more useful

  • I can't wait for the day they decide to build a hyperspatial express highway through our star system

  • that's bad, we'll get a pretty bad reputation around the milky way

  • There's plenty of busy work that requires some level of "thinking" but it doesn't add anything to whoever is doing it for the 50th time. You're the one sounding like an idiot for ignoring this.

  • Right, like I mentioned, it's a scale problem and how people feel about generated code. Abandonware have always been the majority of repos, because people don't have time or interest to maintain most things they create. We just have more things being created now (whether they're any good/usable or not).

  • Disagree. Most projects are never "done". Whether that is defined by the user or by the users, there are nearly always things to work on. Maintainers just lose interest or don't bother. This is as old as open source and it has nothing to do with LLMs, it's only aggravated by it.

  • Hardly an issue with generated code. You could say the same about projects before LLMs were widely used for code generation: "most projects are abandoned within months of release". The difference now is the scale and how some people feel about it.

  • du* - applogies hehe