AdamBomb

joined 1 year ago
[–] [email protected] 5 points 17 hours ago (1 children)

Agree with many others here. Also: Aliens, Terminator 2, True Lies, Bad Boys, The Naked Gun, Top Secret!, Hot Shots: Part Deux, Deadpool 1-3

[–] [email protected] 4 points 1 day ago (4 children)

Who is the first one?

[–] [email protected] 6 points 1 week ago

So, iPhones retain their value better?

[–] [email protected] 11 points 1 week ago

I bought music on cassette and again on CD, but never on 8-track.

[–] [email protected] 2 points 3 weeks ago

I've been using Windows personally and professionally since 3.1, and Windows 11 was the last straw that finally got me to jump over to Linux for my home PC. I hate what Windows has become but I've got a lot of history with it. My experience with Linux (Mint FWIW) has been as smooth as it ever was in Windows, neither of which was perfect. I'm a definite convert from Windows and would encourage most people to consider taking the leap themselves.

I gotta disagree with you about modern Powershell and terminals in Windows, though. Good terminal? Windows Terminal has been around for years now. It's fast and functional. Whether Powershell's parameters are "sane" is probably a matter of taste, but I'm definitely willing to stick up for its usability. Yes, the parameter names are much more verbose, but they all get tab completion out of the box, and you don't have to type the full names at all, just enough of the start of the name to be unambiguous. For personal automation scripts, I think Powershell is way ahead of Bash. Parameters get bound automatically without needing to write for/case loops with getopts. You can write comments at the top of the file that automatically get integrated into Powershell's help system. Sending objects through the standard pipeline means you spend a lot less time and code just parsing text.

[–] [email protected] 3 points 3 weeks ago

Wait, this is for a Raspberry Pi? I thought we were talking about Linux as a desktop OS. You wouldn’t run Windows on a Raspberry Pi, so while I’m sorry you’re having trouble with your Pi’s fans, I don’t see how that’s relevant to the merits of Linux as a desktop OS.

[–] [email protected] 4 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

Is that supposed to be a real example? It’s just that fans are controlled by the BIOS, not the OS, so fixing a fan problem would usually involve either updating your firmware, which I have never seen done via a terminal command, or changing a BIOS setting, which could involve rebooting and holding a key like F2 to enter the BIOS settings menu (not Linux, usually a quasi-graphical mouse-driven UI) to change something there.

[–] [email protected] 7 points 3 weeks ago (6 children)

I really don’t understand the objection to using a terminal to get things done. It’s just a window that you can type text commands into. You don’t even have to come up with the commands on your own, you find the ones that solve the problem on the internet, copy and paste, and boom problem fixed. How is this different from looking up a solution to a Windows problem that walks you with a series of pictures through using Regedit or Group Policy Editor, only instead of pasting text into a terminal, you have to click through dozens of menus, trees, and tabs to find the setting you need to change? You’re still looking up solutions online in either case, but the Windows solutions require navigating windows with dozens of mouse clicks versus copying and pasting some text in Linux.

[–] [email protected] 7 points 1 month ago (2 children)

Meh. It’ll still have all the weaknesses of other LLMs.

[–] [email protected] 3 points 2 months ago

Sure, let a text generator try tactics

[–] [email protected] 2 points 2 months ago

Dean, you gotta try this! It feels like a guy with a fever is yelling at my junk!

[–] [email protected] 1 points 2 months ago

Reading a book Drinking tea — not just as a replacement for coffee; it has a calming effect Petting my cats Exercise lets me expend nervous energy and leaves me relaxed

view more: next ›