No, there was a downturn in both the defense and the aviation industry that hit Boeing like a double whammy. It laid off tens of thousands before the acquisition and tens of thousands afterwards, for a total of over 100k laid off in the 1990s (Boeing has 170k employees today). They used this opportunity to disproportionately target older and more expensive employees which led to many of their best engineers getting canned.
Everyone likes to point to the McDonnell Douglas acquisition as Boeing’s downfall but the truth is that Boeing executives had already gutted the company.
In fairness, everyone probably likes to point to that because it was one of the primary conclusions reached by investigative journalist Peter Robison in the book "Flying Blind."
We only have the perspective as observers outside of China, so I would caution how we interpret this article.
However, it may be possible that this COULD be the Corolla for the Chinese market. They do have a lot of EV manufacturers (300+ I believe?).
State-side (or even worldwide)? It takes some more convincing. And the article doesn't explicitly say it would be the next Corolla killer for the US market..
this is great! The one thing i think to optimize it is to predict how late to start the engine to minimize its usage. The last I got was 730 times used, at 53seconds.
I'm a big fan of Harry's, and I've been hoping to see him publish more details on ITCSS. I built my current website around the methodology based on a talk he gave years ago. When last I checked though, there still weren't any readily-available details or documentation on the topic.
With the prevalence of component frameworks though, and certain new technologies like CSS Layers and :where(), I feel ITCSS may not be as essential as it used to be. Specificity is becoming less of a problem to manage for large-scale websites. I think it still has its place, but is maybe not the universal solution I once saw it as.
Between ITCSS, SMACSS, BEM, and all the other CSS naming and structural conventions, it's been pretty nice to do CSS-in-JS and not really worry about the cascade.
I did a migration/update of a site using this idea (before styled-components became the norm), and it was just insane how much CSS was saved. The new design was AT MOST half the size of the original.
The domain for CSS Guidelines is a real shame. It wins points for vanity but it's on Spain's tld. ccTlds tend to be localised such that you don't see them unless you're in the country.
> ccTlds tend to be localised such that you don't see them unless you're in the country.
In Google results you mean, or by the site operators themselves?
I agree if you mean in Google results. I don’t so much agree if you mean by the site operators. At least not for European cctlds. I find it far more common that sites from the US are inaccessible to Europe, than to see a site with a European cctld inaccessible to people in other countries.
Or did you mean sites that redirect to an international version of the same content? Sometimes that happens but usually only with sites belonging to big multi-national companies in my experience. And even then they often ask whether you’d like to stay on the version you went to or go to the version for another region or country.
I mean that Google won't show the results and you also won't actually remember the domain, because it's clever. And in this case, it's a spanish domain so is expected to cater to Spain.
It's not unique, the .cat TLD for Catalonia requires that you serve your content in Catalan, so as to prevent people abusing the obvious appeal of a TLD that in English translates to a cute pet.
.io, .ly and .sh have been victims of this technical imperialism.
They have benefitted from a large amount of revenue and if they wanted, they could have easily prevented foreign registrations by requiring a mailing address in the country or that the registered site has some tie to the region. Like your example of .cat.
Probably everything, except for .tv (Tuvalu) which do have a good agreement. I'm skipping on .io since it's a rabbithole, but .ly and .sh aren't runned by or on behalf of their governments, they instead are being runned by different companies. The most notorious of these is Niue's (.nu), which their government try their best to recover from a Nordic country to no avail (https://en.wikipedia.org/wiki/.nu) .
To me, that sounds a lot like a 2 year old type of behavior. Does anybody really even care what a TLD is or is "meant" to be used as? Honestly, if it's not a .com, most people are going to screw up and add .com out of sheer habit.
It's the friggin' internet. If it's out there, someone will do something they feel like doing with it even if that's not the originally intended concept.
You can register a .no domain through a broker similar to how whois privacy at most registrars works: the broker is the registrant but then affords you full control of the domain.
That sounds like a bad idea. If your site is successful the broker could jack up the price to let you keep control. Better to stick to registering domains directly through a normal registrar. And if you are not in a position to create a Norwegian enkeltpersonsforetak or aksjeselskap, then why bother with a .no domain?
it's funny this article came up. I just pulled wine from 14 days ago that was in my Eto (mentioned in the article) and it tasted just as great as when I poured it on day 1.
I've used it since the Kickstarter in 2018. For a single glass drinker like myself, this (admittedly expensive) thing really helped me stretch my money over the long haul, because now I don't have to waste my wines.
edit: I suppose the Kickstarter price was 50% of what it is now. oof glad I got it
