Hi, I am a Javascript apprentice. Can you help me with my project?

- Sure! What do you need?

Oh, it’s very simple, I just want to make a static webpage that shows a clock with the real time.

- Wait, why static? Why not dynamic?

I don’t know, I guess it’ll be easier.

- Well, maybe, but that’s boring, and if that’s boring you are not going to put in time, and if you’re not going to put in time, it’s going to be harder; so it’s better to start with something harder in order to make it easier.

You know that doesn’t make sense right?

- When you learn Javascript you’ll get it.

Okay, so I want to parse this date first to make the clock be universal for all the regions.

- You’re not going to do that by yourself right? You know what they say, don’t repeat yourself!

But it’s just two lines.

- Don’t reinvent the wheel!

Literally, Javascript has a built in library for t...

- One component per file!

I’m lost.

- It happens, and you’ll get lost managing your files as well. You should use Webpack or Browserify for managing your modules.

Doesn’t Javascript include that already?

- Yes, but some people still have previous versions of ECMAScript, so it wouldn’t be compatible.

What’s ECMAScript?

- Javascript

Why is it called ECMAScript then?

- It’s called both ways. Anyways, after you install Webpack to manage your modules, you still need a module and dependency manager, such as bower, or node package manager or yarn.

What does that have to do with my page?

- So you can install AngularJS.

What’s AngularJS?

- A Javascript framework that allows you to do complex stuff easily, such as two way data binding!

Oh, that’s great, so if I modify one sentence on a part of the page, it will automatically refresh the other part of the page which is related to the first one and viceversa?

- Exactly! Except two way data binding is not recommended, since you don’t want child components to edit the parent components of your app.

Then why make two way data binding in the first place?

- It’s backed up by Google. You just don’t get it do you?

I have installed AngularJS now, but it seems I have to redefine something called a... directive?

- AngularJS is old now, you should start using Angular, aka Angular 2.

But it’s the same name... wtf! Only 3 minutes have passed since we started talking, how are they in Angular 2 already?

- You mean 3.

2.

- 3.

4?

- 5.

6?

- Exactly.

Okay, I now know Angular 6.0, and use a component based architecture using only a one way data binding, I have read and started using the Design Patterns already described to solve my problem without reinventing the wheel using libraries such as lodash and D3 for a world map visualization of my clock as well as moment to parse the dates correctly. I also used ECMAScript 6 with Babel to secure backwards compatibility.

- That’s good.

Really?

- Yes, except you didn’t concatenate your html into templates that can be under a super Javascript file which can, then, be concatenated along all your Javascript files and finally be minimized in order to reduce latency. And automate all that process using Gulp while testing every single unit of your code using Jasmine or protractor or just the Angular built in unit tester.

I did.

- But did you use TypeScript?

"Is it sexy when I talk in nerd words? Ie 11....backwards compatibility....fallback..."

My fiancé.

3 rants for the price of 1, isn't that a great deal!

1. HP, you braindead fucking morons!!!

So recently I disassembled this HP laptop of mine to unfuck it at the hardware level. Some issues with the hinge that I had to solve. So I had to disassemble not only the bottom of the laptop but also the display panel itself. Turns out that HP - being the certified enganeers they are - made the following fuckups, with probably many more that I didn't even notice yet.

- They used fucking glue to ensure that the bottom of the display frame stays connected to the panel. Cheap solution to what should've been "MAKE A FUCKING DECENT FRAME?!" but a royal pain in the ass to disassemble. Luckily I was careful and didn't damage the panel, but the chance of that happening was most certainly nonzero.
- They connected the ribbon cables for the keyboard in such a way that you have to reach all the way into the spacing between the keyboard and the motherboard to connect the bloody things. And some extra spacing on the ribbon cables to enable servicing with some room for actually connecting the bloody things easily.. as Carlos Mantos would say it - M-m-M, nonoNO!!!
- Oh and let's not forget an old flaw that I noticed ages ago in this turd. The CPU goes straight to 70°C during boot-up but turning on the fan.. again, M-m-M, nonoNO!!! Let's just get the bloody thing to overheat, freeze completely and force the user to power cycle the machine, right? That's gonna be a great way to make them satisfied, RIGHT?! NO MOTHERFUCKERS, AND I WILL DISCONNECT THE DATA LINES OF THIS FUCKING THING TO MAKE IT SPIN ALL THE TIME, AS IT SHOULD!!! Certified fucking braindead abominations of engineers!!!

