Google started work on Carbon due to the difficulty of getting the C++ standards committee to accept any real, fundamental changes to the language. If Google, a grandmaster at manipulating standards committees, couldn’t get something passed, I don’t foresee this proposal getting anywhere.
Null safety is orders of magnitude simpler than memory safety. Kotlin is a null safe language by default. Java is infamously not. Anyone who has worked on a mixed-language Kotlin project can tell you how quickly null safety becomes a pain once guarantees break down - and that’s in a language where these issues are flagged instantly and you can “fix” the problem in a couple of characters! Mixed memory safe/unsafe codebases would be a nightmare in comparison.
Also, C++'s ecosystem consists of deeply entrenched libraries with ancient codebases. Safe C++ might be useful in a decade or two if library maintainers could be pushed to make the switch (good luck with that, if it’s half as much of a paradigm shift as Rust), but by then there will probably be multiple competing language features that claim to solve the same problem. It’s the C++ Way™.
8 changed a lot of UI for no reason other than to chase the mobile market. 8.1 reverted a lot of that and people liked it, but the damage to 8’s reputation had already been done.
If they kept the edition alive for a few years 8.1 might be remembered as a redemption story like Windows 98 Second Edition, but they rushed 10 out the door - as a free upgrade, no less - to get back the goodwill they’d lost.
Windows ME was a crapshoot. One of our computers blue screened a few times during the couple months we had it installed; the other couldn’t even run an hour without hard crashing.
Nowadays I can’t even remember the last time Windows crashed. Newer versions are definitely a lot more stable, though suck in different ways.
The funny thing is the whole commercialization process started with one of the future partners messaging the project lead out of the blue on LinkedIn. I don’t know about you, but taking ideas from a random LinkedIn user doesn’t strike me as good business sense.
Then again, getting something out of your years of unpaid volunteer work must be incredibly tempting, given how many open source projects have sold out over the years. At least it was to form an actual legitimate company this time, unlike when SuperSU (the Android root solution before Magisk came along) sold themselves to a scummy foreign ad company. That one still ranks as the all time top WTF sale.
It’s a forked up world.
CyanogenMod, which was the base of most custom Android ROMs at one point. After taking venture funding, incompetent business majors crashed and burned the project trying to commercialize it. It was then forked and LineageOS was born.
We could also have “karma” on Lemmy, but while technically tracked the environment is better off without it being public in my opinion. I view voting records similarly.
It’s strange that they removed total account karma visibility a while back but are now thinking about making votes public.
I think a good compromise (since Lemmy already tracks that data) would have been to show the upvote/downvote ratio a user receives on their profile page, without showing their total karma. That’d help you spot toxic users without incentivising karma whoring.
Similarly, a display of how often a user upvotes versus downvotes others would help spot bots and trolls without completely obliterating privacy like their suggestion would.
(But ultimately none of this solves the problem of privacy on the Fediverse being one federated bad actor away from nonexistence)
There are two things I can’t stand in this world: people who are intolerant of other people’s cultures… and the Dutch.
Who else is better equipped? In my view it would solely depend on the lawyers that internet archive hires, and money plays a big factor in that.
The EFF. This kind of thing is why they exist.
The Archive making themselves an easier target was a huge misstep IMO. All it takes is one overreaching judge telling them they need to purge all copyrighted data (a common judgment in lawsuits like this) and the world becomes a worse place.
I believe you are correct. I had my MBR overwritten a few times back in the Windows XP days, but haven’t heard of it happening on modern UEFI setups outside of warnings like these.
I still segregate my system drives out of paranoia though.
Just take the first panel, but the end of the parchment goes into a shredder.
I mean technically…
Or some sort of vegetable chopper for megaflora vegetables that didn’t survive the Climate Wars.
“Perhaps for some sort of fertility rite.”
How big is 10 MB anyway?
To be honest, after typing all these numbers, 10 MB doesn’t even feel that big or special. Seems like shipping 10 MB of code is normal now.
If we assume that the average code line is about 65 characters, that would mean we are shipping ~150,000 lines of code. With every website! Sometimes just to show static content!
And that code is minified already. So it’s more like 300K+ LoC just for one website.
An important takeaway, as I feel byte size can be hard for people to intuitively visualize. And for those who didn’t read the article, many of the sites tested sent significantly more than 10 megs of JS, even sites containing nothing more than simple input boxes that should be doing any processing server-side.
I want to see the difference with ad-block enabled. Analytics and tracking are certainly complex enough to account for a lot of that payload. Same with an addon like Decentraleyes to see how much is bloated frameworks that could easily be cached locally.
Go to https://lemmy.world/settings and turn off “Bot account”.
Posits aside, that page had one of the best, clearest explanations of how floating point works that I’ve ever read. The authors of my college textbooks could have learned a thing or two about clarity from this writer.
Cory Doctorow warned us about this!
It boggles the mind that any language - let alone a systems programming language that most of the world’s infrastructure is built upon - wouldn’t adjust their specification to eliminate undefined behavior wherever possible. And C++'s all seem to be in the worst possible places, too.