191–200 of 264 posts
SerenityOS is not something new it has been done 100s of times in the past 20 years. stop wasting your time on this nonsense and go find better jobs.
I highly recommend checking out his YouTube channel [0]. He's an _incredibly_ thoughtful person and provides good lessons in staying focused and keeping scope down. I consider him a mentor and his approach to software is something I really resonate with. He has a keen focus on software quality but understands he can't make everything perfect in one sitting. This approach helped me get away from decision paralysis in…
https://www.youtube.com/watch?v=KehSJ_fdTxU
It has a tour of features for SerenityOS... They have built an impressive amount of stuff at an incredibly high pace.
Watching even half of one of the videos, it's clear that Andreas is thoughtful individual with a talent for explaining things, who has managed to gather a vibrant community around him. This is such an inspiration that I headed right on over to patreon and signed up, too :)
Windows NT/9x/2000 represented the high point for aesthetics. Light grey, rectilinear, clear delineation, all contributed to being easy on the eye and functional. Glad to see it make a comeback.
I never liked Windows NT aesthetics-wise. Personally I find the Windows Explorer ugly and I don't like the Start menu either.
I was hoping Serenity looked a bit more like Macintosh System 7 [0], NeXTStep [1] or BeOS [2]. So I was kinda disappointed when I visited the site.
---
[0]: https://en.wikipedia.org/wiki/System_7
Windows NT/9x/2000 represented the high point for aesthetics. Light grey, rectilinear, clear delineation, all contributed to being easy on the eye and functional. Glad to see it make a comeback.
Configuring the Windows desktop to look like Windows NT makes me feel 20 years younger!
Windows NT/9x/2000 represented the high point for aesthetics. Light grey, rectilinear, clear delineation, all contributed to being easy on the eye and functional. Glad to see it make a comeback.
The more I see those small graphical OSes like this one, Kolibri, etc. the more I wish they were ported (or better conceived from the beginning) to be run on ARM systems. Those small cheap boards with video output would find the best possible companion when bare metal programming is too hard and a full fledged Linux distro would be overkill. Give me a compiler, then libraries for gpio and hardware, GUI, low level net…
[1] At some point, I probably have to do bitmapped text, but I'm trying to keep my scope narrow, and graphics aren't for me. :)
I'm curious, how can someone implement device drivers (without knowing hardware details.) for a self-made OS like this?
General tips: 1. Start with a QEMU emulated device. QEMU is more forgiving than real hardware and you can study, understand, and debug the "hardware impersonation side" of the QEMU code to see what happens when you set a bit in some register. 2. Pick a simple device. Don't start with the USB stack or Ethernet. Maybe try to reimplement the UART driver first. 3. Don't freak out about "device driver architecture" stuff…
A UART driver is great; then if you want to do Ethernet, virtio-net is a good start, and then carefully pick your physical ethernet card; something descriptor based will let you reuse the descriptor concepts you already learned. Realtek cards get a lot of shade, but aren't too bad to interface with and they're very popular; if you've got a bunch of computers, you've probably got at least a few realtek nics. Ethernet is cool, because then you can start communicating with the world (although there's a lot of stuff to get tcp going)