Hacker News new | ask | show | jobs
by zeroq 20 days ago
In 2004 we solved the types for JS with ECMAScript 4 (or ActionScript 2.0).

Unfortunately this was in the middle of browser wars, so no one cared about the standards and all of that work was lost like tears in rain.

Around that time I attended MS conference where they introduced IntelliSense and it was a forming experience for myself. You could do actual programming basically with <space>, <dot>, arrow keys and <enter>.

"x = " and there are only two variables in the scope with the same type so IDE will present them to you in a drop down and you can already think about the next line.

Fast forward to ~2015 when I'm working on Angular project. The whole idea feels like a caricature Chinese whispers of an OOP framework. Each component is divided into three files, all of them have to identify themselves using a magic string, and that string has to be manually entered into each file.

There are couple of type systems, like the one from Facebook, but no one is using them. And everyone claims that OOP and types are the thing of the past.

Part of that corelates to a joke I was making back in 2013, soon after Apple killed Flash and everyone started doing JS everywhere. Major companies where posting job offers for senior javascript devs asking for 5-7 years of experience. But someone who was doing JS for 7 years in 2012 has all his career focused around gluing together jquery plugins.

Anyway, I'm as well glad that we finally did a full circle and finally have some sanity in the industry...

2 comments

> In 2004 we solved the types for JS with ECMAScript 4 (or ActionScript 2.0).

> Unfortunately this was in the middle of browser wars, so no one cared about the standards and all of that work was lost like tears in rain.

> Around that time I attended MS conference where they introduced IntelliSense and it was a forming experience for myself. You could do actual programming basically with <space>, <dot>, arrow keys and <enter>.

I think you’re off by at least 6-7 years. Visual Studio had autocomplete since at least version 6. And yes it was magical the first time you experienced it.

Aye, you're right.

My father took me to that conference so that would be closer to 2000 or 2001.

Fun fact, around that time I attended 3 "microsoft summit" - that was the name of the event - and every time the absolute banger, booked out months before the event, was a workshop with a guy who specialized in optimizing windows licensing for enterprise.

That was still the time when MS charged per CPU on servers, and the guy used to give couple seemingly basic scenarios and asking crowd how would they deal with licenses. Every time his version was 3-4x cheaper than what you would think of.

And by 2004 the browser wars where long over. That was the period when Microsoft left the web languishing on IE6 after destroying all competitors and then promptly disbanding their browser team. Firefox only got its name in 2004 and was released at the end of that year.
Not at all.

Ever wondered why, even on modern websites, css is riddled with repeated statements with this weird "moz-" prefixes?

In 2006 when working at Wikia I wrote a tiny lib for deep linking.

The lib started at 25 lines with naive implementation of the documentation. Two weeks later when I had all browsers on all operating systems mapped out it was close to 1,000 lines.

I've spent half of my coding time working with Flash, and the monopoly was great. You could make a layout, write a code and have absolute certainty that the outcome will look and feel exactly the same regardless if you ran it on desktop, in the browser - any browser, mobile or kiosk.

Few years later I did UI for The Witcher and Dead Island and with that you can add xbox and playstation to the list.

Last time I did some web programming was 3 years ago, but it was still a far cry from that experience.

God, do you remember that presentation Google gave when they introduced Angular 2.0? I think it was December 2015. It was sooo bad that in my eyes it killed Angular's momentum almost completely. I am surprised that it is still around actually. Can't find it anywhere though. Google must've censored it of the internet :)
I joined a consultancy a few years ago and Angular is the de facto standard at most enterprises we work for; I'm as surprised as you are.
Angular has C# and Java vibes, especially with frameworks like Spring. React is on the other side of that spectrum.
Angular is super used across the industry.

It's more common on consultancy than product companies.

And that's probably a product of different incentives.

Consultancy is getting paid for doing things. Product company is getting paid for getting things done.

Angular is a very solid library I personally like how it evolved.

I don't enjoy writing it, but I don't mind to maintain it, all apps have a predictable architecture.

Performance wise it's also extremely good, between stream based rendering and deferred rendering you can trivially ship lean and fast code.

It's a great fit for large parts of the industry defaulting to react which is notoriously difficult to tame when performance matters.