RU version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
57% Positive
Analyzed from 363 words in the discussion.
Trending Topics
#code#linux#vibecoding#don#written#end#platform#compiler#between#used

Discussion (13 Comments)Read Original on HackerNews
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
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.
https://xkcd.com/927/
Meanwhile, a few ranks away on HN:
"Big AI to humanity: drop dead"
"The End Of Upward Mobility – AI is coming for the meritocracy"
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/