Indeed, well said. Seems just as plausible, if not more so, that the anxiety is a symptom of poor familial aptitude for mathematics than the cause itself. But that's a thoughtcrime these days, so best not mention it ...
But until we know something provable about genetics and mathematical aptitude this line of thought is just hand-waving. You still don't know any better than anybody else why somebody is having a hard time with math.
That's why I said it seems "just as plausible" as the alternative. Its the article that's making the more definitive statements, not me. Besides, I think there's a reasonable amount of science that makes the argument for genetics over nurture quite compelling, but 20 years of malpractice and misdirection in the social sciences obfuscated that.
A lot of the latest thinking in (non-JS) CSS suggests that violating DRY is an excellent idea. Copy and pasting CSS rules is cheap, but maintaining and adapting a large complex CSS project that's blowing up in a team's face can be very expensive.
I imagine a common architecture for universal apps will be to just use some sort of thin Node.js app to perform the actual app rendering, and have it communicate with a separate API app written in whatever language is most appropriate. Static files could either be served by the Node.js app, or even a different source.
You have one 'Universal Application', and then you have two small entry points:
- server.js is a small (express) server to send a HTTP response to the client (server bootstrapping)
- client.js renders a page and the mounts it onto a DOM node.
To get around the issues of database access, it makes it a lot easier to put all of that into an API that can be accessed by the server and the client.
For a non-signed in session I can see some advantage in improving the swiftness of implementing supporting changes on the server for the client developers. For signed in sessions, you can't get around the database and an API update for it when the client needs some new feature or access so in the signed in case; I think the benefits of this nodejs part would be diminished.
Why spend energy producing and transporting heavy water and plastic bottles with this pre-mixed Soylent? Everyone already has plentiful water and receptacles at home. Seems like a retrograde step, unless I'm missing something?
True. I'm on my first batch of 1.5 right now. The instructions are pretty clear about it needing to be cold. Room-temperature, the Soylent mix is pretty gnarly (think chalk), but once properly chilled it pretty much tastes like nothing.
What an awful title to the first insight "women are winning". Its that sort of clickbaity, reductionist and divisive language that's turning gender relations in tech into such a warzone. Where's the data for all-women teams vs. all-men teams? Only then could you draw such a conclusion, if you even wanted to in the first place. Total garbage, and damaging to gender relations to boot. A more constructive (and appropriate, given the data) conclusion would be "we work better as a mixed team".
I agree that it's essential and nourishing to understand the basics, but I feel that familiarity with the basics and expertise with these tools represents a minimum baseline standard for professional frontend development, especially when working in teams on medium/large web apps. Granted it's not easy to get up to speed with all of it, but many fields in programming and CS are not easy either. As browsers become increasingly standardised and stable and web languages grow up (ES6+) we'll be able to do increasingly sophisticated things, and frontend web development will attract more serious programmers ... we're seeing that now with the interest in React and functional JS, there's a lot of cross pollination between JS and the Clojure/Haskell communities which until now have remained in their ivory towers. Modern/professional frontend development won't and indeed shouldn't be something you can still just get done with Notepad and a few <script> tags.
> When I see a complex build tool replaced with three lines of bash, that makes me happy
Hmm. There is truth to some of this, but like everything moderation is key. Use your experience to pick new tech that meaningfully improves UX, DX, maintainability or some other metric without creating problems. It does exist. Likewise, don't be the boringest of boring developers because you'll miss out on key innovations and your product will suffer. Unless, that is, you want to make a name for yourself as Supreme Leader of BFEDs for career advancement purposes, in which case host a clickbaity blog about it and argue from a highly polarized position ... oh, wait
Slack, Spotify, Atom, React Native ... I think desktop/native apps implemented using web tech have come on leaps and bounds recently. They started off clunky, but are now starting to feel like native software imo.