What is this I don't even know. Why does it exist? Why?
.d-flex
.d-inline-flex
.d-sm-flex
.d-sm-inline-flex
.d-md-flex
.d-md-inline-flex
.d-lg-flex
.d-lg-inline-flex
.d-xl-flex
.d-xl-inline-flex

Today I saw how the frontend devs on my team write Vue components + TypeScript. It's bad and it further proves that Vue=bad. Not even TypeScript can save it from being bad. Function defineComponent is ugly

NPM = BAD

Convince me otherwise

People do not know the value of simplicity... They want a system that does EVERYTHING ANYBODY EVER wanted, forgetting that this approach will always cause problems in future

Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
I typed every line instead of copying & pasting

Is there a cloud service that does nothing but redirect incoming HTTP requests to your home server without the need to have a static IP or an open TCP port ? Sort of like proxy

People who use destructuring assignment EVERYWHERE; why you do this to me?

In most cases it does not even reduce code length. Like

{ field } = object
save(field)

Why no just type

save(object.field)

Tis' hard to understand

I hate Vue framework with a passion. The only framework that can rival Vue in terms of being bad is: Apache Wicket for Java.

<template #activator="{ on, attrs }">
<v-btn
v-bind="attrs"
v-on="on"

What does this all mean? I remember seeing these 1 month ago but by now I forgot all about it again. This is nonsense; and the worst part is discoverability: there is no easy way to learn what does this mean, navigate to definition (where "on" is defined?) or something

Apparently Vue.js developers invented their own markup language which is neither HTML nor JavaScript, following their own special convoluted logic, using the most indirect approaches whenever possible and all the characters available on the keyboard {{#@.:;$-}}

Bad framework is bad...

I like all features of TypeScript except this single one:
🔴 Strict null checking; because it sucks >:3

The people who thought that providing customers with a template engine to build reports was a good idea - they made a mistake...

Users can't and won't understand a 500-line template file with 'content', 'columns', 'stack' and 'data:image' in it, and nesting levels reaching 10+

Now I have to build those reports with the added complexity of working around template engine limitations.

Can't blame the people who originally invented it. I can see how they might have thought their idea with those templates might have worked out. But it didn't work out, sorry

Not sure if a valid cause for a rant; but my memory stick went bad after being used for just 6 months. Bought this memory kit this summer on computeruniverse. Now Windows reports that there are damaged pages on the 1st stick; though the 2nd stick is fine. Patriot Viper with small heatsinks...

What to say... In ye olde days DDR3 worked for years and never went bad 🤔

I try to log in via SSH to a remote server. In the beginning all is well. It asks for my password, so I enter the password. Next thing: connection closed by the remote server.

So I wonder what the problem might be... I guess that perhaps I forgot to specify the username. Indeed when I try the 2nd time with my user name added in front of the host name - it works just fine.

But why is there no error message? Why not tell the user what's wrong? "User name is required". Can't be that hard?

Sometimes I see stuff and it just blows my mind why on Earth some things function so poorly. SSH exists for dozens of years yet the error message is not there -> it's guessing time.

I had a weird dream last night: at the office, my co-worker sliding a wide rubber band over my cup of coffee up and down 🤔☕

Me setting up Webpack for a project

Error: can't resolve ./src

Guess what? ./src exists. So I go searching for an answer, and it turns out webpack looks for ./src/index.js and if it can't find it then it throws an error.

But the error message is: can't resolve ./src

The issue was reported ages ago but webpack devs never improved the error message

THIS IS WHY WEBPACK SUCKS 💩

Yes it might seem like a little detail but it just makes it all the more obvious that Webpack sucks right from the start when you set up a project the error message is stupid and unspecific

Installed Ubunut 20 on my laptop (Thinkpad). It cannot open the App Store (with A letter on it). Imagine building a system, marking it as stable (long-term-support) and shipping it in such state that it is unable to launch the default (pre-installed!) app-store. This is Linux for you.

Updated the system; still cannot start the freaking appstore.

A frustration and a piece of advice - two in one...
Do NOT use InfluxDB 2 if you have more than 20 GB of data. I spent hours trying to get it to work, but it's no use. It crashes because it creates too many files to store all the data.

Apparently 20 GB is the limit 🤔💭

I'm debugging a script...

It takes 1+ minute to start because it loads data from remote API and apparently loading 80k objects takes a lot of time, even though I need only headers

I could optimize it. Like, add a local cache. But I will not.

Instead I will waste 1 minute, then another minute, then another minute, each time hoping it's the last pass, but no. I will waste the whole day on it and at the end of the day I will still NOT have the slightest idea why it is slow. That is what will happen, I predict it.

Good times

FACTS:
1. Gaming consoles are just PCs with a ton of limitations imposed on them by the manufacturer

Worst experience of 2020 for me was:
👎 that I had 0 time to code my side-projects.
Best experience of 2020:
🙃 can't think of anything good haha

FACTS:
1. Windows Mobile 6.5 was a more open platform than today's Android

Coworker writes functions accepting 8+ arguments, thinks it's ok

🤔 What if my co-workers see my rant on devRant and recognize that I'm ranting about the project that we're building together? Might be awkward *thinking

elites will understand

Google: buys Android
Makes tons of $ from Ads
Meanwhile 7 year old bugs
Are still not fixed

A bug reported in 2012: recently created files are not visible when using MTP protocol.

Guess what? I still have this bug on my 2017 phone, like many other people.
Probably has something to do with file cache.

Because obviously 7 years is not enough to fix a stupid bug. Especially when Google is busy implementing all the other features nobody asked for except marketing department

So I tried to set up Google AdSense on my website to show ads and earn some $... Next day AdSense console tells me that they've found "Adult: Sexual content" on my site. Like, WTF? There was nothing of such sort.