Oh and not only that, this laptop is outperformed by a Raspberry Pi 3B in performance, thermals, price and product quality.. A FUCKING SINGLE BOARD COMPUTER!!! Isn't that a great joke. Someone here mentioned earlier that HP and Acer seem to have been competing for a long time to make the shittiest products possible, and boy they fucking do. If there's anything that makes both of those shitcompanies remarkable, that'd be it.

2. If I want to conduct a pentest, I don't want to have to relearn the bloody tool!

Recently I did a Burp Suite test to see how the devRant web app logs in, but due to my Burp Suite being the community edition, I couldn't save it. Fucking amazing, thanks PortSwigger! And I couldn't recreate the results anymore due to what I think is a change in the web app. But I'll get back to that later.

So I fired up bettercap (which works at lower network layers and can conduct ARP poisoning and DNS cache poisoning) with the intent to ARP poison my phone and get the results straight from the devRant Android app. I haven't used this tool since around 2017 due to the fact that I kinda lost interest in offensive security. When I fired it up again a few days ago in my PTbox (which is a VM somewhere else on the network) and today again in my newly recovered HP laptop, I noticed that both hosts now have an updated version of bettercap, in which the options completely changed. It's now got different command-line switches and some interactive mode. Needless to say, I have no idea how to use this bloody thing anymore and don't feel like learning it all over again for a single test. Maybe this is why users often dislike changes to the UI, and why some sysadmins refrain from updating their servers? When you have users of any kind, you should at all times honor their installations, give them time to change their individual configurations - tell them that they should! - in other words give them a grace time, and allow for backwards compatibility for as long as feasible.

3. devRant web app!!

As mentioned earlier I tried to scrape the web app's login flow with Burp Suite but every time that I try to log in with its proxy enabled, it doesn't open the login form but instead just makes a GET request to /feed/top/month?login=1 without ever allowing me to actually log in. This happens in both Chromium and Firefox, in Windows and Arch Linux. Clearly this is a change to the web app, and a very undesirable one. Especially considering that the login flow for the API isn't documented anywhere as far as I know.

So, can this update to the web app be rolled back, merged back to an older version of that login flow or can I at least know how I'm supposed to log in to this API in order to be able to start developing my own client?

Don't you love it when there is a new minor release or a critical dependency and it breaks backwards compatibility without mentioning any of it in the changelog or docs?
I absolutely love it! ❤️❤️❤️❤️❤️
I certainly did not waste 3 hours of my life to find it. No i didn't.

Just got my Christmas present from Shopify:

You have 45 days to integrate with our new Billing API or lose your app on our app store.

Because I just LOVE dropping everything to deal with yet another mandatory Shopify change. Have you guys not heard of backwards compatibility?

My coworker just spent *weeks* getting our app approved, including submitting an obscene amount of information and multiple live reviews and now they're threatening to remove our listing from their app store if we don't adopt their new API by the end of January, requiring a complete re-submission and review to get it back on.

This is apparently a completely normal way to do business to Shopify.

Game Streaming is an absolute waste.

I'm glad to see that quite a lot of people are rightfully skeptical or downright opposed to it. But that didn't stop the major AAA game publishers announcing their own game streaming platforms at E3 this weekend, did it?

I fail to see any unique benefit that can't be solved with traditional hardware (either console or PC)

- Portability? The Nintendo Switch proved that dedicated consoles now have enough power to run great games both at home and on the go.

- Storage? You can get sizable microSD cards for pretty cheap nowadays. So much so that the Switch went back to use flash-based cartridges!

- Library size/price? The problem is even though you're paying a low price for hundreds of games, you don't own them. If any of these companies shut down the platform, all that money you spent is wasted. Plus, this can be solved with backwards compatibility and one-time digital downloads.

