While an upload queue does sound like a better solution overall, the suggestion of cooldowns as immoral is absurd.
Ever decided to not buy some new technology or video game or product right away and to wait and see if it’s worth it? You’re an immoral freeloader benefiting from the suffering of others who bought it right away.
This is what markets like Polymarket boil down to. Normies can't win. Some will, of course, but that's just chance and there's no way if ensuring it's you.
It's really no different than a casino: if you ever find yourself with more money than you walked in with, cash out and leave.
Best strategy for most people though is to simply not participate and you'll break even.
I fully agree with not participating and would go even further: it's far worse than a casino, which was already bad. It's not regulated. It has a stronger impact on the outside world. With bets you can put a target on people job or head.
Except, the thing is, a decent portion of the population enjoys throwing money away in casinos. If they feel a similar level of enjoyment/entertainment from this type of market, then it's no different and they're playing for a non-financial purpose that your calculus isn't pricing in. Maybe a stretch but theoretically, if they enjoy it enough, it can serve as a much cheaper alternative to a casino and thus could actually have a positive net return to one's personal finances even while losing.
And, I'm not even contemplating gambling addiction. There's a huge market of people that just go to Vegas once or twice a year and come home thousands of dollars poorer. But they don't need it, they may not gamble outside of Vegas, or nothing that would signal an addiction.
> I don't have a gambling addiction, I just enjoy throwing money away in casinos. I come home thousands of dollars poorer. It's a net return to my finances. Totally healthy.
It's all hypothetical of course but I know Vegas has some high table/game minimums and these markets can be pretty cheap if you just want a piece of action. Also, eliminates the cost of actually traveling.
Again, no idea if anyone sees this as a true substitute or not. My guess is not as Polymarket bets don't feel entertaining at all (IMO). So it's not filling that void for anyone, but it hypothetically could.
Input type=date also just saves the day, month and year with no timezone information, which makes sense since the widget doesn't show any and context determines if the date should be in the user's timezone or a fixed timezone (like an event start date or a flight departure). But if you don't immediately convert that date to an ISO date and instead save it to the DB as yyyymmdd, you're in for a world of hurt trying to display date/times throughout the site. I inherited a project like this and have spent countless hours wrestling with nightmare timezone issues.
This is still a partial solution as the user needs to know that their locale is being used and know how their locale is configured to understand the format. This is most problematic on shared computers or kiosks, especially when traveling.
Is is the device display language, the keyboard input language, my geo location, my browser language, my legal location, my browser-preferred website language, the language I set last time, the language of the domain (looking at amazon.co.uk), the language that was auto-selected last time for me on mobile or... something else entirely?
Exactly. Under Windows, this isn't even consistent across applications. I'm in France, with the location set to France, using English display language and "English (Europe)" formatting. This means that the expected date is DD/MM/YYYY. It's what shows up in the taskbar, for example. But many applications seem to do this based on language, so I sometimes get MM/DD/YYYY.
I don't normally run Windows, so I can't check right now, but I think it's mostly "modern" applications that mess this up. Like the MS Store, Teams (obviously).
the only locale i know about is the windows one that's hidden in some menu that i had to set to japan to get some random application to run, and now all of my backslashes look like yen symbols :P
... maybe i won't get mm/dd/yyyy now!
I think modern browsers are actually quite good here. They show a template in the form TT.MM.JJJJ for me (so the German equivalent of MM/DD/YYYY, with the usual order and separator in German). I can just type the date, including the dots if I want (they're just ignored; there would be extra points for moving me to the next component when typing "2.", but the world's not perfect). If I'm confused about the format, or want to see a calendar view, I can click on the calendar icon (also accessible via tab) and select a date there.
For normal date inputs, I really don't think there is a good reason to use anything else. (Possible exceptions I can think of: Selecting date ranges and/or showing extra data about the dates (like daily prices).)
No, modern browsers are horrible at this as they are often ignoring your settings (at least Chrome and Edge on Windows do). They are basing the format entirely on the language instead of the date format configured in your Windows settings. Safari on iOS seems to not have this issue though as far as I can tell.
I mean, once in a different country, you either experience the locale shock once then adapt, or you've seen it before and kind of know what to expect.
And for the rest of the users who have no idea about locales, using whatever locale they have on their computer might be technically incorrect for some of them, but at least they're somewhat used to that incorrectness already, as it's likely been their locale for a while and will remain so.
Well, the issue is when the applications look at the wrong configuration to set this up.
Think about traveling to a different country for a limited time. I want my location, time zone, etc to be set to where I am. I traveled across the US a few years ago, and I would rather not have to mentally follow in which time zone I was. Heck, I don't even know where the limits are. Bonus points for DST happening on a different date than in Europe, and extra bonus for there being no DST in Arizona, except for Navajo Nation? I remember signs saying it was illegal to carry alcohol, but I don't recall anything about time zones.
But as a European, I don't want my date to suddenly appear in US format; I'm only there for a few weeks.
> And for the rest of the users who have no idea about locales, using whatever locale they have on their computer might be technically incorrect for some of them, but at least they're somewhat used to that incorrectness already, as it's likely been their locale for a while and will remain so.
Not really. A lot of computers are set to US locale (probably because it's the default) and the user just has no idea why some programs have dates in some crazy middle-out format and avoids those programs.
That can get messy and confusing if the user's locale is different from the language of the web page.
When I write in English, I of course also want to edit dates and numbers using English conventions. But instead, I am forced to use decimal comma and day/month order because those are the default locale for Swedish, which is my default locale.
I have never encountered an OS that doesn't work that way.
On the web you'll often don't know: it could be anything.
This is the equivalent of requiring all your text to be in Esperanto because dealing with separate languages is a pain.
"Normal" people never use YYYY-MM-DD format. The real world has actual complexity, tough, and the reason you see so many bugs and problems around localization is not that there aren't good APIs to deal with it, it's that it's often an after thought, doesn't always provide economic payoff, and any individual developer is usually focused on making sure it "looks good" I'm whatever locale they're familiar with.
And Sweden. And probably lots of other countries too.
It's a world standard, and there are very few places that use hyphens in dates that are not ISO dates.
A partial solution is to put DD/MM/YYYY (or the appropriate format) as the input placeholder. You could also display the format as a tooltip when the input field is focused. IMO this is better than dealing with date pickers.
You can but you have to tie it to actual devices and a point in time, not simply a specific OS version. Essentially, all devices that existed before the change must still support the old set of characters and devices produced (or sold or activated) afterwards can support the reduced set.
Or wait until a future OS version that will not support any device currently in existence.
This fails if they let you keep your password migrating between devices, though, so you probably need a version somewhere in the middle that flags it as an issue and flags it as not allowing migration without changing the passphrase.
You need to not just force the update, but also forbid using pre-updated ones in migration, since someone might conceivably have an off-for-many-years device they wake up and want to migrate.
The long tail of stupid edge cases is very long indeed.
Law is more akin to philosophy than computer science.
reply