Genius degenerates rule our world

Your best guess: when does LibreOffice save recorded macros? Just give me your best guess. What is it? When you OK the macro dialog? No, you are wrong. It saves them when you exit the last LO window on your desktop and thus exit the whole process.

Yes, they are that terminally genius that they leave the saving of macros to disk to the last moment. If the whole bloody thing crashes in the mean time, which LO loves to do, then your macros are gone.

Yes, you read it right! They are quite capable of saving to disk of keyboard shortcuts that you assign to your beloved new macro, but not the macro itself. So, when you re-open LO after a crash and try to run your macro it throws an error on you to the affect of scripting error, macro not found.

Thank you kindly, genius degenerates!

Posted by: LinuxLies at 03:18 PM | No Comments | Add Comment
Post contains 159 words, total size 1 kb.

Another Linux lie: we can convert PDF to DOCX

Truth is, you can't.

Enter AbiWord that is touted as a PDF to DOCX converter. It converts to plain text, and it does so so poorly that it butchers any formatting and leaves countless blank pages filled with nothing but new lines. And the terminally genius distro maintainers allowed this filth to pollute their repos! Of course, they did not give a fuck as to whether it does its job or not.

Enter LibreOffice. Stellar geniuses who write it did not bother to convert a single illustration! None. Zilch. Fuck you, writer! Nobody wants you stinking pictures.

Ditto about calibre. The file is butchered, no illustrations. Is this contagious? Do they drink from the same toilet sink as LibreOffice team?

So, this is the year 2024, and the people of Earth travel between stars, but we cannot convert between file formats. Congratulations, genius degenerates!

Posted by: LinuxLies at 02:53 PM | No Comments | Add Comment
Post contains 162 words, total size 1 kb.

Genius degenerates rule our world

Fancy that! How to configure the number of undo/redo steps? In their divine wisdome, LO developers default the undo level count to 100. And then, to add insult to injury, a terminal case of an idiot under the nickname 'EarnestAl' dares to barge in there with his moronic stab at the OP and tell him that his workflow is wrong.

You, piece of turd, should shut the fuck up because in your stupid wisdom you do not even understand that LO counts EVERY FUCKING CHARACTER as an undo level. You read me right! Not an act of typing alphanumeric characters in a sequence, like other modern editors do, but EVERY FUCKING CHARACTER, for crying out loud. That is what, like 1 1/2 lines of text?

If anything is wrong, then it is with EarnestAl's brain, and I know what it is: it is made of monkey poop.

Posted by: LinuxLies at 06:08 PM | No Comments | Add Comment
Post contains 157 words, total size 1 kb.

FFS, do you even know what you are doing?

Satya "False Positives" Nadella strikes again. Or rather his Chicom coders do.

My client has this policy that shared DLL assemblies have to have internal access modifier on all classes and InternalsVisibleTo set to all consuming projects. Works well in some solutions but there is one in which it flat out refuses to work.

It builds and passes unit tests. It works once deployed. But intellisense flat out refuses to recognize the internal classes. It underscores them with the red wavy line and does not pop up the code completion on them.

FFS, Satya, have your Chicom coders debug their code. FFS, Satya, once you FUBAR, fix your shit, do not roll out a whole new version. The world cannot keep up with your bugs. We will have to deal with you, sooner or later, you inconsiderate terrorist of an exec, because you ruin the whole world.

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

From one DLL hell into another, but better, nicer, shinier hell

.NET was touted as the final solution to the DLL hell. Hell, no!

Trying to install a CLR assembly into SQL Server.

It needs a missing assembly System.Data.Entity. I do not use EF but to hell with it, here you are, I add that DLL to the references. Huh? It does not show up in the output folder. To hell with it! I find it on the target server, in the GAC, and add it to the publish folder. Solved? Hell, no!

Now it needs System.Runtime.Serialization.dll.

Next, it needs SMDiagnostics.dll whatever the fuck that is.

Next, it needs system.componentmodel.dataannotations.

FUCK! Am I supposed to copy 1/2 of the whole .NET into my publish folder? Wasn't .NET supposed to be available to all .NET assemblies, wherever they were?

WTF is wrong with you, Microsoft? Can you find your ass with your both hands, once in a lifetime?

No surprise we have this exodus to crappy shits like Python: MS discredited itself, courtesy Satya Nadella and his hordes of Chicom coders.

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

Genius degenerates rule our world

Microsoft's Nuget package manager in Visual Studio is a stinking piece of rotten vomit. It was apparently developed by an inept and inconsidering ape some 1/2 world away that was left unsupervised by the keyboard. Having looked at the result, that ape's supervisor apparently thought: "Fuck all!" and allowed this POS to be released.

Had my subordinates done such a piss-poor job, I probably would have fired them for due cause.

No option to do exact match search. Check.

No sorting. Check.

All of the info is lumped together in multi-line blobs. Check.

No option to filter out non-MS packages. Check.

As usual, a dumb as a door knob piece of software totally satisfies Satya Nadella turd of a man waste of skin. The fish rots from the head, remember!

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