Hell is trying to work with time zones in javascript

design @splits | /latenightcrew /event-pass /feud

Explorer. Code, design, and mountains. Building Fern https://fernhq.com

glad to know i’m not alone 😂

i like the simplicity of your solution!

This is a fun read and one of my favourite posts about this topic https://zachholman.com/talk/utc-is-enough-for-everyone-right

I’ve also had to work on this problem https://matall.in/posts/building-an-usable-timezone-selector/

Building Larry, FOSS via @frames, @framesfun /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

I feel you. My previous startup dealt with a lot of IRL events and it was a nightmare of complexity. 

My learnings
- Store timezone (ex: 'Europe/Berlin') along with UTC date
- Compute timezones server side (using users browser local timezone) to avoid loading giant timezone libs to browser
- Don't make any assumptions

cto @ bwl.gg (lunchbreak.com), 80M+ users (bdut.ch) 🙏 built @remindme, @mintit, @gpt, @healthbot, farcantasy.xyz

honestly should be the default... but my struggle rn is parsing into time zones

founder @explorelabs

don't take my casts seriously please (most of them at least)

normally i would agree, except it has a pretty horrible understanding of dayjs/momentjs from my recent experience

Half of the reasons that I've worked (when I was a FT dev) in programming languages that I didn't like was because the TZ support was good

Use a library like those recommended and pray what you need is baked in reasonably. Also if you can convert to UTC and just render display values in the "correct" TZ.

the 'in javascript' part is not needed :)