- Performance on commodity hardware? This is about the only thing these streaming services have going for it. But unfortunately this only works when you have an Internet connection, so if you have crap Internet or drop off the network, you're screwed. And has it ever occurred to people that maybe playing Doom on your phone is a terrible UX experience and shouldn't be done because it wasn't designed for it?

I just don't get it. Hopefully this whole fad passes soon.

JUST SHUT THE FUCK UP AND DONT TOUCH ANYTHING FUCKING IDIOT!

Changes my code while I’m in holidays, deletes the tests that fail and pushes it to master. No backwards compatibility or anything..

Now I can spend a week to revert all his changes because they break lots of stuff and pray that he didn’t mess up the data too much..

The joys of using overpriced enterprise software...

Me: Hey, I tried connect to the server, but I'm getting a "connection refused" error. Is it really running.
Other: hmm, I'll check
Other: The host restarted, but I'll get the software up again, no problemo
Other: I started the server again, but there's, but it's throwing errors while initializing. Time to write customer support

And then you get that premium customer support that think we don't know how to use their software at times. And once they realize we do, they don't know much better either. And once they realize we know how to use it there are 3 possibilities:
* They need our help to debug stuff before knowing what is going on
* They need to release a new version and accidentally break backwards compatibility and create enough work for us to burn through the clients contact hours
* They provide helpful advice (secret ending)

These fuck don't even release a proper changelog for their software nor their manuals.

Have any JabbaScripters ever heard of backwards compatibility?

Nope. Because all the shit on NPM is written by 15-year olds who don't know how to code properly, not to say maintain their packages.

Fuck you.

I make a presentation to explain to the boss why we had to tweak around the requirements in order to keep backwards compatibility and stuff. I take 15 minutes explaining how our system currently works and how these requirements would change it, etc etc.

"So... is this workflow okay for our customers?"

They stared into the presentation slide for a good minute.

"I think we should align this row over here with that square over there."

"Oh don't worry this is a demo. But do you think our customers will still be okay with these changes?"

"Yeah, but these two elements are unalligned and they look pretty bad."

I'm starting to think that fancy speech can deter people from questioning or complaining to you. I'm pretty sure they don't know their own product as well as I know it.

The first two stories on slashdot's homepage are:
1. Google releases Angular 2, breaks backwards compatibility
2. Apple releases Swift 3, breaks backwards compatibility

If you use either of those tools, why do you put up with this? When did software engineering stop being about building useful or enjoyable things for our customers, and start being about doing thankless make-work for Silicon Valley billionaire companies? Is this the legacy we want to leave to the world?

I was just writing a long rant about how my rant style changed, and how I could fix anything that annoys me in a heartbeat by just putting my mind to implementing a change. Then YouTube once again paused the synth mix that was playing on my laptop in the background, with that stupid "Video paused. Continue watching?" pop-up. I even installed an add-on for it in Firefox to make it automatically click that away. I guess that YouTube did yet another bullshit update to break that, for "totally legitimate user interface improvements" or whatever. Youtube-dl faces similar challenges all the time, and it's definitely not alone in that either. I also had issues with that on Facebook when I wanted to develop on top of that, where the UI changes every other day and the API even changes every other week. And as far as backwards compatibility goes, our way or the highway!

So I did the whole "replace and move on" type of thing. I use youtube-dl often now to get my content off YouTube into a media player that doesn't fuck me over for stupid reasons like "ad fraud" (I use an ad blocker you twats, what ads am I gonna fraud against), or "battery savings" (the damn laptop is plugged in and fully topped up for fucks sake, and you do this crap even on desktop computers). Gee I wonder why creators are moving on to Floatplane and Nebula nowadays, and why people like yours truly use "highly illegal" youtube-dl. Oh and thank you for putting me in Saudi Arabia again. Pinnacle of data mining, machine learning and other such wank could not do GeoIP. for a server that used to be in a datacenter in Italy for years, and recently has been moved to another hosting provider in Germany. It's about as unchanging and static, and as easy to geolocate as you can possibly get. But hey, kill off another Google+ when?

