Can't confirm. We had students at university (18-20-ish) that had not used a mouse prior to our courses. That was at least 3-4 years ago now and not a single case.
So something that you can do with PDKs is add your own custom standard cell and tell the EDA tools to use them. This is actually pretty smart, this way you can use most of the foundry cells (which have been extensively validated) and focus on things like this "magic multiplier", that you will have to manually validate. This also makes porting across tech nodes easier if you manage only a handful of custom cells versus a completely custom design.
(I have my guesses as to what that is, but I admittedly don't know enough about that particular part of the field to give anything but a guess).
My "only" experience here is designing ASICs for Neuromorphic Chips. We used sub-threshold exclusively for linearity and energy reduction. No standard cells for us
We have been running Ardour 9 for a while now during band rehearsals. Currently 12 channels that we record and monitor in realtime with some effects on top.
My personal idea revolves around "can I run it on a basic smartphone, with whatever the 'floor' for basic smartphones under lets say $300 is for memory (let's pretend RAM prices are normal).
Edit: The fact this runs on a Smartphone means it is highly relevant. My only thing is, how do we give such a model an "unlimited" context window, so it can digest as much as it needs. I know some models know multiple languages, I wouldnt be surprised if sticking to only English would reduce the model size / need for more hardware and make it even smaller / tighter.
Started a comment to write basically what you said. I've been commuting like that for five years. At the end I didn't bother trying anything productive anymore.
Losing 2-3h per day commuting is not something I am gone miss anytime soon.
I still remember when Google (and Facebook?) used XMPP for their chat functions. You could log into any XMPP client and chat with people using Google infrastructure.
reply