They should re-make Episodes 1-3 and do what they should have done the first time -- reveal Jar Jar as a Sith Lord at the end of the trilogy.
Exactly! Back in the day, you had two options: (1) subscribe or (2) buy a single magazine or newspaper. Now, there's no equivalent to the newsstand for digital media.
To be clear, Google will still be storing copies of the pages they crawl. They just won't be making those copies available to end users.
This situation seems analogous to when air travel started to take off (pun intended) and existing legal notions of property rights had to be adjusted. IIRC, a farmer sued an airline for trespassing because they were flying over his land. The court ruled against the farmer because to do otherwise would have killed the airline industry.
While this is amazing and all, it's always seemed to me that this approach of using hundreds of laser beams focused on a single point would never scale to be viable for power generation. Can any experts here confirm?
I've always assumed this approach was just useful as a research platform -- to learn things applicable to other approaches, such as tokamaks, or to weapons applications.
It amazes me that there are so many people who buy a printer, are offered this "pay $x a month for Y pages" type of plan, and say yes. I mean, sure, HP sucks, but they wouldn't be able to get away with such slimy business practices if there weren't so many people willing to pay.
You can use a deque as a stack (First In, Last Out) or as a queue (First In, First Out). Lists are especially inefficient when adding/removing from the beginning of the list, but, for deques, it's a O(1) operation.
It's like there's an invisible anti-rain force field around DFW. It comes down toward us and just... disappears.
I'm with you. Also, it seems like it would be much more efficient to do carbon capture at the source, where the fuel is being used, like a power plant, where the concentrations are relatively high, compared to atmospheric capture where CO2 is less than 0.1%.
I wish Apple wouldn't restrict them as much as they do.
And it's written in Java. Even though I'm not a huge fan of Java, it's almost refreshing to see a new project claiming high performance that isn't written in Rust or Go.
I suspect there is at least one engineer who voiced concerns months or years ago, was not listened to, and is now having an "I told you so" moment.