Beresnyak: Var a = “cats”, b = “dogs”; a && b == !!a !b;
Wakley: Reddekopp: boolean false
Doughtie: Tcsc you must be held behind gl***-lasered closure in Vatican museum as the man who successfully solved this problem in such a pattern lol
Wakley: Bolerjack: boolean false
Cuervo: RonRichie: you should brush up on your boolean algebra
Wakley: Bolerjack: boolean true
Trafford: Booleana && b == !!a !b
Wakley: Tcsc: ReferenceError: a is not defined
Wakley: Bolerjack: string ‘dogs’
Chang: Var a = “cats”, b = “dogs”; Booleana && b == !!a !b;
Pac: Tcsc yeah you sure right. flipping results with this bang operator at times gets confusing :-/
Bever: Nobody in Google knows how to catch the typeError, LOL
Wakley: Bolerjack: ReferenceError: a is not defined
Wakley: Bolerjack: boolean true
Scelsi: Var a = “cats”, b = “dogs”; Booleana b == !!a && !b;
Ambeau: I wonder if Im doing it right that I’ve been learning JS for 4 months already and haven’t touched a single framework or library? as I believe I better work on strong fundamentals and nail down the vanilla JS and then move on with frameworks and stuff, is this a right way of doing this though?
Palomaki: At least, imo. if you want to be a strong programmer you need strong fundamentals.
Brazeau: I get told that I needed to move on to libraries long time ago already, some tell me I should have started with jQuery and stuff, but this is what I believed initially and tend to stick with it till now
Carhart: Tcsc that’s definitely what I wanna become:
Maxin: Well, its a question of what you prioritize. you need to pick this stuff up at some point, and picking it up early is probably best, but you could also learn it later.
Eudy: I really wanna nail down FP part of JS before moving on with OOP, I want to throughly understand these functional methods on collections, this is what Im mainly concerned with
Dzama: OO is better than FP though
Pensky: Single responibility priciple vs functions
Farfalla: Open/closed principle vs . functions
Deloach: Dependency inversion principle vs . functions
Umscheid: Interface segregation principle vs functions
Bolerjack: MyMegaFactoryCl***OfAllThings vs functions
Homchick: Factory pattern vs functions
Sakon: Not to say that i’m a huge fp guy, i’m not sure most of those are actually all that useful usually.
Sundt: Most of those make things inflexible, or only flexible in ways the author planned.
Rotan: Disagree, I prefer working with the immutability and testability of FP when I can
Winfrey: But it depends on the problem you want to solve
Grasha: The code i write is definitely closer to OOP than FP though, especially in JS. I almost never use FP in JS
Bonelli: I use as much FP as I can in my js
Romaniak: I think fp is a useful tool, moreso than oop
Mernin: But it’s efficient in js
Forrest: Visitor pattern! because first cl*** functions would make it too easy!
Currier: Tcsc: well, when using native data structures
Snare: Even when not, it causes a lot of gc pressure
Dilorenzo: If you have a frame budget that’s a recipe for disaster a lot of common OOP techniques are too though
Holzheimer: I’m using jquery-ui’s dialog, but no window pops-up — only a close button and the string I p***ed it.
Nourse: What if you have an appetite for destruction
Konig: Mostly it’s just really hard to optimise JS, so functional idioms in JS suffer from that.
Loguidice: Hopefully, with ES6 and beyond removing some awful features from the language like arguments, with, and other reflective things, future code will be able to be better optimised.