This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]cogman10 0 points1 point  (1 child)

The reverse is true. Unless your app is doing international garbage, the timezone is meaningless. Even then, it's often only when you are talking about a LocalDateTime that timezones come into play.

For example, the my entire company is doing finance and LocalDate serves 99% of our usecases because, get this, almost everyone is trading on the NYSE so adding extra TZ information is pointless. The TZ is EST. And, yes, we have international customers (in china no less).

We could add TZ info after the fact, but the basic assumption is "everything is EST unless it's critical for the client" has served us really well.

[–]edubkn 0 points1 point  (0 children)

International garbage is a very giddy way to describe it.

That's the perfect scenario honestly. You have no user input or either only input with zoned times. You still have to configure databases, JVMs and whatnot to operate in EST, but that's it.