gayhitler420

What will that money be doing?

how are the ostensible productivity gains from evs going to be used to help american workers?

it's hard to believe that the reduced demand for skilled tooling, die and machining labor will translate into some kind of gain for the communities and people that rely on that work to survive.

and we've seen how anemic reskilling efforts are and how the usual boilerplate response, "learn to code", is completely defunct with the combination of LLMs and the cheap overseas junior dev labor pool.

american conservatives are trotting out these arguments to appeal to people who feel like they're being forced to give up their lifestyle (driving cars with cheap gas), and materially are actually being heavily pressured to get evs without fully understanding the economics of this new class of Second Most Expensive Thing Most Americans Will Ever Buy, but that doesn't mean that the realities that appeal is built on aren't there.

there's a lot youre leaving out. I don't think it's on purpose, but one of the only ways that the korean war can be made to look like a soviet invasion is by conveniently leaving out everything that happened before the norths army crossed the 38th parallel.

korea was one nation and people before it was divided roughly along a line of latitude by two american officers with no input from those knowledgeable about korea or its history. one of those officers, dean rusk, has said that he would have done things differently if he knew that forty years before, the tsarist russians and japanese had discussed dividing korea along a very similar line.

They divided the peninsula because the idea among the allies was to reunify it five years or so after china's civil war ended and it was clear weather koreas only land border would be with the communists or the koumintang.

as the japanese retreated south, the korean people formed their own governing committees. the soviet forces integrated those committees into the provisional government, the american side integrated the collaborators from the japanese occupation into theirs. the north had a democratic election, the south became a military dictatorship.

both sides claim to have held elections, but while a majority of the north wanted to vote for kim il sung, the fighter who was an ally of the liberators that empowered koreans to kick out collaborators and do land reform, the souths election that would put syngman rhee in power were boycotted by the souths political parties and accompanied by what was reported on in even western papers as brutal repression. it's worth noting that one of the leaders of a prominent political party would be assassinated a little later.

there's plenty i'm glossing over, but the north didn't cross the 38th parallel out of the blue for no reason but to impose their evil communist brainwashing on the kindly people of the south. in the south, the repression of jeju island, the military uprising against the government in response to that repression and the bodo league massacre are the backdrop for the norths invasion.

now think about those circumstances and history for a second.

the americans divide your country along the same line the russians and occupiers wanted to use before. lets say youre in the north: maybe you don't trust these soviets, but they respect the peoples committees and theyre doing that land reform youve been wanting for decades. they're supportive of you expelling the japanese collaborators and things feel like they're getting better. how about if youre in the south? the americans put the collaborators back in charge, broke up the peoples committees and are putting the ever growing number of collaborators to work beating everyone into shape for the election.

when 30,000 koreans die on jeju island, there's a failed military uprising and a massacre of south korean communists, what would any right minded person do? of course the north crossed the made up line keeping them away from their countrymen in peril!

since i've written enough already i'll just address what you said about the state of the north being so bad: when and why was it so bad? why did it take a carpet bombing campaign and international blockade to make it so bad?

I’m sorry, but you’re deeply misinformed. I’m saying this not to start a fight, but in the hope that seeing it from someone outside hexbear (I’m banned from that instance!) will be received better.

What you’re saying is the us propaganda during and about the war after it ended. The consensus among even american historians stands in stark contrast to what youve posted.

I’m on mobile at the moment, so I can’t make the biggest post, but if you wanna know something in particular lmk and I’ll get to it as soon as I can.

Ty I’ve spelled his name probably every wrong way in the past.

Ty! That’s really good to know!

When systemd first showed up there wasn’t much parallelized init systems. People managing complex systems with many services may find the tools of systemd make their lives easier. Of course, nowadays all that complex multi service machine stuff is containerized and none of those containers run systemd 🤔

If I were gonna psychologize it, poettering and kay typify what the Linux user of the 0s felt when they actually looked at what windows of the time had going on under the hood. “Look at you, tla username, pathetic creature of twenty text files under a trench coat!”

The problem with that sentiment is that there’s an honesty to recognizing and accepting that you’re not too far removed from the z80 and it keeps you from believing all this computer stuff is more than it’s cracked up to be.

No one who’s happy with python also keeps a loaded gun next to the server for when it acts up and that’s the problem.

🫡

That’s horrifying. I was just writing from memory and resisting pulse for a few years after it was sort of the defacto standard.

There’s both runit and system6.

If you really want the short version:

Systemd was half baked literally when it came out and figuratively as an idea, so much so that there’s already a replacement for it in the works.

A longer version:

Systemd replaced the init script style of boot and process management, which had been in place for decades. init scripts were so simple they could be understood just by looking at the name: the computer is Initialized by Scripts. Systemd was much more complex and allowed many more tools to interact with the different parts of the computer, but people had to learn these tools. Previously all a person had to understand to deal with the computer was how to edit a text file and what various commands and programs did. After systemd a person has to understand how to use the dozens of invocations of systemctl and it’s variants and if they are dealing with a problem, —you know, the only reason a person would ever be dealing with initializing services— they gotta know what’s going on with the text files that systemd uses to run different commands and programs.

So a person who already understood what was going on might rightly say “hey, this systemd thing is just the same shit with different file locations and more to learn”.

People complain about the creator and maintainer of systemd, lennart poettering . Poettering is also the person behind pulseaudio, an powerful but complex audio management daemon in Linux whose name you only recognize because it’s caused you no end of trouble. Pulseaudio was also replaced relatively quickly by pipewire.

The argument could be made (and probably has) that poetterings work is indicative of the problems with foss developers working as employees of major companies with their job responsibilities inclusive of their foss projects. The developer in that situation has an incentive to make big sweeping changes, they’re being paid for it after all, instead of being more careful and measured.

When every big foss maintainer is trying to find a way to justify being paid for it, their projects are never done.

At least poettering is working for Microsoft, ruining windows now…

E: oh my god I forgot about the binary log files! So before (and now), the universal format for log files was plain text. You know, because it’s a log that’s text. Systemd uses binary log files that need a special tool to open and parse. So if you want to look through them on a computer without that tool you’re kinda screwed. Now systemd isn’t the only software package with binary log files, but many people have made the very persuasive argument that it’s not a trait to copy.

E2: actually spelled the man’s name right. Thanks @[email protected] !

In addition to all that @[email protected] said, implementing an am or fm receiver on an existing device is as easy as plopping down one of the existing bga chips that has an antenna input and an audio output. here’s one of the bigger ones that needs a killer 3mm x 3mm land pattern. It’s also only $1.79 or so, which is expensive for an ic, but in the context of a phone wouldn’t contribute significantly to the cost of the device.

The need for an 1/8” out would be the worst part because ironically, phone jacks suck for uhh… phones.