3 ms·
I can see why it may make sense for JetBrains. JetBrains IDEs have extensive support for theming every type of element, and the IDEs are also continually evolvi
by jhanschoo 2y ago
I can see why it may make sense for JetBrains. JetBrains IDEs have extensive support for theming every type of element, and the IDEs are also continually evolving. The actual situation for many JetBrains color schemes (albeit free) are that that you may run into situations where something is not properly styled. I thought of redoing a Nord color scheme for a fun hour-long up to weekend thing and just didn't bother when I learned more about it.
- wruza 2y agoThat’s the issue with these “semantic” color schemes, high complexity with (maybe subjectively) low value. Look at this.name(), is it a variable, a property, a method, a bird, a plane? Who could tell without that lighten(resaturate(green, -20%), 17%) hint hardcoded as a fixed value? Decent coloring systems use a few colors to structure the code/data/ui and that’s it. Nobody needs these hundreds of accents, it’s just a component of upselling.