That just isn't true. You only need to browse caniuse.com for 5 minutes to see there are significant differences between browsers even for mature CSS features. If you want to use anything new it's a minefield.

>If you want to use anything new it's a minefield.

That’s true with any platform. But if you stick with tried and true stuff, it’s hassle free.

I don’t remember the last time I had a layout rendering issue and I write this stuff everyday all day.

Not sure why your ADHD fuelled shiny seeking is an excuse for the shitshow that is electron. Just don't use new stuff?

I'm also unsure how it is even supposed to solve that specific issue considering my laptop is currently running at least two versions of electron for different apps, both of which render text as their primary directive.

The parent comment was stipulating that CSS is mature.

The reply was that it isn't because there are lots of features that are not available to all browsers.

A mature platform would be one where the features are consistent in whatever environment it is in. So in that regard, CSS is not mature.

"Just don't use new stuff" is not an excuse.

I never said it was an excuse. I said it was a valid approach, so are polyfills.

My issue isn't really with that my issue is that the issues with CSS and the valid workarounds are not painful enough to validate electron as a solution.

If electron did what it promised I wouldn't have a problem.

just don't differentiate from your competition using new features, instead focus on features users don't value at all - like memory consumption and being browser agnostic