Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Backend should send and receive in UTC. The format doesn‘t really matter but I recommend iso 8601 because well, it‘s a standard.
Frontend should store in UTC as well and only convert it to local time when it is presented to the user, like as a text in UI. Take the region info from the UI system to convert to local time.
Lost about 4 days debugging bug about date conversion between frontend to backend as an api request.
This shit is mad fucking annoying
The date format was always wrong.
So i gotta ask. Is it better to always have date fields as a Long which contains just a huge number that represents a timestamp, and that way whenever i want to see what date it is i would have to convert it every time on both frontend and backend from timestamp into LocalDateTime, or is it better to keep it as Date/LocalDateTime and not string/long, and that way risk fucking up the date format?
How is it done in real world projects? Whats the right way to do it and why?
rant