Everyone needs to have made a web framework. Everyone needs to have made a programming language. Everyone needs to have made a supervisor. Everyone has to have made a container manager. Everyone needs to have made a text editor.
Absolutely. I recently wrote my first compiler to get it off the bucket list… brainf*ck compiler/interpreter #100010134 or such? :-) Well… it was a fun half hour.
In some industries it’s critical. Think about aerospace where code is almost always homegrown or done by specialized company, and are specific implementations for specific needs. You don’t have that many COTS due to the criticality etc.
The area where I've seen the most homegrown implementations of things like these is HFT, with the caveat it's also designed to be distributed, integrated with isolation systems, start/stop dependency graphs...
I once worked for a company which chose to use Kubernetes instead, they regretted it.
One release every 4 years. So this is like monit or systemd-supervisord and so on, a process manager. I have to say the thing I most enjoy about it is the fact that it's got the classic GNU trend of "here's an obviously pronounceable spelling; let's say it a different way".
Are the collection of components run in some kind of namespace? Say I run a Pies for Gitlab (which in itself had lots of components), and I run a Pies for Frpd, do they share the same space or are they isolated from each other? Am I maybe overthinking this? Perhaps its just a program manager.
It's a collection of tightly-coupled components that are functionally a monolith because large distros tend to rely on the various components rather than allowing modularity.
Almost 20 years ago now I worked for a company that sat a group of about 25 of us down to talk about their latest survey named...CRMPIES.
Everyone looked at me like I was insane as I sat there chuckling. Thank you for bringing back that unfortunate memory.
Everyone needs to have made a web framework. Everyone needs to have made a programming language. Everyone needs to have made a supervisor. Everyone has to have made a container manager. Everyone needs to have made a text editor.
Absolutely. I recently wrote my first compiler to get it off the bucket list… brainf*ck compiler/interpreter #100010134 or such? :-) Well… it was a fun half hour.
What's the value of making a supervisor? It seems to be mostly about gluing together some system APIs.
In some industries it’s critical. Think about aerospace where code is almost always homegrown or done by specialized company, and are specific implementations for specific needs. You don’t have that many COTS due to the criticality etc.
The area where I've seen the most homegrown implementations of things like these is HFT, with the caveat it's also designed to be distributed, integrated with isolation systems, start/stop dependency graphs...
I once worked for a company which chose to use Kubernetes instead, they regretted it.
One release every 4 years. So this is like monit or systemd-supervisord and so on, a process manager. I have to say the thing I most enjoy about it is the fact that it's got the classic GNU trend of "here's an obviously pronounceable spelling; let's say it a different way".
The only thing missing is a recursive acronym e.g. Pies: Pies Is Experimental Software or something equally cringe like Hurd
Pies is eshewing systemd?
how about "Active Development" without any progress in 3 decades
Are the collection of components run in some kind of namespace? Say I run a Pies for Gitlab (which in itself had lots of components), and I run a Pies for Frpd, do they share the same space or are they isolated from each other? Am I maybe overthinking this? Perhaps its just a program manager.
I think they both run as user. But you can put gitlab in a docker
https://www.gnu.org.ua/software/pies/example.php?what=gitlab
https://www.gnu.org.ua/software/pies/manual/Docker-Entrypoin...
Is this the gnu version of systemd?
edit: I know it's not a monolith like systemd but service/unit files are a core component of systemd
systemd is not a monolith.
It's a collection of losely coupled components and services of which basically every single one can be disabled or replaced by another implementation.
It's a collection of tightly-coupled components that are functionally a monolith because large distros tend to rely on the various components rather than allowing modularity.
GNU Shepherd
"Pies" means "dog" in Polish an Ukrainian (пес).
So, "Gnu is Not Unix, Dawg"?
Is that pronounced “peace” or “piss”?
More like pi+[y]es, but single syllable and no y.
EDIT: Here are three audio files to hear: https://pl.wiktionary.org/wiki/pies#pies_(j%C4%99zyk_polski)
When do you use that vs собака (sobaka)?
I don't, I'm Polish. Can't say for sure for Ukrainians, don't know Ukrainian that well, but my reading of https://en.wiktionary.org/wiki/%D1%81%D0%BE%D0%B1%D0%B0%D0%B... and https://en.wiktionary.org/wiki/%D0%BF%D0%B5%D1%81#Ukrainian suggests that пес must be male, but собака is either male or female. I might be wrong.
> pronounced "p-yes"
Absolutely not.
Apologies to the Slavs, but there’s already a utility pronounced like that.
Pies it means "foot" in spanish
Plural - “feet”
'a dog' in polish
If you have to explain the pronunciation of the name of your tool in the first sentence, you've already lost.
Lots of counterexamples to that one.
https://nginx.org/
sudo? gnu? mate? debian? ubuntu? suse?
No.