The feeling is mutual

The more enlightened is the elite, the more perverted is its mind. Such are enlightened ivory-tower dwellers from Mozilla foundation who believe that they can terrorize their dwindling user base with update nagging pop-up in the right-top corner of the screen.

That nagging pop-up would have been tolerable were it not bugged. Sometimes it does not visibly appear on the screen but it is there, it stole the focus, and it locked the FF window up. To realize it I first had to get some gray hair. Only after some clicking and hitting Esc button it shows up.

Of course, the first thing that comes to mind is to go to Mozilla Foundation's bug tracker or support forum and to ask how to disable the nagging. But they are only there to tell us that nagging is absolutely necessary, for our own good.

Bottom line is that if someone does not give a fuck about our opinions, then we are entitled not to give one about theirs.

After Mozilla Foundation gradually made useless the options setting 'never check for updates', then eliminated the policy JSON file's same option, and finally removed the function from about:config options to never check for update, the only way to shut FF up is to set to true the option of silent updates. Google it.

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

What do we call a 1+ trillion $$ global monopoly that terrorizes the world?

The only terrorist entity in the world that we need to be concerned about is Microsoft. They actively sabotage efforts of tens of millions of software developers, by introducing intentional bugs, flaws, and errors in documentation.

Enter ReportViewer control for WinForms or ASP.NET. It is bugged beyond imagination. It is scarcely and poorly documented. It does not work. It throws cryptic errors that not even MS support understands.

They actively sabotage our development efforts. Terrorists, all of them. And by the way, the fish rots from the head.

Posted by: LinuxLies at 05:49 PM | No Comments | Add Comment
Post contains 116 words, total size 1 kb.

Another Linux lie: we work with Windows

Truth is: we don't.

Read this thread to its end! An inept, ignorant, rude bouncer of a developer Christian Erhardt shoves off everyone affected by Ubuntu's new bug, on the grounds that 'there is nothing we can do'.

Oh, yes, German bitch! There is a lot that you can do: revert the bad change that you've made.

He is clearly, in no uncertain terms told that the bug was not there prior to their new release, but he does not give a damn about his user base. How typical of FOSS developers! They:

1. Develop away, without regard for quality.
2. Never test their code prior to releasing it.
3. Refuse to take responsibility for their missteps and to own up.
4. Close the ticket, to flip their users a bird and make them know their place.

Don't you love FOSS developers by now? I hope you cherish a warm, sweet love towards them, the one that makes you keep a box cutter close.

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

Why are they so fixated on the insignificant?

The C++ committee has been busy rewriting the language standard at ever accelerating pace. They want everything changed every few years. New this, new that, unlearn new, by the way, etc.

But they ignore really important stuff: exception handling. This is a gray area that no one in C++ business wants to touch with a 10' pole.

In my recent project I tried every exception-handling method that is known out there: try/catch, try/except, signal handlers - exceptions blow right through all of those methods.

Exception handling has been built into CPUs since time immemorial. It occurs, and the CPU generates an interrupt. Handle that interrupt, sons of bitches! Intercept it! Don't just ignore it in your usual 'anything goes' fashion. No! They are too busy rewriting another operator's specification. As if we are kindergartners whose noses need to be blown and hands held.

And everybody is silent about it! Why are you silent?

While you are, millions of recent students graduate from universities having been indoctrinated in rabid hatred of all things C/C++ and in worshiping shit like Python/Ruby/Go/Rust/Lua and a plethora of other sidekick "languages" that are devised as the next-best-thing to replace C.

End result? We have the dumbest generation of developers out there and have to use dumb products that they roll out. Congratulations!

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

The severe mental retardation of search engine developers is growing

LinkedIn. Touts itself as the worlds's greatest professional community. Filters in job search include the last 24 hours, last week, last month, and all times. Congratulations, assholes! Show me how you search on Monday, and I'll kiss you. The combination of endless scrolling and pagination is priceless. Under the 1st page of results they show you up and down voting buttons that... redirect you to another pages after you submit your vote. Huh? Are you for real, dumb twits? I am not done going through the search results yet. 'Apply' button cannot be right-clicked for opening in a private window. Privacy champions, my ass.

