Laws should be loser for autonomous vehicles with good safety records.
No one is protected by preventing waymos from making rolling stops, and driving like a human Uber driver.
The quality is much worse for me with uncommon words. I also plan to add a thin llm rewrite layer on top so I can write by just speaking but that will be later.
Usually when I go and read the github and zulip threads the reason for paused work comes down to the fact that no one has come up with a design that maintains every existing promise the compiler has made. The most common ones I see are the feature conflicts with safety, semver/encapsulation, interacts weirdly with object safety, causes post post-monomorphization errors, breaks perfect type class coherence (see haskells unsound specialization).
Too many promises have been made.
Rust needs more unsafe opt outs. Ironically simd has this so it does not bother me.
When I read these sorta of articles I ask if I would invest today if given the opportunity. Currently the answer is still yes.
They have barely even monetized users. I think it's possible the bubble pops and openai still continues to win.
So much of this article is copium pretending the world is not radically changing. Even if progress stops today massive numbers of jobs will be and are being replaced. I wish it wasn't true but what I wish has no bearing on reality.
At some point self driving cars will need their own loser driving laws.
Perhaps allowing them to drive around school buses is not a good idea, although personally I have felt far safer biking or walking in front of a Waymo than a human. But rules few humans follow, like rolling stops, and allowing them to go 5 over seems like a no-brainer. We have a real opportunity here to br more sensible with road rules; let’s not mess it up by limiting robots to our human laws.
Yes it does, I mostly use pocket for tts, but the ui is worse. If you use android's local you can only skip forward and backwards 15 seconds, and it frequently loses your place if you pause it. @Voice allows you to tap on the text to seek.
Pocket and @Voice apps tts.
@Voice allows you to jump through text by double tapping and supports more sites and formats (PDF, etc.), but pocket manages your article list so much better so I use pocky 90% of the time.
Pockets uses a readermode view, so it's non tts UI is nicer, so if you don't care about tts just use pocket.
Firefox reader mode is also nice, Firefox preview is great.