he wasn’t much of a programmer to begin with and if you look at the repo for Omarchy…i highly doubt he touched most of it by hand. many scripts in that thing leave you scratching your head as to why the guy from Ruby On Rails would write that and then you realize “ah, yeah, Claude wrote this.”
it’s slop. it’s all slop. They also have well over 1000 “user made” plugins of which NONE are vetted, most are broken, and some just straight up exploit the users system. I found one that just straight up takes the users .ssh directory. It’s the wild west of idiocy amongst Omarchy users.
It’s shades of gray honestly. Sometimes they are very good (especially if you need some small tool that scratches a particular itch or want something that is 50% there right now), other times they’re extremely dumb and write horrible code. Especially of you want them to use some modern feature of your language that they don’t know anything about, or when the language in question isn’t very popular, or when the library you are using at the same time isn’t very popular, changed a lot recently and is big. They can go in circles for hours with 'wait actually …, actually …, but wait …, but actually …, ad nauseam. But when you limit them in scope, give realistic goals and constraints they more often than not work good.
he wasn’t much of a programmer to begin with and if you look at the repo for Omarchy…i highly doubt he touched most of it by hand. many scripts in that thing leave you scratching your head as to why the guy from Ruby On Rails would write that and then you realize “ah, yeah, Claude wrote this.”
it’s slop. it’s all slop. They also have well over 1000 “user made” plugins of which NONE are vetted, most are broken, and some just straight up exploit the users system. I found one that just straight up takes the users .ssh directory. It’s the wild west of idiocy amongst Omarchy users.
It’s shades of gray honestly. Sometimes they are very good (especially if you need some small tool that scratches a particular itch or want something that is 50% there right now), other times they’re extremely dumb and write horrible code. Especially of you want them to use some modern feature of your language that they don’t know anything about, or when the language in question isn’t very popular, or when the library you are using at the same time isn’t very popular, changed a lot recently and is big. They can go in circles for hours with 'wait actually …, actually …, but wait …, but actually …, ad nauseam. But when you limit them in scope, give realistic goals and constraints they more often than not work good.