People get excited about it, post about it, and disappointed by the reality of the license in constant cycle.
It’s kind of the “missing stair” problem. Those who know, can go around it, but knew people need to be informed that it’s busted to avoid it until an actual solution is presented.
I personally yes. Also I’ve seen hesitation in including them in distros because of it
More people would inclined to contribute or include it in there own projects if it wasn’t a regression in terms of FOSS.
I.e. why contribute to this project that could be forked to create tools that don’t respect the users when the main existing project doesn’t have that flaw?
This made me laugh too much
Power over Ethernet
Not the person who’s written on both a desk and a Raven.
Tbf cli help is copy paste, GUI help is something I didn’t want to help with even when I was being paid for it
Every chain broken makes the next one easier to break. This is cool to see a good list break down like this
https://github.com/vosen/ZLUDA I’ve heard is doing pretty well
So Mojo and Python then?
To be fair. SELINUX always seems like THE answer with flexibility it provides with App armor being just SELINUX light…
It would make more sense to me to have better support for leveraging SELINUX primatives to accomplish the same things. I at least, don’t know of any LSM features that can’t be covered user:role:type:security level:catagorey and namespaces?
The issue is always that info is hard to know sometimes and programers can barely stop ourselves from running as root with all files in 777 mode let alone conceptualize those other attributes for files and services
As THE USB-C PD evangelist. I have to say. Fair. Like PD EPD is definitely reaching the limits of the USB-C form factor to me, and data over copper is a dead end at some point too.
Still want ever device I have on it. Though as we scale past the 260 watt range (and I do…) or longer distances (also me) it’s just going to have to be another interface and probably medium for data for the protocol. So far MPO for data and honestly pogo pins for power are the best I’m seeing.
Again for everything thats not a serious power device like well pumps, servers, AC/Heat pump, Power tools, etc or serious data server/client. Its fine, which is seriously impressive.
Rant over I also like the idea of better hardware stats reported to the OS. Its one reason I fell in love with software raid over hardware raid
Right! Tbh I saw their work after playing with git pods on a project that utilized it. By that point though the git pods project had made significant progress IMHO from the fork of Eclipse
Check out ptyxis as well. Terminal with support for opening new tabs into the container namespaces.
Honestly tinkering like this is a lot more stable for me. If I bork it, I can just blow it away. I just need to get better about going from tinker to full Containerfile for my build environments lol
I did have a very real work experience where people went “a what list” when I mentioned we had a black list of software built. I am kind of glad to move past black is bad, white means good phrasing tbh because some people are turned off by it.
If we could just end racism, as in the fucking stupid idea of race at all, it wouldn’t matter. People are even black and white…
This was the best project I was following in the space
The IPC increase is the most sure tradeoff for sure.
Agreed, engineering is deciding what trade offs are acceptable. Cargo culting any pattern is a good way to build runaway junk
Can be more efficient, but it’s not always. You can scale those services more too. Do you need all 16 running on idle? Lazy load then as needed. Also does it really need a whole 500mb? Why? If its just a cache made that’s better handles with another shared service (redis, etc). If it’s software, why? A full “fat” Suse Base Container image uncompressed is 94.8mb and not all of that will be loaded in RAM. Going down to a micro at 23mb. All this and now you can deploy it on the shared infra, no separate OS, Management/security/logging/networking solution.
Honestly probably got the project to more maintainable state. Probably didn’t need the rewrite to do it in a new lang to do it (the real killer hear it sounds like).
Those monoliths suck on the operations side, and even worse when it’s a corpse holding up the foundation to other projects that actually need it to change. Need to scale? good luck that decades old pizza box we call a server isn’t supported anymore. Oh of course we can spend millions virtualizing dead hardware to keep it running the same.
Very cool for archival work!
Not the person you asked but kwin the GPL licensed Wayland compositor. Why do you ask?