Do side projects in no more that two weeks, otherwise it’s doomed.

Just plain facts

My client's using some legacy server side software. I set it all up nice and isolated with proxmox, tunneled it through cloudflare, got the folks to do their install on a windows vm, passthrough their licensing usb. Hosted GLPI on it too (system inventory) and so on.

Wait for it. Windows Server refuses to accept local or domain passwords. WTF. Even went ahead and did a Utilman reset on it which lets you use an admin cmd prompt to the login screen where you could reset the password. Insane that it was even possible, but no good.

Client blamed linux for it, I switched over to Windows Server on baremetal. I setup Hyper-V thinking it should be just as capable as KVM.

Nope.

Guess what, you can't pass through usb for licensing (the legacy software). MOFOS DECIDED TO install it baremetal. I couldn't even get hyper-v to create a decent virtual network. It keeps changing all my network adapter settings. I COULDN'T EVEN PASSTHROUGH PCIE NETWORK CARDS.

This feels like an eternally stagnated, mossy soup of abandonware.

FUCK YOU WINDOWS. You've been sore pain the ass for EVERYONE.

!rant

What are people thinking when they are building datepickers (or any type of angular/jQuery plugin for that matter)?

Lets put all of the code in one file, place everything that should be dynamic and optimizable in constants, provide no localization support, finish it all up, publish it to bower and npm (so poor devs won't have to struggle) and last but not least don't accept pull requests with useful features for months!

Sony.

I don’t *hate* them, but I had really high hopes for Xperia smartphones back then, five years ago.

So I saved up and bought one. That’s what I got:
1. It was getting slower and slower
2. Micro usb broke just months after I got the smartphone
3. Sticky fragile screen with absolutely no oleophobic coating
4. NO UPDATES TO KITKAT AND LOLLIPOP! They just left us behind!

5. The main reason.

I catch moments with my camera. For me, camera is a vital feature, the most significant factor.

I once needed it really urgent and it just said “Camera is unavailable”. And that’s all. Camera is gone forever, broken. Factory reset haven’t fixed it.

You, alongside with Meizu, turned me away from android irreversibly and forever. When I heard about no update, I literally felt abused. Just like a girl whom random fuckboy made a proposal to, fucked and then left just months later.

With that level of customer support, basic respect to me as a user and buyer and that level of quality control, fuck you and your sloppy bricks you call smartphones. Maybe things are changing now, but I don’t care anymore and hardly ever will.

P.S. it heats up as hell, fucking pocket stove

Node developers are something else, you can work on a project that is 2 years old and find abandonware dependencies that were last updated 4 years ago.

Has anybody here ever successfully rescued an abandoned open source project?

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.