In my opinion, I am sure that all of the companies you mention would like to ask for money up front. I am not sure that they can. ASML holds all of the cards in litho. I am not sure any other company would be negotiating from such a position of strength.
I agree Intel wants larger wafers. Racing process is increasing their number of process steps driving moore inefficiencies into their fabrication process.
History shows Intel will bypass disruptive innovations at adoption stage if an alternate method is farther along its development curve;
multi dice package vs. multicore dice comes to mind. Sound strategy reducing manufacturing risk this way. Especially when the moore costly solution is concealed by monopoly accounts practice.
Note of interest at Semicon session Lithography: Extending Double Patterning, Industrializing EUV and Complimentary Technologies in which Borodovsky presented, is that EBEAM was seen as the compliment to 193i & Directed Self Assembly not EUV.
I personally believe Intel will harvest their current lithography investment until applied science passes through innovation phase to identiy the next process commercial industrial art.
I think ASML has a duty to shareholders to announce any (share) price sensitive information. 300mm EUV R&D is done in all but power source/throughput (?). Intel wants 450mm EUV and 450mm ArF,KrF and immersion. This is the beginning of the end for Nikon, Intels traditional lithography partner. My money is on TSMC & Samsung to follow Intel's move.
EUV is part of the deal. But phase one is 450. I think that is what Intel wants more. Intel's Yan Borodovsky spoke today about using complementary lithography, including 193 immersion, DSA and perhaps other technologies. But I think Intel is just trying to cover its bases. Intel still wants EUV badly. But it seems to me that the jury is still out on EUV's economic viability.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.