So...
Slower 5G comms, a snoopy camera and hallucinated photos and videos. Someone (above the age of 16) please explain how this is a good thing?
3572 publicly visible posts • joined 9 Dec 2009
From the article:
[...] until you get your hands on Windows 11 Insider Preview Build 26080 which, as Microsoft today announced, includes "a preview experience of the new, unified Microsoft Teams experience on Windows."
Oh-comma-goodie! We're being offered a preliminary experience of an experience! Or stated another way, a recursive experience. Now hooda thunk that the Micros~1 marketing geniuses even knew what recursion was, much less how to slam several snippets of gibberish together to implement it? Maybe they just got lucky (or, more likely, they managed to cajole Clippy the AI Paperclip to generate it for them).
In either case, this will not end well.
To understand recursion, you must first understand recursion. Good luck wi' dat, Micros~1!
How is entity going to be worth billions? I am totally lost as to where that valuation is coming from.
From Uranus.
No, seriously. It's social media, donchano. It's value is whatever the seller says it is.
...and we all know by now that t'pineapple has a penchant for overvaluing his ass sets [sic]....
American Lager anyway...
OK, time for my favorite Coors joke:
Back in the day when you couldn't get Coors (Banquet; this was before the time of that awful swill smugly referred to as Coors Light) outside of a 500 mile radius of Denver, an enterprising gent wanted to find out what it was about Coors that made it so popular. So he took a sample of it and sent it off to a lab. After two weeks, he received a reply from that lab that opened thus:
Dear Sir,We're sorry to report that your horse has diabetes.
Quite some time ago, I interviewed for a position at a firm that a friend of mine was already working for, and who had suggested that I interview. Naturally, there was a competency/capability test, that had to do with some Windows programming problems, using C++. (No, Not "Visual C++"; there is no such thing.) Got to the second question, and I looked at it hard...something didn't seem right. There was a syntax error in the source code submitted as the question. The question was along the lines of, "What would be the value of variable 'x' at the end of this function?" My answer was along the lines of, "Variable 'x' would have no value because this code would never compile. This line here would raise a compiler error. Now if the intent of this line were to read like this... then 'x' would be yadda-yadda..."
Well, I soon found out that I had committed blasphemy, because no sooner did I submit the test, but my friend came into the interview room saying that I had created quite a ruckus, and that folks were arguing about it, somebody was compiling the example to prove me wrong, and the junior folks were having quite a chuckle at the expense of the tech lead, who was reputed to have made up the test himself. My friend was called out of the room and I was left to cool my heels for about another 10 minutes. Then, the division head (with whom I had met briefly before the test), and the tech lead both came into the room. The division head, a large man, had a big smile on his face, while the tech lead, a rather nerdy looking gent, had this bemused look on his face. The Division head stuck out his large hand, and enthusiastically shook mine, and said, "You're hired!", and started talking about when I could start, then left to fetch some paperwork. The tech lead told me after he left that they had been using that test for over two years, and no one has spotted the error.
But it did explain why there was a wide variety of answers to that particular question.
Seems everything they're doing in the last, oh say 5 years or so, has been directed at running the last users with an IQ above room temperature off the platform permanently.
Maybe their marketers have been infiltrated by an Apple sleeper cell....
From the sub-head:
Those trying to log into Meta's Facebook, Instagram, and Threads for their social media fixes are facing panic this morning after being locked out of their accounts.
Hello travelers. Welcome back to Reality. That blinding light you see is called the Sun; in limited quantities it is not dangerous and can result in seeing things clearly (once your eyes adjust...). Those tremors you're experiencing will subside in due time. Oh, and those other things you see moving around are called "people". With a few exceptions, the tend to be sociable, and can be engaged with using a simple construct called "conversation". It may take some practice reviving this lost skill, but you'll be surprised at how quickly you'll remember. Enjoy the rest of your day.
The US Federal Communications Commission (FCC) made the announcement on March 4, 2024, after months of protests failed to persuadelawmakersthe MAGAts currently infesting the halls of Congress that keeping the Affordable Connectivity Program (ACP) running was worth the expense.
Nobody with an IQ above room temperature could possibly mistake a Republican as a "lawmaker".
That said, it's hard to decide who to root for here
Well, not really. El Muskrat has been rightly and mightily smacked down, so rooting for that is wasted effort (the world already won). So it becomes a matter, IMHO, of rooting for or against the unbridled greed of a handful of scheisster lawyers. Doesn't seem like too difficult of a choice to me. (YMMV, of course, especially if you are a scheisster lawyer with unbridled greed....)
BTW, rooting against the scheissters is not the same a rooting for El Muskrat.
Actually I was the one who filed a bug report to Micros~1 when the released that abomination laughingly referred to as "Quick C" complaining about how they buggered up the time_t and related structures. One of the problems was signed values; another was keying the beginning of the epoch at 1Jan1900 (which, because of yet another bug, was really 31Dec1899). To the best of my reading, nothing in the C standard (up through C99) requires the epoch to start at 1Jan1970, nor requires signed (or unsigned) time_t values of any magnitude. A time_t could be a 64-bit unsigned integer, and be standards compliant (unless, of course, C-standards beyond C99 changed, that...but I doubt they would).
That's 2200 years ago so why hasn't the world learned to take things like leap years into account yet?
Well, we can thank in part the Millennial mindset that anything that happened before they were born is not important. Factor in the corollary that they can do anything better than the previous version (even if they don't have the slightest idea how to do it).
You know, something from 200 BCE just isn't shiny enough.
From the article:
In 2014, LXQt 0.8 switched to Qt 5, and currently it uses Qt 5.15. However, that reached EOL in May 2023. So, just like KDE Plasma 6.0, the project must now change tack to the current Qt 6. [Emphasis added]
Why?
I mean, its not like the Qt shared libraries (I was going to say DLLs, but this is Linux we're talking about, and in that environment, "DLL" is a dirty word (and rightly so)) are some how going to suddenly and summarily stop working, or self destruct like in some Tom Cruise movie. Qt 5.15 is rock solid, and just works. So, other than chasing the shiny, why "must [one] now change tack to the current Qt 6."? What ever happened to the Prime Directive of SW development: If It Ain't Broke, Don't Fix It? I guess that just isn't whizzy enough for today's Yout'.
Speeds and Feeds. Coming real soon to an OS near you!
OK, I'll go back into my hovel, grumbling quietly to myself...
Sounds like the "Texas Blockchain Council"1, and especially Riot Platforms, was doing a bit of judge hunting. Yeah that's supposed to be illegal, but this is Tejas, after all.
1The "Texas Blockchain Council"?!? Really??? I was going to say, "You can't make this stuff up", but I guess you can...
If not for the last part (regimentation ....) I'd say it describes the current USA quite right.
Uhh, no. It does very accurately describe a visible, vocal minority of USAsians (we call them 'MAGAt"s). But they're not in charge. Yet. So stop projecting.
Oh, and as far as regimentation is concerned, I'd say that is quite well underway in our more backwater third of our country.
The article starts out with:
A pro-life group was able [...]
Enough with the marketing bullshit. These people are anti-abortionists, they are most assuredly not "pro-life". If they were truly "pro-life", they would be in favor of:
* Social services and a safety net for those born to poorer (or homeless) mothers.
* Gun reform, so that it's harder to do mass killings. (Are you listening, Kansas? Missouri? Florida?)
* Making adoption easier, especially for same sex couples, or even singles.
* An end to the death penalty.
None of which these anti-abortionists are in favor of. Enough of the feel-good euphemisms; let's start calling a spade a spade, OK?
Who knows, maybe even JetBrains' developers thought their users would love this.
I suspect that JetBrains' developers (if they are like developers practically everywhere), cleave into basically 2 sets: Those who are easily dazzled by the shiny, and who froth at the mouth at the opportunity to imbue their latest opus dei with the latest way bitchin' k3wl whizzy-du-jour, and those who have been burned by the latest shiny, and are therefore more prone to take a measured approach. The former set tends to be populated with the new young bucks, while the latter tends to be populated by more 'seasoned' practitioners of the black arts and sciences of software development. (Yes, this is a generalization, and counterexamples abound.)
Each of these groups tend to project their biases onto their perception of the user base. One could therefore suspect that more of the JetBrains devs fall into the former group. That may be the case, but I also suspect the vast majority of the JetBrains marketdroids also fall into that former group as well. A natural alliance formed within the JetBrains corporatocracy, and the rest, as they say, is history.
What is yet to be written is how will that set manage to stomach the crow that the backlash from real customers is serving them, and how will they respond.
Popcorn, anyone?
I strongly disagree with his take.
I can see why, but I'm not ready to hop on that bandwagon.
I think Andrew is making a distinction between "coders" (which I take to be someone who can cobble up a program more or less by rote; think copy-pasta practitioners), as opposed to "programmers" (those with more highly tuned abstract problem-solving skills, who also know how to manipulate a programming language or two; Andrew refers to "elite programmers" in his tome). I actually think that he is correct in this dichotomy. Those with low problem-solving skills who can slap together a few lines of spaghetti-looking javascript will (and should) be in lesser demand, while those who can design (and implement) more complex systems will still be sough after.
So, if making your kids "learn to code" means plopping them wholesale into the former group, Andrew's premise (as I take it) is that you're doing no one any favors. If that is indeed his take, I agree.
And if it is not, OK, I need to improve my reading comprehension skills...
It's time for the Microsoft shotgun of functionality. We've created something but have no idea what use it could have or whether it even works, so we will throw it at everything and see if any of itsticksdoesn't suck (too much...). [...]
There, FTFY
When Cal Paterson did that analysis, Firefox market share was around 4.9%, in Dec 23 it was 3.35%, by Feb 24 it was 3.13%. Yes, a 7% loss in the last two months.
But...but...but...today is February 9th 2024. So this Cal guy is prescient? Or is he just making shit up?