Like seriously, yes I'm taking your Foobar challenges and you may very well be the company I end up working for. But if anything it feels like there's a shitton of stuff to fix. And the challenges themselves still using Python 2.7 honestly feels like the seldom seen tip of the iceberg.

Fuck jQuery. The only reason I see anyone using it legitemately is because of backwards compatibility. Almost every jq method is either native js or native css. The problem is, some devs become practically dependent on a library. By then, they are no longer js devs. They are jQuery devs. When you find yourself going to the docs of a lib before native methods 9 times out of 10 you've gone past the turning point. When you find yourself including jQuery instinctively, you're gone. StackOverflow is a great example of this:

Question - 1 up
Pure JS answer - 0 ups
jQuery answer (same length) - 2 ups and accepted

Come on man. It's 2018! We shouldn't be writing jQuery anymore. Native methods ftw!

So we were supposed to have another good build today.

Supposed to.

This one guy on our team gets weird sometimes, and refuses to commit his shit until the last minute. He says "Don't worry, I'll handle all the merging, it'll be fine!"

What he forgets is that much of our code relies on his! His latest commits reworked a couple entry points and a class definition. No backwards compatibility.

He made his commit, and nearly our whole stack shit the bed. Jesus jumping Christ. Weekend? Nope.

Don't you just love it when an official Docker image suddenly switches from one base image to another, and they automatically update all existing tags? Oh you've had it locked to v1.2.3, guess what, v1.2.3 now behaves slightly differently because it's been compiled with OpenSSL 3. Yeah, we updated a legacy version of the software just to recompile it with the latest version of OpenSSL, even though the previous version of OpenSSL is still receiving security fixes.

I don't think it's the image maintainers or Docker's fault though. Docker images are expected to be self-contained, and updating the base image is necessary to get the latest security fixes. They had two options: to keep the old base image which has many outdated and vulnerable libraries, or to update the base image and recompile it with OpenSSL 3.

What really bothers me about the whole thing is that this is the exact fucking problem containers were supposed to solve. But even with all the work that goes into developing and maintaining container images, it still isn't possible to do anything about the fact that the entire Linux ecosystem gives exactly zero fucks about backwards compatibility or the ability to run legacy software.

Sitting at work. Just had a convo about older versions of Visual Studio. I was like "you youngins with you intellisense and backwards compatibility. In VS2005 we had to climb 15 miles in the snow. Uphill. And when we only had 200 compatibility issues with VS2008 we thanked Microsoft for the privilege. What Linux? You think my school provided Linux? Linux is for earners. Top sellers. Leaders of men. Cross-platform compatibility meant that it worked on a Dell with Windows and a Gateway with Windows. I tell you those were dark times."

FUCKING IE!
Anyone please remember to ask if the project|s that you're going to work on do|es need Internet Explorer support.
If it's the case just expect any resemblance of modern frontend development skills go backwards into the backward compatibility territory and never going forward.

I'll start looking for another job, can't be bothered for this payment and regressing my dev skills for client needs.
Again FUCK YOU IE!

So star wars republic commando and the only battlefront games just got added to backwards compatibility on Xbox one... Well there goes all my development time and hello childhood!

Finally finished the longest ticket I've ever worked on in my life. The ticket title and description was a pretty simple and straightforward one: "Upgrade from PHP 7.4 to 8".

If it was only so simple in real life. Our application is mostly done with API Platform framework, which is based on top of Symfony framework which is based on top of PHP language.

Once I did PHP 7 => 8 upgrade I needed to upgrade API Platform 2 => 3. But of-course that couldn't have been done as before that I needed to upgrade from Symfony 5 => 6.

This all was literally an equivalent of touching into a wasp nest - it took me a bit over 5 months and 800 hours of work and there was literally not a single source file left untouched.

In the process of all of this I've ran into literally dozen undocumented feature-breaking changes, broken backwards-compatibility promises and inside out architectural changes - from both the frameworks and the language itself.

Upgrading just one major version of anything SHOULD NOT be so hard. And to top it all up just to think I will need to do this again in a year or two..

