magic_lobster_party

jQuery got popular because Internet Explorer, Firefox, Chrome and other browsers weren’t exactly cross compatible. Writing vanilla JS was risky business in that sense.

It also supported AJAX across all major browsers, which meant the website could make API requests without reloading the entire page. It was super revolutionary to press a button and it only changed a part of the page.

Then Angular and React took it a step forward and that’s where we are now.

JavaScript frameworks are invented because pure HTML and CSS suck for dynamically loaded pages, and vanilla JavaScript suck in general.

What’s not shown is that the car doesn’t have an engine. Management was really eager to release it to the customer. Don’t worry, it’s planned to get fixed later (spoiler: it’s never going to get fixed).

I was in on the crypto hate. I don’t really have a hate boner for AI.

Sure, there are things to dislike about AI, but it can be moderately useful. In contrast to crypto, AI is the hype because it’s widely used. Crypto was the hype because a few people hit the jackpot.

Rust and Cargo were built to be in a symbiosis with each other.

NPM is an afterthought of a rushed language.

Then you haven’t seen bad documentation (or had that sex you regret).

There’s also ”we do machine learning”, which usually translates to ”someone trained an SVM model 10 years ago”.

I don’t think the $500 million marketing budget would’ve worked if Java was introduced at a time other than the 90s.

The 80s would’ve been too early. It would just turn into a parenthesis in programming language history (next to smalltalk). The 00s would’ve been too late. It would’ve missed the dotcom bubble boat. Java came in the right time to become a dominant programming language.

I’m not saying the marketing didn’t have any influence. It probably had an big influence in which OOP language was selected for computer science education.

I don’t think OOP is as bad as many people make it out to be. It’s perfectly fine in moderation.

The problem is that it can lead to over engineered applications when abused.

Usually the teachers/professors/lecturers have no real world experience of software development besides the usually university projects

Adding to this: university projects are built on a relatively short timeframe compared to many industry projects. The growing pains that typically occur after a few years of continuous development is unlikely with the small scale of university projects.

I wouldn’t go to a university professor for advice on how to build a system that will last a decade of development.

AbstractionBubbleBuilderFactoryStrategyImplementation mind you

OOP was hype during the 90s. Schools adapted their curriculum to this trend. So they needed a programming language for this, and Java became the choice. C++ is too tricky as a first language.

The result is that a lot of people knew Java, which means it’s a good choice of language if you want to recruit programmers.

I believe most of Java’s success was luck. It released at the perfect time.

People aren’t writing new projects in COBOL. It’s mostly to maintain 40+ year old systems. Unless you’re working in the bank sector, it’s unlikely you will write a program in COBOL.

”Bomb has been defused”

More sensors in the car might help a bit, but the real problem in US is its car dependent infrastructure. If the only way home after a night in the pub is by car, then you’re going to get a lot of drunk drivers. Add to this that bikes have to share road with cars, then it’s a death sentence to ride bike by night.

Don’t forget about the access to free workforce in slave camps.

Fun fact: New Super Mario Bros turns 19 this year.

Yes, that means we’re close to the turning point where New Super Mario Bros gets older than what Super Mario Bros was when it was released.

&& git push --force

Google seem to be particularly bad at this. They did the same with Tensorflow. It was kind of the de facto deep learning framework until Google decided to deprecate everything. Everyone responded by switching to Torch instead.

Not only that. Emulators must often ”cheat” to achieve high speeds. This means emulators doesn’t try to achieve a 1:1 replication of what’s happening inside the hardware, but something that’s gives close enough results and better tailored for modern hardware.

The reason why N64 is particularly difficult is because each game must be optimized individually (due to the heavy reliance on microcode). The emulator must replicate the hardware at a much lower level for an accurate emulation of all games. Emulator developers can apply optimizations on each individual game, but it’s incredibly time consuming to do so for every game in the N64 library.