CEQA itself is a mixed bag. I want to be clear that there are very important things the CEQA does to improve our environmental conditions[0]! The very real issue of CEQA being “weaponized”[1] stems from how environmental complaints have to be re-litigated in their entirety every time one is filed.
Say there’s a coalition of neighbors who do not want something built. They can each file a lawsuit alleging environmental issues and each will have to be handled in isolation
*I am not going into immense detail here. It is admittedly a bit more complex than this, but this is a reasonable summary
After reading over the EPA letter[0], I can't help but wonder whether the final paragraph gives a "bad faith out" to John Deere and their ilk. You could disingenuously interpret the "increment of time necessary to effectuate the repair" to mean the time it would take an official John Deere service technician with a full suite of tools to make the repair.
The following sentence admittedly muddies it a bit, but in general the suggestion that John Deere can still be the arbiter for when the machine can / cannot run without the environmental system in the loop seems like a significantly less meaningful change than what is described on the EPA.gov website.
Been playing around with Clickhouse a lot recently and have had a great experience particularly because it hits many of these same points. In my case the "local files" hasn't been a huge fixture but the Parquet and JSON ingestion have been very convenient and I think CH intends for `clickhouse-local` to be some sort of analog to the "add duckdb" point.
One of my favorite features is `SELECT ... FROM s3Cluster('<ch cluster>', 'https://...<s3 url>.../data//.json', ..., 'JSON')`[0] which lets you wildcard ingest from an S3 bucket and distributes the processing across nodes in your configured cluster. Also, I think it works with `schema_inference_mode` (mentioned below) though I haven't tried it. Very cool time for databases / DB tooling.
(I actually wasn't familiar with `union_by_name` but it looks to be like Clickhouse has implemented that as well [1,2] Neat feature in either case!)
Nebula[0] addresses this and is IMO an improvement over WireGuard. Came out of Slack originally, and it supports peer discovery, NAT hole punching, and some other cool features. Also still uses the Noise Protocol.
In practice, the extra networking features + better first class peer config management baked in is very nice (Nebula’s “lighthouses” are configured with a tool similar to DSNet for Wireguard[1])
It’s been some years but I recall that at one point probably around 2016-2017, California produced 80% of the world’s almonds. This was notable because at the same time, California was experiencing historic droughts.
Honestly, I was so confident in what I thought I knew (namely evil giant Alaskan mosquitoes) that I didn’t bother to read the article I linked, I just added it for others’ context. Culiseta alaskaensis is probably the source of confusion, and I think a switch-up happened when this was first relayed to me.
Looks like the island might be back on, assuming it doesn’t get hot enough to become temperate in the next few years hah.
Stories like these are my catnip. The 500 mile email is another great one.
How did you end up debugging/reproducing? I conjured a picture in my head of an engineer comically exasperated and squeezing the controller followed by an “Aha!”
Interesting. Subscription-based services in the home seem like a disaster waiting to happen. Unless you can self host in the event of a company shut-down, you're beholden to a company and their solvency.
Can't see anything on their website for a transition plan in the event of shutdown (and of course, why would they post that and potentially signal lack of confidence in their longevity).
*I am not going into immense detail here. It is admittedly a bit more complex than this, but this is a reasonable summary
[0] https://youtu.be/TKN7Cl6finE?si=CR4SjVK5_ojk-OKq [1] https://www.planningreport.com/2015/12/21/new-ceqa-study-rev...