Experiences like these really set my hate for time-based model of releases and the state of today's development in general.

I don't want new features or updates anymore. Almost every OS gets bloated with new features I don't want, while also breaking backwards compatibility and a working setup.
Phone? Apps not compatible anymore since update or just disappearing from the phone.
Computer? Often unstable updates, and since this has happened many times before I try to delay updates as long as possible but then caves in from the annoying update notifications.
Would love to get security updates, but come on, stop it with the bloat apps. Let me just uninstall the features I don't want and let me opt in instead. Make it possible to build extensions and plugins to customize behaviour. Why does software have to spoil like this?

The limit of backwards compatibility...

Dependencies and backwards compatibility

Can shit just fucking work instead of me having to download old shit that doesnt fucking work on the newest version of the OS that I use because the fucking program can't use new dependencies?

I'm looking at you you fucks that don't want to update to VS 2019 and force me to uninstall it to download VS 2015, its 4 years old for fuck sake!

(Warning: This rant includes nonsense, nightposting, unstructured thoughts, a dissenting opinion, and a purposeless, stupid joke in the beginning. Reader discretion is advised.)

honestly the whole "ARM solves every x86 problem!" thing doesn't seem to work out in my head:

- Not all ARM chips are the same, nor are they perfectly compatible with each other. This could lead to issues for consumers, for developers or both. There are toolchains that work with almost all of them... though endianness is still an issue, and you KNOW there's not gonna be an enforced standard. (These toolchains also don't do the best job on optimization.)

- ARM has a lot of interesting features. Not a lot of them have been rigorously checked for security, as they aren't as common as x86 CPUs. That's a nightmare on its own.

- ARM or Thumb? I can already see some large company is going to INSIST AND ENFORCE everything used internally to 100% be a specific mode for some bullshit reason. That's already not fun on a higher level, i.e. what software can be used for dev work, etc.

- Backwards compatibility. Most companies either over-embrace change and nothing is guaranteed to work at any given time, or become so set in their ways they're still pulling Amigas and 386 machines out of their teeth to this day. The latter seems to be a larger portion of companies from what I see when people have issues working with said company, so x86 carryover is going to be required that is both relatively flawless AND fairly fast, which isn't really doable.

- The awkward adjustment period. Dear fuck, if you thought early UEFI and GPT implementations were rough, how do you think changing the hardware model will go? We don't even have a standard for the new model yet! What will we keep? What will we replace? What ARM version will we use? All the hardware we use is so dependent on knowing exactly what other hardware will do that changing out the processor has a high likelihood of not being enough.

I'm just waiting for another clusterfuck of multiple non-standard branching sets of PCs to happen over this. I know it has a decent chance of happening, we can't follow standards very well even now, and it's been 30+ years since they were widely accepted.

Why does noone implement autoupdater, especialy on linux side? Is there a reason i dont get? Sure, most system stuff is better in apt, but if i install servers, i do not want to wait for these stupid linux release timings! If it were hard, id understand. But most of this is possible with something like GitHub API and 20 Minutes of time. I mean, yeah backwards compatibility and what not, but then handle that internaly.

Example: I use dnsmasq on a raspberry pi. RPI is running raspbian. Raspian is debian 8. Debian 8 has a version of dnsmasq with a pretty annoying bug, which prevents me from using dnssec, as i cant open any cloudflare pages. Why, o why isnt this updated at MY will? Then, if it isnt, why is it so impossible hard to compile this myself, no docs for that, no binaries, NOTHING? Dear server devs, please add atleast basic autoupdate functionality without having to rely on the base os.

Or, give me easily deployable binaries, if you cant write something integrated.

I hate python.

Who thought that creating a language that doesn't provide any backwards compatibility whatsoever without a way of managing versions is a good idea?

Someone explain this logic?

Contractor makes changes and then I have to fix because he can't as it's no longer backwards compatible.

I make changes and I need to enforce backwards compatibility. Yet these contractors are my seniors

I can work with Angular, even though it's pain in the but.
My current Angular job is actually the job with the first manager that had decent human values and ethics, I like my team, and yeah, what we building is shit. But it's only 30% shit because of Angular, another 30% are due to SAFe, and the rest is the usual stuff.
Still enjoy my job and respect my team.

