1,086 karma · joined May 25, 2012
This would be a good place to mention that even Tesla has long partnered with Panasonic to help with their supply of batteries.
[1] https://www.mitsuba.co.jp/en/
Re: 2 and 3. I'm sure you're correct. But we're talking about salesmanship here. Logic and facts don't always have a buyer. They would need to find ways to sell those used cars to potentially skeptical markets abroad, in huge volume, where they've already got a great racket with ICE cars.
It's true there's a huge industry for white label car parts manufacturing in Japan. These companies are extremely agile. They will adapt. Taking contracts for novel new parts is their daily DNA. They already work extensively with foreign car companies, so they're not anchored to the foibles of Toyota and Nissan.
Furthermore, electric cars still need complex parts! Sensors of all types, electric windows and door locks, key fobs, air conditioners, steering wheels, windshield wiper motors, etc. The list is so very long.
I have one wild guess as counterpoint. Today's Japan would never mandate a shift to all-electric vehicles. Why? It would destroy their domestic car sales industry. In Japan, many people only keep their cars for a few years, then sell them back. Used Japanese domestic cars are worth a lot of money. These cars are exported to other countries around the world, where they're resold. I imagine Japan could no longer resell their domestic cars abroad, at such huge volume, if all their cars were electric. Many countries do not have the conditions or infrastructure to support large-scale deployment of EVs. Batteries would probably need to be replaced, lowering the profit on the resale. And so on.
Consider a site that mostly renders Markdown or XML documents. Tailwind is probably the wrong choice. You have less control of the HTML content in this case, because it's generated. If you want to use Tailwind here, you'd need to make liberal use of Tailwind's @apply directive for basic declarations, which IMO is not the best expression of Tailwind usage. On the other hand, you have a lot of control over the CSS. It makes more sense to write the CSS directly.
Now consider an organization with many separate web properties, which all require consistent branding. The organization has a UI guy who creates universal stylesheets and components for use across sites. Here you have less control over the CSS, and more over the HTML. Tailwind makes more sense. You can add all the utility classes to HTML that you want, with few overrides or other enterprise pull-ups.
This latter scenario also highlights one of Tailwind's strengths. Tailwind limits your options. If you need to keep a brand consistent across a large number of properties, Tailwind keeps you in the guardrails of the style guide. I can't be the only one who's worked at an organization where there's supposed to be only one shade of blue to represent the brand, but you wind up finding 160 different shades of blue throughout the CSS.
Anyway, Tailwind has its time and place. I love it when it fits.
It worked. They have one of the best public education systems in the world.
The other day, I placed an online order for curbside pickup (with a national brick-and-mortar chain). When the time came, I drove up to their curb. But I couldn't access their "I'm at the curb, bring out my stuff" page. It just kept loading and loading. I had to go into the store to get my order.
When I got back to my PC, I discovered a massive webpack bundle on that page, along with an absurd level of tracking software. The page had transferred 50MB before I could even use it.
They knew their curbside page would be used exclusively by people on their phones, in their cars. They knew some of those people would pull up to stores with poor cell reception. That page should've been as light as possible. The page was ultimately just a simple form, so it should've been possible.
The NAACP got involved. There was outrage and shame to spare. The principal wrapped herself in righteous indignation, despite herself being in the position of power.
Months later, she was diagnosed with Alzheimer’s Disease. Oops.
I’m sure this person definitely experienced racism and sexism in her life and career. There were undoubtedly many incidents when she was slighted by white people. It’s America, after all. But in this particular case, she was not the victim. The teachers were the victims. The students were the victims. Yet she still acted the victim. Hence, “victimhood mentality”. “Contentless” can cut both ways.
The insidious thing about these types of incidents is how it discredits the rest of the racial justice movement. We need to hold our outrage to a higher standard.
The best approach requires some level of improvisation; we learn each child’s tendencies, accept them for who they are, and try to mold them into the best versions of themselves. I don’t see a way to prepare for this.
I've faced similarly abusive workplace cliques on multiple occasions. They're very easy to bust if you're willing to put aside your personal shame. But I never had a visa hanging over my head during these confrontations.
I was diagnosed with Asperger's later in life. I received this diagnosis after I already had a successful career, happy marriage, and house full of kids. Not much of a hindrance, right?
On the other hand, my brother suffers a much more severe form of autism. He does hold a profession job in finance. But he otherwise requires a full-time caretaker, tons of medication and understanding, etc. No friends. He's not self-sufficient.
It's a huge spectrum.
EDIT: Here are a few more things to like about Sacramento.
There seems to be a large population of highly educated ex-military types concentrated here. It’s been an unexpected source of high quality hires. I never saw these people in the Bay.
I’m in an international marriage. We were worried we wouldn’t be able to find our people upon moving here. That hasn’t been a problem at all. Fellow expats are everywhere. It’s a fairly diverse area.
One problem. I’m increasingly coming across devs who’ve never used Promises directly, only async/await. They’re introducing all kinds of problems into code because they don’t have that foundational understanding of Promises. I think it’s essential to know how Promises work, even if we generally recommend async/await.
Also, Promise interface can do things that async/await cannot, such as Promise.all, and other unusual async execution scenarios. It’s important to have those tools in your belt.
There's just no strong motivation to try to root my TV. I don't like my smart TV but I don't need to, because the smart parts can be "replaced" by any number of external devices. My point is that I suspect many would-be TV hackers are in the same happy situation.
If I get a smart toaster, such as the Revolution Cooking Smart Toaster, then I'll get a bunch of nifty features: touchscreen controls, notifications on my phone when the slice is toasted, etc. It'll be nice and a lot of fun for a while. Initial experience is great. A year passes. The touchscreen fades. The wi-fi chip doesn't work with my new router. The notifications app doesn't work with my phone's OS upgrades. I'm jealous of the cool new model at my friend's house. I'll be shopping again in the near future.
Instead, I could get a complicated dumb toaster, such as the Panasonic FlashXpress. It's got a ton of buttons that all do different things. Every morning for the next three weeks is going to be an experiment; I'll need to learn the ins-and-outs. Eventually, I can play it like a musical instrument. From there, I'll be able to use it until it dies, probably ten-plus years. The toaster will not be something I think about, really, at all. It's just a tool that sits there and does the job well.
So here's the question. Do you prefer the immediate conveniences of using the latest and greatest, next year be damned? Or do you prefer the long-term convenience of not ever having to think about it?
For example, we just saw an article rise to the top of HN in the last couple days about the pathetic state of Apple's developer documentation. Their focus seems to be less providing integrations into their hardware, and more providing integrations into their services. Meanwhile, developers increasingly distrust Apple because of bad policies and press around App Store review. It's a mess.
I agree that Apple could and should help app developers use this cool new hardware. I'm sure there are good people at Apple who're trying. But the company as a whole seems to be chasing other squirrels.
I try to remind myself that it's more about the other person's insecurities than my own pain, and I try to be gracious. Sometimes I still snap at people who don't take the hint.
You’re right not to fear COVID for yourself; statistics support that view. But common, non-medical masks are not for personal safety. They’re for preventing community spread.
https://deadline.com/2019/03/netflix-tv-series-cancellations...
Just to take my own example, I’m unable to use the Kinesis Advantage because the bones in my right wrist are curved following an old injury. I’m physically incompatible with that keyboard.
But split keyboards work great for me! I can rotate one side to accommodate my arm’s curve. Kinesis Freestyle is great for this. Ergodox also works.
By your logic, I guess this makes me a fanboy?
My point is that different people have different ergonomic needs, requiring different devices. It’s stupid as hell to turn this kind of thing into in-group status symbol pecking. The market for these devices exists because one size does not fit all.
My biggest complaint about web components is that I don’t see a lot of advantages over using React, Svelte, or some other JS library. The author hints at this: if I’m already committing to a big JS build process, why wouldn’t I reach for one of these more ergonomic JS tools? Warm fuzzies for trying to use open standards isn’t enough to convince most people to switch away from more popular JS solutions.
My daughter is very creative and loves to spin up ideas and stories. When she asks me a question about the universe, I throw it back at her.
“Daddy, why do flies have such thin wings? Why don’t they break?”
“Well, what do YOU think?”
She’ll then invent some explanations, we’ll have fun questioning them, and eventually look up some real answers.
My son is much more execution-minded. He usually asks questions because he wants to understand how to build something. With Legos. In Minecraft. Whatever. He’s less interested in creative word play and more interested in creative building. Sometimes I can use the same tricks as with my daughter. “How do you think it works?” With him, I can often reframe the question and make him grapple with his goal at a higher level.
“Sure, here’s how a gear box works. But what do you really want to accomplish here? Is there a better way to do this?”
I haven’t read any books, this just seems to work for us. In either case, it’s critical to encourage kids to ask questions, and to teach them how to ask effective questions.