Started off supporting Chrome, but realized that Safari was 40% of my traffic.... and now pulling my hair out, trying to support both... How do you guys deal with this?

I’m confused. I’m def not saying there’s no gotchas but are people not aware of PostCSS or polyfills/babel in this day and age?

You can spin up a Vite app and get the version of ES you want to compile down to pretty quickly. If you’re using bleeding-edge browser APIs that are being pushed by Chrome then sure, but for most apps for most generic issues, Safari complaints seem so overstated.

It’d be easier for others to offer advice tho if you were talking about more specific topics/problem areas than just venting.

@Hollis
I added a little bit more context in my post in the EDIT sections…

But, I think part of the issue is me being primarily a Java dev, coming into the webdev world in a more serious way just about a month ago.

@Reilly
This is why I hate modern front end. Any other kind of software, you don’t have to do this kind of dancing around build tools that will be obsolete in a year.

Hey, would love to contribute to this, can you make it open source?