This is an easy fix. Ditch the HOV element and make the lane toll-only. Tolls already encourage carpooling -- more people in the car means less toll per occupant.
> given the incredible preservation that Dolphin provides for their original versions.
Does cemu not provide comparable preservation for the HD versions? I played through both WW:HD and TP:HD on my Steam Deck using cemu and found it a great experience.
Trump will certainly consider this provocation, so perhaps the news here is that Amazon considered this worth it, even given the inevitable retaliation.
Isn’t Trump the one doing the tariffs? Isn’t the point to get you to buy products without tariffs? I’d think this plays directly into what Trump wants.
The narrative has been that the 'other countries' pay for the tariff. Not the US consumer. So this may be an issue and not one that you can walk away from easily when the customer sees that it is added to their bill.
Trump has at least 3 contradictory goals that he has spoken at length about with his tariff policies so it’s not clear what exactly would make him happy that you could consistently work towards other than I guess capitulating to whatever demands he has that day.
Prepare yourself for a shock then; bootstrapping rustc starts from an already-built version of rustc[1]:
> the only way to build a modern version of rustc is a slightly less modern version.
(There is, at least theoretically, a non-circular bootstrap chain starting with a very old rustc written in OCaml, but the more practical alternative is probably to use mrustc[2] instead.)
Ocaml has a bytecode blob in the sources (even checked into Git). It uses that to resolve its own bootstrap problem. If you aim for a source-only starting point, your journey won't stop at Ocaml.
The strike emphasizes the importance of automation. We should be prioritizing the investments that will allow us to fire as many of them as possible as soon as possible.
It's no wonder people fight the automation - there is no support to help them upskill or retrain. Although they are fighting a force that nobody has successfully stopped, it makes sense why they would do this when the response to "we don't want automation because it threatens our livelihoods" is "get that automation in place ASAP so we can get these people out of here".
Yeah... it's a pretty strong signal to send to the company owners. It's a direct threat to the company's ability to compete and therefore survive in exchange for maximum personal benefits. I guess it's probably mutual and the company squeezed them for maximum profit too but man.. This is not a fight that can be won unless the entire world stagnates at the current technological level forever.
>The union has made it clear that they're not willing to entertain such discussions.
That's not the same discussion. I am sure they are more than willing to turn docks into worker co-ops, then automate so it's a benefit to them not a threat. But I am sure the shareholders and dock owners wouldn't want that.
Right. I was discussing positions the union has actually taken and what their advocates have actually said. If you're looking to discuss wild hypotheticals about what you think they might support in some scenario that doesn't exist, more power to you, but I don't find such conversations productive.
I find it productive. And I find it maddening that negotiations haven't seemingly entertained the idea of talks like "yes automation will come but we'll make sure you can pay your bills and transition". That would be the first topic in eastern countries.
The west treating labor as a dog eat dog world is what lead to this in the first place.
> Daggett contends, though, that higher-paid longshoremen work up to 100 hours a week, most of it overtime, and sacrifice much of their family time in doing so.
> “We do not believe that robotics should take over a human being’s job,” he said. “Especially a human being that’s historically performed that job.”
You might be looking at the 100 hours thinking that’s grueling work. Meanwhile workers could be looking at that thinking it’s their AWS auto scaling for their family income.
I have a friend doing electrical line work. He’s gone back and forth between IC work and management. ICs trend to get paid better, because of strong overtime compensation rules and there’s a queue of overtime work. Those overtime weeks sound rough though. 12+ hour work days working with heavy machinery and 10 Kv power lines.
Hence they're striking before it's possible to try to get the agreement right? I see what you mean on signaling but this seems like the correct play for them
I'm a little confused about when I'd use this, if I'm quickly iterating on code as I develop it, probably I also want to know whether it type checks, right?
No, during development your IDE will show you type errors and your dev server can ignore them. In CI tsc can type check. It's the best of all worlds: incorrect code will compile and work best-effort, you can see errors in your IDE, and CI will fail if it's incorrect.
The article makes it sound like the system was using eval (probably on a per-request basis, not just on start-up), and also like ceasing to use eval was pretty trivial once they realized eval was the problem. I'd be curious why they were using eval and what they were able to do instead.
