BaumGeist

joined 2 years ago
[–] BaumGeist@lemmy.ml 4 points 3 days ago

was that translated into english from another language?

I love how they blended FAQ with meth-induced psychosis rambling.

I've gotta give them kudos for sticking to their very strict values, but holy hell is this hard to parse

[–] BaumGeist@lemmy.ml 9 points 4 days ago

Debian. Because it's the best about "Just Works" (yes, even moreso than Ubuntu, which I tried). It has broken once on me, and that was fixed by rolling back the kernel, then patched within the week.

BUT I'm also not a "numbers go up" geek. I don't give a shit about maxing out the benchmarks, and eking every last drop of performance out of the hardware; to me, that's just a marketing gimmick so people associate dopamine with marginally improved spec numbers (that say nothing about longevity nor reliability).

If you wanna waste something watching numbers go up, waste time playing cookie clicker, not money creating more e-waste so your Nvidia 4090 can burn through half a kilowatt of power to watch youtube in 8k.

(/soapbox)

My gpu is an nvidia 970 and my cpu is a 4th or 5th generation core i7. I just don't play the latest games anyway, I'm a PatientGamer, and I don't do multimedia stuff beyond simple meme edits in GIMP.

It has plenty of power to run VMs, which I do use for my job and hobby, and I do coding as another hobby in NVIM (so I don't have to deal with the performance penalty of MS Code or other big GUI IDEs).

It all works fine, but one day I'll upgrade (still a generation or two behind to get the best deals on used parts) and still not waste a ton of money on AAA games nor bleeding-edge DAWs

[–] BaumGeist@lemmy.ml 27 points 1 week ago

When does Debian update a package? And how does it decide when to?

These both can be answered in depth at Debian's releases page, but the short answer is:

Debian developers work in a repo called "unstable" or "sid," and you can get those packages if you so desire. They will be the most up to date, but also the most likely to introduce breaking changes.

When the devs decide these packages are "stable enough," (breaking changes are highly unlikely) they get moved into "testing" (the release candidate repo) where users can do QA for the community. Testing is the repo for the next version of debian.

When the release cycle hits the ~1.5 year mark, debian maintainers introduce a series of incremental "freezes," whereby new versions of packages will slowly stop being accepted into the testing repo. You can see a table that explains each freeze milestone for Trixie (Debian 13) here.

After all the freezes have gone into effect, Debian migrates the current Testing version (currently Trixie, Debian 13) into the new Stable, and downgrades the current stable version to old-stable. Then the cycle begins again

As for upgrades to packages in the stable/old-stable repos: see the other comments here. The gist is that they will not accept any changes other than security patches and minor bug fixes, except for business critical software that cannot just be patched (e.g. firefox).

[–] BaumGeist@lemmy.ml 2 points 1 month ago (1 children)

those still require root, they just don't explicitly say so. They still pop up with a password prompt

[–] BaumGeist@lemmy.ml 3 points 1 month ago

Jump ship. If you can make do without windows, do so. It takes away so much of the frustration, and you just learn to let it go when devs won't make linux-compatible binaries: after all, it's basically them telling you they need to be able to spy on you, so why use their app?

[–] BaumGeist@lemmy.ml 6 points 1 month ago (1 children)

The point of security isn't just protecting yourself from the threats you're aware of. Maybe there's a compromise in your distro's password hashing, maybe your password sucks, maybe there's a kernel compromise. Maybe the torrent client isn't a direct route to root, but one step in a convoluted chain of attack. Maybe there are "zero days" that are only called such because the clear web hasn't been made aware yet, but they're floating around on the dark web already. Maybe your passwords get leaked by a flaw in Lemmy's security.

You don't know how much you don't know, so you should be implementing as much good security practices as you can. It's called the "Swiss Cheese" model of security: you layer enough so that the holes in one layer are blocked by a different layer.

Plus, keeping strong security measures in place for something that's almost always internet connected is a good idea regardless of how cautious you think you're being. It's why modern web-browsers are basically their own VM inside your pc anymore, and it's why torrent clients shouldn't have access to anything besides the download/upload folders and whatever minimal set of network perms they need.

[–] BaumGeist@lemmy.ml 14 points 1 month ago (1 children)

image editing

imagemagick for basic transformations/compression/conversions, CLI (locally hosted) AI for the shops

[–] BaumGeist@lemmy.ml 5 points 1 month ago

Debian Testing has a lot more current packages, and is generally fairly stable. Debian Unstable is rolling release, and mostly a misnomer (but it is subject to massive changes at a moment's notice).

Fedora is like Debian Testing: a good middleground between current and stable.

I hear lots of good things about Nix, but I still haven't tried it. It seems to be the perfect blend of non-breaking and most up-to-date.

I'll just add to: don't believe everything you hear. Distrowars result in rhetoric that's way blown out of proportion. Arch isn't breaking down more often than a cybertruck, and Debian isn't so old that it yearns for the performance of Windows Vista.

Arch breaks, so does anything that tries to push updates at the drop of a hat; it's unlikely to brick your pc, and you'll just need to reconfigure some settings.

Debian is stable as its primary goal, this means the numbers don't look as big on paper; for that you should be playing cookie clicker, instead of micromanaging the worlds' most powerful web browser.

Try things out for yourself and see what fits, anyone who says otherwise is just trying to program you into joining their culture war

[–] BaumGeist@lemmy.ml -1 points 2 months ago

You intentionally do not want people that you consider “below” you to use Linux or even be present in your communities.

No, but I do want my communities to stay on-topic and not be derailed by Discourse™

Who I consider beneath me is wholly unrelated to their ability to use a computer, and entirely related to their ability to engage with others in a mature fashion, especially those they disagree with.

Most people use computers to get something done. Be it development, gaming, consuming multimedia, or just “web browsing”

I realize most people use computers for more than web-browsing, but ask anybody who games, uses multimedia software, or develops how often they have issues with their workflow.

(which you intentionally use to degrade people “just” doing that)

No I don't. Can you quote where I did so, or is it just a vibe you got when reading in the pretentious dickwad tone you seem to be projecting onto me?

But stop trying to gatekeep people out of it

I'm not, you're projecting that onto me again. If you want to use Linux, use Linux. Come here and talk about how you use Linux, or ask whatever questions about Linux you want. If you don't want to use Linux, or don't want to to talk about Linux, take it to the appropriate community.

If keeping communities on-topic and troll-free is "gatekeeping," then I don't give a fuck how you feel about it.

[–] BaumGeist@lemmy.ml -3 points 2 months ago (2 children)

I don't think we do, but that's a feature, not a bug. Here's why:

  1. There was a great post a few days ago about how Linux is a digital 3rd Space. It's about spending time cultivating the system and building a relationship with it, instead of expecting it to be transparent while you use it. This creates a positive relationship with your computer and OS, seeing it as more a labor of love than an impediment to being as productive as possible (the capitalist mindset).

  2. Nothing "just works." That's a marketing phrase. Windows and Mac only "just work" if the most you ever do is web-browsing and note-taking in notepad. Anything else and you incite cognitive dissonance: hold onto the delusion at the price of doing what you're trying to do, or accept that these systems aren't as good as their marketing? The same thread I mentioned earlier talked about how we give Linux more lenience because of the relationship we have with it, instead of seeing it as just a tool for productivity.

  3. Having a barrier of entry keeps general purpose communities like this from being flooded with off-topic discourse that achieves nothing. And no, I'm not just talking about the Yahoo Answers-level questions like "how to change volume Linux????" Think stuff like "What's the most stargender-friendly Linux distro?" and "How do we make Linux profitable?" and "what Linux distro would Daddy Trump use?" and "where my other Linux simping /pol/t*rds at (socialist Stallman****rs BTFO)???" Even if there is absolutely perfect moderation and you never see these posts directly, these people would still be coming in and finding ways that skirt the rules to inject this discourse into these communities; and instead of being dismissed as trolls, there would be many, many people who think we should hear them out (or at least defend their right to Free Speech).

  4. Finally, it already "just works" for the aforementioned note-taking and web-browsing. The only thing that's stopping more not so tech-savvy people is that it's not the de facto pre-installed OS on the PC you pick up from Best Buy (and not Walmart, because you want people to think you're tech-savvy, so you go to the place with a dedicated "geek squad"). The only way it starts combating Windows in this domain is by marketing agreements with mainstream hardware manufacturers (like Dell and HP); this means that the organization responsible for representing Linux would need the money to make such agreements... Which would mean turning it into a for-profit OS. Which would necessitate closing the source. Which would mean it just becomes another proprietary OS that stands for all that Linux is against.

[–] BaumGeist@lemmy.ml 3 points 2 months ago

1337 case = k3wlf1l3n4m3

[–] BaumGeist@lemmy.ml 0 points 2 months ago (3 children)

Nano is notepad, but with worse mouse integration. It's Vim/Emacs without any of the features. It's the worst of both worlds

If you want ease, just use a GUI notepad. If you want performance boosts, suck it up and learn Emacs or Neovim

 

Finally, another web engine is being developed to compete with Chromium and Firefox (Gecko), and they're also working on a browser that will use it.

Here's the maintainer talking about the current state of the project, and a demo of the current functionality

 

I occasionally see love for niche small distros, instead of the major ones...

And it just seems to me like there's more hurdles than help when it comes to adopting an OS whose users number in the hundreds or dozens. I can understand trying one for fun in a VM, but I prefer sticking to the bigger distros for my daily drivers since the they'll support more software and not be reliant on upstream sources, and any bugs or other issues are more likely to be documented abd have workarounds/fixes.

So: What distro do you daily drive and why? What drove you to choose it?

 

It's the series finale for our friend Plague Roach. Big props to Drue for all the work he's put into this project

Here's the full series playlist on youtube

 

As a user, the best way to handle applications is a central repository where interoperability is guaranteed. Something like what Debian does with the base repos. I just run an install and it's all taken care of for me. What's more, I don't deal with unnecessary bloat from dozens of different versions of the same library according to the needs of each separate dev/team.

So the self-contained packages must be primarily of benefit to the devs, right? Except I was just reading through how flatpak handles dependencies: runtimes, base apps, and bundling. Runtimes and base apps supply dependencies to the whole system, so they only ever get installed once... but the documentation explicitly mentions that there are only few of both meaning that most devs will either have to do what repo devs do—ensure their app works with the standard libraries—or opt for bundling.

Devs being human—and humans being animals—this means the overall average tendency will be to bundle, because that's easier for them. Which means that I, the end user, now have more bloat, which incentivizes me to retreat to the disk-saving havens of repos, which incentivizes the devs to release on a repo anyway...

So again... who does this benefit? Or am I just completely misunderstanding the costs and benefits?

view more: next ›