can’t even do video playback on VLC.

I remember back in the day when I downloaded the first divx file my K6-400 couldn’t smoothly play… I had been so used to thinking of that as a powerhouse coming from my Pentium 60, which was the first one I ran Linux on.

As bad as his victory was, it wasn’t even vaguely questionable.

Of the people that turned out, more of them voted for Trump, plain and simple, even by the popular vote without having to complain about the electoral college.

The only objective fact that gives an asterisk is he didn’t manage to get over 50% of the popular vote, but he still had the most of any candidate.

I’ve seen the mentions of “inconsistencies” and “Musk manipulated the votes” but a read of them seems about as credible as 2020 election denials.

To your point, at least for third party voters, only two states had enough third party participation to even theoretically move the end result: Michigan and Wisconsin. So even if every person that voted third party instead voted for Harris, she would have still lost 287:251 (though she would have won the symbolic victory of popular vote).

Of course, there’s more than just a single election in the country, so more important to keep active in down ballot races.

The biggest potential complaint of consequence would be non-voters/people who boycotted the election, but no way of knowing anything about it.

Still it is utterly obnoxious when someone seems to act all high and mighty that they didn’t vote for the lesser of two evils.

I’m so glad that the one that did win ended the genocide, got us universal healthcare, and decreased military spending… oh wait…

incorrect behavior that doesn’t even have the courtesy to throw an actual error.

To be fair, this can be said of C. A C executable only really forces a crash out when you royally screw up beyond the bounds of your memory. Otherwise functions just return a negative value and calling code that never bothers to check just keep on going.

Golang is similar, slightly mitigated that if you are assigning any return value from a function, you must also explicitly receive an error and you know full well that you are being lazy if you don’t handle it. Well unless you use a panic/recover scheme but golang community will skewer you alive for casually suggesting that and certainly third party libraries aren’t going to do it that way.

Could I write a compiler in C that does this check on a piece of Rust code?

Well yes, but that code has to be written in Rust. The human has to follow rules to give the compiler a chance to check things.

C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.

I don’t think that’s particularly more true of C than Rust or even Golang. In C you are frequently making function calls anyway for the real fun stuff. If you ever compile a “simplistic” chunk of C code that you think is obvious how it would compile to assembly and you open up the assembly output, you are likely to be very surprised with what the compiler chose to do. I’ve seen some professional C developers that never actually had a reason to fully understand how the stack works, since C abstracts that away and the implications of the stack don’t matter until you exceed some limitations.

Technically any language runtime can end in a segmentation fault.

For some languages, in principle this shouldn’t be possible, but the runtimes can have bugs and/or you are calling libraries that do some native code at some point.

Unfortunately, the ecosystem around github has evolved so that most folks centralize their testing and deployment code into being executed on github infrastructure. Frankly a perversion of the decentralized design of git.

Fortunately for my team, it doesn’t matter because our process requires stuff that can’t be done from github infrastructure anyway, so we have kept the automatic testing and deployment on premise even as github is the ‘canonical’ place for the code to live.

It is still valid to point out that “north of Antartica” is a silly phrase in context, even though it’s fine given the more specific Weddell Sea information. If you did want to help readers know the story based on a more well-known landmark, a less silly phrase would have been simply been “Weddell Sea, near Antarctica”.

Ironically, this is the result of various people at Microsoft at various times declaring “we need to scrap all this shit and start over”

There’s some logic behind each, but each time assumes they don’t have to do anything to port forward the previous approach to new UX standards as those will just die out. If it was roughly 13 screenshots of different developer experience, but consistent looking and behaving UI for the actual user, everyone could just shrug, maybe developers getting a bit grumpy about Microsoft’s inconsistency.

else: # not my list, it is ourlist

In context, one can consider it a bool.

Besides, I see c code all the time that treats pointers as bool for the purposes of an if statement. !pointer is very common and no one thinks that means pointer it’s exclusively a Boolean concept.

I occasionally check what various code generators will do if I don’t immediately know the answer is almost always wrong, but recently it might have been correct, but surprisingly convoluted. It had it broken down into about 6 functions iterating through many steps to walk it through various intermediate forms. It seemed odd to me that such a likely operation was quite so involved, so I did a quick Internet search, ignored the AI generated result and saw the core language built-in designed to handle my use case directly. There was one detail that was not clear in the documentation, so I went back to the LLM to ask that question and it gave the exact wrong answer.

I am willing to buy that with IDE integration or can probably have much richer function completion for small easy stuff I know to do and save some time, but I just haven’t gotten used to the idea of asking for help on things I already know how to do.

That’s been one of the things that has really stumped a team that wanted to go all in on some AI offering. They go to customer evaluations and really there’s just nothing they can do about the problems reported. They can try to train and hope for the best, but that likely won’t work and could also make other things worse.

I understand it fine, and it’s not just a packaging phenomonon, all sorts of software developers have stopped trying to have consensus on platform and instead ‘just ship the box’. 99% of the time a python application will demand at least virtualenv. Golang, well, you are just going to staticly build (at least LTO means less unrelated stuff comes along for the ride). Of course docker style packaging is bring the whole distro. I’ll give credit to snap and flatpak that at least allow packaging to have external dependency packages to mitigate it somewhat.

I’d say actually a bit of the opposite. Generally speaking we don’t need a new package manager or init system, and better hardware support is almost entirely a kernel concern (one might make an argument that the loose bits of key management and tpm2 tools and authentication agents could be better integrated for “Windows Hello” type function I suppose, but I doubt that’s what the meme had in mind.

Not really needing to reinvent the wheel on those, we got a variety of wheels, sometimes serving different sensibilities, sometimes any difference in capability went away long ago (rpm/dnf v. deb/apt).

The best motivation I can think of at this point is to make specialty distribution that is ‘canned’ toward a specific use case. Even then it’s probably best to be an existing distribution under the covers. I think Proxmox is a good example, it’s just Debian but installer made to just do Proxmox. You want to do automated installation? Just use Debian and then add Proxmox (the official recommendation), because they have no particular insight on automated deployment, so why not just defer to an existing facility?

The biggest conceptual change in packaging has been “waste as much disk as you like duplicating dependencies to avoid conflicting dependencies”, maybe with “use namespace and cgroup isolation to better control app interactions” and we have snap, flatpak, appimage, and nix very well covering the gamut for that concept.

For init, we have the easy to modify sysv init, or the more capable but more inscrutable systemd. I don’t see a whole lot of opportunity between those two sorts of options already.

Revolvers aren’t exactly known for being stealth… It’s just too much risk to desecrate a grave of someone who was dead before most of those officers were even born that most folks have never even heard of. At this point even the oldest on the force would be a generation removed from any officers that were working in 1969.

Where’s the beef?

For great justice

You are likely to be eaten by a grue?