r/javascript • • Aug 03 '16

Learn Modern JavaScript (nodejs, npm, webpack, es6, es5, esnext, typescript) for FREE

http://courses.angularclass.com/courses/modern-javascript
198 Upvotes

60 comments sorted by

View all comments

-55

u/[deleted] Aug 03 '16

"Learn to use frameworks around javascript that someone else created so you don't have to actually learn javascript."

67

u/reallyserious Aug 03 '16

Can you point me to a more fundamental js tutorial, like starting by soldering your own transistors and stuff.

0

u/[deleted] Aug 03 '16

[deleted]

0

u/[deleted] Aug 03 '16

[deleted]

12

u/djs113 Aug 03 '16

Hoooo boy! Look at Mr. "Create-Matter-From-His-Own-Thoughts" over here! I'll have you know that real PC builders have to gently strum the strings of reality so that one day a sentient race will develop the tools necessary to create circuits! It takes true patience! Sometimes you have to wipe the whole thing after millennia because they focus their time developing entire chipsets based around Dwarf Fortress!

2

u/[deleted] Aug 04 '16 edited Aug 04 '16

Haha, so true.

Javascript is not THAT complicated in and of itself, but in today's job environment, knowing the new standards and what most of the business world is actually using in their stacks is pretty damn important.

If you're JUST jumping into Javascript, you should probably focus on tutorials that teach you the basics so you at least have an idea of the general syntax of it and how it interacts with the DOM before jumping into modules and more complicated stuff.

→ More replies (1)

4

u/windyfish Aug 03 '16

While I agree in principle with the argument, a framework is a pretty essential for high volume, high data delivered apps. I'm using a front end framework every day for my job but the logic and design patterns stay the same. I just look at it like another layer of abstraction. Nothing wrong with that per se.

Edit: just seeing all the other replies and looool

→ More replies (1)

6

u/apphut Aug 03 '16

in the beginning, there were quantum fluctuations....

→ More replies (16)

0

u/[deleted] Aug 03 '16

[deleted]

3

u/ChronoChris Aug 03 '16

I think he is getting all the downvotes, because the first part of the course, is a break down of es5. It seems like you already need to have a fundamental js understanding.

9

u/emergencyofstate Aug 03 '16

I think the down votes are because the tone comes across douchey.

0

u/yesman_85 Aug 03 '16

Well get used to it. Why learn JS if you can do TS? Why learn C if you can straight into C#?

-2

u/ChronoChris Aug 03 '16

No, why would I want to use TS ever. Honestly. TS fixes the wrong problem with javascript. You don't structure a prototypal language like javascript. THAT IS ITS STRENGTH.

class Greeter {
greeting: string;
constructor(message: string) {
	this.greeting = message;
}
greet() {
	return "Hello, " + this.greeting;
}
}

var greeter = new Greeter("world");
var greetWorld = greeter.greet;
alert(greetWorld()); //undefined

The FUCK is this shit. That's not strongly typed. That's not what 'this' should be. TS fixed nothing. ES5/ES6 are better than ever. There is no reason NOT to default to JS. Comparing C and C# are completely different

5

u/[deleted] Aug 03 '16

since you "assigned" greeter.greet to greetWorld and called it from global scope, which has no "greeting" variable this is entirely expected. if you just used greeter.greet(); directly it wouldn't be undefined. this is JS behavior, nothing related to TS, just common misconception of how "this" keyword works in JS.

1

u/ChronoChris Aug 03 '16

If somethign is strongly typed, each type of data, is predefined. includnig objects. The this keyword should relate to the current instance of an object. If you truly wanted Tscript to be strongly typed, this should make sense in context to the current object.. "an advantage of strong data typing is that it imposes a rigorous set of rules on a programmer and thus guarantees a certain consistency of results."

So Tscript is failing in it's most fundamental attempts in this scenario. And there are many more

I think there is a little bit of bias here from the tools and languages you are accustomed to. I have absolutely no confusion how 'this' should work on the fundamental level of the object instance. Coming to Javascript, I liked this gotcha on the this keyword since technically the object instance was not the Greeter class. The problem I have is with TypeScript not matching what it is attempting to do. Bound the Object to be strongly typed.

0

u/[deleted] Aug 03 '16

[deleted]

→ More replies (1)

1

u/eighthCoffee Aug 03 '16 edited Sep 24 '16

.

4

u/Kminardo Aug 03 '16

The last line should alert the string from greeter.greet, but it will come back undefined (I don't do typescript, but seems to be what he's implying).

EDIT: Also it seems "this" isn't working as he would expect it to in ES5. But since 90% of developers don't actually seem to know how "this" actually works... at least typescript is consistent with most other languages in it's usage.

4

u/ChronoChris Aug 03 '16 edited Aug 03 '16

this works perfectly how I would expect it in c# or any other compiled language I can think of.

Edit: Kminardo. Please see my reply to eigth later in this chain.

→ More replies (5)

2

u/ChronoChris Aug 03 '16

If you see my comment later in this chain, you should understand that this is not strongly typed. The vary nature of the 'object' should not change in a strongly typed language.

→ More replies (1)
→ More replies (2)