I worked for Uber about a decade ago. I was aware of the stories as they'd circulate internally. It's fine, until it isn't. Calling it hilarious is a lack of imagination or critical thinking at best.
As a gay dude I experienced my fair share of "uncomfortable" Uber rides from or to various places. No thanks. I don't need to stimulate those kinds of social skills or whatever.
Gay here, but I've only experienced a concerning conversation once, and that was a longer trip where sometimes you find out too much. I took an exit ramp away from that topic of conversation and it was fine. Otherwise everyone has been decent to downright pleasant.
I'd feel like I'm losing something by giving up that human interaction, such that it is.
I don't care what people think about me. I care about the guy who has Jesus hung in every nook and cranny with a candle lit in his front cupholder telling me that I need to repent. In San Francisco, I might add.
I couldn't care less what people in the Philippines - one of the most gay-friendly countries in Asia - think of me through a camera stream.
Some regulation that limited the operators to work in the city they supervise would be an easy job win for some politicians. Create some jobs and look like you’re standing up to big tech.
> the human supervisors in the Philippines watch you through the Waymo cameras and talk about you
Literally don't care. What I don't need is to be evangelised with whatever conspiracy theory or fringe religion my driver just joined the entire way back from JFK.
In case you’re being serious, sometimes it’s fun. Most of the time, I don’t care. But the reliability advantage of Waymo is usually something I’m willing to pay a bit extra, and wait a bit longer, for.
Haha I was obviously being a bit tongue-in-cheek, and it’s not true every time, but yes I do generally appreciate the wacky convos with cabbies when I land, it feels like a warm welcome home.
Your comment resonated with me because this doesn’t really happen when just taking ubers around town. I don’t really know what’s special about the drive from JFK — maybe the length? or the drivers being used to picking up tourists, who are more chatty? — that brings out the hustle chat and conspiracy theories, but I guess it’s a thing!
A lot of my personal time, and a few others that I know, is being spent either updating, replicating or simulating the classic BBS experience today... while not really simulating the Modem itself.. trying to get the way a certain terminal looked in the old days is a bit of arcane knowledge combined with the time to make it work.
AI does a pretty good job of a lot of it... I've mostly been using Rust for my target language, the biggest parts so far in terms of rework/retries has been getting the "experience" how I want it, which isn't really a 1:1 of the classic experience, but updated. Like mouse scrolling for scrollback controls, etc.
There's also been a lot of activities in enhancing the BBS software that remains today (Synchronet, Enigma, Mystic and a MajorBBS remake) along with continued classics and some door games.
True. And it has the same safety implications as in software and security but more obvious since the slop creeps it's way into the physical world: One of my main hobbies is drones. Lately less flying cause of a long track record of crap weather every weekend for like 6 months so I'm more on the building side of things. I would not trust a slop machine to design and build something that weights 4 kilos, carrying a highly flammable lithium(ion or polymer) battery and fly it in a remote field even. Off the top of my head, I can think of 200 ways this could go wrong. And most people with a functioning brain that have watched the news will agree with me. The line between "Claude sloppus is so good man, look at this awesome thing it did" and "Lost control of the drone, it flew into an airfield and crashed into the engine of a plane taking off" is incredibly thin. What pisses me off is that if this happens, regulations will hit those of us that know what they are doing and will make sure this never happens, and not the geniuses who think slop is a viable solution for everything. Same story with the never ending leaks and supply chain attacks which are a direct consequence of sloppers.
I hate TS's tooling with a burning, deep passion. But its type system is actually pretty incredible for what it is.
There are times that I yearn for TS's ability to do duck type reasoning in e.g. Rust (despite that not being feasible) when working with very large data types.
On the other hand, if the same problem keeps happening, it's hard to argue that the problem isn't foundational to the design and that it should be called out until either the problem is fixed or the design abandoned.
It's not that there isn't a conversation to be had. It's that it's a low-effort, karma farming, reddit-tier comment that always invites emotional/reactionary responses, typically the same ones as before, that usually shoots to the top of the comments section and drowns out any relevant or interesting (see: curious, as per HN guidelines) discussion.
The syntax is of course very Rusty, which is cool. However, a sort of obvious question comes to mind - what is the benefit of this over just writing rust, then? Just because the compile times are shorter?
EDIT: should mention I understand why embedded scripting languages exist, having embedded Lua many times. And I love a lot of these features, but to me having an embedded scripting language should simplify the language/API surface area instead of mirroring it almost 1:1. That's what I'm a bit undersold on.
I'm author of a rust based task manager (not (yet) FLOSS, unfortunately), where we needed "pluggable task sources" (jira, github, trello, etc).
In our setup, the "sources" are more like configuration. Whereas the core, the business logic, is more like code.
Typically, one would configure with e.g. YAML. As we can see in many projects, that have a DSL, in yaml (k9s, GitHub actions, ansible, etc).
But, rather than inventing another DSL in yaml, we realized we do need some logic, something very poorly expressed in yaml. And we went for Lua.
Long story to say: if your config typically has some logic in it, it makes sense to go for an embedded scripting language to provide it, rather than building it into the core domain, or to invent yet-another-yaml-amalgation (yayamla?)
Hot-reloading. You can edit your logic without rebuilding and restarting the host application; this cuts your iteration time from minutes to seconds, especially if the application is in a state that would need to be recreated.
Other commenters have given most of the reasons already, but since you asked specifically for the author, I'll chime in as well.
The fact that Roto gets compiled at the runtime of the Rust application is very important. That means we can ship a binary and still allow scripting.
We also believe that Rust is too complicated for our use case in some respects, we're trying to make something simpler. Our target audience for Rotonda is not people who necessarily know Rust. We can never be as simple as Lua because of the static typing, but we're trying our best.
And finally, we don't have to ship the entire Rust toolchain with our application. Roto is fully embedded into the binary with no external libraries needed and that's quite nice in practice.
reply