I don't think OP was saying subscriptions for road worthiness but rather that they would go out of their way to spite car makers if they try to force subscriptions on us. See "Fuck Me Money".
The gas taxes haven’t kept pace with inflation, though: we already have to heavily subsidize road maintenance with general fund revenue and to be an effective pollution reduction mechanism we’d have to raise it considerably, which is politically infeasible in most of the country.
Almost all states with significant EV adoption have a special charge for EVs each year. What sucks is that it isn’t based on how much you drive, so if you aren’t using your EV to commute, you get charged just as much as someone using it all day for ride sharing.
Charging based on usage would require you to provide your mileage to the government, a tracker in your car, or some other privacy destroying method. I guess the government could just ask for your mileage and take your word for it, but that isn't reliable.
Car inspections that happen in most states do take count of your mileage fwiw I believe. However I also don't think charging based on "usage" makes sense here. Due to the jobs some people have, you may need to just drive a ton more and roads will need to be maintained either way however much you drive.
It’s coming eventually, once enough of the cars are EVs, flat fees aren’t going to be very viable if they don’t want people to game them. It’s not hard to read an odometer, it is hard to say where those miles were accumulated f you want to be really fare and get tax revenue to the state/place you were driving in.
In rural Ohio, the Amish use the roads for their buggies, but don’t pay tax. Wonder if they have registration fees for their buggies? I’ve never seen one with plates.
As far as query languages go, you may want to look into prql, kusto or google's alternative (i forgot its name). They are composable, and more natural.
I'm curious, how do duplicates make it to the front page? My experience in submitting links that are less than a year old, the submission gets rejected and you are pointed to the previous submission.
Well written, and timely for me to get inspiration from. I have been going back and forth between doing off-the-shelf vs using opnsense/pfsense in a rackmount router. Haven't made mind on it yet.
I will subscribe to 10gbps sonic fiber soon, that's what prompted me to look into this. Unifi seems to cap wifi 7 at 2.5Gbps, however.
I can throw in my vote for Unifi. Stuck the UDM and the rest of the gear in a rackmounted enclosure in my daughter's wardrobe and haven't needed to think about it even once in 2+ years. It just manages itself nicely.
I was considering TP-Link at point of purchase, since there are some options there with more throughput. Like everything, it's a tradeoff calculation and this time I favored the convenience
I give UI a +1 for overall quality/integration and being an American company, but TPLink seems also well praised recently. With Tapo Cameras etc they seem to be going in the steps of UI too.
I had two shopping lists written down, one for Unifi, one for TP-link. It was a combination of a couple of factors. It was actually a really tough decision, because they both seemed very good value for money. I wasn't factoring in cameras, just controller + switch + APs.
It was a combination of a couple of factors (this was in 2022):
- UI and integration
- Number of reviews and write-ups
- What I could find in stock
If I were doing it again today, I couldn't guarantee that my decision would be the same. It'd be a tough one...yet again.
This is like the lambda / Linq on .NET. Well done.
Take a look at PRQL too. You may enjoy it, it may even help you simplify query transformations to sql.
Probably not in the near future, to even benefit they would probably need to complete the rewrite to a threaded design. There is a proposal to do this but the proposal notes many roadblocks since the Fork based model currently employed has left the code with quite a few places that still rely on this.
Secondly, there is a bunch of features from the SQL standard that is more or less complicated to get right with RocksDB under the hood, most importantly collations. This is because the bespoke table engines can create collation dependent indexes (ie how data is sorted on disk) whilst mapping an index to a Key-Value storage like RocksDB would require the ability to create rewrites of the strings to a binary encoding that remains sorted as per the collation (This is why MyRocks only supports binary, latin1_bin and utf8_bin collations).
reply