beleza pura @ bunitor @lemmy.eco.br

Posts

23

Comments

383

Joined

1 yr. ago

i wonder if i can do something similar with c++-ts-mode

I don't have the exact numbers with me right now but according to systemd-analyze

before: ~3min

after removing snapd and docker: 1min 50s

i'm not doubting anything after i heard they snapified kernel modules

the official slack package for linux is a snap. the flatpak one is not official and it has a number of issues, especially on wayland. luckly, there's also a beta deb package available, so i'm using that

but i believe snap will only become less able to compete with flatpak as time passes

i realized "the meaning of life" is essentially a christian concept disguised as something universal and stopped worrying. "life is useless", as ailton krenak would say -- usefulness is a property of things, not people, after all

i have a different kind of dread: my own mortality. it comes every once in a while and i just wait for the dread to go away

systemd isn't a pid1; systemd-init is

hi, tankie here

his take is reactionary garbage and he doesn't know what he's talking about. most other tankies i know don't parrot conservative talking points about trans people

hope this helps

oh no thiat's straight hot garbage what the hell

where did he say this?

i've been meaning to try it, but my company's machines are still x11-only

ssh -XC

it runs a bit slow, but it is surprisingly usable. in some aspects, it has almost the same performance as vnc with the difference that it is integrated with the system. i have a 600 mbps internet connection

yup. it's still nice and also pretty funny that wayland provides a better x11 experience than x11

it's not really a need, it's more an imposition. we're forced to do everything via the app

react os is unusable

yes because kde supports client-side decorations and server-side decorations. gnome only supports client-side decorations

technically it doesn't have to (you can always create a .tpp (which is still technically a header, i know, but it isn't a header header)), but i get what you mean

I'm sure they have their reasons

maybe compatibility reasons. i guess they used to support i386 back in the day and didn't want to break the couple of systems that were installed on bo and have been upgrading ever since

Not all 32-bit systems are i386

but the debian i386 architecture means all 32 bit x86 processors. there's no "i686" build of debian

there are no i586 or i686 kernel or iso available, you can look for them. i386 packages only exist for compatibility reasons, so you can run 32 bit applications on amd64 machines. please read the release notes

https://www.debian.org/releases/trixie/release-notes/issues.html#reduced-support-for-i386

From trixie, i386 is no longer supported as a regular architecture: there is no official kernel and no Debian installer for i386 systems

[...]

Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware.

@ everyone recommending debian: it no longer supports 32 bit x86 machines: https://www.debian.org/releases/trixie/release-notes/issues.html#reduced-support-for-i386

i wouldn't recommend debian since they've dropped 32 bit support in trixie, their latest release. the previous release, bookworm, still supports 32 bits archs, but it eol's less than a year from now