You can AOT typescript types from zod schemas if intellisense is your main complaint. I think it generally makes more sense to transform from more expressive => less expressive, and zod is more expressive than typescript (as evidenced by your need to add doc comment annotations to get similar behavior going the other way).
They're talking about window units, not heat pump systems or central air. It's a complete AC that sits in your window. It can't cool a very large space (even in apartments people may have more than one), but it's cheap and easy to install (and equally easy to remove). It might be unsightly on a house, but a lot of that is probably just cultural norms. They're very common in NYC, where a lot of housing was built before central air became the default.
In the times of the French Revolution that was enough, but I think technology is obsoleting us there too. If evil oligarch can make a bunker and ten million $100 kill bots, I don’t think the people are rising up unless existence is worse than death, and even then they might not win.
Another thing I’ve encountered with tree/structured diffs is a concept of identity. diff([{id:1,name:foo}],[{id:2,name:foo}] should show object w/ id:1 removed and id:2 added, not id changed from 1 to 2. Tough because then your diffing algo needs to be aware of the object structure (imo using convention and saying “no objects can contain this key” is pretty tough when you accept any user generated data).
I think if this can keep a knife effectively sharper than the equivalent nice steel with less maintenance, then it’s going to find a market.
I’m a nerd, but Ive found that once I’ve mastered a hobby I eventually gravitate towards convenience, optimizing my time over absolute performance. I’ve built five PCs in my life, and now I only own a macbook. I spent loads of time optimizing my hifi setup, and now most of my apartment is sonos. And I have probably 1k worth of nice japanese knives + whetstones, that I would happily replace with a single knife that needs little to no upkeep.
It seems insanely risky to attempt to fill a niche that only opened up because of these tariffs. If they’re removed, congrats you just spent a bunch of capital to make a factory that is suddenly no longer competitive.
Same deal with other industries with hybrid public/private, like the postal service or insurance. Arithmetic is based on serving some people at a loss but amortizing those losses against the wider public. Private entities come in and eat the winners while leaving the losers. Public option is left with only the clients that were never profitable, and private businesses have no obligation to serve them.
I feel like immigration is effectively unlimited from the perspective of big cities. There's friction moving states, and some things keep people anchored, but the market is nationwide. If you built enough in NYC to make rent comparable to other major cities, then significantly more people would want to move to NYC.
I think all metrics can be reconstructed as “wide events” since they’re just a bunch of arbitrary data? Counts, gauges, and histograms at least seem pretty straight forward to me.
It seems like the main motivation for metrics is that sending + storing + querying wide events for everything is cost prohibitive and/or performance intensive. If you can afford it and it works well, wide events is definitely more flexible. A metric is kinda just a pre-aggregation on the event stream.
There’s a difference between “approving of” something and thinking it shouldn’t be a crime. What’s your feeling on the first amendment? Do you approve of hate speech?