Especially these days. Current-gen x86 architecture has all kinds of insane optimizations and special instruction sets that the Pentium I never had (e.g. SSE). You really do need a higher-level compiler at your back to make the most of it these days. And even then, there are cases where you have to resort to inline ASM or processor-specific intrinsics to optimize to the level that Roller Coaster Tycoon is/was. (original system specs)
- 0 Posts
- 17 Comments
Joined 1 year ago
Cake day: November 13th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
3·2 months agoThank you!
I firmly believe this is how we wound up with tabs as a feature in the first place.
3·4 months agoSorry to hear about your friend. While I’m no doctor, that seems to fit the bill to me. I’ve known people that had other trauma when young, and yeah, maintaining healthy relationships seems to be the hardest thing for them. Your story reminded me of a lot.
Yes, but it’s a little worse than that. One might take that to mean environmental, congenital, or even genetic factors. But there’s more. Consider the role that trauma has to play here as it can directly cause arrested psychological development:
I mean, maybe if you bake a stone cold potato that was in the fridge and then cook it for two hours? But even then we’re probably talking about a handful of minutes at the most.
Which
car companybar did you say you work for?A major one.
I’ll preface this by saying this shady shit gets all my hate.
It’s tempting to opt for telematics/black box insurance because of the initial cheaper prices but the privacy violations and potential downsides make it not worth it.
The overall problem here is that human psychology tends to frame this difference as a loss not a gain. Given the choice, people will see the cheaper option as the baseline, and then ask “can I afford to pay more for privacy?” instead of affirming “my privacy is not worth this discount.”
Also, those of us that have paid for insurance without such a “discount”, are likely keenly aware of the difference. For new drivers, from now to here on out, the lack of past experience presents a new baseline where this awfulness is normalized. Competition between insurance providers won’t help us here since the “privacy free” option is still profitable and is enticing for new customers (read: younger, poorer). So it’ll take some kind of law, collective action, or government intervention to make this go away.
Have fun fighting with your insurance to get them to remove anything from your record. […] If I had spyware insurance they would’ve dinged me for it.
I think this is the bigger problem. If someone has the data an insurance company wants, you probably agreed to an EULA or signed something that makes their ownership, and its sale, legal. With the “yeah go ahead and use my data” option on the table, the machinery to do this without your knowledge is already in place. All the insurance provider has to do is buy the data from someone else. When the price is right, 1st party spyware isn’t required at all.
6·6 months agoa lot of devs love watching stuff like speedrunning
True, but some of them hate it. But with the growing presence of speedrunning friendly features in new titles (looking at you, Supergiant), I think that’s becoming less of a problem.
Either way, these “devs watch” reaction videos are fantastic.
They could save so much money by not mailing every day and hiring people to hunt me
At the scale these mailings are conducted, it all averages out into a net win for Spectrum. It suggests that enough people really do suck it up with the rate hike for some reason or another. Otherwise, they wouldn’t do it. Also, from their perspective, the wasted time, energy, and paper is all someone else’s problem.
1·10 months agoAs a bonus: also runs on my phone.
I’m starting to wonder if all that are symptoms of a company using information technology to it’s most powerful extent.
Services like Door Dash couldn’t exist at the current scale, speed, and service without the internet and highly capable phones/laptops/whatever in everyone’s home. It enabled this kind of gig economy service to come out of nowhere, build very rapidly, and disrupt the market before the law or even social norms could ever hope to step in. But as a consequence of all that, the owners cannot help themselves, and continue with their “Greed% speed run” of running a company straight to its conclusion. Every mistake, every error, every bad take, it’s all accelerated right alongside the good stuff. It’s like enshittification on amphetamines.
TL;DR: the author needs to do a better job of citing sources and building an argument.
The author’s argument from self-appointed authority tone aside, I dug into the only two verifiable pieces of evidence cited. These are almost impenetrable to the outsider, and even with plenty of coding experience behind me, I’m having to go deep to make sense of any of it. After all, sometimes, bugs and design decisions are the result of a best effort in the situation at hand and not necessarily evidence of negligence, incompetence, or bad architecture. There’s also something to be said for organizing labor, focusing effort on what matters, and triaging the backlog.
The original author really needs to pony up a deeper digest of the project, with many more verifiable links to back up the various quality claims. If anyone is going to take this seriously, a proper postmortem is a better way to go. Cite the version reviewed, link to every flaw you can find, suggest ways to improve things, and keep it blameless. Instead, this reads like cherry picking two whole things on the public bug tracker and then making unsubstantiated claims that’s a part of a bigger pattern.
My personal take on what was cited:
- I’m grossly unqualified to assess this codebase as a Wayland or GUI programmer, but work plenty in the Linux space as a cloud practitioner and shell coder.
- The first article smells like inadequate QA for cases like placing Wayland programs in the background, which is not typically done for GUI apps under normal usage (IMO).
- The second article is a two-line change that I suppose highlights how ill-suited C is for this kind of software. Developer chatter on the MR suggests that the internal API could use some safeguards and sanity checks.
- 162 open issues, 259 closed, oldest still open is five years old. Not great, but not terrible.
- None of this is particularly egregious, considering the age of the project and the use it enjoys today.
Links:
1·11 months agoJust don’t tell their investors who are clearly pushing to make it a social media hub.
Edit: it’s the second-to-last place I would ever consider for that purpose. Right after Venmo.
This is a good point. My interactions with the Fediverse over the last few months has been sublime. Maybe users here are just proportionally more active?
Numbers are nice, but they’re not everything. Yeah, we could onboard 2 billion lurkers, but how would that improve anything?
Honestly, I’m not 100% sure. I would bet that a modern compiler would just “do the right thing” but I’ve never written code in such a high performance fashion before.