This is great! I enjoyed flexboxfroggy.com, but this seems to go into a bit more depth in terms of the number of flexbox properties being shown off. It takes a bit to work out what the actual css being used is, but it's otherwise a great way to play and learn what flexbox can do.
We all have monkeys on our backs. We all search for the best tools to use to make our lives easier and our products better and more reliable. When something new or improved comes out, we evaluate it, we weigh its use against everything from performance to code quality to backwards compatibility to having everyone learn yet another tool/library. If the benefits outweigh the drawbacks, then we make the switch. If not, then we leave our tool chain as it is.
Are there people who blindly switch to the Next Big Thing (tm) every 3 months? Yes. But I've found that in general they are few and far between. Perhaps you happen to work with one or more, but know that the entire web-dev community discourages that behavior.
The web-dev community might discourage that, but in my experience (someone who does backend/analytics and some devops, and who occasionally needs to modify the front-end projects that communicate with said backend) every time I setup one of the projects for local development it's a dependency nightmare and a good couple hours of research to figure out how all these pieces work together.
We've done the jQuery -> Angular -> React mambo. The RoR -> Node.js mambo. The Grunt -> Gulp -> Webpack mambo. The underscore -> lowdash mambo... I could go on. That's without even counting the CSS related fads.
Another thing I've noticed is that we've gone from projects trying to optimize for minimal JS and are light on browser resources, to installing multiple megabytes of Bower/Webpack/NPM dependencies and pages that perform (pardon my French) like crap. Famously, one of our backend devs wrote a Chrome extension that would disable the animated backgrounds in a bunch of stuff because they sucked our laptops' batteries.
So I feel the pain of poster who said it's become almost impossible to support JS projects unless that's your daily job. The tool churn is too big and don't get me started on all the new terms ("isomorphic websites", "polyfills", "shims", etc.) that seem to pop up every couple months.
I understand it's growing pains of a maturing ecosystem, it's just that the churn speed is insane.
Fair point! Although I'm just as tired of the rat race there, too. Of all the things listed, we're only using Git. I've looked at most, but I'm not bothering implementing it unless it's a huge benefit over the status quo. Chances are, better solutions will be around before we've finished migrating to the last Next Big Thing. I wish development finally got that memo.
Several years before that purchase, Stephen Elop (an MS executive) became CEO of Nokia. Within 6 months of his hire, Nokia signed an agreement with MS to sell Windows Phone devices; the classic Symbian OS and the Linux-based Meego - both of which had shipping hardware - were canceled in favor of exclusive focus on Windows Phone. Within the next few years, Nokia laid off over 20k people, their stock dropped by about 85%, and they even sold and then leased back their HQ in Finland. They were a lot less successful by that point, and a lot less expensive to purchase. Which Microsoft did.
There was some amount of controversy associated with the above.
Although technically MeeGo had no shipping hardware at the time. The N900 ran Maemo, the first (and sadly only) MeeGo hardware to ship to the public was the N9 which didn't ship until months after the "burning platform" announcement
Exactly. This panders to their anti-immigration base. If it were a serious proposition, then he would have at least tied the salary to some percentage of the median salary for the job being applied for.
That said, it's still weird because it'll likely piss off the large donors. I understand that he's trying to take some of Trump's base using Trump's tactics, but the only reason that Trump gets away with it is because he's financing his own campaign and couldn't care less about fundraising.
> Do you think apple never supported SD cards because they wanted more people to put stuff in icloud?
Uhh... of course? Both companies charge extra for more space — Apple past 5GB and Google past 15GB. They make money by forcing you to upgrade your online storage.
Is that configurable? That is to say, can I change what's printed to the prompt to add more info like # of files added/removed/modified? I looked into it a little bit it looked hard-coded.
yeah it's pretty configurable, the syntax to do so is rather ugly though. I'm using it like this: https://gist.github.com/lorenzhs/c8b442ce831f0211f3d8 which shows me whether I have staged and unstaged changes, the current branch and commit, rebase/... status, etc.
I don't remember from where I got this config, it's a mix of things I found online.
Push Git is great! I've been looking for a comparable solution for *nix for a while. Zsh's git completion/prompt just showing the branch and dirty state isn't enough.
