Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Learn React for free

scrimba.com

Post reply on HN
Print view View original

41–50 of 73 posts

Re: Learn React for free

#41

Post by tracker1 »

thrower123 wrote: post #22
danellis wrote: post #17

Earlier quoted context omitted.

There seems to be a culture of collecting Udemy courses among fledgeling web developers.

Young web developers certainly seem to love video courses for some reason. Maybe I'm just old and crotchety, (well, one of those is certainly true), but I would much rather get my fix textually and go along at my own pace. Flipping pages or scrolling is still superior to trying to scrub through a video timeline.

It depends... if you're new to an entire workflow, it's sometimes easier. If you're learning something specific and adjacent to something you already use, text is usually best.

Re: Learn React for free

#42

Post by jammygit »

narwally wrote: post #18
danellis wrote: post #17

Earlier quoted context omitted.

There seems to be a culture of collecting Udemy courses among fledgeling web developers.

Do people actually put that kind of stuff on resumes? I've done a good handful of MOOC courses (usually not all the way through to be fair), but I can't imagine actually paying for a certificate so I can put it on my resume. If I want to show that I know React I'd rather just build something with it, throw it on github, and list it as a side-project.

Doesn't matter if you put it on your resume. You can use what you learn to build a portfolio project

Re: Learn React for free

#43

Post by jhcl »

mrborgen wrote: post #23
jhcl wrote: post #21

What on earth is the purpose of non-informative comments from non-informed accounts like these: - I started listening to this yesterday and really like it! Great, short videos! - Excellent. Thanks for sharing. - Great work Bob! - this is great The same time you can't find other background info about the company except that they collect VC money and the video's you create are MIT licensed.

What would you like to know about our company? The accounting for Norwegian companies are public, ours can be found here: https://www.proff.no/selskap/scrimba-as/oslo/internettdesign... We're two co-founders, Sindre and I. Our Twitter profiles are here: https://twitter.com/perborgen https://twitter.com/sindreaars If you actually spend some time researching, you'll find plenty of information about us and the company.…

Thank you for the information. I am however not an investor but a developer. When 'a free tutorial' is advertised i am always afraid i'll be forced into later payments or becoming the product myself, especially when professional investors are willing to support the company financially.

Giving information on your website about the user do's and don'ts are always appreciated without having to file a request in triplet to the board of directors. Still I highly appreciate the links to the company information.

Re: Learn React for free

#44

Post by matthewmacleod »

azangru wrote: post #39
matthewmacleod wrote: post #35

Earlier quoted context omitted.

Because it's kind of right, in the way that it's not technically accurate, but a bit of an approximation that's reasonable for a beginner-level introduction.

But how, how? I wouldn't be able to bring myself to say something that I knew to be strictly inaccurate. Even if you are talking to beginners, don't you owe it to them to say only things that you believe to be true? There are lots of ways to put it differently so that it wouldn't be so outrageously inaccurate and so that, if you are a beginner, more senior developers don't laugh at you if you repeat those things.

It's not that inaccurate. It's in the right ballpark, just glossing over all of the details of what that means in practice. Would you prefer "The virtual DOM helps make React work a lot faster than doing direct manipulation of the DOM using vanilla Javascript"? Doesn't really seem like it makes that much difference – and the author links to an external video that explains it all in more detail.

Anyway, any senior developer who laughs at a less experienced one for repeating that kind of thing is a bad developer. I'd like to think they'd take the time to correct the inaccuracy :)

Re: Learn React for free

#45

Post by tracker1 »

azangru wrote: post #39
matthewmacleod wrote: post #35

Earlier quoted context omitted.

Because it's kind of right, in the way that it's not technically accurate, but a bit of an approximation that's reasonable for a beginner-level introduction.

But how, how? I wouldn't be able to bring myself to say something that I knew to be strictly inaccurate. Even if you are talking to beginners, don't you owe it to them to say only things that you believe to be true? There are lots of ways to put it differently so that it wouldn't be so outrageously inaccurate and so that, if you are a beginner, more senior developers don't laugh at you if you repeat those things.

Sometimes it's easier to brush off a question, or make a statement in a learning context than get tied up in nuances. Do you really want to learn react with a 4-hour video on framework comparisons in the middle before you've learned the one you're looking at?

Re: Learn React for free

#47

Post by azangru »

matthewmacleod wrote: post #44
azangru wrote: post #39

