Mcneal: It’s fast and easy, but isn’t scaleable/maintainable.
Iverson: But the “fast and easy” part isn’t that fast and easy either. There’s still a learning curve to follow the tangled architecture
Morral: And still there’s that code repetition etc.
Ferioli: Natrixnatrix89: I suppose, I only new javascript at the time, so in that sense it was easier than learning ruby, clojure, or whatever
Carson: Natrixnatrix89: I’d do MERN, mongo express react and node
Benard: Yes, that would be interesting. But still I’d like to see more sanity in how the expressjs is handled
Rusko: Ok. I’m relieved I’m not alone. Let’s get back to work
Carson: Natrixnatrix89: try hapi or strongloop if you want more architectural guidance above express
Carson: Express is more like sinatra or flask
Carson: Hapi/strongloop are more like rails or django
Heidema: Carson: don’t worry I enjoyed your ****ogy
Praylow: I definitely enjoyed it too ! :
Praylow: I mean if there is more you would want to add I am definitely ears!
Carson: That’s all folks 😸
Cremin: How important is bundling for performance? I’m getting obsessed with the perfect build system using gulp – the next part I have to do is bundling and I want to just start working on the actual freaking app at this point. Is downloading one huge js file *always* better than say 9 or 10 individual ones?
Blonigan: Wbdl: There is no such thing as “always better”.
Mula: I see gulp-bundle-***ets – is that pretty standard for gulp users?
Carson: Wdbl: just make the app. I too sometimes get stuck on over optimizing
Tebbe: Wdbl: bundling isn’t about performance, it’s for organization in development.
Coiner: Wdbl: Do your app first, then think about optimization. Otherwise you will never finish.
Shorrock: Is bundling usually easy for everyone? JS devs. I’m kind of an old but new JS dev all this new stuff keeps making me feel like a newb
Juback: Wbdl: At the end do performance tests. It’s easier to otpimize when you have the final product. If you start doing it upfront you are making ***umptions about the final product.
Solak: I just wonder if I’m making a mountain out of a mole-hill
Hissem: Ok i must still be doing something wrong
Boudreaux: Https://jsfiddle.net/3tnk4ong/3/
Stelluti: Holodoc, laserco – thanks for your advice
Hissom: I will get it out of my head that I *neeeeeed* bundling to be in place before getting to work
Rowland: Wdbl, I’d prefer 20 javascript files. It’s easier to debug, and they get cached
Schutt: Returns this as print_r $_POST
Darnold: Array contactlog = undefined
Carson: Wdbl: you just uglify then pipe to concat. done.
Stutzman: Ok great, I actually prefer NOT bundling too because I like things to be simple
Wess: Wdbl, Don’t worry about bundling unless you have huge images and ***ets to send over. 20 javascript files is nothing. Let the browser handle the details there.
Okken: Sweet guys. Thanks so much for your support
Carson: To get debugging you generate a sourcemap as well wdbl https://github.com/mikach/gulp-concat-sourcemap
Leithiser: I work alone all the time and I’m sick of not having anyone to lean on for stuff like this
Wilebski: What does {,*/} means in grunt file ?
Sempertegui: The ideal performance scenario is that the user supplies the libraries. This is what Stallman proposes.
Kipp: Same idea as cachine, but more like homebrew
Antronica: Hello, I have a doubt about scopes and binding
Knust: I have have created a “scope object” like this: var scope = { ‘context’ : context }, then used that object to bind a function: var func = otherfunc.bindscope;
Hersom: In otherfunc, if I call ‘context’ it’s not found, but if I call ‘this.context’, it works nice