Indeed. Another clinical case of dumb and dumber. Every search resets filters. What did you think when you coded that? That you hate your job and would rather play golf?

Monster... I am begging you! Can't be dumber than that! It is so retarded that every time agents call and tell me that they found my resume on Monster, I make huge eyes. The reason being, Monster is a clinical case of 3 nested enldess scrolling in a confined vertical space, which is excruciatingly hard to manage with a mouse wheel. It becomes an exercise in extreme acrobatics. At least when LinkedIn or Indeed do not have any results for my search they have decency to say so. Monster silently dumps irrelevant jobs on its user: here, software developer, enjoy cleaner or plumber jobs!

Now, our civilization depends on search engines like it never had, but they fail us. Is this the fate that we deserve? Give it a thought, for a change, once in your lifetime.

Posted by: LinuxLies at 06:44 AM | No Comments | Add Comment
Post contains 291 words, total size 2 kb.

What can trillions of $$ not buy you? Sanity.

In C# projects, Visual Studio has zero problem creating copies of source files, with '- Copy' after their names. Not in C++ projects! No, that'd be too nice to developers.

We are witnessing global, wholesale sabotage of C++ development, by Microsoft. They bully C++ developers. Why do they do it? Perhaps, like I had written, they only want to develop performant software themselves. They want to keep the monopoly on high-performance Windows software. No one but MS devs is allowed to develop it.

They are so small, so tiny in their mind and soul that they want the death by 1000 cuts on us. There is no other explanation why C++ projects in VS are so retarded.

Insanity of the situation is nailed by the simple fact that MS considered it a gaping problem, an urgent matter to introduce range operator to replace String.Substring() in the latest C# but did not want to touch any pain points in it. They focus on the insignificant, every time, all the time. The small-minded biggest corporation in the world. Who would've thought?

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

Another Linux lie: systemd has advantages over whatever

Truth is: it does not. It is a lie.

Did you ever try to run journalctl on a system with history, through ssh? Try it! I will take bets on how long it will take you to curse everything and install rsyslog or syslog-ng.

Genius is as genius does: as a degenerate. Genius degenerates in systemd dev team do not care how their bastard child journalctl performs. Zeal is their driver.

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

That bitch jusst mocks the all Linux users and laughs at us from under its rock

Some time around the release of Fedora 19, the inbred piece of garbage who calls himself the developer of xrdp fucked something up in his code, and the package stopped working under all Linux distros.

Google 'xrdp login error', and you will find many questions about how to fix it and very few answers. This crap just does not work anymore, but the waste of skin who develops it does not give a flying fuck.

Decades pass, but Linux users still edit tons of files, fix bugs in them, copy files around, create new files, run scripts, restart services, to no avail.

Why are you silent? Why do you not scream into the bastard's face: You, bitch, must learn to test your software before you release!

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

Logical fallacy of the year: Protonmail bans service registrations

One cannot use Proton mail, to register on sites, because according to Proton mail's notice, they do not want to be banned by those sites in case subscribers try to avoid registering with their "real" emails.

Now, give that a thought! Proton mail cannot be used to register because they are afraid that they may be banned for allowing subscribers to register. So, either way Proton mail cannot be used. Congratulations, dolts! Your hyperactive minds invented something that keeps you occupied but achieves net zero result.

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

Another Linux lie: we have a web browser

Truth is: no, you don't.

Tried to print web pages to PDF from a recent Firefox. They cannot be opened either in Acrobat Reader (file is damaged blah-blah-blah...) or LibreOffice (file is encrypted blah-blah-blah... on Windows or ASCII filter is offered on Linux) or Firefox itself (shows a cute blank tab with modern Acrobat Reader controls up top).

