Comment by johng
10 hours ago
Looks well done, nice looking TUI. Does not specify if it's vibe coded or not, which I think should be normal practice now ;(
10 hours ago
Looks well done, nice looking TUI. Does not specify if it's vibe coded or not, which I think should be normal practice now ;(
why would it be normal? the code is there for you to look at and use or not. It is open-source, licensed as open source and is very clear about that. Why would you feel that the author(s) should need to specify anything else at all to satisfy your curiosity?
> the code is there for you to look at and use or not
Perhaps this is a matter of different perspectives? Every tool I use is an investment for me, it might be light if I only use it once, it might be heavy if I use it for years. That investment is all the time I take to learn the various concepts involved and how to think about problems to fit the tool. But it is also all the time needed to constantly keep in mind if that tool is affected by the latest security vulnerability, how changing trends in the industry affects my use of the tool, and what to do if the tool becomes abandonware.
Reading code is hard. Writing can sometimes even be faster than reading, especially when there are many unknowns involved. So saying "you can just read it" doesn't really work for me. There's no "just" in reading. Taking in new tools is an investment, a burden, and I am perfectly entitled to avoid tools where that burden is harder than the expected outcome. It's impossible to know for sure, of course, but you can often guess pretty good very early.
There's a Kroger grocery store near my house. It's very convenient -- I'm near it almost every day I'm alive. They have all kinds of things there, including factory-made bread and factory-made eggs.
There's also a tiny little Amish bakery that I know of. They make all kinds of things there, but the most interesting to me are the loaves of plain white bread that they bake every day (except Sunday) in their wood-fired oven. It is not near to me and is also off the beaten path a good bit, but I try to make a point to go there when I'm in the area. I usually just get a loaf of that plain white bread along with a dozen eggs from the chickens that they have roaming around outside eating bugs.
I wouldn't call any aspect of it artisanal or anything like that, but it's definitely not made by machines.
And for reasons I can't really rationalize or explain, I enjoy having things from the Amish bakery in my kitchen more than I do the superficially similar things that I get from Kroger.
And yet: I usually eat the factory stuff from Kroger. On a strictly functional basis it's about the same to me.
---
Anyway: Software. Did a bot write it? Did a person? Was it a combined effort? Does it even matter?
I can accept that folks might prefer to have software in their library that is written by people. My acceptance of this does not require them to rationalize their preference, or for me to agree with it or even understand it.
It's fine when someone cares about that kind of thing. And it's fine if they don't care, too.
We're allowed to like what we like. It's good to have options, and it's OK to prefer one way over another.
> Does not specify if it's vibe coded or not, which I think should be normal practice now
I am trying to say that when people freely share software with the world, I do not think you are entitled to try to add conditions. People are free to share whatever they like, in the conditions they like - in this case the MIT license. Everybody else is free to take the code AS IS.
There is a difference between a commercial transaction and software which is shared without any expectations in return. With software shared without any expectations in return. I don’t believe that we should be trying to create normal practices on top of existing licences or trying to specify under what conditions somebody can share something
> It's fine when someone cares about that kind of thing. And it's fine if they don't care, too. > We're allowed to like what we like. It's good to have options, and it's OK to prefer one way over another.
I agree and never said anything different, but if somebody wants to share under different conditions, then their conditions will always trump yours
Kroger has bakeries within their stores where they bake bread they sell.
If the tool meets your needs, does that matter? Were you planning to make a meaningful contribution to the source? My assumption is that the vast majority of the people making these comments would have never even bothered to read the code, nevermind contribute to it.
To put it another way, if you're enjoying eating sausages then what difference does it make how they're assembled?
If I'm eating a sausage, I like to be certain that no asbestos was used in its production.
This is a ridiculous analogy. Test the app. Read its source code. Developers could always write toxic instruction in your tools. AI may write inefficient or messy code, but it’s far from nefarious. “Asbestos” code is written intentionally by humans, not unintentionally AI.
2 replies →
Not every conversation has to be a conversation about AI.
it ships with a SKILL.md file, so if they're trying to enable AI to use it, it's a good bet that they used AI to build it.