If I may toot my own horn, I wrote a somewhat more opinionated, reactive, frontend framework using PyScript. It's inspired by Vue.js, a bit: https://puepy.dev
PyScript can use Pyodide or MicroPython. MicroPython is actually quite small.
On top of the runtime, PyScript gives you some pleasantries and a lot of quality-of-life improvements for actually using Python for web programming, not just being able to run Python code.
If the military has fighters that can refuel in the air, why does United refuel on the ground like chumps?
First of all, sometimes even AWS makes mistakes and has downtime. They have downtime (usually unplanned) fairly often. Companies like VISA, that do payment processing, where countless dollars could be lost in just a few minutes of downtime, almost never update their old systems. They still have programs running FORTRAN. When they do update, it's complicated.
You can try to get really good uptime by doing things like forking your database and replicating your commit log to the fork. You can do rolling updates, where different customers are served different versions of a system. You can do extremely thorough testing.
But are you? Can you afford to do that and do you even have the engineering talent to make it happen even if you want to? Are you going to pass on new business opportunities and new features just to avoid a 20 minute downtime for a database migration at 2am? I suspect you are not.
>> We hear so much talk about urban congestion, with cities ranked by the hours drivers “lose” being stuck in traffic. How much should we care about congestion levels?
> I would say almost not at all.
>
> ...
>
> All the cities that have solved congestion have only done so because it’s a city where nobody wants to be.
Maybe no one has really "solved" congestion, but the places with the worst congestion are objectively worse places to be because of it. Mumbai, New Delhi, Lagos -- places in the developing world where there was never really even an attempt to reduce congestion.
In terms of world cities, New York and Los Angeles aren't even that bad. Compared to New Delhi, commuting in LA is a delight. And LA is still definitely a safer place to be a pedestrian. And even if you don't drive to work, congestion harms you, because you rely on services that use roads.
A more nuanced take would be that easing congestion matters, but we shouldn't design meta-cities with the idea that everyone should drive to work every day.
At first glance, these tools seem to be a bit behind the likes of GitHub Pull Requests combined with any number of the great review tools out there. Not to say reviewers at Google aren't doing quality work, and ultimately the tool itself doesn't matter as much as people think, and I don't see any special sauce here.
A lot of big tech companies have developed totally in-house tools and procedures for basic software development that mirror, but aren't quite the same as, widespread industry practice.
Before the Google Way of doing things, there was the Microsoft Way. Before that, there was the IBM Way, etc.
> Several studies show that people who live near parks, canals, rivers – any green space – are less likely to struggle with mental health issues. And this is the case even after we account for individual differences in socioeconomics. The risk of developing depression is about 20% lower in people who live near or spend a significant amount of time near green spaces. But what we don’t know is which specific aspects of the natural environment are beneficial.
So when you control for socioeconomic status, and an effect remains, is the remaining actual effect 20% or something much less? Worth asking anyway.
