Thanks for joining me @pluralsight to talk about javascript frameworks. We had 150+ awesome questions, so I'll try to answer the ones I couldn't get to online right here in a tweet stream
Watch the video -->
pluralsight.com/resource-cente…
A. @Polymer is an excellent way to create web components, which are ideal for creating sets of interactivity that can be shared in web apps.
2/n
A. At one time, quite possibly. A few years back we literally had framework overload. I feel it really has solidified into a few very strong choices.
3/n
A. See my previous question on this ... but in general, I think there is a lot of room for Web Components with frameworks.
4/n
A. Great for UI constructs, themes, styling, and experience.
5/n
A. Ha! My favorite language is JavaScript. I love the ease of jumping in, the flexibility, & how it works in all major browsers. @typescriptlang is awesome too. with it we get great tooling in editors like VS @code
6/n
A. not a question, but true that the space is evolving. And that is good!
8/n
A. I love PWAs. I look to those first. If an app is needed, then I look to @Ionicframework as it's very web focused and can create great apps. When all else fails I move to native.
10/n
A. No. Not even close.
11/n
A. Check out PWAs first. Then look into tools like @Ionicframework , @NativeScript or @reactnative
12/n
A. Easy is relative. They are all excellent. Try them.
13/n
A. Ask your stakeholders what their requirements are. Some apps can lose money if they are over a threshold. Some apps are ok with longer loads. While the solution may be technical, the experience holds the answer.
14/n
A. Spend a few days trying all 3. Cap each at a day. Then compare the experience that suits you. I see more jobs for React and Angular now, but Vue seems on the rise
16/n
A. Charts in my video show various answers. Angular paved the way & solidified a large field. React & Vue have risen strong and fast to join it. I'm not sure I would care about the fastest riser tho.
17/n
A. Great question. The community support & resources are hugely important. Good news is that all 3 have a lot to offer here. It's a key reason they all rock.
18/n
A. Angular. TypeScript will look very familiar to C# devs, and Angular is excellent with TypeScript. However, Vue works very well in TS now too!
19/n
A. Hmmm, great questions. I first recommend learning javascript and the sliding into a framework. Vue can be a great first step (drop a script tag in a page and go)
20/n
A. Entirely up to you as the developer. With any of these frameworks, you can pull in more complexity as needed. They just have a different way to solve problems.
21/n
A. I cannot speak for them, but Google is a big company, and I feel these tools (while have some overlap) solve different problems.
22/n
A. Technically, it feels solid. I don;t see as much usage and other data to support that it's anywhere near widespread as the other 3.
23/n
A. Best question yet! Totally off my head ...
Vue 👉 Darth Vader
React 👉 Darth Maul
Angular 👉 Padmé Amidala
24/n
A. Not that I am aware of. Why? Do these 3 lack for something you need?
25/n
A. Comet. Asteroid. Shooting star. Oh ... you mean the framework! (I joke). Very cool, but I stick to the 3 I mentioned.
26/n
A. Try each for a day, build a proof of concept, then compare
27/n
A. Thanks for asking! You get points for calling me out on not explaining it earlier! Progressive Web App. developers.google.com/web/progressiv…
28/n
A. Try all 3 for a day each. Then see which feels best to you.
29/n
A. Assuming we have an app not written in one of these now, then I feel Vue may be easiest to slide a small piece of code into it. Angular elements too.
30/n
A. Welcome to the community! Go right to Angular (v6 is the latest). The docs are awesome at getting going.
31/n
A. Try each for a day, then compare your experience. Then build something awesome! Lean on the community and resources, someone has done it before
32/n
A. Only in the sense that @typescriptlang will be familiar. i think @angular and @vuejs work great with it.
33/n
A. CSS all the way. So yes, but it's really CSS
34/n
A. They all support testing well.
35/n
A. It already is affecting them. They all have options for creating PWAs from their CLIs. I see this only becoming more prevalent.
36/n
A. If you mean ES5 ... Vue. If you mean modern standard ES 2017+, all of them. Classs, decorators, arrow functions ... all there.
37/n
A. I like @knockout_js . I built a lot of apps with it, and it's excellent at handling the views and bindings. I prefer the 3 I mentioned for full apps these days.
38/n
A. Sigh ... lots of great places to check out data on this. Me? The perf on these for 99% of the apps I see is fine in either of them.
39/n
A. Not so bad. They guide you on this. See this awesome guide from the Angular team's @stephenfluin update.angular.io ... Also, for the future, the CLI will do a lot of it for you!
40/n
A. All of them. Vue specifically was built with this in mind, but they all do very well.
42/n
A. Performance, features, tooling, resources, modern build tool support, docs. if you are doing it from scratch, yes, look to latest versions.
43/n
A. Check out the polyfills file and see the docs on this. it will help you fill in any javascript gaps in browsers that have any.
44/n
A. Very cool and a lot of promise. it may help get folks from other platforms to the web.
45/n
A. I'm not worried. NgRx has some great core team members. One is on the Angular team (@robwormald).
46/n
A. Yes. PWAs, @Ionicframework , @reactjs , @NativeScript ... all good options. Or @electronjs for desktop apps.
47/n
A. yes. features, community, resources ... pretty much everything is on par. It's like Java or .NET ... both are great.
48/n
A. People are successfully building small, medium, large apps with all of these without hitting major walls.
49/n
A. Thank you for asking ridiculous questions :)
50/n
A. Ha! I loved Silverlight ... the web changed ... a lot. I love html/css/javascript even more!
51/n
A. I don't think we need one thing to rule them all. Can you build a great app in javascript for a desktop app? Sure. But choose the right tool for the right job.
52/n
A. I get it. But spend a day w/ each. You won't regret it. Always start w/ the CLIs
53/n
A. I'm not aware of any.
54/n
A. Great move! Grab a JavaScript book, video, or online course. There are plenty of great options.
55/n
I'm also working on setting up a follow up video with @pluralsight to address trying all 3
A. Flutter intrigues me. But I use neither.
56/n
A. See my video ... depending on which survey, any or all of them. Take all surveys as input, but don't accept any single one as definitive.
57/n