By GPL, they're only obligated to release an offer that allows costumers to request the source code. They can still keep the source "closed" by default.
It has to be the source of the distribution the user currently has a copy of. So they can't just say "sure" and then wait until the next public release. I'm not sure about timeliness, though.
I work in payments and yet I once gave my card (and 3DS auth!) to a phisher. Thankfully I realized what had happened pretty quickly and immediately deactivated the card. But the fact that I went through the whole process before realizing was pretty harrowing. For all I know, that might not have been the first time.
Interesting there now seems to be an insurgence of SQL workbench type apps. I also saw DB Pro recently.
Despite all of these really polished query editing experiences in these new apps, I reach for Redash every single time. Even though Redash's editor is horrible. The ability to generate even extremely simple sharable visualizations, and alerts is insanely useful.
So to any of the devs of these programs out there: ship visualizations and alerts and I will buy your product immediately.
No disrespect to you, but this solution is unacceptable.
The onus should not be on customers to workaround corporate wrongdoing. DoorDash states that 100% of the tip goes to drivers. They conveniently omit that some of their base wages will be covered by the tip. That should be illegal, and paying drivers under the table gives DoorDash the right to keep acting badly, my convenience be damned.
But let's say I was willing to gloss over this. The extra logistics just aren't customer-friendly.
Drivers see te tip before they accept the delivery mission. I would have to tip normally (so that drivers will deliver to us), take out cash (which I almost never use), add logistics for giving them a cash tip, then drop the tip to zero post-delivery (which could mess with my rankings and threaten our future with the service).
Tipping in cash is easier with something like Uber, where you'll already have cash on hand (because you're already out) and the money can change hands at the end of the ride. (To be clear: I'm not giving Uber a pass here. They also do shady stuff with driver payouts.)
The OP wasn't about doordash though, it was about uber (poster mentions the ride-sharing part of the business in a comment elsewhere). I don't believe DD is lying about 100% of tips going to drivers, particularly given Tony Xu also publicly denied this behaviour was happening at DD on his twitter
I work in Ruby a lot on large/old projects. I think the main reasons are: people nowadays are very dependent on editor intellisense, and "undefined method ... for nil" errors in production are very frustrating.
That said, I am actually in the "don't want types in Ruby" camp. Intellisense isn't as needed if you're good at using irb (the repl). And the dynamism makes it super easy to write unit tests, which can give you back a lot of the guarantees you'd otherwise get from static types. Most importantly, a lot of the fun in Ruby comes from the ability to make nice DSLs and aggressively metaprogram boilerplate away.
I hope at some point people don't feel the need to justify using or not using LLMs. If you feel like using them, use them. If you regret doing that, delete the code and write it yourself. And vice versa - if you are in a slog and an LLM can get you out, just use it.
You have to break down the problem into manageable chunks anyway, might as well feed those into a code agent while you write it yourself. If you don't like what it did explain what it did wrong. Shouldn't take long to figure out what parts are the biggest waste of time to write yourself. Do still have to hop tools and adjust your confidence as they improve.
reply