the question becomes, is it the end user’s decision to decide what packages they download/use or is it the repository/package manager’s responsibility to show end users which apps are allowed to be used or not.
I understand the objections to vibe coding, but for those of us who don’t care how a good tool was built (when it actually is good), this just forces us away from your favorite platform. Like it or not, this is the present and these AI tools are available. People will use them.
That said I think it’s utterly ridiculous that this article was written using AI.
This is good to know. ‘I’ built a compiler for a language I call ‘xc’, similar to Objective-C but designed to be cross-platform and have less square brackets :). It can run on any of {Windows, Mac, Linux, Zynq} and produce code for any of {Windows, Mac, Linux, Zynq, WASM, iOS, Android, m68k, 6502}.
It needs no host-platform tools to compile code, so for example I have a signed binary on my iPhone, written and signed entirely on Linux.
The compiler (v 0.61, not the released v0.6) currently produces code that is between 5x and 0.5x the speed of clang when measured at -O3 on both, against ObjC code, which is pretty good for a nascent compiler. The geometric mean of 19 mini-benchmarks comes in at xc being roughly 6% faster than clang.
Since there is also a framework and gui-designer under way, I’d like to release it as more than a tar.bz2 file for Linux at some point. Flatpark would seem to be appropriate :)
But the policy doesn't distinguish between someone who prompted an LLM to generate an entire app in five minutes and a developer who used Copilot for autocomplete while writing 90% of the code themselves.
How is using autocomplete "Vibecoding" now? I remember y'all that the "definition" for vibecoding requires the "prompter" to not look at a single line of code
Sure it's not a crime but I don't want your vibe-coded shit mingling with my actual code written by actual humans.
the question becomes, is it the end user’s decision to decide what packages they download/use or is it the repository/package manager’s responsibility to show end users which apps are allowed to be used or not.
I understand the objections to vibe coding, but for those of us who don’t care how a good tool was built (when it actually is good), this just forces us away from your favorite platform. Like it or not, this is the present and these AI tools are available. People will use them.
That said I think it’s utterly ridiculous that this article was written using AI.
This is good to know. ‘I’ built a compiler for a language I call ‘xc’, similar to Objective-C but designed to be cross-platform and have less square brackets :). It can run on any of {Windows, Mac, Linux, Zynq} and produce code for any of {Windows, Mac, Linux, Zynq, WASM, iOS, Android, m68k, 6502}.
It needs no host-platform tools to compile code, so for example I have a signed binary on my iPhone, written and signed entirely on Linux.
The compiler (v 0.61, not the released v0.6) currently produces code that is between 5x and 0.5x the speed of clang when measured at -O3 on both, against ObjC code, which is pretty good for a nascent compiler. The geometric mean of 19 mini-benchmarks comes in at xc being roughly 6% faster than clang.
Since there is also a framework and gui-designer under way, I’d like to release it as more than a tar.bz2 file for Linux at some point. Flatpark would seem to be appropriate :)
1: https://compile-xc.org/
How is this supposed to be relevant to the article we're discussing?
'I', presumably
Yeah, thought that was pretty obvious, alongside the “AI-friendly” flatpark. Guess I’ll be more explicit next time…
How is using autocomplete "Vibecoding" now? I remember y'all that the "definition" for vibecoding requires the "prompter" to not look at a single line of code
Intentional littering is a criminal offence in most places.
"Vibecoding isn't a crime"
Meanwhile, a few ranks away on HN:
"Big AI to humanity: drop dead"
"The End Of Upward Mobility – AI is coming for the meritocracy"
Further evidence that Flatpack does not solve the problem of distributing applications.
https://xkcd.com/927/
Well, there is still AppImage, this might be the right way to go with in this case.