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

61–70 of 143 posts

Re: Front End Development Topics to Learn in 2019

#61

Post by koboll »

cageface wrote: post #49
Etheryte wrote: post #42

> CSS grid > If you’re still using heavy-weight grid frameworks from UI toolkits like Bootstrap or Foundation, you are falling behind. This is a pretty sensationalist way to word this and honestly an absurd statement as a whole. If you have a public-facing site, ignoring everything that isn't up-to-date is a luxury you can't afford and blunt statements like these show ignorance in that regard.

CSS grid is supported in all modern browsers. Depending on your audience, there is a very good chance you can use it in favor of older and much less powerful and pleasant grid layout tools.

According to CanIUse, it's supported in browsers used by 88% of users in the United States. Which means sites will fail to render properly in 12% of browsers.

Developing for a b2b or enterprise product? That percentage is going to be lower. Developing for users outside advanced industrial countries? Lower.

And it's not like you can polyfill it or use a fallback -- CSS grid is a completely new way of building layouts that isn't amendable to automatic fallbacks, so you literally have to build an entirely different parallel way to do the same thing if you want those 12% to have the same experience. At that point... why bother using CSS grid at all?

The simple and sad fact is that until IE 10/11 fall totally out of use, grid is simply not worth learning for many projects.

Re: Front End Development Topics to Learn in 2019

#63

Post by cageface »

koboll wrote: post #61
cageface wrote: post #49

Earlier quoted context omitted.

CSS grid is supported in all modern browsers. Depending on your audience, there is a very good chance you can use it in favor of older and much less powerful and pleasant grid layout tools.

According to CanIUse, it's supported in browsers used by 88% of users in the United States. Which means sites will fail to render properly in 12% of browsers. Developing for a b2b or enterprise product? That percentage is going to be lower. Developing for users outside advanced industrial countries? Lower. And it's not like you can polyfill it or use a fallback -- CSS grid is a completely new way of building layouts…

CSS grid works in IE11 with a few restrictions. Requiring IE11+ support is quite common for websites targeting the US market at least. Unless your audience is pretty unusual it's easy to make a case for excluding older browsers than this.

Re: Front End Development Topics to Learn in 2019

#64

Post by pascalxus »

It's pretty difficult to keep up with all the new frameworks these days. That's why I created a faster way of learning. I noticed that everytime I wanted to learn a new framework or new library, I was always creating examples and modifying them to learn how they worked. So, I created a Tutorial/Example code website that combines tutorials with real working examples: https://codeorc.com

By not having to set up every single example anew, I hope this saves people some time in allowing them to learn things quicker.

Re: Front End Development Topics to Learn in 2019

#65

Post by marcosdumay »

DanielBMarkham wrote: post #34
aphextron wrote: post #31

Earlier quoted context omitted.

>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.

Besides Internet Explorer, what failure mode does CSS grid have?

Re: Front End Development Topics to Learn in 2019

#66

Post by fineline »

acemarke wrote: post #21
Zelphyr wrote: post #15

Earlier quoted context omitted.

Oh, yeah, it is. I used to love npm and then didn’t use it for several years. I’ve gone back to it lately and find myself screaming “what have you people done?!” on a regular basis now. And while we’re on the subject of package managers; do we really need so many? I know npm is terrible but it seems like everyone has decided to create their own now. I swear to god I had to use a package manager to install a package m…

There's only two primary package managers for Javascript that are in common use. (For point of comparison, Java and Python are in a similar situation: Maven and Gradle, pip / pipenv / poetry / pip-tools, etc.) NPM is the package manager built by the NPM company. It's included with Node. Primary selling points: it's "official", and NPM has included the package auditing tech they purchased. Yarn was created by a team f…

There is a third alternative with a clear advantage over these two. PNPM is an NPM client that installs versioned packages into a central location and uses file system links within the 'node_modules' folder of individual projects. For a typical developer with many local projects this is a huge disk space saver. It also uses the original and much clearer nested structure of node_modules. I don't know why NPM didn't adopt the shared package approach, or why yarn didn't either, but PNPM gets it right.

Re: Front End Development Topics to Learn in 2019

#67

Post by acemarke »

fineline wrote: post #66
acemarke wrote: post #21

Earlier quoted context omitted.

There's only two primary package managers for Javascript that are in common use. (For point of comparison, Java and Python are in a similar situation: Maven and Gradle, pip / pipenv / poetry / pip-tools, etc.) NPM is the package manager built by the NPM company. It's included with Node. Primary selling points: it's "official", and NPM has included the package auditing tech they purchased. Yarn was created by a team f…

There is a third alternative with a clear advantage over these two. PNPM is an NPM client that installs versioned packages into a central location and uses file system links within the 'node_modules' folder of individual projects. For a typical developer with many local projects this is a huge disk space saver. It also uses the original and much clearer nested structure of node_modules. I don't know why NPM didn't ad…

I did list that one in my comment :)

Re: Front End Development Topics to Learn in 2019

#68

Post by gammateam »

I need a site that tells me that something as simple as

npm install

would really be

sudo CXX=clang++ npm install --unsafe-perm

with some explanation of what really went wrong alongside the disclaimer about the negatives of using anything unsafe-perm

every framework or language has developer tool nuances like that which waste devs hours.

Re: Front End Development Topics to Learn in 2019

#69

Post by AznHisoka »

freedomben wrote: post #56
nishmastime wrote: post #18

Earlier quoted context omitted.

I think it's weird to compare server application development to client development which is an entirely different beast. Client development on any platform is more complicated than the server stack. Back-end API devs have a much simpler job for most apps too. We as back-end devs like to pretend otherwise even though our app runs on just one machine.

> Back-end API devs have a much simpler job for most apps too. We as back-end devs like to pretend otherwise even though our app runs on just one machine. I don't see how you could possibly say this in such general terms. Every app is so different. Even simple crud apps of any size are not running on "just one machine." Even most small backends have at least an API server and a job server, plus database(s) and queue(…

Yep, sometimes the front end is more complicated - it depends on the application. Generally speaking though, the hardest problems in the backend are much harder than the hardest problems in the front-end. Like, I'm sure the PhD's Google are hiring are not working on front-end stuff.

Re: Front End Development Topics to Learn in 2019

#70

Post by gammateam »

Vue, Angular function similarly with prefixed/namespaced directives and insertion techniques

v-if

ng-if

This is more of a matter of untechnical recruiters, resume crawling bots, and technical interviewers understanding that these are the same skill sets and concepts to make the labor market slightly more efficient.

All the company's devs are going to be using the resource manual and stackoverflow either way, and most of their time will be messing around with the dev tools than figuring out the most academically efficient solution within the allotted time.

Post reply on HN