u/stalde

also! apparently they don’t bark which is a bonus

yeah, i did research based on the size of my apartment and how would a certain dog get along in a smaller apartment. basenji seemed to fit the bill and on the plus side - they also seem to be okay with being alone at home during workdays. spoke to a friend of mine who has two basenjis and they both were caged for the first few months when left home alone. it sounds cruel, but this was for their own good and to make sure they wouldn’t hurt themselves since basenjis get quite bored quickly :) although, i’m still scared to get a basenji due to the unknowns about actually growing it

holy shit. literally have the same situation as you and considering a basenji as well. what are the odds, huh

That's why you don't learn frameworks, but rather problem solving in general. Being limited to a single framework just because you can ONLY use that, is foolish. Being able to work with any framework on the go, because you're proficient at the underlying concepts and language of said frameworks, makes you already hireable and wise.

way too overengineered

Exactly. CSS modules also give you namespacing after the component which basically provides you with BEM by default. E.g your component is Card, then all the classes will be namespaced with Card__class. Obviously this can be customized via your Webpack conf.

It's 2017. CSS modules are a thing.

https://jsfiddle.net/8L035shj/ - Play around with justify-content a bit :). You're welcome.

Something like this https://jsfiddle.net/vvcux17s/ ?

https://github.com/kyle8998/Optbnb/blob/master/js/graphs.js#L169

wat

heroku-postbuild script in your package.json

formspree.io

wat

No - the fact that you can only justify using Angular or React is if you are the size of Google or Facebook is just fallacious and doesn’t work like that.

my bad. was sleepy and got confused for a sec.

small tip: you don't need the removeClass in jQuery when using toggleClass afaik. I tried it without and it worked.

use proper input elements next time with a :focus pseudo selector instead of redundant jquery magic for toggle'ing a active class for your div "input"

lolwat

what does that have to do with anything. my point just was that in 9/10 situations jQuery isn't justified and you can just do everything with vanilla JS instead.

ES6 is the language. Obviously you use JavaScript without jQuery.

yeah. okay. "without including". happy?

In some cases, an easier API, or better support for esoteric browsers.

my point was made in the world where your browser support are the latest browsers compatible with ES6 and nothing else.

Yes, in both cases, you are using JavaScript for DOM manipulation.

yes. but the difference is are you using the vanilla version or including a library that actually does the same thing for you and then some, with syntactic sugar. why not do the whole manipulation in the vanilla language yourself instead.

what. of course you can use ES6 without jQuery, but then what is the point of including jQuery in your project if all your browser requirements are met with ES& already? my point was that using ES6 for DOM manipulation is easy enough on its own, that jQuery isn't necessary anymore. jQuery was great for adding syntactic sugar onto things that were stupid and mundane to type out.

and how does opening new developers up to the ACTUAL syntax of the language of the library that they're using harm them? I'd say it helps them instead, so they can understand the underlying vanilla language instead.

fair enough. just a extreme example. tho, most things are easier in ES6 syntax than jQuery imo. see -> https://css-tricks.com/now-ever-might-not-need-jquery/

or they could just use native vanilla JS ES6 features for the same things which are arguably easier

Nah. A CMS is usually designed for non-technical people, so they can easily edit content and styles pretty much effortlessly. Webpack is definitely solely for developers and mostly large projects, where many languages are used.

Think about being a developer and wanting to use a CSS pre-processor and a JS framework. You would somehow need to compile them to pure CSS/JS. It would be absurd to combine all of your multiple .sass and .js files manually to get minified, compressed HTML/CSS/JS outputs. That's where Webpack comes in. Obviously, you can use task runners like Gulp for doing the same thing, but Webpack allows you to customize your workflow very specifically and can do a lot more than a task runner.

Many sites use something called a module builder - the most popular being Webpack, which allows you to separate your production build from development. This means that you can separate your code up into multiple modules and files and once Webpack is run, it spits out static, compiled and bundled HTML/CSS/JS files from SASS, React, jQuery or any other compiled languages that your project might be using. Usually the production version's code is minified & uglified, which is what you're seeing here.

InvisionApp