Dreaming the future of software; Project Editor ECMAScript 2015;
Reformed Smalltalker
JavaScript historian dl.acm.org/doi/abs/10.114…
@allenwb@mastodon.social
“Despite my personal attempts since 2004 to subclass Arrays and others, it’s not really possible to extend builtins in ES5 in a useful, or meaningful, way.” @WebReflection
This problem directly inspired the design of ES6 class features. I’m very proud of what we accomplished.
JS classes are *not* just sugar.
There are various details to consider, be aware of, or use, to write better, faster, and modern, code.
I hope this post clarifies at least the most obvious parts that demonstrate prototypal inheritance is not equivalent.
webreflection.medium.com/js-…
Booch, Object-Oriented Design with Applications. Among others. #shelfie
ALT Close-up of a shelf of computer books. Authors: Grady Booch, Aho Sethi and Ullman, Fred Brooks, Larry Wall and Randal Schwartz, Gamma Helm Johnson and Vlissides, Kent Beck, Peter Norton.
1/ In government, there is a flawed belief that software development is a skill that they cannot afford, but software governance is a generalist’s domain, and any required specialist skills can be quickly acquired.
I know you are trying to be a good historian but I thing you are making the classic error of projecting the present on to the past.
I was a self taught programmer, first paying job 1970. CS degree 74-76. I going to focus on the the 70 with issues I see in your analysis 1/
“Instead of encoding information via language alone, the GUI uses a much richer multilayered approach to simultaneously encode information via language, symbolism, hierarchy, and context to produce an interactive interface.”
@thisisehsan
The concept of "Personal Digital Habitat" in the quoted thread is my attempt to provide a long term vision as a counter to the pervasive incrementalism that dominates industrial and academic systems research. Envision the future you want—encourage invention that goes there.
1/
At low levels that would be occurring. But orchestrated in a manner that allows a user to conceptualize a single unified “habitat" of artifacts and applications accessible from all devices. User attention shifts among devices but stays in the same habitat. A “OS” created illusion
Nice thread by @geoffreylitt, read it! He's one of a wave of thinkers/developers exploring next generation platforms and UX models. One issue is what does "local-first" mean when we (the users) have multiple "devices" that we constantly switch between.
1/
I'm super impressed by the approach @craftdocsapp is taking to data ownership.
At the same time, I think they're hitting the limits of modern data storage platforms, and hinting at precisely why we need a new kind of "collaborative filesystem".
Quick thread to explain:
Nice thread by @geoffreylitt, read it! He's one of a wave of thinkers/developers exploring next generation platforms and UX models. One issue is what does "local-first" mean when we (the users) have multiple "devices" that we constantly switch between.
1/
I'm super impressed by the approach @craftdocsapp is taking to data ownership.
At the same time, I think they're hitting the limits of modern data storage platforms, and hinting at precisely why we need a new kind of "collaborative filesystem".
Quick thread to explain:
What we need is a non-siloed "local-first" PDH operating system that provides the PDH common user experience and the services&APIs that enable the creation of PDH integrated apps.
5/
Timesharing, GUI-based personal computing, touch-based mobile computing, cloud computing all required fundamental operating system reinvention. It's time to reinvent again and create an OS that manages a federated PDH rather than a single computing device.
6/6