Microsoft engages in IT terrorism and actively sabotages software development, worldwide

Enter the fabulous new class/method StructuralComparisons.StructuralEqualityComparer.Equals() that is touted as the next best thing since sliced bread.

This POS is 25x+ slower than the dumb but tried and proven for( ; ; ) loop method.

25x+ slower. I kid you not. Well, of course! How otherwise can they drive the world's IT into the cloud? Only by twisting our collective arms into mute obedience, by way of the slowness of our on-premise solutions that they covertly but persistently sabotage.

So, if you operate on simple value types, use a loop. Only if you operate on unpredictable complex types, and the performance does not matter to you, use the MS gizmo.

You've been warned.

Posted by: LinuxLies at 08:04 AM | No Comments | Add Comment
Post contains 135 words, total size 1 kb.

This is what $1,000,000,000,000 cannot buy you: consistency

Google 'teams 404' and you will be presented with pages of results of people around the world not being able to log into Teams or to join meetings. There are plenty of Q/A on MS's own web site answers.microsoft.com about this problem. Resolution? None whatsoever.

You would think that a one trillion dollar corporation should have architects who architect sound solutions. Nope.

You would think that a one trillion dollar corporation should have QA who catch bugs before their product is released. Nope.

You would think that a one trillion dollar corporation should have monitoring of their infrastructure that detects issues when something goes down. Nope.

None of that, at Microsoft. They code away, release if it compiles, slap together some servers and retire to a Florida beach, with cocktails and hookers.

So, watch your "Unable to connect you, HTTP 404" error messages, you unwashed masses, and shut up.

Posted by: LinuxLies at 07:06 AM | No Comments | Add Comment
Post contains 165 words, total size 1 kb.

They break your systems and still get a good sleep at night

When they break things they do not offer anything in return and always refuse to roll back the bad change:

$ sudo dnf install jdk-8u111-linux-x64.rpm 
[sudo] password for adm7:         
Last metadata expiration check: 0:35:23 ago on Wed 26 Jun 2024 08:38:45 AM EDT.
Error: 
 Problem: conflicting requests
  - nothing provides /bin/basename needed by jdk1.8.0_111-2000:1.8.0_111-fcs.x86_64
  - nothing provides /bin/cp needed by jdk1.8.0_111-2000:1.8.0_111-fcs.x86_64
  - nothing provides /bin/ls needed by jdk1.8.0_111-2000:1.8.0_111-fcs.x86_64
  - nothing provides /bin/mkdir needed by jdk1.8.0_111-2000:1.8.0_111-fcs.x86_64
  - nothing provides /bin/mv needed by jdk1.8.0_111-2000:1.8.0_111-fcs.x86_64
  - nothing provides /bin/pwd needed by jdk1.8.0_111-2000:1.8.0_111-fcs.x86_64
  - nothing provides /bin/sort needed by jdk1.8.0_111-2000:1.8.0_111-fcs.x86_64

The reason? They moved the base system tools around. Motivation? Who knows why. Probably out of spite and disdain for users.

$ which basename
/usr/bin/basename
[adm7@localhost Java]$ which cp
/usr/bin/cp
[adm7@localhost Java]$

Try to report this to distro maintainers, and they will 1) deride you; 2) ignore you; 3) ban you.

Someone should give them a strong reality check and teach them that such behavior is unacceptable. But most of us in IT world do not give a damn.

Posted by: LinuxLies at 08:23 AM | No Comments | Add Comment
Post contains 196 words, total size 2 kb.

Genius degenerates rule our world

This is what the enlightened ivory tower dwellers entertain themselves with: MATE volume applet missing in panel after upgrade to 30

They find a functionality to destroy and destroy it, to watch us, unwashed masses, writhe in pain and agony and try to find the way to restore normal operation. I conclude that the majority of the so-called members of so-called FOSS community are sadistic sociopaths, judging by their behavior.

The gist is that once upon a time there used to be a volume control in MATE desktop. It lived in the tray applet of any panel. This had not been good enough, and the genius ivory tower dwellers removed it and re-coded it as a separate applet that has to be added to the panel separately.

Since the enlightened elites of the FOSS projects who live in ivory towers never test their releases, they do not know that this applet is not added by default during OS upgrades, causing us to scramble to find it. This does not bother those said ivory tower dwellers, in the least. To add insult to injury, they changed its icon as well, from a well-defined, large speaker to a tiny speaker that coincidentally is exactly the same as that of QasMixer. Since many of us who need to tune their sound adapters use both, we have two identical icons in the panel now. How genius!

Let me break this to you, genius turds: your volume control is known to crash when the sophisticated monstrosity of PulseAudio crashes, or on its own. When it crashes, we need a way to restart it. Now, you have removed that opportunity. We do not appreciate it at all. Theoretically, at some point, some Linux user might eventually become fed up with your bullying and make it a crusade of their life to avenge us, Columbine style. I am worried for the safety of the said elite ivory tower dwellers.

Posted by: LinuxLies at 07:25 AM | No Comments | Add Comment
Post contains 332 words, total size 2 kb.

Another Linux lie: we have file sharing

This is a followup to a recent post on this topic.

Read man mount.cifs and you will realize that its developers are intimately familiar with the versions of SMB protocol that Microsoft upgrades with each version of their OS. But being familiar does not translate into a working solution. At least, not in the oh, so wonderful world of FOSS.

So, you, ivory tower dweller developers, know well to code the support for vers parameter, but you are so inept and inconsiderate that you make zero attempt to detect the server's version and configure CIFS accordingly. You leave it up to us to figure out that we have to use that parameter and to set it to the correct value. As result, your mounted shares exhibit all sorts of problems. How are we supposed to know to supply the vers parameter when the share mounts and work without it, and only later problems occur? You waste our time and efforts, by having us to investigate and research, only to discover that all of those problems could have been avoided had we only used that parameter and set it to the latest version supported by the server?

