highfestiva

Jacob Barber worked 30 years for USINT. Quite the specimen I must say.

I'd love to have all those problems fixed. I constantly bump in to exactly those things myself, and I believe a majority of developers would find the language better with than without remedies. Especially the trivial things (like flatten, moving reduce back out from functools, lambda state and so forth) takes no time - it's just politics.

Starts as a local sci-fi movie, heat-ends as a cosmological documentary.

I just knew it! Soon it won't be that local after all. ;)

An expert without basic generalist know-how is just ignorant. An expert in only a single field is single-minded (think "SAP expert":). A generalist without expertise is just average.

Do both, as people always have. But start out a generalist to get an understanding of what is good to specialize in. Then pick 2, 3, 4 diverse areas to home in on.

A job well done, congratulations! The idea is fantastic and your implementation, including the choice of non-lossy reference image, has a sound design. The purpose and intent is obvious.

And please ignore the complaining bunch! Any metric can of course be misused (think unit test coverage, linting, soft coding, etc.) but writing software is craftsmanship. We're half-way to art. To even be able to measure is an achievement, and what gets measured gets better. Me and my senior colleagues immediately took it to heart and will use it as objectively as language shootout. Many thanks for planting an industry standard seed!

Performance is the most important feature. Also on web apps. https://www.google.com/search?q=%22performance+is+the+most+i... 2M hits on exact match can't be wrong.