At Square most of the applications run in the datacenters and this project allows AWS Lambda instances to seamlessly call into the datacenters -- basically developers can break out part of their apps and deploy them as Lambdas.
I don't know if it's true. People tend to conflate the price for cells with those of modules and entire battery packs. IIRC, the holy grail is < $100/kWh for a battery pack.
Batteries are a commodity, so I doubt Tesla would want to reduce themselves to an OEM and shrink their margins. Their energy business might eventually be bigger than their automotive one, but either way I think they will continue selling vertically integrated products.
I think the takeaway here is not that some corners of Go are not performant (and should be swapped for C++/D etc.), but that there are tools in the Go ecosystem that help you figure out what the issue is.
Until Twitch hit the bottleneck with their service, they were reaping multi-year benefits of faster development using memory-safe language (huge gain for security).
Their short- (or mid-) term solution seems decent and more importantly Go core team is working on addressing this particular issue (which given the Go 1.x backward compatibility promise makes it really easy to reap all the benefits with each Go release).
You're incorrect, Square has non-SF offices, too. I think @nrp has put it well in his comment https://news.ycombinator.com/item?id=21342101. Square is categorized differently than Salesforce by SF tax law and pays a different proportion of taxes than Salesforce.
Very recently there was a flurry of articles about Apple copying popular apps, among them woman health apps [1]. Although they were not wrong to voice their concerns about Apple, it's hard to cheer for the app makers when you later find out they don't exactly value your privacy and are not upfront with you, as a user, about that.
It's so that you can have a seamless module version checksum [1]. The checksum in proxy ensures that you don't "trust on first use" whenever you update a module.
Yes, we can definitely incentivize people to change their energy usage habits as well. EVs will come very handy if/when their charging schedule can be centrally managed (thru automaker car networks or smart chargers).
Yes, renewable energy like wind and solar are intermittent, so we will need to invest (a lot) more into energy storage. So far storage has been expensive and need to drop a lot, so it can reach mainstream [1].
I thought it was really thorough and quite technical, so if you're interested in the early day of electricity more than just personal anecdotes, then this book might be for you :)
It definitely depends on your use case, so it's hard to tell what's better for you. HAProxy is solid and doesn't take a long time to get started.
At the same time, some of the HAProxy 2.0 features have already been available in Envoy and tested in production, at scale (if HAProxy provided those features, there wouldn't be a big need for Envoy). For example, Envoy is pretty extensible, has good performance and has good support for dynamic cert management (including service-to-service mutual TLS).
Tesla Semi has multiple packs that can be charged in parallel. The Megacharger will (likely) be 4 Superchargers combined. 1MW should be enough ;)
re: announcement, I'm surprised not much has been said about the flagship cars (S/X). With their current battery architecture (using 18650 batteries), they're not capable of 250kW charge rates. I wonder if they have recently updated them to new 2170 battery packs or if they're going to do that soon.
This is a deep-dive on the mTLS set-up for Lambdas, but for general overview check out https://developer.squareup.com/blog/enabling-serverless-appl...