Honest Question. What is breakdown of market share angular versions market share? does anyone have these stats? I know not a lot of new projects are being done in angular 1 but I am under the impression that majority of jobs are still for angular 1.
Guide to JavaScript Frameworks
131–140 of 244 posts
Re: Guide to JavaScript Frameworks
#132Earlier quoted context omitted.
Same. Recently I had to do some web work and it is so daunting. Any tutorial for a given technology asks you to use a bunch of other tooling dependency that you don't understand. It's just mixed up dependencies everywhere even for little example projects. Something like create-react-app that is supposed to help you learn react. Set it up and just look at node_modules. Just a shit ton of dependencies and you have no i…
> Set it up and just look at node_modules. Just a shit ton of dependencies and you have no idea what any of them do. All this sort of scaffolding set up that you're supposed to ignore. Yeah, good luck going through legal/license compliance audit in any serious company doing software.
Funny, I've worked with multiple companies and their lawyers who were very serious about license compliance and what not. It took all of fifteen minutes to prepare a spreadsheet of our licenses (planned, anyway). Not a complaint from any of them, other than an "oh, that's more than I'm used to seeing."
The one sticking point was webpack 1; they had some dependencies with unlicensed dependencies. Fortunately, we were already leaning towards browserify anyway at the time. Webpack 2+ resolved those issues.
Re: Guide to JavaScript Frameworks
#133Earlier quoted context omitted.
> Set it up and just look at node_modules. Just a shit ton of dependencies and you have no idea what any of them do. All this sort of scaffolding set up that you're supposed to ignore. Yeah, good luck going through legal/license compliance audit in any serious company doing software.
Funny, I've worked with multiple companies and their lawyers who were very serious about license compliance and what not. It took all of fifteen minutes to prepare a spreadsheet of our licenses (planned, anyway). Not a complaint from any of them, other than an "oh, that's more than I'm used to seeing." The one sticking point was webpack 1; they had some dependencies with unlicensed dependencies. Fortunately, we were…
Fair enough. Now imagine that your product or service is gaining popularity on the market where Google or Facebook consider you a competition.
Re: Guide to JavaScript Frameworks
#134Earlier quoted context omitted.
To me React is superior for a very simple reason. There is a huge deficit of intermediate-advanced Vue tutorials compared to React. There are like 30 advanced-level tutorials on Egghead on React and like, what 3-4 advanced Vue tutorials (Nuxt, Nuxt and using Angular-like decorators to write proper classes instead of the 'it just works' vanilla boilerplate)? Learning the ropes of Vue is easy. It's a go-to framework of…
Add to that tooling compatibility issues with TypeScript & Vue
Mind elaborating? As of late, Vue's TypeScript support seems pretty nice.[1]
Re: Guide to JavaScript Frameworks
#135Earlier quoted context omitted.
That's how I feel configuring networking and load balancers and other backend stuff. I know its essential but for some reason front end and all its quirks makes more sense to me
Eeeh, configuring load balancers and networking are not backend tasks....... I mean yeah, that's done on the backend as well, but that's generally not what people mean with that term.
It depends on the developer. Myself I like to get in touch with where my code is deployed. So I like to do that stuff myself but most of the time there
Is somebody dedicated to that.
Re: Guide to JavaScript Frameworks
#136Come on. Where the heck is Mithril.
Re: Guide to JavaScript Frameworks
#137Earlier quoted context omitted.
Add to that tooling compatibility issues with TypeScript & Vue
Mind elaborating? As of late, Vue's TypeScript support seems pretty nice.[1] [1] https://vuejs.org/v2/guide/typescript.html
React has already has PropTypes, though. Just a few lines of code and you got state/context types covered, no need change your webpack config even.
Re: Guide to JavaScript Frameworks
#138Earlier quoted context omitted.
Honestly I don't think Vue is better than React, or React better than Vue. They are just different, and that's where a lot of the arguments come from. For me, Vue is such a monumentally large step backwards. I loved React because there are no templates, there is no 2-way binding, you don't have the vuex style state handling. Using Vue is an exercise in frustration for me, dealing with all of the templating headaches…
To me React is superior for a very simple reason. There is a huge deficit of intermediate-advanced Vue tutorials compared to React. There are like 30 advanced-level tutorials on Egghead on React and like, what 3-4 advanced Vue tutorials (Nuxt, Nuxt and using Angular-like decorators to write proper classes instead of the 'it just works' vanilla boilerplate)? Learning the ropes of Vue is easy. It's a go-to framework of…
ekhem.. check this tutorial: https://www.udemy.com/vuejs-2-the-complete-guide/ <- that's the only tutorial You'll need to master vue that's not its official documentation. You know why there's not many more advanced tutorials for Vue? Because that one COVERS IT ALL - once You finish it You're basically Vue.js dev that will solve any problem related to it.
Re: Guide to JavaScript Frameworks
#139I am trying to transition from Ember to React, but calling Ember "historically significant" is odd given adoption by big name companies (including Apple and LinkedIn) and very active development (3.0 should be out in a few weeks).
Re: Guide to JavaScript Frameworks
#140Earlier quoted context omitted.
But that shows some kind of misunderstanding, because you can literally build single page applications in 50 lines of code and a JS include in an html file. None of this stuff is that much work. People are really overestimating how hard it is, and you realize it once you try it. It's just people aren't familiar. https://mithril.js.org/simple-application.html Here's another app in another framework. Hard to get easier…
No, no misunderstanding. I was being snarky and referring mostly to the laundry list of items that most FE devs have running or install just to start building a FE. To me that seems ridiculous and shows me that FE devs have either not paid attention to the bloatedness that is Enterprise style development or have and walked away with all the bad habits.
Sweet summer child. Enterprise is churning out TypeScript as if it was the new Java.