pixelpush

You are mixing up "waste material" with "material waste". The parent was making a point about cost. It's cheaper not to feed male baby chicks. It's cheaper to raze the forest. It's cheaper to let cows fart.

There are externalized costs to these things, but they don't really affect the prices that people are going to pay for the produce, at least not directly. I guess you can charge a small markup for being "green" (or pretending to be).

Now maybe a cow is only "3% efficient" in terms of calories, but the calories it takes in are really cheap and the calories it puts out are prized. It's a profit deal! In engineering, higher efficiency generally is more expensive and the economic optimum is never the efficiency optimum.

"Grown in sterile conditions" and "cheaper" are two completely contradictory features.

Most agriculture is still done in the field, not indoors, because that's the most efficient way to do it. A large part of the inputs is "just there". Waste doesn't really happen in production, almost everything is put to some use. Real waste happens on the store shelves.

You really have to ask yourself, what are the inputs to the "lab grown" process and what are the requirements towards purity etc. It's an open question.

"We’re a lot closer to the nasty low-level imperative code that drives people to using templates. When we looked at real Flutter code, we were sad to see a lot that looked like this. So, about a year ago, the Flutter team asked us on Dart to come up with language changes to make UI code written in Dart easier to write, read, and maintain."

Nothing about this code snippet is "nasty" or "low-level". It is trivially easy to write and understand. It is fully maintainable due to its simplicity and clarity.

It's sad to see that developers think this is somehow bad code. It probably takes a lot of experience to understand why it is totally fine.

Too many developers are lost trading added complexity for aesthetics. One more way to write the same thing. One more thing that will be inconsistent across the codebase. One more thing to learn how to read. It all adds up. All the tooling has to be updated to support this stuff. How will it look and feel in the debugger? (Does Dart even have proper debugger support?)

In the end, all you get is the looks of being declarative while having none of the benefits of being declarative.

"Windows high DPI screens support sucks. I have a 4k screen and everything looks very small. There is an Accessibility option to increase the size of the windows. However, when you do that, most of the applications look very blurry and it is even more annoying."

In my opinion, Windows 10 has the best High-DPI support of all systems. It allows you to change scaling in fine increments on per-display basis. Moving windows from one display to another scales them pixel-perfect, if supported. Pretty much all applications I use regularly work fine.

On Linux, the only thing I found to work out reasonably well is 2x scaling. I can't speak for Mac OS, but in my recollection the non-2x scaling isn't pixel-perfect.

"The text is rendered very poorly in Windows, creating a kind of chromatic aberration around it."

This is ClearType sub-pixel rendering and again in my opinion it's the best font rendering of all platforms, though FreeType on Linux works about as well. Font Rendering on Mac OS is just blurry by comparison. With Retina displays it doesn't matter so much anymore, but it was really annoying on the lower res displays.

Perhaps the author has it misconfigured for his displays and needs to run the builtin "ClearType Text Tuner" tool.

"Microsoft has made great efforts to support the needs of developers and creators, but as of 2019, I think OSX is still a stronger option for developers."

If you implicitly rely on a lot of UNIX-specific stuff, Windows will suck. That probably won't ever change.