But please do not expect me to pretend Angular is on a comparable level to React. Angular hasn't brought any actual innovation in most major versions but releases those breaking major updates still at least twice a year.
Ivy might be awesome, but only because Angular told the world 3 years ago also to have Ivy compatible compile targets for their libs/packages doesn't mean everybody cared.
And the ngcc, the awesome compatibility compiler, mutates node modules in place. So ne parallel stuff, no using yarn2 or pnpm.
At the same time, React brought so many innovations into the frontend world but is basically backwards compatible.

Not sure how the Angular partial compilation and whatever needs to go on works, but it seems like there's hardly anyone that really knows, so you can't use Vite or whatever other new tool.
And sure, if you're really good, you can write Angular without producing memory leaks.
But it's really hard. Do you know what's also quite hard: Producing memory leaks with React!

And for sure, Angular Universal, which isn't used by anyone, it feels like, will still be on a comparable level to an open source product that's used all over the world, builds the basis for an open source company, and is improved by thousand of issues day by day.

And sure, two kinds of change detection are a great idea. And yeah, pretending Angular comes with all included makes it worth it that the API is fucking huge and you're better of knowing nothing, because you have to read up things, than knowing quite a lot, since making assumptions and believing apis work in a similar way and follow similar contentions...

Whatever... I work with it. Like the time. Like the company, even my poss. But please don't expect my lying to you this was a good idea, or Angular is even remotely the same level of React.

Java 17 and I see methods in the API that apparently were deprecated back then in Java 1.1! Shouldn't deprecation be the precursor to being eventually removed? Or is backwards compatibility so much important that is ok to have shit in this limbo state for decades?

I have a nightmare project that I will probably be ranting about quite a lot in the coming weeks, but I don't want SEO to pick up the specifics on the off chance my peers Google the issues we're facing and my profile comes up.

Let me set up the scene by describing the predicament, and then I'll get to the most outrageous thing I've heard while working at this job. It gives you a CLEAR idea of why we're in this situation in the first place.

Anyways, the nightmare project only runs in IE with compatibility mode set to version 6. So it only runs in IE 6 at the latest.

And it is massive. I'm talking real, real enormous.

The most recent roadblock I ran into while Chrome-ifying it is the extensive use of a browser API that was removed 8 years ago.

It involves synchronous data input and I know for a relatively certain fact there's no way to fix it without combing through every single reference to this API and converting the ones that need sync data (not all of them do) to callbacks. How big of an issue is that?

Well, just one of that 15-ish modules has over 900 references to it. Even just creating a spreadsheet of "commented out / doesn't need a fix / needs fix" for each reference in 1/15th of this project would take days of manual labor.

Here's the rant.

