The source code isn't the idea, the idea is. That's what needs to be communicated.
The web page is huge, though, with an unbelievable amount of information if you want to build your own.
The source code isn't the idea, the idea is. That's what needs to be communicated.
The web page is huge, though, with an unbelievable amount of information if you want to build your own.
If what they want is for people to try and reimplement Dynamicland without their guidance, then they’re certainly doing the right things. But if their goal is to convert people to a new way of thinking about computing, this is not a great approach.
What a low opinion you have of yourself. On the contrary, you're likely to learn a lot more (and of course, spend orders of magnitude more time) recreating something interesting from the ground up than you are simply copying the source code.
The source code isn't the interesting part.
Ultimately trying to tightly control a technology because he wants it to have a particular impact seems like it's just going to ensure it stays a niche demo instead of making and impact at all. If the idea is strong enough people will adopt and adapt it for themselves because it's good.
Bret is also in no rush here, the plan has taken a decade so far and has milestones ahead of it for a decade more.
Maybe this is also a little frustration that it's been 10 or so years and there's not actually much new news, it looks better but I'm seemingly further than ever from being able to experiment with it.
If have taken the time to understand what he means when he says "Realtalk is not made of source code", and disagree with his conclusions, that's not quite the same as him being dishonest.
I disagree on every single line.
This is not about software. Having the software on its own won't help you.
If in 2006, the year before the iPhone came out, you had the software as FOSS, would that help? There was no hardware yet. There was nothing even with a capacitative touch screen with multitouch yet. The whole point of the design was to do away with styli, but all extant touchscreen devices needed styli back then.
I was implementing corporate networks in 1991. I built them with NetBEUI for PC-to-PC comms, and IPX/SPX or DECnet for talking to servers. Occasionally all 3.
If I gave 1991 me the source of timbl's WorldWideWeb, it would be no use. I didn't have NeXTstep. My corporate workstation ran X11 and talked to servers over it but it didn't run TCP/IP. I had no TCP/IP in the building.
The point of the Web is the protocol, having clients and servers. Having docs is much more use than having code. Code is useless fragile stuff.
Android reproduces a lot of the interaction model of the iPhone but it came from seeing iPhones and trying iPhones. It did not come from getting source. Nobody ever got the source.
Forget the source. Source code doesn't matter. It's an irrelevant distraction.
Source code is not the big deal here. Inventing a new way to interact with computers is the big deal here. Getting at the software does not matter.
If you want to implement it, then maybe you have to study this implementation, study with the implementors, and understand what it is and what it does and how it does it, and stop obsessing over some ASCII files that encode a little bit of the logic.
Life is sometimes a jigsaw puzzle. It is the picture that really matters. Having a map of the shape of all the pieces, with no images, would not really help you. It might after an epic amount of work help you reassemble a square of cardboard but that is not the picture.