C’mon, so lame. I mean, I agree with the comments saying that being obsessed with a war is dumb, but obviously the right answer would be the Thirty Years War. Far more factions, more casus belli, more fights. Plus, it bolstered German nationalism, which led pretty directly to the Great War, which led to World War II, so those are technically part of its history.
But maybe I’m biased, because my surname originated in the Huguenot diaspora?
It’s the other way around. Residential properties are used as investment vehicles, because it’s profitable. It’s profitable because the prices are high and rising. The prices are rising because of the housing crisis, which is caused by lack of supply. Lack of supply is caused, in large measure, because of restrictive zoning.
If there were a glut of housing on the market, prices would crater, and it wouldn’t be profitable, investors wouldn’t buy residential properties. They could still try to buy up all of the properties, and create artificial scarcity that way, but the idea is to make a profit, not just collect residential property for the sake of having it. As soon as they started selling or letting properties in large numbers, supply would rise and prices drop again.
It’s the artificial scarcity mandated by law that’s driving the high prices. This explanation is confirmed by many cities, like mine, that have a very low rate of private equity ownership, and still have a housing crisis.
“Carbrain” is a real mental disorder, though. How else do you describe somebody who looks through a windshield and sees a long line of idling cars into the distance, and thinks, “clearly the problem here is bicycles.”
(e: improved punchline)
Of course, I drive (I kind of have to because of the way our landscape is designed to mandate it), so I have to include myself in this. It’s well-established by psychological research that drivers have very little empathy for other drivers, but especially little empathy for bicyclists and pedestrians, viewing them as less-than-human annoyances. Add in that driving in a city requires that one subject other people to the noise, the pollution, the danger, and the arrogation of space by one’s vehicle, and you pretty much have to suppress any empathy for the people who live there, otherwise it’d be unbearable to do. That lack of empathy is textbook sociopathy, induced by the activity of driving. It just happens to be widely normalized, but we still see posts even here on Lemmy from new drivers who are struggling to suppress those thoughts.
Putting the shoe on and loudly announcing that it fits?
Getting trapped in a building with a mass shooter is something very, very unlikely. On the other hand, I face the danger of death by automobile at least twice a day, on my ride to work, and my ride home. More, if I go other places. It may seem not that bad because it’s so normalized. Dying in or under the wheels of a car is something that happens to people every single day, and it barely rates a mention in the local news. Sometimes the victim doesn’t get even get a name. By contrast, the stochastic nature of mass shootings makes them scary, like plane crashes or terrorist attacks, the natural order of things is upended. Death is death, though, and I wouldn’t be less dead if it were a texting driver rather than a gunman.
And the texting driver is a whole hell a of a lot more likely. So, yes, it’s entirely logical that I’m afraid of that. Not being able to understand and denying that fear is exactly the kind of car-induced sociopathy that I’m talking about.
Throwing insults is not a discussion, by the way.
You don’t understand what fear is like?
They’re not the same. This is privilege speaking, I know, but gun violence mostly occurs between people who know each other. I’m not in those circles or neighborhoods, so only the occasional mass shooting might affect me.
But cars? They’re omnipresent. There’s a steady stream of them in front of my home, so I can’t avoid the danger. My life is threatened by cars every damn day, and my quality of life degraded by them. And you can’t tell me that driving a car around a city is anything but sociopathic disregard for the well-being of others, because that’s what it amounts to.
Cars as bad as guns? No, they’re worse.
An automobile, at the end of the day, is a luxury item. A toy. Humanity existed for most of its history without cars, and even today, you can get to work or the grocery store without one. (Granted, often not easily, but that’s only because we’ve made it difficult to get there any other way. But making it difficult was a deliberate policy choice designed to exclude poor people.) One could argue that the automobile is an anti-tool, as its use is making our lives materially worse (traffic violence, health impacts, pollution, ecosystem destruction, climate change, the burden on government and personal budgets), but that ignores a car’s major function as a cultural identity marker, and for wealth signaling. We humans value that a lot. Consider, as but one common example, the enormous pickup truck used as a commuter vehicle, known as a pavement princess, bro-dozer, or gender-affirming vehicle.
In that way, they’re exactly the same as firearms, which are most often today used as a cultural identity marker. (Often by the same people who drive a pavement princess, and in support of the same cultural identity.) Firearms are also also luxury toys in that people enjoy going to the firing range and blasting away hundreds of dollars for the enjoyment of it. But beyond that, the gun people have a pretty legit argument, too, that their firearms are tools used for hunting and self-defense. They are undeniably useful in certain contexts, and no substitute will do. One certainly wouldn’t send mounted cavalry with sabers into war today.
Has it? My complaints are: I have to use VPN software for work that replaces /etc/resolve.conf with a symlink to another location, one that sandboxed snaps can’t access. There’s no way to grant them access; the “slots” that you can connect are fixed and pre-defined. You can’t even configure the file path; it’s defined right in the source code. Not even as a #define, but the string literal “/etc/resolve.conf”. That seems like poor practice, but I guess they’re not going for portability.
Also, I have /usr and /var on different media, chosen for suitability of purpose, and sized appropriately. Then, along comes snap, violating the File Hierarchy Standard by filling up /var with application software.
Minor annoyances are the ~/snap folder, and all of the mounted loopback filesystems which make reading the mtab difficult.
It depends how you define it. I first installed Slackware at work on a retired IBM PS/2 in '94 or '95, because somebody was working on MicroChannel bus support. (That never materialized.) Later, we checked out Novell Linux Desktop, maybe Debian, too. At a later job, we had some Red Hat workstations, version 5 or 6, and I had Yellow Dog Linux on an old Power Mac.
At home, I didn’t switch to Linux until Ubuntu Breezy Badger. It was glorious to install it on a laptop, and have all of the ACPI features just work. I had been running FreeBSD for several years, NetBSD on an old workstation before that, and Geek Gadgets (a library for compiling Unix programs on Amiga OS) before that.
Only if you have installed the correct license file.
Ah, yes, I come at it from the boat angle, so I didn’t think of the grid-tie AIO inverter being the cheaper option! It might be less expensive, then, to simply add in a wind charge controller. There’s no issue with running two charge controllers in parallel to the same battery bank. They sense state-of-charge by voltage, so if one is running, the voltage is high and the other backs off. I think that makes the system slightly less effective, but probably not enough to notice.
Pardon if this is a naïve question, but the mention of hooking a turbine straight to the batteries makes me ask, why not just use a hybrid wind/solar charge controller?
One that Linux should’ve had 30 years ago is a standard, fully-featured dynamic library system. Its shared libraries are more akin to static libraries, just linked at runtime by ld.so instead of ld. That means that executables are tied to particular versions of shared libraries, and all of them must be present for the executable to load, leading to the dependecy hell that package managers were developed, in part, to address. The dynamically-loaded libraries that exist are generally non-standard plug-in systems.
A proper dynamic library system (like in Darwin) would allow libraries to declare what API level they’re backwards-compatible with, so new versions don’t necessarily break old executables. (It would ensure ABI compatibility, of course.) It would also allow processes to start running even if libraries declared by the program as optional weren’t present, allowing programs to drop certain features gracefully, so we wouldn’t need different executable versions of the same programs with different library support compiled in. If it were standard, compilers could more easily provide integrated language support for the system, too.
Dependency hell was one of the main obstacles to packaging Linux applications for years, until Flatpak, Snap, etc. came along to brute-force away the issue by just piling everything the application needs into a giant blob.
ZFS is more than just a filesystem, it’s a fully-integrated disk management system which replaces mdadm, LVM, LUKS, nfsd, rsync, as well as the filesystem. It’s great for NAS boxes and file servers, since you can give it a big pile o’ disks, and it slices and dices, and offers simple commands to create whatever volumes you need.
You have so thoroughly captured the Windows experience. Bravo!
As a long-time Linux user who had to dive into the Windows world after taking an admin job, this is such a bizarre thing to hear. So many how-to articles that I found to make a change to user-level Windows settings start with opening the Registry Editor. Technically, that’s a GUI program, but still a major challenge for the average user. On the admin side, the documentation and how-to articles are dominated by PowerShell scripts, because Microsoft has embraced the command line.
In my experience learning Windows 10 for my job, the results of searching for how to do something are: ‘click-this’ tutorials that don’t work because Microsoft changed something in the next edition, editing the registry, or PowerShell commands. The registry editing sometimes doesn’t work because Microsoft changed something. The PowerShell method is the way to go, because Microsoft has embraced the command line.
I make my guess that there are two factors:
The Baader-Meinhof Phenomenon (or frequency illusion If somebody has a chip on their shoulder about rude Linux users, the rude Linux users they see will be highly memorable.
People tend to get back the same energy that they project to other people.
My instance has a very laissez-faire policy, so it’s federated with almost everybody. My experience is the same; I’ve only ever seen self-aware mocking of the Linux-user attitude.