Most companies where I worked have a history of rebuilding their applications every 3 to 5 years, some even 2 years. This has extremely high costs, it has a major impact on how successful the application is, and therefore how successful the company is, besides being extremely frustrating for developers to work with a messy code base, and making them want to leave the company. A serious company, with a long-term vision, cannot afford any of it, not the financial loss, not the time loss, not the reputation loss, not the client loss, not the talent loss.

Webpacker used to configure Webpack indirectly, which lead to a complicated secondary configuration process. This was done in order to provide default configurations for the most popular frameworks, but ended up creating more complexity than it cured. So now Webpacker delegates all configuration directly to Webpack's default configuration setup.

ts geo-metric meaning is also more obvious as the rotation axis and angle can be trivially recovered.

this is so stupid (that there is no sensible way to run a Desktop file from the terminal)

When one is searching for it on the internet, there are many many people wondering how one can open .desktop files. It seems trivial, since one usually just has to click an item on the launcher so one thinks there must be some way.

If I can find some time, maybe I can help pitch in somehow.

That should work, but it's a non-trivial change.

Writing the uniqueness validations yourself is easy so I felt it was better to leave this up to the developer

why a company like Facebook invests so much research and engineering into the network performance of things as seemingly trivial as notifications.

The change is too consequential to be developed in situ.

But it sounds like the library could use some way to setTouched()

Wondering how to get field state from multiple fields at once? People coming from Redux-Form might be wondering where the equivalent of Redux Form's Fields component is, as a way to get state from several fields at once. The answer is that it's not included in the library because it's so easy to write one recursively composing Field components together.