I mean, you’re free to continue using your crescent wrench as a hammer if you find it drives nails for you decently well and you are comfortable using it that way. But it was neither designed with that purpose in mind, nor does anyone expect you to use it that way, so no one will be writing how-to guides on it.

A Post-It and a pencil, usually.

Not because “app bad” or “return to monke” or anything like that. Mostly because if I stow the note in a dedicated app, that somehow just makes me less inclined to write it down and read it later.

A scrap of papersticking out like a sore thumb on my desk or burning a hole in my pocket? I’m going to be cognizant of that all day long. But an obscure text file chilling in a disused part of my phone, or a txt file lost in the shuffle of random shit on my PC? Outta sight outta mind.

I also find all digital input schemes to be frustratingly less flexible than physical paper. Provided I have a writing utensil on hand that is functional (not always a given, granted) it is trivial to put anything I want on a note. Write anything I want. Draw diagrams. Underline or strike text. Write some things larger or heavier than others. All of these things are possible in note taking apps, but they come with the idiosyncracies of needing to know the selection techniques and menu options to activate them. In this way they’re all death by a thousand tiny annoying cuts for me.

I even had a smart phone with a built-in stylus for a good long while. It definitely extended the things you could do with ease, but it was a far cry from a pencil.

The only thing a note taking app can do in my mind that paper can’t is yell at you with a loud noise at a pre-programmed time. If I need one of those, I just set an alarm in my clock app.

I live in the US and I consider it unusual to fly more than once every two years.

I always hear this statistic on how proper zipper merging increases traffic flow rate over no strategy at all, and I simply do not understand how it helps.

They keep pointing to how much of the upstream second lane is “wasted”. But like, from a strict perspective of flow rate, is it really?

The bottleneck restricting flow is the reduced speed single lane. Put a vehicle counter on it. Assuming no one wastes time getting through whatever funnel point there is, this flow is consistent. The same number of cars passing at the same speed are getting through regardless of whether the zipper point was a few cars back or ten kilometers back. Unless I can hear an explanation on how zipper merging changes this I remain unconvinced.

Zipper merging still has unquestionable advantages that are obvious to glean, of course.

Putting the merge point as close to the blockage as possible minimizes the time spent in the shared lane. Flow is the same, but the overall time spent in the jam is averaged over all drivers.

That “wasted lane” does not, as far as I can tell, improve flow. But it does improve storage. If cars are piling up at the choke point, utilizing the full extra lane keeps the pilup from backing up as far down the road, reducing potential domino effects through the road system.

Zipper merging is fairer to all vehicles by promoting a FIFO processing order. No one in the closed lane gets screwed, everyone gets through in roughly the order they showed up.

It has lots of advantages, and is clearly the winner, but I fail to see how increased flow is one of them.

Of course, I’m making a lot of assumptions about perfect behavior of drivers, while this statistic is supposedly real-world empirical data. That suggests there are significant inefficiencies in real-world human driving, and that the zipper merge addresses them somehow. But I can’t fathom what those are or why zipper merging is relevant to them.

I just got home from a 12 hour day of work. This has been my entire week.

Help.

For work, it’s usually IDE on the right (my larger screen) and a live build of the thing I’m working with on the left (a laptop screen). Though it varies a lot throughout the day. Primary screen gets the app that needs most scrutiny, small screen gets auxilliary things like passive communication apps or reference materials.

For home use, where I have two monitors of equal size, it’s usually Discord on one screen and a web browser on the other. Comms on the left and active task on the right.

I don’t see a use case in my workflow for a third screen, especially not one that is a weird size or is in portrait orientation. But if one was simply bestowed upon me, I’m sure I’d find something to do with it sooner or later. There was a time where I though two monitors was overrated, I’m sure I can adapt my opinion again for 3+.

As an American who was raised Lutheran, who was taught a bunch of Romance-Euro-centric world history in school, I always considered Roman Catholic to be the “default” flavor of Christianity. Protestantism in all of its forms are hard forks. It’s in the name, even–the Roman Catholic church is what Protestants are “protesting”.

To unironically “-and Zoidberg” Catholicism out of Christianity while leaving Protestant flavors included feels completely backwards. I’ve never heard anyone do it.

But if I did, I could only assume it was due to some No True Scotsman bullshit. “Only we practice the correct way. Everyone else isn’t just interpreting it differently, but interpreting it wrong.” Sounds like an Evangelical line of thought to me.

it’d be poor style to put more than one statement on a line

Unlike Python, most languages do not endorse a specific concept of style. You’re free to dabble in all the bad style choices you like, on the off chance that once in a blue moon they prove to be situationally useful.

As a very strong believer in Danny DeVito’s quote, “When I’m dead, just throw me in the trash!”, if any medical party is even remotely interested in dumpster diving for my parts when I’m done with them, they can have 'em. Better than throwing them in a box and taking up land in a cemetary. The less of my remains uselessly taking up space on this planet after death, the better. If I get my way upon my demise, anything they don’t take is going into the incinerator anyway.

The exception would be high-paid remote work, I guess. But with the reputation that corpos big enough to field those salaries have been recently building, going mask-off with no warning for no reason and asking employees to start filling desks again, I don’t know if I’d risk it.