They do not test their software. If only they tested, they would have noticed that files are corrupt/unreadable. Or they did notice it but did not give a fuck. Oh, this wonderful new world of untested releases and inept developers. Soon, this filth will spill into air traffic dispatch and nuclear station control software. Mark my word.

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

Another Linux lie: we have portable C++

Truth is, you don't.

The one-size-fits-all answer to all questions in C++ world is not 42 but 'you do not need it'. The know-it-all types at C++ whatever committee and around it bestow their divine wisdom on anyone who tries to do something. That wisdom is 'do as I say or'.

Enter std::chrono namespace and its steady_clock type that is only suitable for accurate measurement of short time intervals. It is a thing of its own, incompatible with just about anything.

You are not supposed to convert it to any meaningful, reasonable time units "because you do not need to". When you get strange results from your code and want to ensure that it is doing what you want, you will not be able to output any time_points that your code populates along the way. There is no conversion from steady clock time points to any other data types that can be output to console. End of the story. Dead end. You are either allowed to take accurate measurements or you are allowed to output them, never both.

Enter std::thread. There is no way in hell to obtain the current thread's native handle. These fucking idiots do not give a fuck that we have to interact with OS-specific calls. They do not give a damn that we may have to manipulate threads in OS-specific way. They are all portability, and fuck all.

I am beginning to hate std namespace with passion. I wish their authors slow and painful death because they go out of their way to achieve extreme sophistication and in the process make things so unfathomably complex that they throw baby out with water.

Posted by: LinuxLies at 05:55 PM | No Comments | Add Comment
Post contains 290 words, total size 2 kb.

Only Microsoft is allowed to develop performant software. No one else is!

Suppose, you are like me, and you need to write a high-performance application. Its performance has to be as high as your hardware would allow. Naturally, you would write it in C++ instead of .NET languages. Not so fast, sucker!

Microsoft has gone out of their way to make your life as miserable as possible. The tooling of Visual Studio for C++ development is nearly as rudimentary as a text editor.

In .NET projects, you can create copies of files, by Ctrl-dragging them to the same or different folder. In C++ projects, it is "Screw you, Benny!". You cannot drag-n-drop files unless you turn on "Show all files" but to add insult to injury, even then VS won't allow you to drag and mock you with a pop-up dialog that asks whether you want to copy a file onto itself.

Microsoft just won't allow you to develop in C++. You are not allowed.

Did I mention that no refactoring is available to C++ developers beyond basic renaming? Now I did. I tried to extract functions, only to be mocked by error message that told me that VS could not extract due to an unknown error. MS never knows their errors. Who wudda thunk?

Did I mention that C++ unit test projects are a gimmick? Now I did. They essentially do not work in a sense that it is not enough to #include your .h or .hpp files. You have to include .cpp files as well!

How did they manage to make .NET projects work? By project references. The reason being that every .NET assembly, no matter whether .exe or .dll, is an assembly. It does not matter the format. But unmanaged .exe does not expose functions, so you have to re-include all sources into your test project. MS did nothing, nada, zilch to alleviate our pain. Essentially, unit tests for C++ do not exist, i.e. a gimmick.

Posted by: LinuxLies at 04:11 PM | No Comments | Add Comment
Post contains 341 words, total size 2 kb.

Instant messaging sounds like freemason handshake

Did you too notice strange similarity among all instant messaging FOSS projects out there, without exception: they are secretive as fuck?

Whenever issues occur, it is futile to ask for help: none will be provided. They will ask you all sorts of intrusive questions and demand that you post their software's logs to which they dump plain-text passwords, IP addresses, domain names, user names, logins, contact details, yada, yada, yada.

When you challenge them as to the reasons for such prying practices they will circle wagons, push back, and resort to all kinds of social engineering techniques designed to discredit you as a user and your competencies as IT professional.

I've seen this with quite a few: Jitsi, Gajim, Pidgin, Jabberd, OpenFire, Spark, Asterix, Kamaillo and others that I can no longer remember. Never ever I got any resolution to issues with those softwares, no matter how blatantly obvious it was that it was their fault.

