Earlier quoted context omitted.
I can't really understand the sentiment that front-end dev is absurd. I started with .NET years ago and find _anything_ that becomes 'standard' in the front-end more approachable than the constant reinventing of the wheel / new framework releases MS did circa 2004 - 2014. It was something like: - Learn ASP, opps we meant ASP.NET web forms. Actually, we meant .NET MVC. - Oh no, the world wants APIs ... please learn WC…
A while ago you could get away with doing front-end dev with nothing but a text editor and an FTP client, compared to those days I can see how things seem absurd now.
Front End Development Topics to Learn in 2019
101–110 of 143 posts
Re: Front End Development Topics to Learn in 2019
#102Re: Front End Development Topics to Learn in 2019
#103> 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.
Re: Front End Development Topics to Learn in 2019
#104Related to this topic: What are the minimum technologies needed to get a solid front-end stack, with a nice balance between modern features without framework/library/build tool/transpiling hell? For example, I don’t want to learn TypeScript when vanilla JavaScript will suffice. I’m wary of picking up the “hot” new frameworks because they haven’t stood the test of time and may get deprecated/irrelevant. Basically, I w…
If you like “pythonic” simplicity, use Vue.
Re: Front End Development Topics to Learn in 2019
#105Fullstack dev here, I'm still happy with jquery.
Simple example: your new dev changes layout or an ID or classname, and some code somewhere that relied on it via jquery breaks.
Re: Front End Development Topics to Learn in 2019
#106This 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 can't really understand the sentiment that front-end dev is absurd. I started with .NET years ago and find _anything_ that becomes 'standard' in the front-end more approachable than the constant reinventing of the wheel / new framework releases MS did circa 2004 - 2014. It was something like: - Learn ASP, opps we meant ASP.NET web forms. Actually, we meant .NET MVC. - Oh no, the world wants APIs ... please learn WC…
Meanwhile front-end has been changing continuously without adding much benefit.
Re: Front End Development Topics to Learn in 2019
#107Earlier quoted context omitted.
It's frustrating how the go to solution for a problem tends to be to install another module. I agree it's not smart to keep reinventing the wheel, but when the solution takes less than 15 minutes to implement the recommended answer shouldn't be another module.
why? I mean it takes far less than 15 minutes to install a module, so why should I implement it myself?
Any additional dependency introduces, among other costs:
* a potential point of failure
* a potential source of security vulnerabilities
* a potential legal liability and maybe some licensing constraints, and
* an additional aspect that needs to be maintained indefinitely and understood by any future developers.
Accepting all of this just to save a few minutes writing a simple function and maybe a test or two doesn’t scale very well. At best, it is replacing a superficial problem with a deep set of extra and ongoing responsibilities.
This is before we consider the time required to find and evaluate a suitable package, and even then, there is no guarantee that some random small NPM package from a source you’ve never heard of will be any better than what you’d have written yourself if you’re a halfway decent programmer.
Re: Front End Development Topics to Learn in 2019
#108Web dev is a complete mess, it’s true.
I also think the direction of travel is good from what I’ve seen, we’re making progress in improving it. For example, introducing types, getting away from hacks like bootstrap etc.
What I do find infuriating is that it seems most of the problems are not new and already well solved. Ultimately it looks like web dev is going to be quite similar to Android/iOS/Java Applet dev, which themselves are not particularly innovative (XML layout, MVC-variant style). Package management has been done a gazillion times but we have yet another tool, etc.
Anyone understand exactly how we got here?
I’d also be interested if more experienced people have a good idea what the endgame is, where this is all headed.
Re: Front End Development Topics to Learn in 2019
#109Interesting that Graphql makes the list - any frontend devs without considerable backend experience out there that have adopted it? Would be interested in your perspective on it vs rest or rpc.
Re: Front End Development Topics to Learn in 2019
#110This 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…
Wow you're right. And a lot of devs can't resist that temptation.