

The Circle of Slop


The Circle of Slop


Something less degenerated


Vibestrapping


I’ll give it a pass because it’s an OpenCode plugin, meaning the typical user is not tech-savvy enough to be able to edit a simple JSON configuration file.


I do not believe a permissive license has any notion of consent. You can’t stop someone from forking your code as long as they follow the rules of the license, like crediting you.
Does the LLM ever credit the original author when it spits out code?


I’m willing to recommend Windows 10 to someone who considers “upgrading” to Windows 11.
Did you go back with a time machine to make sure it didn’t make sense back when it was written?
Also the source of most of the things Rust gets criticized for. Ugly syntax? That’s mainly because of the lifetimes, which server as instructions for the Borrow Checker. Too many types of strings? So that the Borrow Checker can determine how the memory slice the text is stored in is managed. And of course - the complicated error messages are where the compiler is trying to explain to you what the Borrow Checker is thinking.
(Lack of any idea to program more than anything tbh)
Make a launcher. Apparently they are all the rage nowadays.
Even if the pay is good - unfucking vibed code is going to be very grueling. Like fixing legacy code but so much worse - because legacy code at least used to make sense at some point in the past.
It can do it better than I thought. Normally it’d spin Python, as you said, so I tried asking it to not use tools:



In your defense, it’s written in the only “modern” programming language that encourage this category of errors.


Though you forgot the curly braces and the semicolons are unnecessary.
Yup. These are pretty big issues. But there are also some minor, trivial, purely-preference-based issues - like returning an error if err == nil instead of when it isn’t.
There is a world of difference between “not getting the best experience” and “the entire computer is unusable now”.
Login with sudo
Since it’s about birth dates, shouldn’t it be an astrological amount of people?


He is not making MCPs. He is just maintaining a list of MCPs other people made.
If this repo really was the source code for MCPs, I’d understand - MCPs are (part of) the boundary between the LLM and the external world - you don’t want to let bots implement their own sandboxing.
But for an “awesome list”? Who cares?


I still don’t understand why it needs to be implemented as part of systemd, and not - say - as a service. Or, if we want to “go with” the law - make it a kernel module, which sounds more impressive (“we are complying at the kernel level!”) but in practice so much easier to opt out of.
Is that like an arch nemesis but a friend?