Starting a new subscription is not the same as renewing an existing subscription. You must be retarded. Entering new subscription details into every product/Visual Studio instance is a pain in the arse.

No, I never mentioned a perpetual license. How you treat the fallback version is completely irrelevant.

OK, just to name a couple - Sublime Text (ever heard of that cunt?) and JPEGMini Pro. You clearly don't know as much as you think you do.

I never mentioned anything about a perpetual license. Every other subscription software I have purchased (say for a year) gives you free updates for a year that can be used after the subscription has ended. Otherwise you can get left with extremely buggy software because your subscription was renewed shortly after 2023.0 was first released. Everything is wrong with that.

The problem is (clearly) that the end of the new subscription date should be exactly 365 days after payment was made. We have been shafted 1-2 weeks because JetBrains just add 365 days to the date the previous subscription ended. Everything is wrong with that.

No, they don't.

If you pay for a year subscription, it would be expected that you can continue to use the last version released before the year was up. Instead they only allow you to use the version available when the yearly subscription was first purchased.

They also shaft you when renewing - based upon when the subscription expired rather than when payment for a new subscription was made.

On my Windows environments, Edge is being forced down my throat.

Because of this, I will never use Edge and never use Bing.

Also "Microsoft Compatibility Telemetry" is a process that should not exist, or be disabled by default. It makes my laptop fan turn on and slows everything down when it is running due to CPU usage.

Also, when disabling the Microsoft Antivirus realtime protection - it should last for a week. Not mere hours. It slows down solution build time and just general usage of my PC.

McKinsey - creating a problem than only McKinsey can solve.

Just like every Tom, Dick and Harry that invent a new Pattern/Practice that solves a problem that rarely exists, making development/debugging more complex - just for the sake of earning money - rather than getting stuff done and meeting expectations - on time and budget.

Love it!

See that's what I am talking about, good old fashioned fun online.

I also heard your Mum likes to put Five Guys in her mouth, grab the buns, and taste the special sauce.

and I've talked my fair share of trash

As much as I agree with everything you wrote, your mother handles more sausages than a butcher.

Robotaxis - cum and go at the same time.

https://tech.slashdot.org/stor...

You have one job.

You can play many older DirectDraw/Direct3D/DirectX games on modern windows using dgVoodoo2:

http://dege.freeweb.hu/dgVoodo...

What the hell? Fahrenheit is far superior to Celcius?

Inside my place right now it is 20.3C. If it was 19.3C or 21.3C - most people would not notice the difference. Unless people who grow up in places that use Fahrenheit have somehow evolved to be far more sensitive to temperature? Either that or very occasionally using a decimal place is too complex for their brains to handle?

Weather forecasts (and most weather reports) do not even mention decimals (with Celsius they are too insignificant to care about). The first decimal might be mentioned if a heat/cold record was broken or it was unusually hot or cold, but that's more a discussion point for people who talk about the weather.

Github/Microsoft is not accessing gmplib.org. A Github user's script is, which executes as a Github action (for testing). Blocking the IP ranges on the firewall is only going to cause a problem for the user with the FFmpeg-Builds repo. It's not going to impact Microsoft or Github in any way. Blame the user, not the service provider.

It was a poorly written script by a contributor to the FFmpeg-Builds repo. The requests were not cleverly chosen at all.

Torbjorn Granlund sounds like a paranoid idiot who doesn't understand how this happened, and is misplacing blame.

Parents let their kids use social media, fully aware of the negative impacts it can have on the mental health of both adults and children.

Parents fail to monitor their kids usage of social media.

Parents want a large pay out for their own inadequate parenting and decide to sue social media companies.

Welcome to litigious society.