I think that trucks are in worst position for moving to EV.
Customer base is quite conservative in how the truck should look like. For example,F150 lightning had to look like F150.
While a look of truck (and even ordinary car) is defined by the function - need to have beefy, but somewhat serviceable/accessible engine in the front. There is no need for this in the ev truck like at all. It's all dead space now.
I suspect that proper EV trucks eventually will look like current box-over-engine trucks (similar to kei trucks). Like Super crew truck with standard bed will probably have the same dimensions as current short bed truck, with better turn radius. But it won't look cool, and probably have the same stigma as minivans.
So, one of the main reasons it needs to look like a truck is because it needs to have a structure like a truck to be compatible with basically all of the aftermarket parts.
I want a truck with flat bed rails so I can put a cap on it. It needs to have a proper frame under the bed so it’s not bending with point loads.
I need a bed that’s a separate piece from the cab so they have flex for uneven grades.
Yeah, it's one of my favorite spaces in the whole truck. A great big trunk protected from the elements and not part of my passenger compartment. I hope we always have that feature.
FWIW, plenty of work trucks in lots of Companies are boring Vans or Pickups...
Even so, the issue comes to fit for use, cost (initial, ongoing), repairability and value. The F-150 Lightning only checked the fit for use box, since parts backlogs made it unrepairable for potentially months. The initial cost was okay at initial list price, but the actual price for purchase after dealer gouging and the factory raising prices through the roof was kind of insane... on top of a minor fender bender keeping your truck off the road an excessive amount of time killed a lot of momentum.
If there is no white 1x1 pixel that is stretched in an attempt to make something that resembles actual layout, or multiple weird tables, I always ask: are they even trying.
In all seriousness- they got quite a good run with xslt. Time to let it rest.
1x1 pixels for padding and aligning were absolutely a thing in the late 90s (1997+). Don't know what alternative history you have in mind, but it was used at the "table layout" era.
What came later was the float layout hell- sorry, "solution".
The 1x1 pixel gif hack arrived shortly after Netscape 1.1 introduced tables. I belive this was before colored text and tiled backgrounds became available. So the hack is definitely part of the “golden age” of web design.
The most surprising thing for me is that Toyota had such a big head start, but their hybrid trucks rather suck, comparing to f150 powerboost.
Abysmal power generation capabilities (I can use my as 7.2kw generator), small batteries. I really wanted Toyota, but they somehow don’t deliver, while ford is pushing hybrid f150 hard.
As someone who at a time had preorders for both cyber truck and f150 lightning, and cancelled them in favor of a F150 powerboost with 6.5 bed, I’m not surprised the slightest.
They both underdelivered on range and capabilities. Lightning has only 5.5 bed. Cyber truck didn’t had published specs with bed size for very long time.
Honestly, if it weren’t Volkswagen and it had better range, I think that something like ID BUZZ would be the best for me (daily driver, occasional hauling + camping truck).
I want the same exact truck, but with a battery that’s 10x as big (which is still very small for a hybrid). I want a truck that will actually power my stuff without needing to cycle on every 15 minutes.
I strongly dislike the way the polroblem is presented and the “solution” is promoted. Author mentions merge join with count of top, and if th database supports index merges, it can be extremely efficient in described scenario. There are a lot of real optimizations that can be baked in such merges that author chooses to ignore.
The generalized guidance without even mentioning database server as a baseline, without showing plans and/or checking if the database can be guided is just a bad teaching.
It looks like author discovered a trick and tries to hammer everything into it by overgeneralizing.
For sure, there's definitely a lot of cool techniques (and I'm not aware of all of them)! And the first example is very much contrived to show a small example.
I'm not super familiar with the term index merge - this seems to be the term for a BitmapOr/BitmapAnd?
> I'm not super familiar with the term index merge - this seems to be the term for a BitmapOr/BitmapAnd?
Different databases will use similar terms for different operations, but I would guess that the comment refers to something similar to MySQL's index merge (which is essentially reading the row IDs of all the relevant ranges, then deduplicating them, then doing the final scan; it's similar to but less flexible than Postgres' BitmapOr).
That only covers the 'transaction time' axis though? And the page says retention is limited to 1 week. No doubt useful for some things, but probably not end-user reporting requirements.
reply