console

I totally agree with this. I actually quit my job at Red Hat because of the culture of non-criticism. I kept getting in trouble for pushing back against stupid decisions, even though I never insulted a single person. For example: When the design team added 10MB of web fonts to the app, I said something like, "Users don't care whether the font is Open Sans or Arial. They care whether things load quickly and don't re-flow. This is a bad decision." I got nothing but condemnation for pointing this out. Today, every user downloads several megabytes of web fonts which have broken kerning and hinting on some platforms.[1] It was a similar story when people wanted to change our build artifact to be based on RHEL instead of Alpine Linux.[2] This would have bloated the build artifact from 11MB to 200MB, introduced a host of security concerns, and d

I work at Red Hat (part of the CoreOS acquisition) and I have to say that PatternFly has not been useful to the project I work on.[1] First, PatternFly is big. We were mandated to adopt it, and it tripled our CSS (from 45kB to 145kB). PatternFly also bundles Open Sans web fonts, which (depending on font format) add another 200kB to 4MB to the initial page load.[2] Second, development is slow. There's a rewrite of PatternFly in the works, and its roadmap predicts a 1.0 release after April of 2019.[3] It's a CSS framework! How can it take over a year to make?! There will be two major releases of React in the same time. Speaking of React... PatternFly-React has similar shortcomings. Their babel setup doesn't seem to support tree shaking, so if you use any PF-React component you'll have to bundle 2MB of JS. The speed and quality of developmen