That’s… a good point. When I make communities, I usually try to err on the side of more general rather than more specific (just because Lemmy doesn’t have quite the userbase of… that other site we never speak the name of), so in this case, I probably should have thought to name it in a way that limited it to just COVID.

But now, I’ve up and named the community. I’d be fine with making it clear in the sidebar that consciousness about the spread of other diseases is entirely welcome, but I don’t think I can change the name (like, the URL) of the community.

But, honestly, I’m also down with just making a whole new community and deleting this one. And, to be fair, I haven’t looked to see if a community like that already exists.

Oh sweet! Glad you got it solved!

So, just from what you’ve said, without getting more info from you, my guess as to what’s going on is that Windows has set things up to where it uses its own bootloader which isn’t set up to boot into Linux or chain-load your Grub2 or whatever Linux-capable bootloader.

And this F11 you’re talking about is probably the key your BIOS uses to let you into the BIOS configuration, yeah? And from there you can tell it to load Grub2 or whatever bootloader Mint set up when it was installed – the one that was nuked by Windows.

(I keep saying “Grub2”. It’s possible you selected something else like Syslinux or rEFInd or something when installing, but I think Grub2 is default for Mint.)

I think, just from some googling, what you’ll want to do, assuming the assumptions I’ve assumed above haven’t made asses out of anyone, is (in Mint with both SSDs plugged in):

>sudo grub-install <whatever your boot drive is -- something like /dev/sda or /dev/nvme0n1 or some such>
>sudo update-grub

(And you’ll need to replace the angle brackets part above with the actual drive name. sudo grub-install /dev/sda or whatever.)

I think that first one should tell your system to switch from the Windows bootloader (which… I don’t think can even boot Linux… I haven’t used Windows since XP, so I don’t know for sure) to Grub2 which is capable of booting Linux, and capable of asking you which OS you want on boot. The second command is just to ensure Grub2 is properly configured. (It probably is already, but it won’t hurt to make double-sure.)

If that doesn’t work, it’s likely your Mint install is set up with a different bootloader. If that happens, I’d say:

• Let us know any error message you get from the above commands.
• Let us know what behavior you’re seeing instead of the desired results. (Like, no change and it’s still booting straight into Windows? Now it shows an OS-selection menu but only Mint as an option? Something else?)
• Search in your package manager for “bootloader” and report back which bootloader it says is installed.

Good luck! Hopefully that gets you going, but if not, definitely let us know your results!

Followup question.

“As opposed to what?”

If everyone is “insane”, what would a “not insane” person look like if one hypothetically did exist?

All but you?

hack into any mobile phone

(Emphasas mine.)

Seems a bit hyperbolic.

Source? Like is there seriously a Star Trek series aimed at young kids coming?

Yeah, I know about the binary repositories. I’m running Gentoo as well (on one box with the intention to expand to other machines), but haven’t had occasion to use the official binary repositories yet.

I imagine I’d probably only ever use them if I wanted to install something temporarily. Install LibreOffice, view a file, uninstall. Just seems weird to have one package compiled with different USE flags than the whole rest of the system.

And, the compiler optimizations definitely aren’t why I use Gentoo. Probably more than anything, I’m sick of SystemD. And Gentoo feels a whole lot more “under my control” than Arch. (Arch is great for the most part, don’t get me wrong. I just like what Gentoo has to offer.)

I’m not RanzigFettreduziert, and I don’t know much about PopOS, but…

• Rolling release is awesome.
• Amazing documentation.
• Helpful user base. (The forums are great.)
• Does pretty much nothing that you don’t specifically tell it to. (Like, very little is installed without your express say-so, for instance.)
• Customizeable as fuck.
• Doesn’t making things harder by trying to hide the “hard parts” from you.
• Doesn’t take days to install Libreoffice like Gentoo.
• AUR is great for software that isn’t available in the official repos. (Always review the pkgbuild, but practically everything is there.)
• Very up-to-date (even cutting-edge) on everything.
• And surprisingly stable given how cutting edge it is. (That said, I’ve never run a keyword-unmasked system.)
• Definitely will teach you a lot.
• Very actively developed.

Downsides:

• Learning curve. (Definitely not as bad as, say, Gentoo, though.)
• You’d definitely have to get really comfortable with the command line. (Arguably as much a good thing as it is a downside.)
• The biggest exception to the “customizeable as fuck” bit is that you’re stuck with SystemD, which is practically a whole OS. (And Artix (Arch but with a choice of init systems) is… kinda janky last I tried it.)
• Support for non-x86 (like ARM, for instance) is abysmal.

