Clearly you didn't read the article. The professor was considering changing her classes / assignments in a way that students can't use AI, but that a) limits the number of topics severely, b) that list may be empty soon.So she decided against it. Second, in-class papers do not benefit everybody and are taking up a lot of time, including that of the professor (who could arguably be doing some work while the students are scribbling away).

So next time before you call someone lazy, do the work and read the article.

This is my take on it. Let's consider the typical workday in an industrialized country. Let's also assume the sun is near it's highest point at 12:00 local time (noon).

You wake up around 7:00, have your breakfast and go to your work; a 9 to 5 job. Or better phrased, a 9:00 to 17:00 job. Here is already the first hint of a mis-alignment: the halfway point of your working period is already at 13:00, an hour behind noon... After work, you go home, shop, cook, eat dinner, the usual stuff. You're done by 19:00, perhaps a bit later. Then, every other frickin' human leasure activity is in the evening! Sports, cinema, watching tv, visiting friends, a night out, playing computer games; etc.; everything is crammed in those hours between 19:00 and midnight. You're lucky to be in bed by 23:00.

The sun however, rises X hours before noon and sets X hours after noon, by definition. But as shown above, human activity is centered around 15:00, not 12:00. No matter the season, the discrepancy between solar time and human time is simply too large. And artifically shifting it by one hour doesn't help either, thus the endless complaints.

As to why human activity hours have shifted so much, I can only assume that is caused by artificial lighting. Trying to 'unshift' it is unlikely, as is there is not much to do at 5 in the morning...

Come to Europe. We are sowing both wheat and windmills in the ground for decades and they are growing very well together.

The amount of work you had to put in is probably okay for a hobby project or an open source library. However, for real business code, this is unacceptable.

Really, the developers of PHP are making it difficult to make this language attractive for long-term stable development. Nobody at 'PHP headquarters' is going to give any guarantuee that even a minor update from 8.0 to 8.1 won't break things. They put the burden of checking & modifying your code, with every version update, on you, the developer. On all the developers in the world that use PHP. And just imagine the following conversion: "Sorry, boss, we need 2 weeks of extra time because we need to upgrade to a new PHP version because it's EOL now and we found a few things are broken and need to test all our code..." "Wait, didn't you upgrade to a new version last year?" "Yeah....."

Sure, PHP has gained some useful functionality and has shed a lot of technical debt, but the constant deprecation of functions doesn't feel right... When does it stop? What things will be broken in the next version? When I develop with PHP, I feel like I am constantly walking on thin ice.

Isn't that the plot of a sci-fi novel, in a future where secrets are forbidden by law, and some scientists try to push the black hole out by some graviton-thingies?

Unfortunately, the use of std::unique_ptr and std::shared_ptr in code isn't as easy as I had hoped. The main problems I encountered are:

• Creating an object as a shared/unique_ptr isn't as straightforward as a "new Object"; it's always a two-stage process.
• The use is extremely invasive: you must use shared_ptr everywhere or your code becomes a mess with dereferences, casts, weak_ptr, etc.
• Related to the previous point is that external libraries never use a shared_ptr/weak_ptr in their calls; only naked pointers.
• There's a range of 'automatic' pointers to choose from: auto_ptr, weak_ptr, shared_ptr, unique_ptr. Which is the best choice is not always clear. For example, look at the descriptions for unique_ptr and shared_ptr; they are very similar and they don't explain when you should use either of them.
• More typing: "function do_something(std::weak_ptr var)" doesn't roll of the tongue (or keyboard) as easily.

Finally, a small niggle: in earlier standards auto_ptr was pushed as "the" automatic pointer type but that has been deprecated since C++11; leaving the cleanup / conversion to you.

In any case, my opinion: nice concept, but it just feels clumsy.

So now I need a phone to tell me I'm tired? Wow, that's some serious progress.

Agreed. This ludicrous tendency to make devices slimmer and slimmer has to stop. At this point, adding 1mm of thickness could increase your battery life by 20%, even more. The frontal area is still the same so adding a bit of depth doesn't make the device any bigger visually.

Actually, I was contemplating supporting a few YouTubers with just that, 10$ a month or so and split it among the ones I liked. Then I read about the change in policy this week and I was like "Wait, this means I have to pay for *every* creator? Who came up with this nonsense?"

So that means no Patreon, simple. Sorry Big Clive, 8-Bit Guy and Today I Found Out.

It's not the feeds themselves, it's the continuous barrage of push notifications. Ever noticed how many sites want to enable them? I just say no.

At one point I realized that WordFeud was one of my greatest productivity killers. Every few minutes it goes bleep and you pick up your phone to place a word. Kil-ling! Nothing gets done! So I disabled all notifications, sounds and vibrate; the only thing left is the LED. Now I work for a while and when I take a break I'll see the LED flashing (or not) and have a little distraction. Then put the phone down and continue working. Do this for all your apps: WhatsApp, Instagram, Telegram, email, et cetera and you'll find peace and quiet. And yet, nobody has complained yet that I was late with replying, or that I missed a funny must-see video.

So instead of push, pull.

Yup. Started in 1993 with 2 boxes of floppy disks and I still use it today (Slackware, that is, not those floppies :)). I never switched from it and it is my day-to-day OS. I'm currently running a pure 64 bit version of Slackware.

The only naggle I have with it is that there is no easy upgrade path from version to version. I do upgrade software occasionally and I even use the package system from Slackware so that I can restore older versions of packages, if necessary. It also lacks dependency tracking so sometimes it's a bit of a hunt to find the correct set of packages. Other than that, it's very simple, transparant and robust.

So Microsoft finally commented:

So the usual marketing blabla of "improving your experience". When, for crying out loud, is a company going to admit that they were wrong and going to reverse course??! Just for once, please. Just say "Oops, sorry. We hear you; here's the previous version." Now that would be really listening to your customers.

Post mortem? There are still tons of websites, even ones that are being developed and maintainted today, that use Flash to display videos. I very regularely see the message "This content can't be played with your setup." and if you dig deeper it's always a Flash plugin...

Oh, it gets worse. From the article:

So in order to build Rust, you must have... Rust. Chicken-and-egg omelet, anyone?