They already run on gcp and presumably have a negotiated agreement on pricing. Their core competencies don’t include managing hardware. Migration off is deliberately expensive and hard. Own hardware still needs a story for backup and restore in lieu of attached volume snapshots, or they’d have to figure out if their database can do something for them there. Any of the above are good reasons to not migrate willy nilly, in fact the only reason to migrate is that either you can’t do what you need to in the cloud or the margins can’t support it.
I love the sentiment of avoiding the totalitarian dictatorship but you don’t exactly have any control there. Technology is leverage and it can be used for evil, just as with IBM tabulating machines in nazi Germany
Maybe the thing to solve this will be individual electric motors that are mounted to subframe as to not add unsprung mass but articulate with the wheel somehow. Or more realistically instead of huge angle on undriven wheels, a bit of an angle on all wheels. It’s been done for a while, in the 90s on Japanese sports cars and now German luxo barges.
Exactly, Rust has been around for a while and it hasn't reached parity in terms of LoC with C and C++ in Gecko's codebase, presumably because it's impossible to rewrite individual units unless the API is impossibly narrow. This new language will be more like different JVM langs in terms of interop.
Big-tech has solved this internally. Everything down to the linux kernel they're running in prod is versioned and has people maintaining it and interacting with upstream (if any). This is obviously a full time job for at least a person per dependency on average.
What have they done with your data? Also have worked at a few FAANGs and from what I’ve seen (admittedly not working on social or B2C products) data is subject to rules and is generally used in aggregate only.
I’d agree, it matters not whether the surrogate for a person’s missing personality is a designer label and a lime green Lamborghini or a second home in Sonoma and ayahuasca trips to burning man.
Aversion to sex work aside, how’s this different than some of what’s done in Silicon Valley? Uber will happily extract the remaining equity in your car as you teeter on the brink of homelessness at which point DoorDash will be happy to make you your own boss. Maybe I’m just jaded because it’s hard to find a place to rent wherever there’s a booming market for Airbnb rentals.
But a gas car with no cats, tuned for maximum power is not really comparable to a diesel truck rolling coal. One might leave soot on its own rear bumper, the other covers everything behind it in disgusting soot.
I think iOS makes use of NX bits such that for your vanilla app, the executable pages aren't writable and writable pages aren't executable. Historically, this resulted in WebViews not having JS JIT which severely impacted performance. Apple later came out with WKWebView which underneath the covers runs the browser engine as a standalone process which is able to write executable memory and thus able to JIT JS.
The load time is contingent on ping, for instance with TLS over TCP you need 3 full round trips to get a pipe that can carry HTTP, this is 3x as many as with TCP alone. In the author's scenario there's a 500ms delay, so naively that's ping of 250ms which is really high. In the case of HTTP/1.1 or asset loads from other origins, there may be additional connections that are made which will all incur the extra overhead as well, though the author's blog is served over HTTP/2 which wouldn't incur this cost for same origin asset requests. For me best case for author's blog (just the HTML via curl) is 250ms plaintext and 600ms TLS. What's more interesting is that plaintext is a lot more consistent for me because I have pretty bad packet loss and the HTTP request fits into a single TCP segment.
Plaid is a menace. My checking account was synced on Venmo just fine using the small transfer method for years until plaid was introduced. I redid the old school verification 3 times before giving up and linking via Chase. I changed the password afterwards but of course that unlinked me again. Can’t wait until some regulatory agency comes after them.
As much as I'll miss being able to type raw HTTP into an nc/telnet/openssl s_client when H/1.1 support is dropped, these are all caused by HTTP originally being a simple, textual protocol that got thrust into supporting connection reuse, "flow control" and a bunch of other stuff. All solved by H/2 and beyond.
You actually do, what Tulsi generates is an XCode project that has shell script build steps that call out to bazel. Bazel underneath the covers will end up calling the clang that comes with XCode.
You need a full Santa exemption with business reason to use brew. The average person working on some server that deploys to borg does indeed use their Macbook as a thin client. Who's obtaining deps for their builds from brew? If you're building stuff on Mac, it's via bazel and all your deps are in source control.
Possibly a new Prius, which should be less environmentally destructive to produce given its lower price (this is kinda disingenuous since price is only a rough predictor of env impact, there’s economies of scale, taxes and subsidies, etc) than an EV. Here’s another question though, in a state like CA which wants to shut down its last nuclear plant, has a bad outlook for hydro in the near future, where would you charge this EV? During the day at work?
You could be running gas through fuel cells if you want, still not as efficient as amortizing existing infrastructure. This reminds of the EV debacle, you should be buying a used Prius or walking places if you care about the environment, everything else is just posturing.