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

Front End Development Topics to Learn in 2019

zendev.com

Post reply on HN
Print view View original

31–40 of 143 posts

Re: Front End Development Topics to Learn in 2019

#31

Post by aphextron »

DanielBMarkham wrote: post #24

This is a good list. Also web development has went down some insane rathole that it needs to eventually get out of. Let's look at it. Typescript: Javascript, only with strong typing from OO you love React: Use Javascript as if it were OO with IOC Vue: Finally the web component architecture that the web itself is coming up with in another few years, only here today CSS Grid: Miss tables yet? GraphQL: Install your own…

>CSS Grid: Miss tables yet?

It literally makes me feel like I'm cheating or something. What used to be an hour of fiddling around with floats and percentages is now two seconds of declaring a grid layout. Thank god for the evergreen browser revolution.

Re: Front End Development Topics to Learn in 2019

#32

Post by kokokokoko »

juddlyon wrote: post #4

This is a solid list, but front end dev has gotten a bit absurd. I feel like I need to install 86,000 dependencies via NPM to do something that server-side frameworks already figured out. I was following a simple Vue/Vuex tutorial the other day and my node_modules directory was 200MB+. Use yarn or npm to install XYZ.... What's the difference? Why do I have to google this as step 0? Why do you assume I know the intric…

I understand your frustration. One thing I'd like to mention is that a comment similar to your comment is frequently mentioned in any HN post about typical frontend/JavaScript topics. So frequently, that I'm not sure what it adds to the discussion at this point.

It's possible you are not aware of that and just wanted to let you know.

Re: Front End Development Topics to Learn in 2019

#33

Post by hanoz »

2019 may or may not be the year, but I'm sure it's coming - this inexplicably expansive land grab of web application functionality by client-side technologies is going to peak, and things will start to swing back towards the server side.

Re: Front End Development Topics to Learn in 2019

#34

Post by DanielBMarkham »

aphextron wrote: post #31
DanielBMarkham wrote: post #24

This is a good list. Also web development has went down some insane rathole that it needs to eventually get out of. Let's look at it. Typescript: Javascript, only with strong typing from OO you love React: Use Javascript as if it were OO with IOC Vue: Finally the web component architecture that the web itself is coming up with in another few years, only here today CSS Grid: Miss tables yet? GraphQL: Install your own…

>CSS Grid: Miss tables yet? It literally makes me feel like I'm cheating or something. What used to be an hour of fiddling around with floats and percentages is now two seconds of declaring a grid layout. Thank god for the evergreen browser revolution.

Happy path on all of this tech rocks. It's quite impressive.

Re: Front End Development Topics to Learn in 2019

#35

Post by evanriley »

kevinflo wrote: post #28
juddlyon wrote: post #4

This is a solid list, but front end dev has gotten a bit absurd. I feel like I need to install 86,000 dependencies via NPM to do something that server-side frameworks already figured out. I was following a simple Vue/Vuex tutorial the other day and my node_modules directory was 200MB+. Use yarn or npm to install XYZ.... What's the difference? Why do I have to google this as step 0? Why do you assume I know the intric…

This (or something like it) is always the top thread. I wish this was something the frontend community cheered about, not lamented. Those 200MB of node modules are developers ad-hoc cobbling together an alternative to xcode and android studio, except entirely modular and where we have complete control. Serious application development for the open web is hamstrung by limitations and definitely in an awkward growth pha…

> Edit: and for the record, xcode is a 13.8GB install

Not to take anything away from your post, but you're comparing a complete IDE & Simulator with dependencies for building a website.

Re: Front End Development Topics to Learn in 2019

#36

Post by jordache »

igotsideas wrote: post #29

Out of curiosity, are most companies/devs disregarding angular or is it slowly picking up?

>slowly picking up?

You seem to assert Angular is growing from a position of weakness? It's a very popular framework. Very structured, and with the introduction of the new Ivy rendering engine, I think it will get a bump in popularity.

Re: Front End Development Topics to Learn in 2019

#37

Post by ui-explorer12 »

juddlyon wrote: post #4

This is a solid list, but front end dev has gotten a bit absurd. I feel like I need to install 86,000 dependencies via NPM to do something that server-side frameworks already figured out. I was following a simple Vue/Vuex tutorial the other day and my node_modules directory was 200MB+. Use yarn or npm to install XYZ.... What's the difference? Why do I have to google this as step 0? Why do you assume I know the intric…

Why would someone need to preemptively learn both React and Vue? I can get saying you want to understand how they accomplish their respective roles, but is there an actual (non-crazy) scenario where your core, day-to-day job depends on really knowing both?

Or is that the whole point? Am I erroneously assuming "learn" means really deep knowledge(which for me really digging into any single one of these would be enough) when it means "known enough to pass a job interview when I ladder-up to the next company"?

Re: Front End Development Topics to Learn in 2019

#38

Post by acemarke »

kevinflo wrote: post #28
juddlyon wrote: post #4

This is a solid list, but front end dev has gotten a bit absurd. I feel like I need to install 86,000 dependencies via NPM to do something that server-side frameworks already figured out. I was following a simple Vue/Vuex tutorial the other day and my node_modules directory was 200MB+. Use yarn or npm to install XYZ.... What's the difference? Why do I have to google this as step 0? Why do you assume I know the intric…

This (or something like it) is always the top thread. I wish this was something the frontend community cheered about, not lamented. Those 200MB of node modules are developers ad-hoc cobbling together an alternative to xcode and android studio, except entirely modular and where we have complete control. Serious application development for the open web is hamstrung by limitations and definitely in an awkward growth pha…

Yep. To repeat Dan Abramov's standard reply:

> The set of dependencies that Create-React-App uses includes:

> A compiler. a bundler/linker, an optimizing minifier, a linter, a development server with live reloading, and a test runner

All of those are isolated and scoped to that one project, and they are all build-time dependencies only. It's also important to understand that Javascript packages are effectively distributed as source, which affects the number of files on disk. (Granted, many NPM packages do include unnecessary files in the published artifacts, but Javascript itself is a major factor there.)

As you said, a full-blown IDE like XCode or Visual Studio is easily multiple gigs, and if you were to look at the actual file size on disk of any C++ compiler toolchain, that would be a minimum of dozens of MB - those are just usually preinstalled on Linux or Mac systems.

So, context is pretty important here. A couple hundred MB for a complete JS build toolchain is understandable. I don't think it's necessarily _good_, and I think it can be improved a lot (especially with upcoming tooling like NPM Tink and Yarn PnP), but it's not the catastrophe many make it out to be.

Re: Front End Development Topics to Learn in 2019

#40

Post by hnmonkey »

evanriley wrote: post #35
kevinflo wrote: post #28

Earlier quoted context omitted.

This (or something like it) is always the top thread. I wish this was something the frontend community cheered about, not lamented. Those 200MB of node modules are developers ad-hoc cobbling together an alternative to xcode and android studio, except entirely modular and where we have complete control. Serious application development for the open web is hamstrung by limitations and definitely in an awkward growth pha…

> Edit: and for the record, xcode is a 13.8GB install Not to take anything away from your post, but you're comparing a complete IDE & Simulator with dependencies for building a website.

Yeah, it is completely missing me how web application dependency libraries relate in any way to an IDE for building applications. I don't get this argument and it doesn't seem to me like it makes sense. Perhaps I'm wrong and there's a connection I'm not seeing. Can anyone clarify this?
Post reply on HN