This style of simulating faux-realistic materials (such as glass or aluminum) on the screen looks dated and cheesy now -- (Windows engineering team 2012)
Utility-scale solar is very unpopular in Japan. Because most suitable lands of them are densely forested, and installing utility-scale solar systems requires destory the forests.
There are concerns landslides due to reduced water storage functionality, and emotional antipathy at having their hometowns' mountains covered with solar panels.
I think Rust is the biggest winner that has from LLM support. When I got an compile error, it is painful without LLM to reverse-thinking how to re-write something and why it needs to be written that way.
Funny trivia. But of course -- there is absolute zero reason to base64 encode ascii text. Evenmore laughable to put Json encoded in base64 text inside regular Json.
The ideal HTML I have in mind is a DOM tree represented entirely in TLV binary -- and a compiled .so file instead of .js. And a unpacked data to be used directly in C programming data structure. Zero copy, no parsing, (data vaildation is unavoidable but) that's certainly fast.
This style of simulating faux-realistic materials (such as glass or aluminum) on the screen looks dated and cheesy now -- (Windows engineering team 2012)
They skipped iPhone 9 once. So iPhone 17 and going for iPhone 2026 could be better for measuring the age of the device and could be beneficial for consumers -- but what about the OS version? No one care that.
From an engineering standpoint, skipping a sequential number is just wasteful.
If Android had provided an defining UI API like this entirely in C without using Java, Android would have 100% monopolized the mobile OS market. So fast, efficient.
https://web.archive.org/web/20120614042824/http://blogs.msdn...
--
"Cheesy and dated" -- it keeps hitting me through the years.