Jitsi team, for example, was totally uninterested in their 'thing' freezing solid when keyboard layout was switched as if there was only one language in the universe. Did I mention that they blamed Java? Yes, Emil Ivov had audacity to tell me that Java had a bug with switching layouts even though that nothing written in Java at all on Earth had any issues switching keyboards.

The reason for that is likely that IM projects do not act in good faith. Their goal is to be malwares. Once I mentioned that my IM infrastructure was behind a firewall, and they told me it was the reason it did not work as expected. I lied: there was no firewall. I baited them, and they bought it.

Careful with FOSS: many of them are neither F or OS.

Posted by: LinuxLies at 12:34 PM | No Comments | Add Comment
Post contains 304 words, total size 2 kb.

Genius is as genius does (usually as degenerate)

Gitlab is great, isn't it? It is awesome. Its developers are also awesome and genius. So genius that they dump plain-text SMTP and transactional email service provider passwords to logs and then they ask to see the logs when someone comes to their site for troubleshooting.

What is with this world that insists that software development be done by genius degenerates, preferably in China

Gitlab devs in particular and Rubi devs in general are so exceedingly genius that they need layers and layers and layers of sophisticated shit like this in order to achieve trivial things like sending an email.

Listen to them! You need to run a Ruby console (whatever the fuck that is) and ensure that the method is the same as in gitlab.rb... Why do you keep one thing in two places? Too genius for the universe?

They are so exceedingly genius that their log format is the opposite of human-readable: it has timestamps at the end of the line and only on some lines. Good luck investigating WTH is going on!

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

Microsoft: "I don't give a fuck!"

For decades now, cohorts of .NET developers try to code their applications to play the default system beep and fail. This simple line of C# code just does not work, no matter what:

SystemSounds.Beep.Play();

Search online, and you will find questions with no answer. Questions from way back, from the earliest days of .NET and up to the present time. Solutions? A plethora! But nothing that works in 100% cases.

People of Earth! We have to become concerned because even a multi-trillion-dollar global monopoly that makes the OS, framework, compiler and WAV files involved is not able nor willing to address this problem. They instead blow their budgets on redrawing their products' icons, almost every year.

If they are such inconsiderate, careless, rude, brazen jerks, then why are we supposed to be nice to anyone? Answer me!

Posted by: LinuxLies at 01:13 PM | No Comments | Add Comment
Post contains 149 words, total size 1 kb.

MS: When you document something, try to make your documentation accurate

After all, Microsoft is a multi-trillion $$$ global monopoly that apparently has enough $$$ to blow on the annual redrawing of icons and reshuffling the GUI.

If you are like me and going nuts because you are trying to serialize a collection of POCOs w/o those fucking namespaces being added to the collection element, and you are using DataContractSerializer and its supposedly but not-so-helpful attribute [CollectionDataContract(Namespace = "")] but still getting shit like

xmlns:i="http://www.w3.org/2001/XMLSchema-instance"

on your collection element, then do not try to find any wisdom in Microsoft's documentation: it's not there.

Documentation says that the attribute's Namespace property "Gets or sets the namespace for the data contract. That is not true. That is misleading and inaccurate. In reality it setts an ADDITIONAL namespace on top of the above piece of shit. You are SOL unless you massage the generated XML, which is lame.

That is why you may get the feeling that [CollectionDataContract(Namespace = "")] is being ignored. It is not! It works exactly like Microsoft's developers Hu and Wen designed it. It is just that Microsoft's technical writer Wei neglected to mention its true function. Or maybe they are developers Abishek and Kumar and the tech writer Rajendra. All the same shit.

Having written the above post, I went googling to see what other unfortunate souls tried, and I found this lament that does not have an answer to the day. The genius degenerate Frère Chloé suggested a custom serializer. She gets the Wasteful employee of the year award.

Someone commented how insane is the complexity of getting correct XML out of MS' classes. Yes: insane is as insane does. Wink, wink.

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