I’m learning a lot, so I’m not a fan of the people flaming and downvoting OP for having genuine confusion. I want us to incentivize more posts like this.
Easy… decoupling. You hit the pause button on your keyboard, it does not need to “know” (in code or compile time or at runtime) what your music player is, and it can still pause it. Similarly, you can write a new media player, and not have to convince 1000 different projects to support or implement your custom api. en.m.wikipedia.org/wiki/Enterprise_service_bus
There’s nothing about dbus that makes decoupling easier, you can do it just as well with sockets. Pipewire and pulse both speak the same protocol, and they both rely on sockets, not dbus. The vast majority of the apps on my system don’t know or care that they’re speaking with pipewire instead of pulse. Read my comment here lemmy.world/comment/6284859
I know you said don’t suggest Vim, but I use Neovim for my writing and write in markdown. Any markdown editor will do. Marker is fine. It’s really easy to convert to another format like HTML or EPUB with pandoc. Markdown has minimal formatting, too, so it shouldn’t bug you so much.
FocusWriter is another good suggestion if that’s more what you’re interested in.
There is one named neonmodem overdrive but it is buggy.
It really is buggy, iirc I couldn’t even get it to run properly.
It also support discourse forums any plan for this?
I really don’t have any plans (or even a name) for the app, as I’ve just started playing around with pythorhead yesterday. I just hoped posting a prototype or a proof of concept might spark a discussion and maybe inspire someone much more competent than me.
Sockets are effectively point-to-point communication. Dbus is a bus. Your question is similar to “what is the point of I2, or an ATA bus when directly wiring ICs gets the job done”. Both have different strengths and weaknesses.
No. DBUS has its roots in freedesktop.org and the KDE+Gnome projects. It’s basically a desktop agnostic reimplemented of KDE’s DCOP, which was itself a simplified CORBA (gnome was using ORBit at the time, if I recall correctly). DBUS was so useful that the domain spaces its been applied to soon rapidly outgrew the desktop space, and this is why it’s usually started earlier these days.
Can confirm, I’m using a dock (from Razor) daily without problems. Hot switching doesn’t work though, you need to restart X/your display manager to connect or disconnect the eGPU. I’d recommend the gswitch utility to configure the graphics card to be used (on X11). Haven’t tested much on Wayland, but I know that at least Gnome (Wayland only) has trouble mixing eGPU and the internal display if that is important.
If you use X and need to restart it, you can probably preemptively use XPRA to proxy your Xclients and move them to the new Xserver, except maybe for those that need low latency or DRM (e.g. games)
I don’t think hot switching is an issue. It would be setup and not disconnected unless I’m traveling. Does it use the egpu for everything when its connected? Or can you set it up like hybrid where it’ll only use it for games etc?
I use it for everything, because I connected my external monitors through the eGPU. wiki.archlinux.org/title/PRIME has a few methods for running only selected applications via the eGPU, but I haven’t tried them. Edit: See also wiki.archlinux.org/title/External_GPU#Xorg for eGPU specific setups.
Undoubtedly Wayland is the way forward and I think it’s a good thing. However I wouldn’t piss all over X because it served us well for many years. My LMDE 6 still runs X and probably will for the next 2 years at least because both the Mint Team and Debian team don’t rush into things. They are taking it slow, testing Wayland to make sure no-one’s system breaks when they switch to Wayland.
This is the best approach. Eventually it will all be Wayland but I never understood why this is such an issue. Like any tech it’s progress, no need for heated debates. It’s just a windowing system after all.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.