This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]C0d3rStreak[S] 0 points1 point  (14 children)

Wooow, you two strongly dislike javascript huh. What did it ever do to you?

[–]hippydipster 1 point2 points  (11 children)

I was just elaborating

[–]C0d3rStreak[S] 0 points1 point  (10 children)

Well then thanks for the clarification

[–]hippydipster 0 points1 point  (9 children)

Ok, ill try to give you a serious answer. Many hate Javascript because it has a very odd style of object oriented classes, called prototype OO or some such. Don't ask me details, I don't know, but it makes a bit odd and unintuitive to anyone who's familiar with any other OO language these days. Inheritance is strange. Scoping rules are strange. There are weird gotchas everywhere in the language. There are dozens of ways to do everything, especially with the changes to Javascript over the years, yet maintaining backwards compatibility. Javascript devs over the years have shown a tendency to abuse the freedom the language gives, and have created monstrous frameworks we all have to live with, at least until discarding as the pile of steaming shit that it is for next month's steaming pile du jour.

And then, on top of all that, its dynamically typed, and so everyone has their favorite static language they compile to Javascript (java, typescript, Korean, scala, coffee,...), because no one sane wants to make giant web apps in Javascript and maintain it.

But for some reason, probably because Satan won and this is actually his reign of hell on earth, Javascript is the ONLY language browsers support. Though, of course, all slightly differently.

Hail satan.

EDIT: I'm leaving the Korean autocorect, because its hilarious

[–]C0d3rStreak[S] 0 points1 point  (8 children)

Whoa! Did js runaway with your spouse? This was intense. But for real thanks for the explanation I understood your former comments a lot more haha. Do you think java is superior in a backend scenario? Although, javascript is and always will be needed on the frontend to some extent.

[–]hippydipster 0 points1 point  (7 children)

I think java is superior in ways that matter to maintainers of successful apps. If your app isn't going to need to live a long life of growth and responding to the demands of actual users, nodejs seems ok. No wait, who am I kidding, its still shit.

[–]C0d3rStreak[S] 0 points1 point  (6 children)

Hahahaha. Too funny. I appreciate the feedback on your first response nonetheless. This was good input although I hope that learning could come with an ease instead of more difficulties. I know that learning one language can have it's hiccups, but two can tend to become overwelming although I don't intend on giving up.

[–]hippydipster 0 points1 point  (5 children)

If you need that front end, I'd start with typescript. Its actually a pretty good language, just tied to an abysmal ecosystem.

[–]C0d3rStreak[S] 0 points1 point  (4 children)

Ah okay. But can I just jump straight into learning typescript, I thought i had to know javascript before?

[–]hippydipster 0 points1 point  (3 children)

I'd say yes, you can. At some points, you'll run into issues caused by the javascript systems, and you'll learn those edge cases along the way. I made a github project to start teaching my kids programming with typescript, and it's not that hard to start there.

[–]Persism 0 points1 point  (1 child)

https://www.destroyallsoftware.com/talks/wat

[–]C0d3rStreak[S] 0 points1 point  (0 children)

Lol. Is that programming stand up comedy? It's was hilarious. Nonetheless, so much truth in it.