I also recently came to learn that the mainframe run jobs in batches, so I'm not sure how does that affect performance, if it even does.
647 karma · joined October 30, 2016
I also recently came to learn that the mainframe run jobs in batches, so I'm not sure how does that affect performance, if it even does.
Maybe these are all short term necessities for Mozilla, and when things get back to normal they'll pick up where they left off. One can at least hope.
<div style="padding: 20px;" />
and <div class="p-2"/>
it's like variables for styling. Instead of throwing some random numbers developers can bump the numbers up p-3, p-4 or text-red-200, text-red-300. It helps to keep things consistent.For a simple website semantic HTML or SMACSS can work, but for any semi-large scale websites with many variations of components it'll quickly descend into specificity hell. Using atomic classes keeps the specificity flat, and it avoids an entire category of errors that haunts many large projects just by making the styles sort of self-contained (you still need the stylesheet).
Of course there are other approaches to this problem such as "namespacing" your CSS using BEM and dynamically generating class names using CSS-in-JS, but using atomic classes is a very maintainable way to style HTML, if a little hard to read.
you can use it in all major browsers except Safari
I used to feel the same about iOS but if you search screenshots of it now at least to me it really didn't stand the test of time.
I just dislike that it became so ubiquitous now and it's a train wreck on desktop
However, if you're concerned about users on older browsers, you can use Babel to "transpile" your code to equivalent code that older browsers can understand, often at the expense of size.
npm and yarn are simply 2 competing implementation for package management. Start with npm and you'll know it when you want yarn.
Webpack and other module bundlers are just tools to automate things like transpiling, code-transformation, bundle-splitting, minification which are not all that essential actually.
The point is all of these are extras. Think of them as enhancements/optimizations. If you have a solid understanding of JS you can write JS in a way that doesn't require any of this. I blame the tutorials out there that say you need this and that without many justifications that make it seem more complicated than it is.
1. https://developer.mozilla.org/en-US/docs/Web/JavaScript/A_re...
I know some people run Emacs in daemon mode, but it's not always convenient to do that
This and when I ssh into any machine, I know there will be a vi at the very least
It's not even that FF's dev tools are bad -- it's good, but sadly Chrome is still better in some marginal yet significant ways.
Most notably Chrome is still better for CSS work when I'm trying out colors, tweaking shadows and animation timings, where Chrome has some nifty widgets to preview changes quickly and easily.
wow really
The way I look at it this is just the acts of a few people and has nothing to do with overall movement of the entire company
One can't help but think, maybe web stack makes it the easiest to build good looking apps that are responsive
The difference is I can make Emacs do things just the way I want it vs can it do what I need it to do? And I find that for most part I don't miss it that much (even I'm shocked) but I still open Emacs for Magit from time to time, because there's just nothing else like it, and boy is Magit slow when I have to merge big changes (probably exacerbated by Emacs Mac port's slow vfork).