It’s kindof the second-most hardcore OS out there after Gentoo. (Nobody actually uses LFS as a daily driver, so I’m not counting that for this.) It’s the sort of OS that will teach you a lot and let you get down in the guts. But also avoids a lot of the downsides of Gentoo by remaining a binary OS.

People are spending all this time trying to get good at prompting and feeling bad because they’re failing.

This whole thing is bullshit.

So if you’re a developer feeling pressured to adopt these tools — by your manager, your peers, or the general industry hysteria — trust your gut. If these tools feel clunky, if they’re slowing you down, if you’re confused how other people can be so productive, you’re not broken. The data backs up what you’re experiencing. You’re not falling behind by sticking with what you know works.

AI is not the first technology to do this to people. I’ve been a software engineer for nearing 20 years now, and I’ve seen this happen with other technologies. People convinced it’s making them super productive, others not getting the same gains and internalizing it, thinking they’re to blame rather than the software. The Java ecosystem has been full of shitty technologies like that for most of the time Java has existed. Spring is probably one of the most harmful examples.

What ever it is you’re smoking, stop smoking it.

Good stuff. If I’m being honest, I’ve kindof felt a bit “out of the loop” on general “news” since quitting Red…acted. I’m glad to see more news here, and Democracy Now! is a fantastic news source.

Not to say I only ever come to Lemmy for news. I do visit news sites sometimes, and Democracy Now! is one of my most preferred sources. Still, though, it’ll be good for DN articles to show up in my Lemmy feed.

TIL my taste in music is considered “neutral”. I think I’m insulted.

By George, I think OP’s got it.

“A friend”, huh?

I’ll let you him know when I figure it out.

I hate this whole article. It’s right, but I hate it.

A couple of quibbles, though.

The performance gains from decades of JVM optimization are insane. Garbage collection? Mature. Just-In-Time compilation? Rock solid. Cross-platform consistency? Still unmatched in many cases.

Bullshit. I can’t imagine how you can think this if you actually work with Java in “eNtErPrIsE”, customer-facing applications that receive more than a trivial amount of traffic. Java is the only garbage-collected language I’ve used where you have to tune cryptic parameters like -Xmx and -XX:MaxMetaspaceSize to make your application not fall over in prod. And in my experience, Java 21 seems to have made memory management worse at least in some ways.

Want a mature web framework? Spring Boot basically invented “Java, but not painful for web dev.”

Oh, Spring Boot is painful all right. It’s just that the pain is outsourced to the most senior dev. The more junior devs spend a few hours banging their heads against something “simple” that the Spring docs say should “just work” but doesn’t (just add a dependency here and an annotation there and viola; now your application makes your end-users breakfast), so they take the issue to the one developer on the team whose full-time job is to field these “intractable” issues because they’re the only person on the team who will bother to learn how to properly read a ./gradlew dependencies output or who is willing to point their debugger at Spring classes themselves and go look at the Spring source code for answers, or even who actually know what a DispatcherServlet is. The junior devs think Spring Boot makes things “not painful” because when Spring Boot make things really fucking painful they just give the problem to someone else, get back a one-line fix (“you didn’t put the @DefaultReverseButtholeRotoRooterFactoryDelegate annotation on your @Autowired member variable on line 86”) without having any understanding why it’ll fix the issue (Spring and Spring Boot aren’t supposed to be “understood”; they’re magic; you just slap it in your project and copy-paste shit from StackOverflow or god forbid Claude until it seems to work) and go on with their day.

What do you mean you “cannot scream”, exactly? In what way does the closest approximation to a “scream” you can do not qualify as a “scream”? Just pitch specifically? Can you sing higher than you can “scream”?

Or if it’s not specifically the pitch, and if it’s something you’d like to change, I might suggest you look into… well… learning. Search for “fry scream” on YouTube. It’ll take some practice, but it’s certainly a way to scream. And as a bonus, learning to do it “right” can avoid straining or injuring your voice.

I very much do not understand the question. I think you accidentally a word. I’m guessing you mean “why can I only scream when I sneeze”. But even that, I’m not sure I understand. Do you mean you can’t scream when you’re in the act of a sneeze? Or that you scream every time you sneeze and cannot prevent yourself from doing so? Both?

Was this post meant for the !shittyasklemmy@lemmy.ml community?

Just my guess here, but…

The desktop/laptop sort of form factor is associated in people’s minds with unlocked bootloaders. People expect to be able to install Linux on them if they want to. Tablets, game systems, and other sorts of consumer electronics, not so much. I’m thinking Microsoft will do what it can to push hardware manufacturers and the software industry as a whole more in the direction of the kinds of devices that consumers already expect to be locked down like tablets or game systems that are “streaming” game systems. And that way, the bootloader will prevent folks from switching to Linux.

“Nee Jabba no badda.”