Live data from Hacker News

DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

github.com

61–70 of 150 posts

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#61
post #26
post #11

Earlier quoted context omitted.

These guys used to be on the Fuchsia subreddit fairly frequently. They were definitely far from experienced or professional. IIRC, the founder is very young and was very much a beginner to OS development.

Usually hn is very positive towards young folks doing stuff, and doesn't measure it by the bar that older people get measured by. Why is this different this time? Also even then, you'll probably find people doing mistakes, committing hacks, etc all the time. It's like complaining that the initial Linux release doesn't support x86... Linus didn't write it for x86 originally.

Being positive about young folk doesn't imply a confidence in the tech they produce. This applies just as much to Linus Torvalds as it does to everyone else: you'd be a fool to trust the disk image just based on his enthusiasm.

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#62
post #40

It also seems to combine the worst of both platforms: Apps. Is there any OSDEV work that goes towards a more integrated, component-based architecture? As sad as it seems, Unix tools & pipes seems to be the most successful and enduring attempt in that direction. Systems doing that on a language basis seem mostly dead (Lisps, Smalltalks, Oberons), component architecture isn't doing much (OpenDoc as the prime example, C…

Dbus seems to be doing really well in recent decade. Sound, networking, system management already use it on Linux. It's likely only going to get more common. With the well defined interfaces seems to be a reasonable solution for system and user components.

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#63
post #45
post #40

It also seems to combine the worst of both platforms: Apps. Is there any OSDEV work that goes towards a more integrated, component-based architecture? As sad as it seems, Unix tools & pipes seems to be the most successful and enduring attempt in that direction. Systems doing that on a language basis seem mostly dead (Lisps, Smalltalks, Oberons), component architecture isn't doing much (OpenDoc as the prime example, C…

Component architecture is everywhere on the desktops, just not on those using UNIX text terminals. COM has been the underlying driving technology of Windows since Vista, where the Windows team took the Longhorn .NET ideas and redid them with COM, since then we got COM improved as WinRT/UWP. Which despite the common mix with the store (blame marketing teams), is what to this day most Windows 10 APIs make use of, and n…

> XFCE, GNOME and KDE make heavy use of DBUS.

Only for IPC. There is no IPC within a typical glib app.

GObject keeps working flawlessly, but it is too arcane to newcomers (which are already few because of C itself becoming an arcane art these days)

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#64
post #58
post #44

Earlier quoted context omitted.

That's perfectly understandable, I even feel that I went a little too "slick marketing" with the website, but I have extremely high, maybe even too high goals for the project.

Having high aspirations for your rock band is perfectly fine, but designing the album cover and the poster for the world tour when you only play some covers from other bands is probably not the best way to make yourself a name in the scene. I don't know your project in particular so I don't know if this is what you are doing, but I agree with ploxiln in that it is a general trend nowadays.

The criticism about programming projects is good, but do not take this advice for your band.

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#65
post #63
post #45

Earlier quoted context omitted.

Component architecture is everywhere on the desktops, just not on those using UNIX text terminals. COM has been the underlying driving technology of Windows since Vista, where the Windows team took the Longhorn .NET ideas and redid them with COM, since then we got COM improved as WinRT/UWP. Which despite the common mix with the store (blame marketing teams), is what to this day most Windows 10 APIs make use of, and n…

> XFCE, GNOME and KDE make heavy use of DBUS. Only for IPC. There is no IPC within a typical glib app. GObject keeps working flawlessly, but it is too arcane to newcomers (which are already few because of C itself becoming an arcane art these days)

Systemd uses DBUS for comunication between its processes & the Cockpit admin web UI uses DBUS for talking to all the things it can manage.

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#66
post #63
post #45

Earlier quoted context omitted.

Component architecture is everywhere on the desktops, just not on those using UNIX text terminals. COM has been the underlying driving technology of Windows since Vista, where the Windows team took the Longhorn .NET ideas and redid them with COM, since then we got COM improved as WinRT/UWP. Which despite the common mix with the store (blame marketing teams), is what to this day most Windows 10 APIs make use of, and n…

> XFCE, GNOME and KDE make heavy use of DBUS. Only for IPC. There is no IPC within a typical glib app. GObject keeps working flawlessly, but it is too arcane to newcomers (which are already few because of C itself becoming an arcane art these days)

As much as I like to bash C, even Microsoft was forced to reconsider their position and latest MSVC now supports C11 and C17, and UNIX kernels won't ever use anything else.

So anyone serious about OS development should know it, regardless of their opinion towards the language.

As for GObject, there are bindings for almost any relevant language.

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#67
post #11

Earlier quoted context omitted.

These guys used to be on the Fuchsia subreddit fairly frequently. They were definitely far from experienced or professional. IIRC, the founder is very young and was very much a beginner to OS development.

Hi this is Camden, yeah I'm pretty young. I was very new to OS development. Some of us aren't the most experienced at this kind of stuff, but we're doing pretty well I think for what we can do. A lot of my stuff is learning about kernel development and is mostly what I do. I do a lot with porting devices to fuchsia, and tinkering with the zircon kernel. Thats mostly it.

Nice Project, and always remember:

Have FUN!

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#68
post #66
post #63

Earlier quoted context omitted.

> XFCE, GNOME and KDE make heavy use of DBUS. Only for IPC. There is no IPC within a typical glib app. GObject keeps working flawlessly, but it is too arcane to newcomers (which are already few because of C itself becoming an arcane art these days)

As much as I like to bash C, even Microsoft was forced to reconsider their position and latest MSVC now supports C11 and C17, and UNIX kernels won't ever use anything else. So anyone serious about OS development should know it, regardless of their opinion towards the language. As for GObject, there are bindings for almost any relevant language.

You have my solidarity, but I do not see C having a resurgence.

Can share horror stories of expensive hires with MSc/PhD degrees, and years of experience having a fright of their lifetime when they see real world C.

Re: DahliaOS operating system, combining the best of GNU/Linux and Fuchsia OS

#70
post #45
post #40

It also seems to combine the worst of both platforms: Apps. Is there any OSDEV work that goes towards a more integrated, component-based architecture? As sad as it seems, Unix tools & pipes seems to be the most successful and enduring attempt in that direction. Systems doing that on a language basis seem mostly dead (Lisps, Smalltalks, Oberons), component architecture isn't doing much (OpenDoc as the prime example, C…

Component architecture is everywhere on the desktops, just not on those using UNIX text terminals. COM has been the underlying driving technology of Windows since Vista, where the Windows team took the Longhorn .NET ideas and redid them with COM, since then we got COM improved as WinRT/UWP. Which despite the common mix with the store (blame marketing teams), is what to this day most Windows 10 APIs make use of, and n…

Are you talking about Component Object Model, COM? If so, that predates Vista by many Windows releases.
Post reply on HN