This smacks of the typical Apple, "you're holding it wrong" condescension. I understand why MacOS does things the way it does most of the time. That doesn't mean that I can't still find it frustrating.
As a Windows user, I'd be pretty concerned about the multiplatform story here. They say that this is MacOS only for now but they intend to eventually ship a Windows App, Linux App and web app.
It just sounds like a recipe for a Sketch situation where it's really just a Mac app and web (and other platforms) is a second class citizen.
You and the author are conflating two different kinds of "openness". The user is talking about the openness of the default visibility where you're presumably referring to the openness of the implementation.
That may be true today but it feels like it's changing, though. And I think it kind of aligns with what the authors are talking about. Apps started today are natively collaborative and they're written with web technology.
It's funny to me that there's no acknowledgment that high fidelity web apps and electron apps are taking the wind out of the sails of platform specific desktop app development.
Tweeted at you but copying here for visibility! Am a full stack dev, and enthusiast pianist and have hacked on some music software in the past. Would be interested in contributing!
Mostly comfortable in TS web frameworks, React / Angular / Node
It's less "settling a debate" and more "clearing up major misconceptions than most people will come away with from watching Veritasiums video". I've taken several physics and electronics courses in my life and after watching Veritasiums video, I was under the impression that the majority of the current would be flowing through the lightbulb immediately which is not the case. So this video is just demonstrating that there's an initial "residual" current induced in the lightbulb from the electric field but the majority of the current is propagating at the speed of light through the wire.
Urbit sounded interesting but I dug into the source code a bit and found that the core of the whole system (the Nock language) has "loobeans" instead of booleans in which 1 represents false and 0 represents true at which point I nope'd out pretty hard.