> The active class is clearly redundant here. If you want to style based on the .active selector, you could just as easily style with [aria-selected="true"] instead.
I vaguely remember (from 10+ years ago) that class selectors are much more performant than property selectors?
The TL;DW is: yes, class selectors are slightly more performant than attribute selectors, mostly because only the attribute _names_ are indexed, not the values. But 99% of the time, it's not a big enough deal to justify the premature optimization. I'd recommend measuring your selector performance first: https://developer.chrome.com/docs/devtools/performance/selec...
From first principles I think the concept can make sense. From car-specific function-specific ECUs, to platform-shared (but still function-specific) ECUs, then to Zonal architecture and domain controllers. The goals: consolidate and generalize HW across the lineup moving model-specific bits to FW/SW/Config (amortizes the development cost and simplifies certification), and also simplify wiring (saves you precious copper wires which are costly, messy, and heavy) because you can pretty much just plug every miscellaneous sensor or actuator to its nearest "anchor point" without worrying (too much) about arbitrary ECU limitations.
This might sound like purely implementation detail, but having the (non-safety-critical) "business logic" of a car as software gives the manufacturer flexibility to late-bind behavior as new use cases / demands inevitably get discovered.
Something can simultaneously be a good idea, buzzword'd by marketing, and/or deviate from the original intentions.
I'd argue that chassis tech is more sophisticated in the BEV case due to more weight. Adaptive dampers, air springs, rear-axle steering, etc. might not be necessary on a comparably sized ICE vehicle.
OTOH, ABS and ESP systems can achieve similar or even better results with less complexity because motor torque control is inherently low-latency, which can also complement brake deployment (hydraulics is not as well behaved as e-motor).
You do get rid of emissions control and tiny little sensors / flap actuators sprinkled all around the engine bay, so yeah, probably overall still a simplification win, but I doubt you can get very far without "massive amounts of [Mechatronics] engineering".
How is it distinct in any way that would undermine their argument? Do people go airport to airport to then not drive, where people going to downtown would want to drive? Their point is that people go to other cities without their vehicle all the time with plane travel, so high speed rail would have plenty of demand up to a certain distance.
You're not wrong, but that just means the <adjective> is where the bulk of information resides. The trade-off matters. Maybe it's a model with good enough quality but really cheap to serve. Maybe it's a model that only plays poker really well but sucks at everything else because it bluffs too much. Etc. etc.
With inflation and the terribly high cost of housing in places like the Bay Area, “seven figures is the new six figures” is an apt observation. I make six figures, yet I can’t afford to buy a home within a reasonable commute from my job, and even finding a decent rental near my job is challenging. Seven figures is indeed the new six figures.
+1. Frameworks learning costs are non-trivial. After you worked so hard to become productive in a particular framework it's frustrating to see its core and/or ecosystem fizzle --- especially when your existing code already tied the framework's unique constraints, making it a hassle to port to other frameworks. In this sense the "bus factor" / resilience of the framework dev does matter to the app dev building on top of it.
> as the overall development workflow is lightyears ahead of C++, mostly due to tooling
My experience has been the other way around. Eclipse-based IDEs from NXP, TI, ST all have out-of-the-box usable tooling integration:
- MCU pinout and configuration codegen
- no need to manually fiddle with linker scripts
- static stack and code size analyzers (very helpful for fitting stuff in low-cost MCUs)
- stable JTAG-based debugging with:
- peripheral registers view (with bitfield definitions)
- RTOS threads view (run status, blocked on which resources, ...)
And yes, these are important enough for me to put up with Eclipse and pre-modern C/C++. I really want to write Rust for embedded but struggling with the tooling all the time didn't help.
The SFBay I-880 and US-101 are always packed, often under construction, but still pothole-filled, with sections of extreme roughness. Compare this to our OR neighbors, where there are signs saying "your tax dollars at work" by ORDOT everywhere. I used to scoff at this as a display of insecurity, but apparently (from TFA at least), Oregonians' tax dollars _are_ at work.
CA takes so many tax dollars from my hands. Why aren't they "at work"?
On the contrary, I believe they are. There are thousands of miles of back roads in California built and maintained by Caltrans that are in absolutely incredible condition. Drive up and down any random mountain/hill/pass off a main freeway and enjoy a road the envy of almost anywhere else: well-built, smooth, with painted lines and signage.
880 and 101 suffer because their high traffic volumes cause much higher wear and tear while also making it difficult to make repairs.
Oregon is 60% the size of California by land area but only 10% of the population.
Roads like 101 & 880 can't be worked on during the day because of massive congestion issues. But drive up & down 101 after 9 or 10pm (even on weekends), and you'll see crews hard at work.
Hats off to those crews working the night shift.
Anecdote: Worked road construction summer 2010 as the guy who put those little sticky tabs on the road to mark where lines are repainted after construction is complete.
Sometimes I'd finish early and get odd jobs. Between Roseburg and the Oregon coast a colleague and I were assigned to stand one of those "your tax dollars at work" signs on a steep slope. Took 2 hours at prevailing wage OT and for total labor cost of $480 between the two of us. By far the steepest labor rate I'd ever been able to charge. Thanks for the money, irony!
Only because those people can't find somewhere to live that's near work. So sick of this incredibly stupid line of thinking from otherwise very smart people who refuse to realize that increased demand on transportation infrastructure is the flip-side of the housing shortage.
Agreed, but I would say that inducing demand is the point of building anything. Nobody uses that term when it comes to building homes people want to live in. They only ever use it to oppose people being able to exercise their freedom of movement.
I said it. Seems pretty straightforward to me that I am inherently less free to move via rail/sea/air than via my automobile unless the train/boat/plane can also take me anywhere, at any time, 24 hours a day, any day. I do prefer to commute via train if I can. In fact my office just moved and I've had to give up my one-shot train commute just in this last month :/
Unfortunately the alternative to divesting in road infrastructure won't be investing in rail infrastructure, it will be telling people to stay home. For sure a lot of demand for rail investment will come once it becomes harder to get around and more people lose their autonomy, but the reality for many people will just become not going anywhere at all. That means segregation-with-extra-steps for all too many places, and I was raised to believe that's a bad thing. Peep the Bay Area for example — it's really bad! http://radicalcartography.net/bayarea.html
Aside: I'm a huge railfan and have actually gotten to drive a locomotive at the Western Pacific Railway Museum even though it was very expensive and confined to a tiny circle of track. Highly highly recommend a trip out there for anyone, even if just to sight-see the gorgeous Feather River Canyon: https://museum.wplives.org/ral/
I'd like to see California consider reducing the total mileage of roads and focus on having a smaller amount of higher quality paved surfaces. My neighborhood street does not need to be 60ft wide, and our freeways do not need more lanes.
I imagine that all states would have more trouble managing more roads than they currently do, and less trouble managing fewer roads than they currently do.
Start with the fire department. They are the ones demanding 60 ft wide residential streets so that their trucks can turn around without having to drive a few blocks out of the way.
I know this hasn't been updated, and I know it's a fork of CoffeeScript, but https://livescript.net/ has had a lot of the "magic" syntax here for quite a while.
Yes, Civet has taken a lot of syntactic inspiration from LiveScript. At this point, I think we have most of the good features, but we might be missing some. Let us know what you think!
The big difference, of course, is that Civet fully supports TypeScript, and is up-to-date with the latest JavaScript and TypeScript features.
I vaguely remember (from 10+ years ago) that class selectors are much more performant than property selectors?
reply