whom?

>>108008577
>session log
>it's a journal
true vibes

64 sessions to the replication machine remember and copy things that are already inside his training data...
I don't who is more useless between the human and the AI

>>108008577
>needs human to compose the generated vibecode
call me again when I can tell AI: build me an OS and in a few minutes I get the OS ready

>>108008577
Kind of reminds me of KolibriOS

>>108008577
Based as fuck. AI won, codetrannies lost.
Keep coping luddifags

>>108008687
2 or 3 years. Maybe this year if they figure out how to successfully get around context windows

>>108008577
Is "ping" actually sending ICMP echoes? Or is it just printing "Reply from $1: Seq=$n" because that's what it thinks a ping program should print?

I wonder where it pulled its code from. Neat project though I guess. I do wonder how long it took, and how much it cost to run. Looking at it, it basically just reimplements libc and some Linux-y looking kernel APIs. I imagine a lot of it is just copied from others hobby OSes, and this kind of well-defined problem space is the kind of thing I’d expect LLMs to manage well enough. What amuses me, is that some dude is somehow able to accomplish a more convincing example of AI usage in coding than Cursor, who literally sells this shit.

I’m not really convinced of its usefulness in reality though. This project mostly amounts to an inefficient copy and paste job. It’s a very, very generic Linux-like hobby OS. And it took nearly two months to put together. That’d be impressive IF this OS did anything remotely interesting, but it’s essentially busybox + a very basic kernel with hardcoded drivers, where syscalls are made by passing the address of the kernels API struct to every program.

>>108009551
It should be, looking at the source it at least claims to be sending packets, but I can’t be bothered to check.

>>108008912
I dunno, they do very well if you give them a very extensive list of “this is how it’s architecture, do this that way, and this this way”. Essentially, if you give enough instructions to them that a junior dev couldn’t fuck it up, it’ll work. The downside is it’ll never get better lol. And that you need a good understanding of how things work to make them useful.

>>108008577
Amazing. SLOP: The OS.

>>108008687
GNU took at least 5-6 years to put together everything but the kernel. Doing this in just a few minutes would feel strange.

>>108009758
Linux with that timeframe had already commercial editions.

>>108009764
When Linux was started, they were simply porting over all the programs that GNU put together, including X11, Emacs, TeX, games, etc. They jusy wrote a kernel and modified the GNU system to make it compatible with it, hence why it's called GNU/Linux.

Fun fact: Linux (the kernel) was not free software in 1991, so you could not sell copies of even distributions, until the license was changed to GPLv2 in February 1992.

>>108009551
Pretty sure it isn't doing anything actually.

>>108009551
>>108009835
nvm I checked and it does seem like it's sending packets.

>>108009891
At least through virtio, yes. It isn't dealing with the details of interacting with real hardware.

Better than Windows 11.