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.

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

But hey, at least we increased the tech debt!

lol, it's always the way. My codepen is full of not quite finished experiments

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.

It's possible to scroll past 23:59.

See screenshot:

When going past 23:59, the timer shows 00:00 but the scrollbar's handle is still past half way. It's possible to scroll past 23:39 to 00:59 on the right side of the scrollbar. Going past the second 00:59 resets the scrollbar back to the first 00:00 all the way on the far left.

Cool prototype

I'd fix the vertical scrollbar by changing SCSS' line 19 to: overflow-x: scroll; (also, you may as well just switch the editor to CSS instead of SCSS to make it load faster)

I'm a little confused why I can't drag all the way to the right, and also why it seems that the scroller does 25 hours and not 24.

Good.

A programming company which produces nothing, has more lawyers than programmers, and whose entire company runs on signing ridiculous deals with corrupt managers who then leave the blast radius before anyone else finds out how bad the deals are deserves to die.

Hopefully once the company is torn apart into a million pieces and each piece sold off, maybe sensible things start happening again and the Javascript language can finally get the rights to the name Javascript.

Seconding other's comments for: Signalis and Soma

Some unorthodox / overlooked suggestions:

• Project Zomboid (PC).
  • Imagine the Sims 1, but it's during a zombie apocalypse with a GTA sized massive map. The situation is so dire that the game outright tells when you start that your character dies, and the actual gameplay is just you finding out how your character died.
  • The survival: is needing to move to scavenge for resources and trying to build a safe place to sleep.
  • The horror: is trying to escape the literal hordes of zombies.
  • Sidenote: This is a great grindy multiplayer game.

• Metroid Fusion (GBA).
  • It's a platforming game, but it's legitimately terrifying.
  • The survival: revolves being trapped on a space station going around fighting and fleeing difficult enemies
  • The horror: revolves around the antagonist: [redacted for story spoiler reasons]
  • Sidenote: This is a great game to show people who haven't yet realized that you can make horror without being an FPS.

• Frostpunk (PC).
  • It's a city-builder game with survival resource management gameplay and with non-lovecraftian cosmic horror themes.
  • The survival: You are the last city on Earth. If you run out of resources: you die. There isn't enough resources to save everyone and you have to make hard decisions. If the people lose hope from your decisions: you die.
  • The horror: The world's climate dropped another 3 degrees today. There are 100 of us left. Only 5 people from yesterday's expedition made it back with food. We need to send 20 survivors out to look for scrap metal to repair the heating system or everyone will freeze. We need to put our children to work in the coal mine, it doesn't matter how many die, if they don't mine, we all die. The next day: things get worse. The day after: things get worse. etc... Will you survive?
  • Sidenote: This has one of the best soundtracks in all of gaming. I'd put it up there with Halo, Skyrim, Homeworld.

This looks like it's stealing someone else's work, and got it wrong at the same time.

Original work: https://petervelnl.blogspot.com/2021/11/vision-encoding-language.html

Getting it wrong: Red should be the Chevron as a metaphor for fire, Yellow should be Circle as a metaphor for Sun, Blue should be line as a metaphor for the sky + horizon.

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

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

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.