libwebsockets VS systemE

This is just the endemic result of C++ lacking a package manager.

Every library starts out small, adds its own vendored utilities, adds its own dependencies, and eventually becomes boost.

To be fair to this project, theyve worked quite hard to make the library consumable by others… but yes, its hard to look at the code like https://github.com/warmcat/libwebsockets/blob/50ba61082dc40b...

…and not go… really? As part of the core of libwebsocket?

When you read the justification it’s mostly “well we have a good framework now, so why not use it for other things too?”

C++ life.

/shrug

I'm trying to setup a project using libwebsockets.

Libwebsockets a powerful and lightweight pure C library\ (48 comments)

and how others have implemented the client

This was posted by someone else in the thread, but SystemE is close to that dream [1]:

> Using the tooling in this repo, I am able to boot from linux to sinit as PID1, and from there to Emacs acting as PID2 using --script mode, performing all typical rc.boot system initialization using Emacs lisp until we hit the getty.

[1]: https://github.com/a-schaefers/systemE

Emacs people are the same

A bit too late now lol

I think there is one already

Replace whatever puny old init you’re using with https://github.com/a-schaefers/systemE

Cool otherwise, I had some thoughts that Emacs could be used as a cron replacement, but I was never sure it would be worth it to be honest. Systemd is probably the way to go. By the way, I remember there was also a SystemE, I have never tried it, so I don't know how good it is, I totally forgot it actually until now.

Hello there