Skip Navigation

spartanatreyu

@ spartanatreyu @programming.dev

Posts
0
Comments
147
Joined
3 yr. ago

  • Codeberg had a major outage today! About 7 hours of complete down (July 31, 2026)

    Jump

  • Yes but that tracks issues of all severities and with all of GitHub’s services of which there are a great many.

    Yes. Remember there are two different main types of github users.

    1. Devs who just use github as a repo host, and maybe as an issue tracker
    2. Devs who use github for everything. Repo hosting, issue tracking, CI/CD pipelines, linting, testing, deployments, code editing, auth providing, and LLM slop generation.

    Users in the first group won't notice anything going wrong until only the services they use are affected.

    Also “days since incident” is a terrible metric because it doesn’t capture how long the incidents last.

    Users in the second group experience full blown "intelligence brownouts" when any service goes down because they're coupled so strongly together. That's why that metric is useful (and also because it shows the true "number of nines" used in SLAs).

    And, github is doing every insidious trick they know to push group 1 users into becoming group 2 users.

    So yes. I am not sure GitHub is worse.

    If github weren't trying to force users into the second group, then I think we could give them some more leeway here. But they're not, so yes github is much much worse.

    [...] For example the latest incident is that copilot had degraded performance with Fable due to an Anthropic issue. It only last 18 minutes, only affected part of a part of their service, and it wasn’t even their fault!

    That’s very different to “all of GitHub is down for 7 hours”.

    If you want something a bit more granular, then you can check: https://mrshu.github.io/github-statuses/

  • Codeberg had a major outage today! About 7 hours of complete down (July 31, 2026)

    Jump

  • Codeberg voted to disallow projects consisting mostly by "generative AI"-tools

    Jump

  • I'm perfectly happy with this.

    Why?

    Because at the end of the day, the users of the code forge can be broken up into three categories:

    1. Traditional coders with human made projects
    2. Vibe-coders who slop out 100 throw away projects, each of which is a dead project as soon as that user moves onto the next project
    3. Vibe-coders who focus work on only a single project.

    Category 1:

    • Code forges were already valuable before LLMs, so we already have a proof of value/utility/whatever for hosting projects from users in category 1.

    Category 2:

    • Projects from the users in category 2 have a half life of a couple of weeks.
    • They're so quickly made that most of their contents is going to be rehashes of previous existing content, so there's a reduced value holding on to them as reference when the original sources exist.
    • Since they were generated so quickly, a more up-to-date version can be generated in the future if they're ever needed again.
    • Since the projects aren't going to be used by others, they don't actually use the features of a code forge, so it's not a great idea to allocate so many resources that aren't going to be utilised to host them on a community code forge. A better place for them would be cloud storage (dropbox, google drive, etc...). Most cloud storage services have a free tier. Anyone with a crazy amount of projects and assets that would exceed free tiers and who just wants to hold onto the projects for the future can use something like S3's glacial deep archive which is about $1.20USD a year to hold onto 100GB of zipped up projects.

    Category 3:

    • These projects may actually get used by people
    • Since they're developed with LLMs, there's so much churn that there's no actual point of reading the code since it's quickly out of date. That means there's no use for using the code forge's source file features
    • Issues that reference code will go out of date as soon as the code goes out of date which is far more likely than with category 1 users.
    • These projects tend to have so much code churn that their builds are more inefficient than hand coded projects. This means that they'll tend to want more powerful hardware to run their CI/CD pipelines than a community code forge can provide. So from their perspective, they're better off running their own code forge anyway.

    Keeping category 1 users on community code forges, saving the code forge's resources from being used by community 2 users, and letting community 3 users tailor their own code forges for their own needs seems like a win for everyone actually using the community code forge, and not those treating it as a file dump.

  • VS Code 1.130 released

    Jump

  • Great, another slopped out update with no actual features for programming.

    But hey, at least we increased the tech debt!

  • Kitty 0.48 Terminal Emulator Introduces Vertical Tabs

    Jump

  • I thought this was going to be something cool like building features around the vertical tab character (␋), but no, it's just a tab-bar on the side of the window.

  • Do you like to have music while coding/studying? If so, what genres?

    Jump

  • Make sure you check out the Mirror's Edge soundtracks, they were produced by Solar Fields.

  • Have you ever been disappointed with Linux?

    Jump

  • Open Office

    Uhh, isn't that old, like really really old?

    I'm pretty sure the only reason Open Office exists is because of Oracle's lawyers.

    Everyone shifted from Open Office to the Libre Office fork back in 2010-2011-ish.

    Have you been trying to use Open Office? lol

  • Have you ever been disappointed with Linux?

    Jump

  • Disappointed at linux directly? No.

    Disappointed at linux indirectly? Absolutely.

    • Nvidia's linux support: https://www.youtube.com/watch?v=iYWzMvlj2RQ
    • Ubuntu
      • Unity (at least it's gone from main installs now)
      • Snaps
    • KDE
      • Version 4 (at least it's good now)
    • Fedora
      • Forcing their own broken version of OBS that didn't work (they finally removed it)
    • Wayland
      • Not supporting screenshare (fixed with portals)
      • Not supporting global shortcuts (currently being investigated)
      • Accessibility (currently being investigated)
    • Gnome
      • Not supporting system trays
        • Most people don't want their background apps (discord, teams, docker/podman, OBS, etc...) to be filling up the foreground.
      • Not supporting server side decorations
        • Literally the stupidest decision ever made
        • Not supporting it forces all other developers to spend their time integrating their own client side decorations just so users can move/close a window in someone else's desktop environment. (example: https://factorio.com/blog/post/fff-408#%3A%7E%3Atext=Client-side+window+decorations)
        • Not supporting it means every developer has to deal with issues being reported to them that aren't their fault.
        • Not supporting it means every developer now has less time to work on their own applications.
        • Not supporting it means that humanity has wasted a stupid amount of time reimplementing the same thing over and over again instead of just once.
        • Gnome saying that: "it's not part of the standard"
          • Buddy, you're the only one holding it back from being standardised.
            • Cosmic: Supported
            • Hyprland: Supported
            • KDE (Kwin): Supported
            • Unity (Mir): Supported
            • Niri: Supported
            • Sway: Supported
            • etc...: Supported
            • Gnome (Mutter, and those downstream like Muffin): Not Supported
            • It has... by all metrics... become... THE defacto standard.
          • "It's not in the official wayland standard"
            • Buddy, wayland needs to support more than just the desktop metaphor. It also needs to support things like phones, handhelds, kiosk machines, car infotainment systems, etc... where having a window on a screen doesn't make sense. You are a desktop environment using the desktop metaphor, you need to support the basic functionality of moving windows that pop up on the screen, and you are the only one failing, and not only failing but failing so hard you're negatively affecting all those around you, and not only that but you're also not being accountable to how your actions are negatively affecting others.

  • Ask Lemmy: What do you currently use for AI coding?

    Jump

  • That's not how a brain works.

    People forget the language they grew up reading/writing/speaking simply because they stopped using it.

  • VS Code 1.123 released

    Jump

  • Oh look, another slop filled release.

    And since they've been hacked by a vsc extension, have they committed to fixing their broken extension permission model?

    No, they just delayed extension updates by two hours.

    So now they'll just be hacked two hours later...

    Face meet palm

  • What cursors yall use?

    Jump

  • The API Tooling Crisis: Why developers are abandoning Postman and its clones?

    Jump

  • Yes and no.

    There's a lot to be said about empathy, assumed knowledge/expertise, acquisition of knowledge/expertise, mentorship, deadlines, etc...

    But on the other hand, there are psychological effects that result in people being truly blind to alternatives. It's not that they don't think the alternative is correct, or that they don't want to spend mental/emotional energy on learning an alternative. It's that they truly can't even consider that there is an alternative until they are explicitly told to use it. That website exists for those people.

  • Ubuntu Linux Will Begin Landing AI Features Throughout The Next Year

    Jump

  • Hosting LLMs is different from pushing AI crap down end users’ throats Copilot style.

    That feels a lot like "War profiteers aren't guilty of shooting the gun".

  • Framework announced the Framework 13 Pro with full Linux compatibility from the Start

    Jump

  • You misunderstood the first sentence in my comment.

    I've edited the word had to needed to make it more clear.

  • Framework announced the Framework 13 Pro with full Linux compatibility from the Start

    Jump

  • All the CEO needed to say after funding that fascist was:

    Oops, sorry. I didn't check out that developer's history before funding his project. It won't happen again. I promise going forwards that we'll google people's names first before sending them any money.

    They didn't have to make a big deal about it, even a simple quickly forgotten post on their personal social media account would have been enough.

    People still ask him about it, and he'll talk about anything else.

    But he won't give a simple apology.

    His silence is deafening.

    Better to just go for the EU version of framework without the fascism: https://novacustom.com/

    Edit: Changed "All the CEO had to say" to "All the CEO needed to say" to avoid confusion.

  • I just tried vibe coding with Claude

    Jump

  • Only something created by a human can be copyrightable. (See the copyright status of monkey who took a selfie for precedent).

    Any code written by an LLM is not copywritable because a human did not write it.

    Also the company that trained the LLM is likely in breach of the licenses the code palls under.

  • I just tried vibe coding with Claude

    Jump

  • If the rewrite is based on something which has a license that your company can't use, then the rewrite likely can't be used either

  • I just tried vibe coding with Claude

    Jump

  • write something that already exists so it doesn’t need to think

    If something already exists, it shouldn't need to be rewritten.

    Doing otherwise is a sign that something has gone wrong.

    That was the case before LLMs and it is still the case today.

  • January 1st is not always on the first week of the year

    Jump

  • The first month is inputted with a 1 and exported as a 0.

    The first day is inputted with a 1 and exported as a 1.