487 karma · joined December 27, 2019
foreach(var (f, l) in enumerationOfPersons) { ... }
tells him absolutely nothing about what's going or even that there are names involved
foreach(var (firstName, lastName) in enumerationOfPersons) { ... }
is better but doesn't give him an object to inspect to see where they come from and what else is available.
var (f, l) = person;
is so much worse than
var (f, l) = (person.FirstName, person.LastName);
I don't want to have to refer to documentation or class implementation to understand what a destructuring expression does.
Second, this is independent of structural vs nominal typing - implementation of an interface can be thought of as inheritance of a class whose methods all have noop implementations, and in fact this is (almost) how it's done in languages that don't have interfaces like C++
IIT is pure sophistry - some years ago Scott Aaronson showed that using their definition of potential for consciousness electronic devices employing certain kinds of algebraic error-correction codes have it - meant as a reductio-ad-absurdum of IIT, apparently its promoters have decided to try and own the absurdity.
In other news - nautil.us is an utter garbage chute of an outlet, the new-science-journalism equivalent of British tabloids and I fully expect them to publish a psuedoscientific apologia for astrology or an evolutionary theory supporting the existence of Bigfoot and the Loch Ness monster - post-Darwinnian cryptozoology anyone ?
Why ? An ecosystem consists of multiple offerings and there are also multiple commercial ecosystems.
> And it's totally feasible to produce a superior ecosystem. The hard part is absorbing years of financial loss while building the new ecosystem from the ground up while it isn't compatible with the existing proprietary system.
Being able to finance something is an inherent part of its feasibility.
Which in practice binds absolutely no one to absolutely anything.
In other news: 2020 is not the year of the linux desktop.
No-one, at all, for the love of jeebus: Do another node-like thing, but make it in rust on top of C++ (or is the other way around ?), somewhat similar but generally incompatible, have a whole different set of APIs, a bunch of new tools and yet another package/module system.