I would like to know which.

Versteegh: Cool, well, that answered that then lol. cheers

Mcgaffee: So just to clarify. i’d use something like modernizr to check that the specific html/javascript/jquery i’m using is supported by the browser, and if its not, i have a fallback code aka polyfill that will replicate that functionality?

Kiewiet: You generally just include the polyfills and they do nothing if it’s a modern browser

Savory: If you want to optimize it check user agents on the server and send different js

Frid: So modernizr will check to see what i need and load the missing functionality anyway

Khanna: I haven’t used modernizer recently, so I dunno

Worman: Do you know any tutorial which will describe “modern web” development?

Linnane: And I mean basics. Tools, HTML, js libs

Sowders: By the time it’s written it’s out of date.

Sowders: Just go learn some fundamentals. ignore libs/frameworks.

Halvorsen: Kindley, are you comfortable with js?

Munz: Schaetzle: Well, I lack good practices, because in most projects js was a second cl*** citizen, however I like the language and know my ways around it.

Prevette: Kindley i can recommend ‘The Complete Web Developer Course — on udemy’, ‘Javascript & jQuery — by Duckett’, and ‘WordPress Theme Development with Bootstrap — on codecollege.ca’

Loxtercamp: I’ve also read Stoyan Stepanov’s “Javascript patterns” and am trying to use that in daily work.

Mallick: Siba: Thanks, googling.

Macri: The js patterns book isn’t something you need most of the time

Colantonio: It’s more of something you’d use if you were writing libraries or other abstract code

Gorn: Yeah, but it was a good insight into how js works.

Cleckler: So for application development: webpack or gulp+browserify are good tools; for the client you can use react, ember, or angular 2 once it stabilizes

Conkrite: I worked with angular a little bit and it’s a mess

Muzzey: Angular 1 is terrible

Wojtanowski: Angular 2 is “we *****ed up hard, and we’re trying to fix it”

Waggoner: I also worked with knockout a bit and I liked it. Simple and powerfull tool

Fraleigh: I’ve checked out browserify – very nice thing

Brooks: Knockout is good for small things; I never figured out how to scale it, though

Manlangit: That’s what my buddy told me – give it up if you don’t know the scale, because at some point it will become a mess

Selvey: React is great; it’s what I use currently, but it’s only good for when you need very custom apps

Kment: Yes Kindley I second looking at how people are using Webpack

Kment: I’m behind the times with it too

Fellon: However, thing I’m gonna write now is rather small and simple

Sorman: Ember or angular 2 are for apps where development speed is more important than control

Gerbatz: So I want to keep my js stack as simple as possible

Kment: What are your data sources Wizard

Demeglio: This is gonna be an electron app, so disk files

Otega: Kindley, I’d recommend using react; not so much because it’s the best tool for small/simple projects, but because you’ll learn a lot from it

Creselious: I’ve heard bad things about react

Crowley: Ah, no, it was about backbone

Romack: And actually I’ve heard good things about react

Flitt: Sorry, it’s so much of that crap out there that I’m kinda lost

Jardell: Can I check crypto using caniuse?

Kment: You went from kicking me in the shin to kicking me in the nuts

Brounson: Backbone is odd. I can’t imagine people saying good or bad things about it because it’s so simple

Kment: What’s wrong with backbone?

Joice: I would like to know which browser versions support window.crypto