Oracle rolls out the new generation of MySQL Workbench. Need I tell that it's a fiasco?

My prior incarnation lived in a world in which web applications were designed to mimic the desktop programs, for the user's convenience.

My current incarnation lives in the reverse dystopia in which desktop applications are designed to be web applications to piss off, alienate, and infuriate the users.

Enter MySQL workbench. It used to be marginally functional until the terminal geniuses in Oracle re-designed it to use a JavaScript-for-desktop framework and in the process broke every fucking UI advantage of desktop apps. Now, nothing works intuitively, as expected, but instead we got pop-up toasters in the corner of the screen.

You, genius developers, need to begin to worry about your lives because the now perpetually pissed off users may begin to stab you in the eye with a fork or slam you in the face with a brick. I am praying for these times to come.

You may ask how Oracle pushes everyone over to their oh-so-wonderful new version? Simple! By breaking the old one: Bug: Fedora 42 packages

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

Another Linux lie: we have Java build infrastructure

Truth is, you don't.

Enter Maven touted as the build system for Java. It is such a piece of shit! Well, everything that originates from Apache is, but this wins this disgraceful race hands down.

This crap rains sometimes errors, other times warnings (no rhyme or reason which it will be) on the developer, and its deluge cannot be shut off by the quiet optional parameter. Maven ignores it.

Need I tell that most of those warning errors are false positives? It will whine and moan about missing Javadoc for things like main description or @return, even after you go back into your code and add each and every /** Javadoc to all of your public methods? The skunk cannot shut up even when all of them are properly documented and keeps complaining about line numbers on which there are not even public methods or fields at all, like in the middle of a private declaration.

The fucktard complains about URLs in @see annotations. FFS, what else do you want, bitch? Try to remove https:// from your reference, and it will switch to complaining that the reference is not found, as if someone asked it to look for it.

The retarded brain child with an extra chromosome complains about missing @return description for void methods, for crying out loud. Shut the fuck up, already, Dumbelina!

It demands descriptions for throw. What? It's bad enough that I have to add them. All right, the IDE kind of takes care of that, but now I am even supposed to document their shit? As if I give a fuck about why some library function deep inside the JDK throws what kind of shit! Of course I don't give a damn. Document yourself, bitches.

Need I tell you that, like all genius developers, Maven's developers do not sort their warnings by the package or unit name? You can get warning errors about the same unit scattered all over its gigantic whine and moan sheet and go on chasing them over and over, cursing the universe.

Overall, Maven is an insatiable, stupid, lying beotch.

To add insult to injury, it whines and moans about plugins that are not even included in your POM!

Without doubt, Maven is developed by geniuses, and genius is as genius does: always as a degenerate. To gas chambers, all of them!

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

Netbeans is a piece of shit, but at least it is not Eclipse!

Just thought I'd went.

The idea of saving the IDE state is so foreign to Apache. They must be not using their own product. Otherwise they might have noticed how tediously inconvenient it is to re-open the same tree nodes every time.

As always, genius is as genius does: always as a degenerate.

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