As Ferrari has been proving over the last few generations, they know how to make engines but Pininfarina knows how to design cars. I'm not even slightly surprised by the Luce.

I wonder if that explains why mahinda's designs are significantly better (if still not great).

Really the only thing keeping me from going all in on keychain is the lack of a UI for the times when it doesn’t autocomplete or I need a password in terminal or something.

I’d pay for something that provided a global hotkey and an interface that isn’t nested in Settings.

The keychain app gets you out of settings, though leaves much to be desired.

Yeah - I’ve never understood why I need to type my user password twice to reveal a keychain password. It’s really annoying.

At least in Los Angeles, Teslas are more of an upgraded Prius. Most people with money have been replacing them with Taycans or E-trons over the last 2-3 years.

The wait list for a Porsche Taycan is 18 months to 2 years. They just can't make enough of them.

With generics around the corner I am really hoping we see some flavor of Option & Result coming to Go. But I won't hold my breath for ?.

> I won't hold my breath for ?.

Good idea :) `?` hides a control flow that Go takes great pains to make explicit. Adding it to the language would be a disaster.

I use Tiller for this. By initial comparison this looks more expensive with less features and a limit on total accounts, am I missing something? Tiller is a bit weak on tracking stocks in investment accounts.

Call me pessimistic, but my thoughts on the matter is that TSLA and by association Musk have become too big to fail. Anything that would take Musk down would harm a lot of very wealthy investors.

There are people looking to take him down along with SpaceX / Tesla etc. Others are glad to have someone powering ahead relative to competition in places like China etc. We will see how it plays out.

Is it superior? I have seen people on YouTube wrapping the connectors in wet rags in order to cool it down enough to charge at maximum watts.

I've never used one, our Audi is CCS but we have never had to resort to any antics even in 110f weather.

I don't think thats whats going on here. This is more like highlighting that DDG is a rebranded/privacy focused Bing.

They'd have to sell these at a significant loss to make up for the risk any company would have to take to build out a DC on first generation hardware from a startup.

I mean, how many companies are building out DCs left and right these days? Not many. This will fit in nicely for brand new projects that require nothing more than a rack. Once a company puts something through the paces for 2-3 years, and the engineers managing it love it, then the slow migration from UCS (or Nutanix) to Oxide begins. This is usually how I've seen new hardware architectures introduced at mid and large size companies.

as a heavy user of CDK, sst looks pretty cool.

i'm curious why you didn't go the direction of adding this functionality to CDK directly? i'd like to use some of the functionality in here like live lambda development, but i also don't want to take on converting my org's already built CDK extensions and deal with migrations.

Thanks!

We had to change the build process of Lambdas to support deploying a mock version of the function. And we need to add a new command that deployed the debug stack.

Here's how it works internally — https://docs.serverless-stack.com/live-lambda-development

Your existing CDK app should work with SST. The main difference is that SST deploys per stage (or environment). This allows you to do `sst start` that goes to one environment and `sst deploy --stage prod` that goes to another.