To me this is solving Tailwind's biggest issue: consistency & context.
Comparing it to Bootstrap or Foundation adding the class `alert alert-danger` to a div tells my coworkers that it's an "alert" & it will look like an alert everywhere. If I want to change how alerts look, I change the CSS
With Tailwind you'd have `bg-red-100 border border-red-400 text-red-700 px-4 py-3 rounded relative`. Then I'd have to change my HTML everywhere to update the appearance of alerts & its not always obvious that I'm looking at an "alert" in code. I'd end up with different looking alerts, cards, buttons, etc all over my app
I agree; for smaller components like labels and buttons, having some compound rules would help. They tend to be well-defined. I believe you can create composite styles in Tailwind.
Another reason Bootstrap > Tailwind is consistency & context. Adding the class `alert alert-danger` to a div tells my coworkers that it's an "alert" & it will look like an alert everywhere. If I want to change how alerts look, I change the CSS
With Tailwind you'd have `bg-red-100 border border-red-400 text-red-700 px-4 py-3 rounded relative`. Then I'd have to change my HTML everywhere to update the appearance of alerts & its not always obvious that I'm looking at an alert in code.
Nope. Once you see same (sub)set of classes repeated, you would instead define .alert and .alert-danger using Tailwind's @apply directive, and you now have a single place to change how your `alert alert-danger` looks :)
Was the hope that the code would be temporary, or that the external conditions the code was dealing with would be temporary? Remember this is flight control software. There might be transient conditions that the system can handle fine, but could lead to failure if they persist.
That call to STOPRATE was there to zero out attitude rate commands at the moment the astronaut switches into the semimanual final descent program P66. It was removed in the final few revisions before the first, unflown release of the Apollo 14 software (Luminary 163 [1]) because it was preventing attitude control of the spacecraft when Rate-Of-Descent commands were skipped [2]. Skipping ROD commands wasn't normal, but was something that was added as part of the effort to make the computer more cleanly handle large unexpected additional load, like happened in Apollo 11.
People frequently seem to think this is about the line number it's on (666), but that doesn't have anything to do with it. That line number is a totally modern construction; the original source code was on punch cards. That particular comment was punched onto card number 0562 in the LUNAR LANDING GUIDANCE EQUATIONS log section. The original developers only referred to code by punch card number, and page number in the listing. So it really is just a coincidence, and the "NUMERO MYSTERIOSO" is referring to whatever is in GAINBRAK,1.
No, it's not. The 1 here is using interpretive index register X1 to index onto GAINBRAK. The star on the DMP means that multiplication is indexed. GAINBRAK is one of the pad-loaded descent targeting parameters; the index selects the appropriate number based on the phase of the descent.
CDN helps with the page load/latency variable of Google' PageRank but won't equal AMP.
To get AMP-like speed you'd need: CDN, no render-blocking javascript, minimized image files, "lazy-loaded" assets & inlined CSS for "Above the Fold" content. On the server side you want to cache content with something like Varnish & send it over an "Edge" network like Akamai or Fastly. Ideally everything is served over HTTP2 or SPDY.
That's sort of my point: publishers seem mad at the temerity that they can't festoon their web pages with tons of stuff and then not also be put in a category that is meant to be fast.
There are other parts of AMP I am less okay with, but tbh I trust the publishers even less than I trust Google with respect to sketchy tracking bugs and data collection and useless javascript ux.
>There are a few details that may save Picnic’s pizzas from tasting as if a robot made them. For starters, the dough preparation, sauce making and baking — the real art of pizza — is left in the capable, five-fingered hands of people.
The dough making & stretching is still done by humans.
It looks like this robot distributes sauce, cheese & toppings (it only shows one topping, though). Then cooks it.
Oddly enough, it doesn't even do the cooking. The bit you cited says the humans do the baking. I'd have thought that'd have been an easy bit to integrate - places like Pizza Hut already bake on readily automatable conveyors.
Why should I pay for a Tailwind hero when, if I apply myself, I can get a Bootstrap hero for free?
https://tailwindui.com/components/marketing/sections/heroes https://getbootstrap.com/docs/4.4/components/jumbotron/