City. Around 100k is the comfortable size.

Not like I require the city’s wider array of amenities all that much. I will still be spending 97% of my time at work or at home.

But if I lived in a small town again (born and raised in a town of <8,000), that extra 3% of the time I wanted to go out I’d have to remind myself, “Oh yeah, I live in a dead end town in the middle of nowhere that services none of my personal interests,” and that 3% would rapidly become 0%. I’d live fine with that, but eh. Why take a strict net loss when I can simply not?

The walkabiity and community arguments for small towns are complete non-factors for me, seeing as I go basically nowhere and talk to basically no one. And I’m not persuaded by the cost of living argument for small towns, since lower rent would be almost equally counterbalanced by lower salary opportunities.

Finally found out why I couldn’t renew my Let’s Encrypt cert.

Did you know fresh installs of Debian Testing come with firewalld installed and enabled to auto-block all incoming connections? Me neither!

I just click the litte nag icon in my taskbar whenever I notice it.

Since I’m on Debian Testing that is often daily. But it varies. If I don’t look at that part of my screen that day, w/e.

I thought I turned on auto update so it would just do it on its own. But it didn’t work for whatever reason. Sigh… Linux moment. There is an answer, surely, but the cost of debugging it outweighs my patience. Typing in my password an extra once(ish) a day is fine, I guess.

Edit: Just realized this is the Arch community. D’oh.

The only difference between a novice and a professional is that a professional checks what they are copying to understand it first before allowing it into their codebase.

Novices copy code to avoid having to understand it. Professionals copy code to avoid reinventing the wheel.

Getting static shocked by the TV screen.

A lot of folks blame this on kids simply not wanting to go outside anymore. But I believe a significant dimension to it also lies in the fact that the world is a lot more hyper vigilant about punishing things like trespassing, loitering, hooliganism, and the like.

The woods? Whose woods? Someone owns that land. Are they gonna call the cops on you if they notice you’re in there? Do they not want you damming up their creek? Is that going to be considered vandalism? Do they not want to be liable if you injure yourself on their property? All questions that probably aren’t in a kid’s head, but I imagine would be on a modern parent’s. The safety risks are high. Always were, that’s not new. But the legal risks are new.

And yeah, it’s not like getting in trouble for these sorts of things didn’t happen back in, say, my dad’s childhood. But I’d wager my dad would have gotten picked up by cops in his youth and sent off with stern tut-tut by the local sheriff for being just another incident of rowdy boys being boys, while my kid (if I had one) would be far more likely to make it out with a criminal record if they’re old enough, or trigger a lawsuit against me for my negligence if they aren’t.

Briefs. Actual support. The singular function underwear has.

Boxers are just commando with extra steps. Utterly pointless.

I consider all enlightened boxer brief centrists to be strictly in the briefs camp as boxer briefs are just briefs with leg extensions.

It would have been Fucking, Austria. But it finally broke under the pressure and was renamed. I have not dedicated any brain cells to remembering what exactly its new name is, which I guess is the intended effect.

What’s a FOSS pword manager

There are probably more that these two out there but the two I know of that fit this bill are Bitwarden and KeePass. The latter comes in two flavors, the original KeePass that kinda looks like shit and tries to stay lean and defer niche features to plugins, and the fork KeePassXC that tries to give it a sleeker UX with more features natively baked-in. I will refer to both simply as “KeePass” for the rest of this comment.

that is easy to use

“Easy to use” is relative. If you’re savvy enough to know what FOSS software even is, to care about using it, and to find your way onto an experimental platform like Lemmy to ask about it, I’d say youre more than capable of handling either of the above choices with ease.

reliable, likely to be around and working in 5 years

I’d wager that on both Bitwarden and KeePass.

and won’t leave me feeling shit up a creek if my phone dies or I’m using a public terminal with software installation restrictions

Bitwarden offers free cloud hosting and a web interface. As long as you have access to a browser and an Internet connection, you have access to your Bitwarden key store.

KeePass is offline-only and requires specialized client software to read its key store file format. Though, since all it is is a file, you can use simple and straightforward methods to make it accessible wherever you need it. Copy it to a flash drive. SCP it between devices. Put it on a cloud service like Dropbox. You have options. It’s just up to you to use them.

Bitwarden also lets you save locally stored files and manage them like KeePass, if you’re into that.

Honestly, since each can be made to more or less behave like the other, which one you pick largely comes down to taste. Bitwarden is more turn-key if you want cloud hosting, KeePass makes you work for it. Bitwarden is a company providing a premium service you can buy, while KeePass is a completely free project funded only by good will donations.

I prefer KeePassXC, personally.

I replied to that thread.

OP was claiming to be working on a static HTML-serving search engine. They suggested that because it’s just HTML and CSS, and that interested parties can use Inspect Element to read the network requests, that it constituted “open source”.

Commenters then got on his case about not open sourcing the server backend. OP defended that choice saying they didn’t want a competitor taking their code and building a company off of it that would “drive [them] out of business”. Uh-huh. So, proprietary software, then. Bye.