There's nothing much to doubt. The evidence is always the same: "our web server logs show scrapers originating from IP addresses owned by someone who didn't pay us."
The Verge article is a little clearer. 100,000 threads pilfered over the past year with scraping! Oh no!
(See also: the actual legal filing. I have to admit the headings sound a little unstable.)
Just you wait—they're way more over-represented they are in subreddit moderators... and in the accelerationist movement.
"Actually" read them? Are there a lot of people running around purporting to have read TSR novels, or to have credentials that require doing so?
There are no real downsides to saying the 2026 version is 26 and the 2126 version is 126. It's just [year - 2000]; you can even imagine this is release 026 rather than 26. Personally I'd worry more about what happens in the year 3000 when they have to release version 1000.
Moreover—these are just version numbers, imitative of dates, rather than actual date fields. It's not like someone is going to be charged for unpaid bills because their iOS version number was accidentally parsed as being in the past. Take your damn pills, grandma!
And yet you registered on Slashdot. Curious.
(The social credit system isn't real. See here for debunking.)
They kinda did; Diet Coke is based on the New Coke recipe.
C++: You accidentally create a dozen instances of yourself and shoot them all in the foot. Providing emergency medical care is impossible since you can't tell which are bitwise copies and which are just pointing at others and saying "that's me, over there."
(cribbed from https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww-users.york.ac.uk%2F~ss44%2Fjoke%2Ffoot.htm, but widely circulated in the 90s)
It's tests, baby, all the way down! Midterms! Quarterlies! Weekly quizzes! Your grade is now 10% attendance and 90% exams! Good luck! Just be thankful they aren't oral.
No one was forced to use Internet Explorer, except when they wanted to browse the Internet after bundled IE with Windows and drove Netscape out of business.
No one was forced to install Windows, except when they wanted to use a PC and Microsoft was threatening PC OEMs that provided alternatives.
No one was forced to buy a telephone line from the Bell system, so long as they didn't mind not having a telephone in the United States.
No one was forced to lease an IBM punchcard tabulating machine, except when IBM held all the patents and refused to sell their equipment at reasonable prices.
No one was forced to buy oil from Standard, except when they wanted to heat their homes after SO bought up all the competition.
This story is about Google monopolizing the advertising industry, not search, you absolute bingus.
Ah, dear, sweet Panorama... gone before your time! In the garden of youth, you were known as TabCandy, and you were a delight upon mine eyes, and saviour of many a Mac user, whom you liberated from the depths of taskbarless window management ignorance, up, up, to the dizzy heights of spatial window management! How much duller and greyer the world has been since you last languidly cached all those many tab thumbnails in your round-corner'd groupings... Were it only possible to summon you forth once more, with Ctrl-Shift-T, as in the age of your glories!
But seriously, it was a casualty of its own implementation. It was an enormous memory sink written in jQuery, at a time when Firefox was haemorrhaging users to Chrome because of its performance. Many of the browser APIs it depended on were also purged.
Sure thing, AAANUS SNIFFER. It goes a little like this:
Hope that cleared things up for you.
Rust is now 13 years old. When Linus first released the Linux kernel in 1991, the C programming language was 19 years old, and Unix V7 had only been out for 12 years.
There are more than a dozen kernels written entirely in Rust. The claim that Rust is immature is pure propaganda.
I'm not saying he must go; there are alternatives. More like he should be insulated from managerial decisions until he actually has the credentials and social skills that the job requires.
This is a cultural flaw that exists in pretty much every CS department, big and small. There is a default assumption among computer scientists that we do not need bureaucracy or HR. This comes from several sources: the hacker culture around MIT, CMU, and Berkeley was deeply entrenched in the hippie counter-culture of the 1970s; the general absence of women in the field (especially declining during the early decades of the open source movement) somewhat averts one of the most common categories of HR problems; and the paperwork required by external offices and departments tends to be a matter of "following instructions" in a very programming-like way, which goes miles to reinforcing the belief that bureaucracy is merely a kind of programming for non-programmers. (Relatedly, the US banned freelance programming contractors because it feared they would cheat on their taxes, because of a general paranoia about hackers finding loopholes. The actual data suggests programmers have an above-average rate of honesty and obedience when filing.)
So we pretty much universally skip over all the hard-earned lessons from other organizations about the value of managers as diplomats and intermediaries. Fred Brooks made this worse; the Mythical Man-Month demonstrates that traditional corporate structures are inefficient for programming, which we take as validation that we should not wear any yoke that chafes. But it doesn't do or say anything about the baby in that bathwater; it assumes that all programmers are perfectly rational agents with no interpersonal difficulties or competing agendas, working toward the same ends.
The reality is that humans, being humans, are always flawed people, and often need various forms of managing, whether it's encouragement, a sounding board, or policing. Without managers to act as referees, all large open source projects are basically voluntary treadmills: work until you burn out, but only when you feel like it. Some of these duties end up on the shoulders of founders and project leads, but since those people are just programmers themselves, they will invariably be mismatched to the job, and will themselves encounter burnout as they must struggle with the burdens of pretending to be extraverts for the good of the rest of the team.
I don't think codes of conduct are the answer, not really. A code of conduct cannot provide any of the positive benefits of management, nor can it respect the nuances of context. I admit that I think they are well-intentioned, but they're also a half-assed libertarian band-aid for a deep part of the human condition that requires real talent to treat properly.
Creating a toxic workplace tends to get people fired, yes. Next time post from your actual account, you paragon of bravery.
Reference the NULL within NULL, it is the gateway to all wizardry.
