3

I found out that my favorite library is way outdated, like a whole version of its biggest dependency. Upgrading breaks everything. I never noticed until I got working with something else that needs the newest dependency. But good news, thus guy has full test coverage. My own vibe cli tool is thundering trough it. Hundreds of updates within minutes. I expect that the original owner just gave up after 20 things. So good about AI, it just doesn't get tired. I did these few ai queries in a few days: https://static.molodetz.nl/rp.cgi/.... I appearantly uploared 400+ mb to AI trough my cgi gateway. Iirc python wants to delete cgi from its library. I don't care, I made my own cgi server (setting env vars) and client (reading env vars) and stdin if it's a post. It's an aiohttp server executing an async subprocess. The dashboard is quite nice huh? Want some more stats but I have different priorities. I am trying to make the best autonomous build tool ever made. It's already better at building than gemini. Gemini is a fine coding LLM but it just can't beat my software so far. This is an old version but here it just built a reddis mvp, working, with tests. https://elon.app.molodetz.nl/termin...

I'm future I'll make it controllable online, so people can vibe then selves. It'll be a platform that will deploy your vibed code on a https molodetz supdomain and it will offer vscode development environment for your project: https://thomas.app.molodetz.nl. It costs literally a second to configure and five seconds waiting to deploy a while vscode instance. Now I only have to build a service where a zit can be uploaded and it'll auto deployed with some quota. I'll support Rust, python, php, c, c++, Java. Rust is sadly not so good for the vibing tho and requires much resources in storage. Every container is a new Rust install. I think it's more than Java. Soon we can do the language wars again. With isspam was leuk.

Comments
  • 3
    So many stores. Was tired. Still am. Geen slaap tot osdorp!
  • 1
    "I'm future I'll make it controllable online", you need some sleep man.
  • 2
    This actually bit me in the ass today.

    My fault for allowing major version hoisting.

    The motherfucker maintainer of dotenv decided he would push a new major version (which, in his defense, is okay, breaking changes are allowed), where the breaking change was his fucking module writing an ad for his newest, -more powerful, more SaaS, and more everything- module.

    Yet for those of us who expect stdout to be, well, output... It fucking borked everything.

    Raged hard at that one. I mean, I get being an OSS maintainer is thankless work, but even for a breaking change, that was a dick move.
  • 1
    @CoreFusionX haha, dotenv. I've seen an llm literally writing a split operation fir every line and then split on = to resolve all properties. Wtf huh.
  • 2
    @whimsical

    It's not about complexity or what retarded AI models do.

    This was a package, used by millions (not me anymore tho) that out of the blue broke whichever CLI tool that depended on his shitty library. (It's not shitty, but the author is)

    It was a dick move no matter what. I already have my replacement, and I will not look back. It's gonna backlash on him *hard*.
  • 2
    Specially since, when it was brought up to him in the official GitHub, he just brushed it off as "people need to know about my new product". Which is legitimate, but still a dick move. Why would I ever trust anything you do, if you are willing to break millions of pipelines just because of your greed?

    If you feel it's not worth it for you to maintain the package, let community handle it.
  • 1
    @CoreFusionX No it's not legitimate and he deservers to be taken out back. Just like the creator of the faker library that threw a shit fit
Add Comment