You deem yourself geniuses. You demand respect. But you do not make a slightest attempt to earn that respect. What does that make you? Right! That makes you genius degenerates.

Sorry that it does not occur to you and that I have to break it to you, but respect demanded is fear, not respect.

Posted by: LinuxLies at 08:26 AM | No Comments | Add Comment
Post contains 264 words, total size 2 kb.

Respect has to be earned, not demanded

Linux developers and distro maintainers dwell in ivory towers, from which they bestow their divine wisdoms on us, mere mortals. One of the wisdoms is that we have to pay respect to them. Fuck no.

I counter that with another wisdom: respect has to be earned.

When all you do is break compatibilities, butcher specifications and APIs, retire widely-used commands, configuration options, command-line parameters, files, and other items of IT infrastructure, i.e. when you make unnecessary, unwanted breaking changes, you lose respect. If and when you still continue to demand it, you have unrealistic expectations.

We are equal human beings, regardless of whether you recognize us as such or not. When we inform you of that, by way of bug reports, you have to live with that.

Posted by: LinuxLies at 11:03 AM | No Comments | Add Comment
Post contains 141 words, total size 1 kb.

Hatred and contempt

A sane and intelligent human being is more often than not capable of detecting hatred and contempt towards self, when dealing with others by way of verbal or written communication. This includes myself. When I see the obsession of Microsoft and many in the IT world with immutable objects and collections, I realize that they hate, despise, and distrust me.

What purpose do immutable objects and collections serve other than to tell the consumer of them, a developer in our case, that he/she is not to be trusted? None.

Allow me to break it to you, enlightened ivory tower dwellers: I have no intent of altering your objects or collections when I consume them to extract data for my functions or algorithms from them. You do not have to fear me misusing your precious objects. I possess enough intelligence to take 1-2 fields from them, to iterate them, and to forget about them because I am done. But you go out of your way to jump through hoops in order to make them immutable, read-only, or whatnot.

Well, I do not really care. They are your objects or collections, so you do with them however you see fit. You already have read-only collections that do not implement Add() or Remove(), but it is not good enough for you. Being a compassionate human being, I still pity you for having to spend so much unnecessary efforts in vain, and I also realize that you hate and distrust me. Get a life!

Posted by: LinuxLies at 10:56 AM | No Comments | Add Comment
Post contains 256 words, total size 1 kb.

They finally killed network scripts

Somewhere around Fedora 40, they removed the possibility to disable the monstrosity of Network Manager and to revert to network scripts. ifcfg-eth0 no longer works.

We used to be able to revert to sane network configurations, and they removed that workaround. Further versions of Fedora are as dead from my perspective as Solaris 11.4 and up. Why are they doing that to us? Why are we silent?

I have a conspiracy theory: the combination of systemd and Network Manager afforded true owners of Linux repos an opportunity to create a backdoor, by allowing them to re-configure the network however the fuck they want, at any moment. Network scripts stood to remove such opportunity. How's that for a hypothesis?

Posted by: LinuxLies at 10:27 AM | No Comments | Add Comment
Post contains 128 words, total size 1 kb.

Another Linux lie: we have file sharing

An informative reading: mount.cifs hangs and becomes unresponsive

Basically, the problem of CIFS shares nounted in Linux has been created by some inept, inbred twit in the oh, so wonderful Linux FOSS community, 10 years ago, and since then no one gives a flying fuck about fixing it.

WHY DO YOU NEVER REVERT YOUR BUGS?

No one wants your new shit. You release some obscure features that none of us wants, but when you create catastrophic show-stopper problems, you never revert. There is no value in your new code. It does not work. But you never revert.

What recourse do we have to make you revert your bad changes, other than physical?

Posted by: LinuxLies at 11:18 AM | No Comments | Add Comment
Post contains 126 words, total size 1 kb.

We used to be free. Now, we are slaves.

When genius degenerates in Linux "community" came up with unpredicable "predictable" network device names and introduced NetworkManager that everyone is supposed to enjoy, we found way to circumvent that crap. Not anymore! In Fedora 40, there is no longer a way to revert to network scripts.

Why do you hate us so rabidly? Why do you subvert our every effort to configure our systems to our ideals and satisfaction? Why do you want to be our enemies so direly?

Once SHTF, you will have to watch over your shoulders, for the rest of your lives.

Posted by: LinuxLies at 10:25 AM | No Comments | Add Comment
Post contains 113 words, total size 1 kb.

FOSS developers clearly have nothing to do

Been upgrading some Linux boxes because I have to, not because I want to. So, went 2 versions up to the most recent and found that one of the apparent changes to KDE Plasma was that they lifted up the taskbar panel and hung it 1/8" above the bottom side of the monitor.

I kid you not! They spent effort to shrink the panel by 1/8" on each side and to hang it 1/8" from the bottom.

These fucktards do not have any bugs to work on! Their ticket queues are empty. Users do not come back with bug reports that frustrate or infuriate them. No! None of that is in existence! FOSS developers on KDE team have their hands empty, and to avoid sitting around doing nothing they uplift the panel by 1/8".

HELL NO! Your fucking product is full of bugs. Your UI is shit. You've ruined great applets and changed your color scheme to be fucking dark-gray on black that no one can see anything on. Your console profiles make no sense. You ship out broken major releases. But you still uplift the panel by 1/8 of a fucking inch!

Posted by: LinuxLies at 08:59 AM | No Comments | Add Comment
Post contains 207 words, total size 1 kb.