So after discussing this issue in the meeting (we ended on "they don't believe me that we can't just replace it with jQuery") I brought up the next issue. One of our 3rd party libraries is so old it doesn't work anymore and we can't modify that code (it's compiled).

They said that even if it was backwards compatible (no fucking way. This version is like, at least 10 years old, I guarantee it) they can't simply replace it because we don't have a subscription to this product anymore (suggesting we find an alternative).

And I fucking kid you not, this is what happened next.

They then began discussing how this is why you shouldn't use 3rd party code. Because it becomes obsolete and you can't even fix it yourself because it's not yours to edit.

Yes. They said this DIRECTLY after we discussed our 900+ references to a browser API >>REMOVED<< 8 years ago. Yes, they said this about a 3rd party library that receives regular support but is totally FUCKED because we NEVER updated it after adding it and we never even renewed the LICENSE.

What the FUCK

Is this a technological metaphor?

For some Hacker challenge I was reading up on different keyboard layouts, Dvorak and stuff. And the technological lock in is baffling me: The rationale for qwerty was to reduce jamming of the typewriter letter arms. Today that doesn't make sense anymore, yet we stick to it. Wondering how much of today's tech is dragged down by things like that.

This stuff often also makes me weary of the first decisions, like choosing a protocol or data base - its kind and layout, because we might be stuck with it for reasons of backwards compatibility.... Like when Microsoft opted for the backslash as a directory separator..

Built a Svelte app year ago and it's broken today.

This is not the case with Windows. You can still run a app built on 1999 today.

Opened an issue on their repo requesting that they should add backwards compatibility.

No later than 5 seconds. It got closed and locked with this comment,

"Welcome to development when you don't write your entire stack yourself by hand.

Please open helpful bug reports or don't open any at all."

This is what every FOSS project got as defense. They think since they work for free, they can do what the fuck they want.

The defense is false because they put their OSS project on their resume and in return they get hired for full time work or consulting.

I fucking sue you Svelte if I had money to hire expensive lawyers. This time you are just lucky.

Fuck Oracle and their lack of backwards compatibility. Come on...

Fuck. I just realized that because I picked Firebase for an SPA I was making for a client a year ago, I will need to keep updating the damn backend forever. Node 8 has reached EOL in the end of 2019, so Firebase has deprecated it and will *remove support* for it in 2021. Ok, I updated the app to work with node 10. But what happens when node 10 gets deprecated and loses support? Am I going to be forced to update the project once again so that it can keep running? Have the people at Firebase heard of backwards compatibility?

The reason I chose Firebase in the first place was because I wouldn't have to deal with servers (stuff like that scared me back then) and because it was free (client likes free stuff, of course). Had I picked a simple Express + MongoDB combo I would be able to deploy the thing when I was done and just leave it there forever, at the cost of ~$5/mo on DigitalOcean. But no, I was scared of the unknown so now I have to live with the shitfest that Firebase is. Fucking hell.

Disclaimer: I would not use Express and MongoDB in a project today, I have outgrown JS backend (thank god) and I prefer the safety of a relational DB.

I fucked up my Windows installation by moving AppData to a secondary (1TB HDD) drive... dude... I wish they started a new and better Windows without all the backwards compatibility shit for new computers like mine, so we can do not complex, but not simple shit like freaking moving a "system" folder (that should only be for *apps data*).

I started with cakephp 2. I did a TON of projects with it and made my own reusable plugins for future projects and everything was nice and smooth.

then cakephp 3 came out with breaking changes and was not backwards compatible. I learned the new rewritten ORM and tried to do a project with it along with plugins.

then cakephp 4 came out with breaking changes and was not backwards compatible...

ok... look i dont claim to know more than the people writing frameworks but u want people to use ur framework u cant fuck them up in every major release and render their old projects unupgradable... fuck you im switching to laravel this was the last straw

Why is customer support sometimes so shitty? A coworker good a Win10 Laptop (Win7 before) and one program wasn;t working there anymore. So we reached out to the support asking to help us fix it. After over a month later and x-amount of E-mails back and forth. The answer was, you have to upgrade everything (Webserver, Database, Client) to use Win10 (no backwards compatibility). Which is fine, I don't mind upgrading and understand that software sometimes is not backwards compatible. BUT THAT IS SOMETHIGN TO STATE IN THE 2nd E-MAIL. Not an infinity later after a tiring back and forth of nonsense.

Why can we deprecate a regular language like Python 2 (26 months can't come by fast enough) but yet it seems web development is impervious to the idea? If you want to make a website, you must use HTML, CSS, AND JS (or a transpiled language).

I get we use it for backwards compatibility but this combo makes web development so messy and weird, it's hard to understand from a newcomers perspective.

Maybe I'm just too stubborn to understand 🤔

Software or hardware design solutions that are retrofitted for Legacy systems. I understand the value of backwards compatibility, but Gah damn!

Java/Maven Question

We have a project with source==target==1.7 in the compile plugin.

But on our servers we actually run it using 1.8 JVM. Is there any reason why we can't see it to compile with 1.8?

Or is it like the Windows backwards compatibility options?

Ok see this "trend" of adding a number 2 to a class name. To denote the new version of an object, surely I'm not the only person who thinks this is horrible. E.g Entity2, Renderder2 etc. It just creates a really bad API, I understand it's needed for backwards compatibility, but honestly there must be a better way....