Earlier quoted context omitted.

But how, how? I wouldn't be able to bring myself to say something that I knew to be strictly inaccurate. Even if you are talking to beginners, don't you owe it to them to say only things that you believe to be true? There are lots of ways to put it differently so that it wouldn't be so outrageously inaccurate and so that, if you are a beginner, more senior developers don't laugh at you if you repeat those things.

It's not that inaccurate. It's in the right ballpark, just glossing over all of the details of what that means in practice. Would you prefer "The virtual DOM helps make React work a lot faster than doing direct manipulation of the DOM using vanilla Javascript"? Doesn't really seem like it makes that much difference – and the author links to an external video that explains it all in more detail. Anyway, any senior dev…

> Would you prefer "The virtual DOM helps make React work a lot faster than doing direct manipulation of the DOM using vanilla Javascript"?

I am not sure this is even correct. Firstly, the famous js framework benchmarks (https://github.com/krausest/js-framework-benchmark) based on adding/removing list items used to have vanilla JS as an unbeatable winner, despite its direct manipulation of the DOM, and React was definitely significantly behind. Secondly, as the README for morphdom says, the real DOM is very fast (https://github.com/patrick-steele-idem/morphdom). If I remember correctly, virtual DOM was supposed to solve the particular performance problem where you would otherwise just throw huge chunks of DOM away rerendering them anew every time your app state changed. But this is a very special (although brilliant) approach to keeping your UI in sync with your app state; you wouldn't necessarily do so if you wrote your app with vanilla JS.

Re: Learn React for free

#48

Post by azangru »

tracker1 wrote: post #45
azangru wrote: post #39

Earlier quoted context omitted.

But how, how? I wouldn't be able to bring myself to say something that I knew to be strictly inaccurate. Even if you are talking to beginners, don't you owe it to them to say only things that you believe to be true? There are lots of ways to put it differently so that it wouldn't be so outrageously inaccurate and so that, if you are a beginner, more senior developers don't laugh at you if you repeat those things.

Sometimes it's easier to brush off a question, or make a statement in a learning context than get tied up in nuances. Do you really want to learn react with a 4-hour video on framework comparisons in the middle before you've learned the one you're looking at?

I'm just saying that there are more valid selling points for React than speed.

Re: Learn React for free

#49

Post by azangru »

azangru wrote: post #47
matthewmacleod wrote: post #44

Earlier quoted context omitted.

It's not that inaccurate. It's in the right ballpark, just glossing over all of the details of what that means in practice. Would you prefer "The virtual DOM helps make React work a lot faster than doing direct manipulation of the DOM using vanilla Javascript"? Doesn't really seem like it makes that much difference – and the author links to an external video that explains it all in more detail. Anyway, any senior dev…

> Would you prefer "The virtual DOM helps make React work a lot faster than doing direct manipulation of the DOM using vanilla Javascript"? I am not sure this is even correct. Firstly, the famous js framework benchmarks ( https://github.com/krausest/js-framework-benchmark ) based on adding/removing list items used to have vanilla JS as an unbeatable winner, despite its direct manipulation of the DOM, and React was de…

Oh, I am sorry, I re-read your sentence, and I think I misunderstood it. Yes, if React were using real DOM rather than virtual DOM it would have been slower, but the author was not trying to make _that_ point.

Re: Learn React for free

#50

Post by crooked-v »

acemarke wrote: post #30
crooked-v wrote: post #29

Earlier quoted context omitted.

Redux has the problem that (a) the read-only reducer concept is totally at odds with how a bunch of JS builtins work and so conceptually hard to understand for a newbie, (b) it has just so much boilerplate for "best practices" for even the simplest use case, and (c) it's not immediately clear what the benefits of wrapping your head around all that are. For me, it took me a while of working on a web app with derived d…

We've actually got a new `redux-starter-kit` package which includes some reducer utilities similar to `redux-actions`, but using the Immer library internally. That allows you to write simpler immutable updates that look like "mutation". There's also some helpers for common use cases like simplifying store setup, and generating entire "slices" of state at once (including generating action creators and action types aut…

createSlice is an interesting approach, though it feels like it's missing the use case of being able to set multiple keys in the same reducer from one action, as with my valueAB example above. It might be worth putting some thought into how to make a variant of it that can produce multiple reducers (one per key to be affected), not just one.
Post reply on HN