Yup that's what SST wraps (or at least it did when I was fiddling with it). And even Pulumi still is at the behest of the cloud providers... it still has to mirror complexity of the providers to a considerable degree. Devexp is leaps and bounds better with Pulumi than CDK though.
This ultimately needs to get addressed at the OS level. Why is a random JS file on disk allowed to read my browser cookies without my awareness? Why is a native extension downloaded from S3? This goes across all package managers (npm, pypi, cargo).
I think security controls on macOS have been trending in the right direction to tackle these types of things comprehensively with secure domains, sandboxing, etc. but there is always a war of how much friction is too much when it comes to security.
We saw the same thing with 2SV where people were vehemently against it, and now many are clamoring that it should be the only way to be able to do things like publish packages (I agree! I have no issue jumping through some extra hoops when I publish something a million people will install).
This might be a hot take but I think a lot of loud mouths with their personal preferences have been holding security in this space back for a while, and recently people seem to be getting tired of it and pushing through. The engineering leadership that won't just make these types of high impact security decisions because it might irritate a handful of highly opinionated workflows is unfortunate!
Really good internal security practices by the people who make the OS :) I don't think an attacker would be able to pull off disabling features like secure domains, secure enclave, etc. in macOS without anyone noticing seeing as it takes months of approvals, testing, etc. for a single build to even hit the beta channel.
Retro68 is indeed very cool, I started writing some Think C and it is fun to code on such a tiny screen but Retro68 allowing you to code on your regular dev environment using more modern C has been great. I've been playing around with it last week to make some applications (not a plug because these projects suck!) - If anyone wants a simple Retro68 application boilerplate to start off with:
I wasn't even alive when these computers were out but enjoying coding for them - something to be said about the simple interfaces (both in C and UI) and challenge of making things work with the constraints of the hardware.
Retro68 community has some really neat stuff like MacHTTP (https://github.com/antscode/MacHTTP) as well so you can offload some work to services (assuming you buy one of the many SCSI Wifi thingys).
You can’t use those extensions on almost any cloud like AWS, GCP, Aiven, etc. - I think Azure is the only one offering a citus product because they acquired them. Also extension updates are a major pain point in hosted DBs - always lagging behind. Having some solution in core would resolve this, even if it was just bundling some best in class extensions out of the box to bypass these cloud providers very selective extension support.
RethinkDB (RIP) was really big on this concept and we used it for a few applications back in the day. Even since then (~2016) it doesn't seem to have caught on to any other major DBs.
Most of the 1-10M+ homes in NYC, SF, etc. were built 100+ years ago. I know a number of people who live in perfectly nice homes built in the 1700s in rural areas that have consistently kept their values. Homes don’t depreciate and need demolition “within a few decades” if you just keep up with basic maintenance. If you don’t believe my anecdotal evidence, you can do a basic Zillow search and filter by price over 1M and built before 1980 and see how many results you get all over the country.
I wish this were true legally - my property tax bill on my 40 year old house would be 0, but sadly it increases every year as my home value appreciates.
Currently working on Android + iOS apps that handle the ipfs:// protocol natively and allow users to upload files as well. I think you're right on target RE: more protocol adoption and hopefully something as simple as making the links work natively and letting people upload with a simple interface will help out. The IPFS extension exists for Chrome/Firefox/Opera for similar functionality.
Out of my hands but getting more browsers than Brave to add support seems like the next place to start pushing IMO.
Phoenix has some location advantages (large rivers flow into the valley, warmer climate, better soil for agriculture) than northern Nevada that makes it more desirable and spurred growth.
Seeing the same - I have projects in us-east1 that went offline first, then us-west1 went offline a few minutes after. Everything green on their status page and nothing in the dashboard - everything returns a 404 so I'm assuming a really high level LB just took a dump.
