BaumGeist

I'll justbuse this excuse to repost my thoughts from the other threas https://lemmy.ml/comment/8358568

Should you ignore any give AI? Yes.

Can you? Also yes. Except the one your employer gets duped by.

Should you ignore the technological revolution that is Machine Learning Algorithms in general? No, not if you're willing to use other tech anyway despite its negative impact on privacy.

Can you? Also probably no, not if you want to eat.

Has AI affected my job? No, not yet. Well, not directly, although now every vendor uses AI to deal with customer service. If I worked at a larger company in my field, they'd probably include AI somewhere in the process.

My thoughts on it all: let's use the correct descriptor, Machine Learning Algorithms, since "AI" is just a marketing term to generate hype. I like MLAs, they're a neat tool and cool toy. It's also possible to own and run your own on your own PC in the privacy of your own home. Do that. Run the models, generate conrent, learn how to use the tool, learn the CS and math theory behind it, understand it, have fun. Be a scientist, learn by doing, get your hands dirty, understand that which you fear. Oftentimes our fears really just boil down to our lack of understanding.

We're in a painful growth stage rn. Operators are stillbtesting boundaries, and those of us affected are trying tonfind ways to reassert those boundaries. Whether it's enhanced tracking algorithms, harvesting data for training, or stealing intellectual property, it's all boundary testing. Give it a few years, and there will be more compromise and it will seem more mundane to see MLAs in the wild. So it's best to make peace with them now than to be that boomer that still refuses to learn how to use the internet.

Or if you prefer the privacy-oriented incentives: it's called "Adversarial Machine Learning" and it's cool as fuck. Sometimes it's about figuring out how to craft inputs to exploit a MLA, other times it using your own MLA to fuck with someone else's.

The point is: you don't learn anything by sitting around pontificating, you learn by engaging with things. If you want to learn about me or the users of c/Privacy, this is a great way. If you want to have your fears validated, this is a great way. If you want to grow as a person, lead your best life, and not be ruled by fear, then the only way is to learn about things you don't already understand even if—no—especially if it's things that are used to do evil.

I use i3 and don't have a mouse. Rn I'm using Alacritty because I want to keep things minimal. Is foot a good fit for my usecase?

My counterpoint is terminator. The logger plugin saved my ass a few times, it remembers the commands I ran and what their output was so I don't have to.

I guess it depends on if you're willing to take advantage of the extra features, or just want to do as little CLI as possible

TLDR: try them out, see what you like. It's a relatively easy switch-out, it's not like you're debating different web stacks.

I used zutty for awhile. It was fine and lightweight, but broke when I switched back from the nvidia drivers to nouveau (it's an older laptop that has no reason to milk every last bit of performance out of its gpu).

Now I'm using Alacritty. I like that I can configure it in a .yml file instead of needing to use my mouse, I like that it's written in Rust, I like that I got it to do transparency within minutes. I love the vi mode.

On my daily driver I use Terminator. I like the multiplexing/tabs/panes, the infinite scrollback when needed, and the logger plugin when needed. I might see if I can get it to do transparency tomorrow.

xterm has always treated me well too. Just a good, solid choice.

I guess my two biggest pieces of advice re: terminal emulators are

1. use tmux, it's extremely convenient once you get the hang of it. It's like any terminal-based text editor: hard to learn, but such a pleasure to use once you've got it down. Why waste time moving over to grab your mouse when you could just hit 2-3 keys?

2. configure the hell out of whatever you pick. It doesn't feel comfortable, like it's your command line—in the same way that it's your bed, or your chair, or your computer—until you've configured it. After you do, it just feels comfortable. Change the color scheme to all custom colors, change the font, change the shell, change the sounds, change the cursor blink rate, disable cursor, disable animations, disable text output, enable scrollback, enable logging, enable transparency, enable autopilot, adjust the retro encabulator, fasten your seatbelts, eat your veggies, stay in school.

3. use transparency. There's just something so pleasant about something more than a solid color background.

"Hyperbolic" this, "logarithmic" that, I'm here to propose a radical new theory: all spheres are tasty, your mouth just isn't big enough to have the right tastebuds for the larger ones

stable ✅
technically comparable to Ubuntu ✅
not related to IBM ✅
doesn't feature snaps ✅
KDE plasma ✅
not DIY ✅

WCGW

Isn't TW the rolling-release variant?

Maybe I'm just scarred from years of IT, but I would avoid recommending any rolling release to someone if they specified "stability" and were likely fresh out of the Ubuntu/Green Ubuntu kiddie pool.

Just assume that they mean they want to set it up with minimal user interaction and then never, ever, ever have to change settings again.

-it should be more or less stable, comparable to Ubuntu with or without LTS

Ubuntu was based on Debian, which touts its stability

-it should not be related to IBM to any way (so no fedora/redhat)

Debian has no afiliation to IBM, they're not even loosely part of each others' "partners" programs

-it should not feature snaps (no Ubuntu or KDE neon)

Debian doesn't use snaps (welcome to the greener side of the fence btw, fuck snaps)

-KDE plasma should be installable manually (best case even installed by default)

Debian uses KDE as one of it's default install options when installing the OS, and it can be installed later with tasksel (or by just getting all the packages if you want to do it the hard way)

-no DIY Distros

Debian has a barebones headless option, but the installer defaults (which come with the whole DE and oyher convenienve packages) are pretty user-friendly

In summary, I have no fucking clue what OS you should use.

P.S. newlines on lemmy are either done by using two spaces at the end of a line
and then pressing enter
(make sure your phone doesn't autocorrect/one of the spaces away like mine does) or by pressing

Enter twice (without the double spaces), so there's a

blank line in between

I might give Fedora a try then, finally see what's so yummy to all the users. Originally stayed away because I heard it was based of RHEL and didn't want an office-grade OS to do tinkering on.

Also, how about that "freedom," Red Hat?? what happened to FOSS????

I would reckon your original hardware also played a big part if it worked swimmingly this time around. I've installed half a dozen Debian- and Arch-based OSes on 3 different PCs and four different hypervisors at different times, and run a few more live CDs to boot, and my experience is that there is simply some hardware/emulated hardware that Linux in general refuses to play nicely with.

Debian does make it harder if there are no free drivers, but my non-free wifi cards (an intel and a broadcom) don't play nicely with any of the OSes' defaults

I'm just gonna copy from my other reply to ulterno

Once again overestimating beginners. Any OS installation is inherently not beginner friendly, and requires helping them, regardless of Debian/Arch/Nix/windows/Big Sierra Lion Yosemite III, Esq. Jr. MD or whatever Apple’s calling it nowadays.

I find Debians defaults during installation very beginner friendly, set and forget type stuff. It won’t use the hardware to full potential, but that’s up to advanced users to decided after they’re comfortable with the training wheels.