Programmer's best friend
Programmer's best friend
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
Programmer's best friend
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
one the only good things to come out of freedesktop
get fucked
tbh this only works on an intelligently designed system. everything but plan 9 has so much boilerplate retardation that you're better off just using something else.
i don't see how
What are some of your favorite *nix applications that use a 9p server?
My favorite ones are the application I write myself that work on more platforms than just POSIX. :^)
Your Hello World in the current g flavor of the month language doesn't need IPC.
I'm not sure what you're referring to or what you mean.
acme and ii
>lightweight ipc
>20ms roundtrip
lop, lmao even
>lightweight
>involves fucking XML
To be clear, that xml is not used for communication. Communication in dbus is binary based. That xml is for optional introspection, to allow others programs to ask your program what interfaces it supports, and possibly then show that in the dbus inspect gui. It's a very nice tool. Although I agree, it didn't have to be xml based even if it's only optional.
i'm aware
why does this shitcunt always pop up to defend the worse crap imaginable
Because I am actually employed and I recognize the usefulness of dbus over some suckless tinker tranny minimal "alternative" IPCs.
figured out gtk yet?
To bait you, Kek.
Mission Accomplished
He uses garbage full-time to troll people? Seems like a self-own more than anything.
Why would you willingly use dbus?
>muh walkable system
i have seen dbus pop up a lot of times in htop. what does it do?
It's just overcomplicated IPC.
what does ipc refer to in this context?
instructions per clock?
https://en.wikipedia.org/wiki/Inter-process_communication
thanks!
>overcomplicated
understatement
https://lkml.org/lkml/2015/6/23/657
"pure shit user space code"
"written by a retarded monkey on crack"
pre "educated" linus was absolute savage.
I love that ol boy.
Ok
I love Linus Kernel Tips.
>uses gRPC over domain sockets
Problem?
k
o even
Thank fucking god it exists, otherwise it would have been a nightmare.
what year is it for you guys? in the current year ipc is done via web api
Yes let's over engineer everything just for the sake of it
>overengineer
you already have an endpoint for external monitoring, adding an endpoint for receiving data is less engineering than adding some brand new protocol
>you already have an endpoint for external monitoring
Quite a big assumption
Latest dbus is broken in Proton (steam) games.
Anon-tachi, I'm using JSON-RPC over WebSocket for IPC on my last project, what do you think about this setup?
just use named pipes
But the fastest and easiest IPC already exists: pipes. If you've ever used the linux terminal you've already used pipes.
The fastest and easiest IPC is shared memory because it doesn't involve a kernel transition.
Not concurrent
Modern OS's don't allow it
>Modern OS's don't allow it
why do i come to this board?
Because you're here forever :^)
Speed doesn't matter in modern era. Convenience matters
>1 + 2022
>dbus still hasn't been merged into the kernel
what gives?
It was shit and got rejected. They made bus-1 instead or whatever it was called. Not sure if anyone actually uses it.
And a glownagger's puppy.
How come this stagnated?
https://github.com/bus1/bus1
Is there something that replaced it?
kek even the homepage link is taken by someone else