1,759 karma · joined November 11, 2014
I do think they should have a more obvious warning that the current directory is untrusted, right now the little green warning in the corner is way too unobtrusive and will result in many people having the same issue as you.
Trying to take something like a windsurf board on a train, and then having to navigate multiple train changes along with whatever other baggage you have makes it a non-starter.
The "last mile problem" you mention is unresolved when it comes to getting from the closest public transit stop to the actual destination (frequently in a park or even off road).
And finally, the final cost to the rider would be significantly higher, as sleeper trains are not cheap.
I think America could do quite well if it focused on public transit in and between densely populated areas. Fewer cars in cities could make for denser cities, which in turn could allow for even more public transit. But outside of population centers, America is much more spread out than Europe, meaning that trains are less economical, and often wouldn't get the ridership that would allow them to make sense.
The first seems like it could be resolved with an escalating fine schedule, and the second could be mitigated by requiring Apple/Google to remove it from the app store (one of the rare cases walled gardens are on consumers' side).
> Now, here's the kicker: the bigger the focusing lens is, the larger the cone of light rays is, meaning the the out of focus parts of the image will be more out of focus
From the page [0] it takes the depth of focus image from:
> [Depth of focus] differs from depth of field because it describes the distance over which light is focused at the camera's sensor, as opposed to the subject
[0] https://www.cambridgeincolour.com/tutorials/depth-of-field.h...
That seems like a pretty lame gotcha--saying "Aha! The language you write in uses your hated paradigm under the hood" seems to invite the immediate response of "So? I don't use it."
> I wouldn't care so long as I wasn't expected to maintain it.
But, if you’re the one putting out that software, of course you will have to maintain it! When your users come back with a bug or a “this flow is too slow,” you will have to wade into the innards (at least until AI can do that without mistakes).
I disagree. If you discover that a bug that makes an open source library unusable to you, after spending time on learning and using that library, and the authors close the bug as a wontfix, I think being annoyed is quite reasonable, even expected.
I think the question is, how much risk is involved and how much do those mitigating methods reduce it? And with that, we can figure out what applications it is appropriate for.
To expand on this, a given power line can only take a set maximum current and voltage before it becomes a problem. DC can stay at this maximum voltage constantly, while AC spends time going to zero voltage and back, so it's delivering less power on the same line.
An MP3 player seems like a good compromise, and far cheaper than the phone they’re replacing.
That being said, if I were to start a new project requiring that kind of work today, I would probably try Polars first. Their greenfield implementation allowed them to get rid of many of the crusty edges of pandas.