substandard EQ that somehow manages to be broken in my system. No, I don't want to debug it and submit bug reports, I just wanna listen to music. Thanks you.
somehow Audacious manages to munch on more resources than the latest Winamp. Winamp works like it's 2007, rarely going about 100 megs of RAM. Audacious easily gulps triple or more of that. Not that I care, I have 128G of that, but still it's nice to use more thoughtfully written software.
@threat@rek2 kinda same. Which is why I use Winamp to listen to music on L'Eunuchs. Funny, but it works much better via Wine than any native L'Eunuchs music player. I'm dying of irony.
I also heard of people using Windows versions of Firefox in Wine for some seemingly valid reasons I can't remember.
@threat@rek2 because Electron is the only somewhat portable GUI out there. Except maybe Qt, but Qt comes with it's own barrel of worms (ahem C++ ahem..)
@threat@rek2 depends on your target platforms. A lot of devs target Android and iOS too, and Qt has weak support for those. Especially for iOS.
I'd take Qt + Kirigami too, KDE people did a magnificent job of splitting their libraries into small reusable components that do not pull the entirety of Plasma desktop. Still, I understand the rationale behind using Electron even though I hate it.
It's actually stupidly funny that the most portable after Electron GUI framework out there is...
WAIT FOR IT!!!!
Winapi + MFC! Because Wine exists and works virtually everywhere, and this makes older Windows apps portable as fuck. Even if you consider L'Eunuchs world alone, you have much higher chances of successfully launching a winapi binary than anything in GTK.
@threat@rek2 your workflow doesn't, but I'm willing to bet money that your Signal app for both phones and desktops is actually the same code. Element, for one, does exactly that, it's the same code base for browser, desktops (Electron), and mobile, with just slightly tweaked UI settings.
As for Wine, it's not just them. Say what you will about Macrohard, but they do a stellar job of supporting backwards compatibility. L'Eunuchs gnutards can only dream of something like that. It's much easier to launch Windows versions of even not that old games (say, early 2010s) with Wine/Proton than their native L'Eunuchs ports.
One peculiar consequence of fat CPUs with enormous core counts is that measuring CPU load in percentage of allocated time slots - as in, most monitoring software does now - is kind of useless.
For example, when talking about a CPU with 64 logical cores, one process utilising two cores to the full will only show up as 3% load, and yet this might just be enough to ramp up the cooling system and make some noise. Meanwhile, a bunch of small loads spread across the cores will add up to the same 3% and yet the overall load will be lower, your fans will stay quiet. If you throw dynamic clocking into the mix, the entire idea of counting allocated time slots goes to shit. 50% load on a core at 2GHz and 50% load on a core at 5GHz are entirely different things. Therefore, this metric is most useless any way you look at it.
The better idea, as I see it today, would be to RETVRN to tradition and measure load in... Watts against the maximum TDP that your CPU can draw. A mostly idling CPU at low clock wouldn't draw much power, whereas a CPU at high load would draw as much as possible. Number of processes or cores loaded doesn't matter here, and the number is pretty easy to grasp.
I write at around 10 lines of code per day. With this new syntax I save up to 30 keystrokes. That’s at a huge increase to my productivity!
we have created a font that allows you to display Ada code with the new syntax <...> The font contains other useful ligatures, like displaying the Ada assignment operator “:=” as “=”, and the Ada equality operator “=” as “==”.
The court in Fr*nce ruled against Orange (large European cellular carrier) in the GPL violation case, and now they will be forced to pay a bunch for using GPL code without disclosing their changes.
One may see this as a win for the open source community. This is anything but. It took the developer, Entr’Ouvert’s Lasso, almost 15 years and tens of thousands of Euro to prove their case and win this process. Which means, GPL is basically useless for individual developers or small teams.
Hear me out, lads. You all know how to run tar, right? "tar -cf derp.tar herp dee doo" will create a file called derp.tar with stuff in it. So far so good.
But what happens if that file name contains a colon? Like this, "tar -cf d:erp.tar herp dee doo"? I'M GLAD YOU ASKED!
Just so that you know, loading GMail interface requires downloading about 11 megabytes of data. Which is a lot more than the entire contents of my GMail inbox. What is the point of this, again?
Should an application trust that the keyring and its access are secure? Perhaps. Should the implementation just forward secrets over a bus without any access restrictions? FUCK NO!
Here I would like to remind you again that freedesktop.org people are a bunch of backwards shit-for-brain cockfaced retards and nothing - I repeat, NOTHING - that they have ever made is good for anything. The whole organisation is a circus full of clowns.
Hot tip: If you run `busctl --monitor user` in L'Eunuchs, you can watch every password that any application requests from your system keyring in plain text.
@cho l'eunuchs kinda does. DBus and freedesktop shit does not. L'Eunuchs can grant or deny access to various resources based on your user and what not. The problem is, once you get access to dbus bus, all bets are off and you're a god. And since more and more programs use dbus for ipc, l'eunuchs security is compromised.
@cho nuke Red Hat. Seriously, I mean it. Treat every Red Hat employee with repugnance and revulsion. Tell every single one of them to either quit and commit suicide. Red Hat is the primary corposhit behind FDo and is the driving force behind L'Eunuchs enshittification (have you even see GNOME?) and hence must suffer the consequences.
Other than that, I'd start looking for an OS with another desktop stack. No, BSDs won't do since they run effectively the very same user space code.
We must negate the machines-that-think. Humans must set their own guidelines. This is not something machines can do. Reasoning depends upon programming, not on hardware, and we are the ultimate program! Our Jihad is a "dump program." We dump the things which destroy us as humans!This is the tech account of @newt, formerly located at @pureevil. If you reached this place, it's your own fault.Expect long posts about the metaphysics of computing. Don't blame me for any adverse side effects.