879 karma · joined July 12, 2014
Often even without my input: "(thinking..) Oh I discovered that I misjudged XYX, let me fix that.. (thinking) (executing scripts) Okay I corrected my mistake, I had accidentily ABC."
These are affected, too, and will probably all stop selling to other EU countries because how could they ever fully grasp that regulation in all its details.
It's a shame, life and doing business is difficult enough already, and then millions of people get those regulations thrown at them.
They already had a big wave of newsletter closures when the EU's GDPR came around and everyone was scared to handle customer data. Now here's the next round.
Or rather, if a little bit of X is bad, why would you want more of X?
In this case no, it would be a lot easier to make business without the EU than with it.
Having the EU should make things better and easier, not harder and worse, for the members of said EU.
Internet businesses by contrast have a power law distribution. Meaning if you perform average you will end up with just $100 per month. The potential upside is infitite though.
The outcome of the average business person is very different between physical and online business.
Could also be a bug hunt "Sometimes we get an error message about XYZ, please investigate how that might happen." or "Please move setting XY from localstorage to cookies".
About adoption I want to add that at some point a whole generation will turn 16/18 (legal driving age) and just not do a driver's license anymore because they will buy an autonomous car anyway. And IMO from that point on adoption will be very fast.
My outage averages around 20 minutes per year, so an uptime of around 99.996%.
I have no idea where you see those "huge outages" coming from.
And in the table example you don't need the "where", because it's obviously in the restaurant's timezone.
Just picking the year is so difficult already on both Android and iOS as well as desktop Chrome, so a custom widget is immediately 100x better.
Yes, in theory it would be best to display the native picker because in theory it has a great UX, but in practice the native browsers' implementations are mostly just really, really bad, for whatever reason.
That's what I really dislike about the linked article - it doesn't even check the native implementations for their quality but just argues as if they are great.
And I think their paid hosting was actually really good, up until they switched their $20/month plan to a whatever-it-may-cost and we-send-you-10-cryptic-emails-about-your-usage-every-month plan. That's when they lost me, not because it got more expensive but because it became intransparent and unpredictable and annoying instead of carefree.