Live data from Hacker News

The 4th Year of SerenityOS

serenityos.org

121–130 of 144 posts

Re: The 4th Year of SerenityOS

#121
post #100

Earlier quoted context omitted.

Modern tools are good, but the culture around it is pretty toxic, and in my own opinion, cringy. 10 years ago you would get booed for saying things like "Unused RAM is wasted ram, so let's build this in Electron". I am happy to see a pushback.

“Unused RAM is wasted RAM” is only relevant if you’re writing an OS.

It's also relevant if you're writing software that's intended to be run side by side with other software.

Re: The 4th Year of SerenityOS

#122

Fantastic progress. My only concern is looking at it... I can't help but worry slightly about feature creep. We went from an OS, to an OS + Web Browser, to an OS + Web Browser + Programming Language. Next year it might add an Office Suite at this rate. Edit: I don't mean this as a bad thing, just that it would be a shame to get so large that everything becomes half-baked and overwhelming to finish.

To stay true to the theme of being 90s-inspired, the office suite will have to include: Serenity Works!

Re: The 4th Year of SerenityOS

#123

Earlier quoted context omitted.

Super welcoming community + a clear and strong vision to guide the project. Other OS projects I have seen either lack vision (same as x, but written in y), or they are just for the personal learning of the developer who started it.

Is that vision written down somewhere? Surely there is something more than "Unix-like core with the look&feel of 1990s productivity software" keeping people engaged with this project?

If you ask me:

- write the whole stack yourself so you can fix any problem or make any improvement without external dependencies or coordination - the implementation is never written in stone and it is always possible to move to something better ( which is why you need to control the whole stack ) - no problem is too big to start solving - implement something basic that works and then improve it ( see all of the above ) - evolve everything in the open

Re: The 4th Year of SerenityOS

#124

I wouldn't be surprised if, at some point, some commercial project adopts a part of Serenity and turns it into a huge hit, even outside of tech. Such things have definitely happened in the past.. Not many (average) people have heard of KDE or its web engine, KHTML, but almost everybody these days uses Chrome, which, through Apple's WebKit, is descended from KHTML itself. Serenity uses its own libraries everywhere, to…

They’d have to use something that wasn’t a weird proprietary language that only cross compiles to C++ (!) for that to be a thing.

Whether they like C++ or not, no one’s going to want that generated C++ output as a basis for source code, and you’re not going to use the weird single source compiler either.

Re: The 4th Year of SerenityOS

#125
post #73

Earlier quoted context omitted.

> This project embodies Donald Knuth's principle of being the author of software, rather than just consumers of other's APIs. I feel that this comment unfairly criticizes people who build on other things. This OS runs on hardware, which is someone else's API, and is a hobby project, as far as I can tell. If someone wants to build something cool that uses others' APIs as a hobby project, more power to them.

It's not criticizing anything at all, just suggesting an alternative. We're all always using products that are other people's work, why not ALSO work on something where you author and build your own system?

Whilst that's a valid point of view, it needs to be balanced against good old "don't reinvent the wheel."

I'm not quite sure how I would marry those two concepts.

Re: The 4th Year of SerenityOS

#126

I wouldn't be surprised if, at some point, some commercial project adopts a part of Serenity and turns it into a huge hit, even outside of tech. Such things have definitely happened in the past.. Not many (average) people have heard of KDE or its web engine, KHTML, but almost everybody these days uses Chrome, which, through Apple's WebKit, is descended from KHTML itself. Serenity uses its own libraries everywhere, to…

They’d have to use something that wasn’t a weird proprietary language that only cross compiles to C++ (!) for that to be a thing. Whether they like C++ or not, no one’s going to want that generated C++ output as a basis for source code, and you’re not going to use the weird single source compiler either.

Only because they aren't a big name company with weight to arm strength developers into using their language on their platforms.

Re: The 4th Year of SerenityOS

#128
post #98

I found out about SerenityOS because of the post about Ladybird here on HN a few weeks back. I have since watched hours of his stream and found it super inspiring. To the extend that I now want to learn some C++ and make some contributions to the project. It's really refreshing to see people code for fun and build whatever they feel like. I think a lot of profesional devs lose that when they go all in on their work (…

Start with "Programming -- Principles and Practice Using C++" from Bjarne Stroustoup.

It is a good book to learn C++ the modern way, instead of a couple of appendixes in what is otherwise a C programming book.

Re: The 4th Year of SerenityOS

#129
post #68

Earlier quoted context omitted.

It seems like you -are- crediting MS for bundling a browser with an OS. Their reasons are irrelevant. OSs didn’t come with browsers. Microsoft bundled IE with Windows. Now every OS comes with a browser.

Of course they did, or if they didn't, browser was one of the first things installed. Windows was nothing new in this regard. What was new was that OS was deeply connected to browser, so that uninstalling it was not an option. But that is not what GP claimed, and that is of course not a rule with newer OSs. But anyway, let's talk about this great new SerenityOS instead. :) Over and out.

As proven by Web widgets on mobile OSes, game consoles and TV firmware, they were just ahead of their time. :)

Re: The 4th Year of SerenityOS

#130

Earlier quoted context omitted.

“Unused RAM is wasted RAM” is only relevant if you’re writing an OS.

It's also relevant if you're writing software that's intended to be run side by side with other software.

It's relevant in the sense that you should not be using that as your guiding principle, yes.
Post reply on HN