Doing something that's true invention is far more difficult, and the results are far less impressive in the short to mid term. As an example, you probably won't find Objective-Smalltalk [1] very impressive, I would say that a good part of the reason for this is that it is really trying to invent something new. This is slow/difficult because you must eschew the easy/obvious answers. It is difficult to communicate for the same reasons: everything is subtly strange.
Rust? I'm sure there are many other counter examples too.
The kind of game changers Kay is talking about are not that easily approachable. You won't be able to take your existing knowledge of language X and suddenly see how they mostly apply to Y too. If that were the case then you've not really changed the paradigm, only given a glimpse of how it could look from the existing one.
And the reason you don't see many of these kinds of innovations in the FOSS world (although they definitely exist), is because they don't gain traction. If something is clearly new and takes significant effort to learn, very few people are going to take the time to investigate it. Meanwhile, solutions which fit well into the existing paradigm are easily accessible by masses of developers, and they flourish. This is probably one of the main reasons that real invention is rare: people are after fame, and adoption rates aren't going to go up quickly if you challenge existing conventions.
Innovation like the one at Xerox PARC needs lots of money.
Imagine how much a Interlisp-D, Smalltalk, Mesa/Cedar workstation would have cost in the 70's versus a plain PDP-11. Also a reason (among many others) why the market didn't adopt their technologies.
Rather, I'd say it needs people working full time. With things like basic income, this can be decorrelated from "money" a good deal.
A product like the Alto doesn't get done by a few hipsters subsisting on "basic income".
But, to quote Wayne Gretzky:
I skate to where the puck is going to be,
not where it has been.
You can build today's complicated things cheaply. But if you really want to achieve a quantum leap you need to think 10 years out. It is not cheap to build today the prototypes of things that will be desirable in 10 years. That is what Xerox PARC was doing.It is tempting to look at an FPGA and say that it only costs $10. Or maybe even $1000 for the top end. But that's the tip of the iceberg. Designs that go into a high end FPGA could easily require 10 man-years of engineering time. That's for a single FPGA hardware design itself, not the system it goes into, not the associated software.
Once you need to do those sorts of things you won't find the right people by recruiting basic income hipsters that are lounging around at your local Starbucks. And you will need money to pay the considerable non-salary expenses, even if you could convince all the people to work for nothing but equity.
Right now, it's relatively cheap to do software-only things. Which explains why there are so many of those sorts of startups. But it's not cheap to design and build physical things.
People seem happy to donate to Kickstarter projects, the amounts needed would be smaller if the participants already had enough to live on.
What would be the Alto of today designed with hardware from 2030, not with a cheap FPGA from 2015?
What do you want to build today that is too expensive to try out ?
That, as they say, is the $64,000 dollar question.
I sure don't know. I'm not creative enough. Do you know?
My intuition is that there is about 0.01% of the population that is visionary enough to properly answer that question.
From what I have read, the people at PARC got there by similar routes, there was one group from SDS and another from Evans & Sutherland. I'm not sure we still have the same kind of "landmarks" that will attract the right people.
I'm one of that 0.01%.
I encourage others to contact me to get the discussion going.
You are more right than you think. The initial manufacturing cost of an Alto (adjusted for inflation) was...
http://m.wolframalpha.com/input/?i=12000+dollars+from+1973&x...
I'm sure you get the reference, but since we're dealing with a worldwide audience, here's where it originates: https://en.wikipedia.org/wiki/The_$64,000_Question
It was a meme: "a common catchphrase for a particularly difficult question or problem"
It is fairly simple to you today, given that Alto exists.
It wasn't that simple for those guys in 1968, trying to imagine how a 199x computer would look like (Alan's words). That was their goal.
> What do you want to build today that is too expensive to try out ?
That is why they are called inventions and there are patents to assign to them.
Nobody knowns without doing the proper research.
It was pretty simple. I've used and programmed an Alto, back when Stanford had a few around. It was basically a reworked Data General minicomputer in a small rackmount case. 16 bit word oriented, programmable in BCPL or Mesa at the low level, Smalltalk at the higher level. The removable hard disk was the same as a DEC RK05 cartridge disk. The Ethernet interface was very simple, and coax Ethernet was electrically simple. Alan Kay referred to Ethernet as "an Alohanet with a captive ether". The CPU was microcoded, and cycles were stolen from the CPU's microcode engine to run the peripherals. None of this was pushing the state of the art. The CPU hardware was a minimum viable product.
The keyboard, mouse, and display were all new, and nicely engineered. Most of the hardware effort went into those. The keyboard had nice key switches and a massive metal casting. The display was the first good black-on-white display, with a big portrait-format screen. The original mouse wasn't that great.
Virtual reality environments with good graphic. Or maybe something like microsoft hololens. Glasses which work like AR HUD and tracks your movements, your gestures and maybe voice. This requires a lot of custom hardware (microsoft developed ASICs for this to do it in realtime).
Also .. it would be awesome to port smalltalk to 3D.
https://www.youtube.com/watch?v=NdSD07U5uBs
As an example of the type of research being done, you must be willing to build something that will be considered commodity in 15 years time at today's price.
You won't get there with basic income.
Just don't agree it is enough to innovate at Xerox PARC scale, as what is being discussed is funding, not salaries.
Eh, if they'd put Altos in serial production instead of small batches at a time adding up to 2,000 units it wouldn't have been vastly more expensive. There was nothing both exotic and wildly expensive about them compared to contemporary PDP-11s + a graphics console. The extras were a mouse, chord keyboard, network adapter, and more memory per person than normal for a PDP-11.
If you have a problem, you write code that solves the problem and give it to others to use. Software should be at least minimally usable to be adopted. It should work with other software.
Look at the software in Alan Kay's VPRI: http://www.vpri.org/ They don't write software for you to use. They build software to use as platform to test ideas. If some of those ideas is good, someone may rewrite the whole thing to fit into current software infrastructure.
Time.
I'm working on a Ruby ahead-of-time compiler. I started in 2008. I slowed myself down a lot by all the blog articles I've written about it, but yet, at this point it's only now getting close to being able to compile itself.
The reasons it's been so slow going, is that in those years, I've only put in the equivalent of a few months of fully time work on it - it's not my only project, and working on my side projects have to compete with spending time on my son and other leisure activities.
It takes a lot more people to get the equivalent output of a lab of fulltime staff. Even more so because this slows down interaction and communication as well.
The landscape is very different from what it was in 70s. They were working on a clean slate before half of the human population had computer terminals in front of them. Their battle was to get the terminal in front of people, but I'd argue that the biggest accelerator to adoption has been social media, not the way GUIs behave or programming languages function. The web is now the legacy software we're stuck with if we want any impact at this scale.
Say for example, if you had a completely new idea for a general purpose operating system which simplified things greatly, but was unlike Unix, and it had no web browser. Now what? People aren't interested - they want their web browser.
Most innovation is coming directly from the OS community: hardware, software, systems, etc.