>By far the most important aspect is that we need to keep the new codebase as compatible as possible, both in terms of semantics and in terms of code structure. We expect to maintain both codebases for quite some time going forward. Languages that allow for a structurally similar codebase offer a significant boon for anyone making code changes because we can easily port changes between the two codebases. In contrast, languages that require fundamental rethinking of memory management, mutation, data structuring, polymorphism, laziness, etc., might be a better fit for a ground-up rewrite, but we're undertaking this more as a port that maintains the existing behavior and critical optimizations we've built into the language. Idiomatic Go strongly resembles the existing coding patterns of the TypeScript codebase, which makes this porting effort much more tractable.
TLDR: Typescript -> Go is much easier than Typescript -> Rust/Zig/$OTHERNATIVELANG
This is a very interesting reference/jupyter NB/historiography someone put together about deciphering Khipu, the cord-based numbering system/ancient Excel from the Inca's.
"Welcome to The Khipu Field Guide - Travel back in time to the Inkan empire of the 14th through 16th century. Explore how the Inkas used cloth to communicate and record commitments. Journey with me, as I work with other khipu scholars, to decipher the enigma behind a knotted mop of camelid yarn."
There is some statistical analysis here but part of my hopes in posting on HN is perhaps someone here might get nerdsniped by it.
As far as I know, it's the opposite (using Skia to render). Flutter for the web is a second-class citizen, whereas for mobile apps, it's quite productive.
Super cool demo. The potential for "contextual search engines" to live up to what I really wanted from Google Glass a decade ago is exciting.
Never tried the later enterprise Google Glass, but it always seemed generally to be more of a smart watch with a prism strapped to your face than a future-tech(tm) assistant strapped to your face.
Can you elaborate why we're living in the era of Textual? Genuinely. It seems like a pretty nifty library but I'm not sure it transcends to killer library territory. Thanks!
I stopped using phones all together since they are nothing but sources of stress, annoyance and frustration. Quality of life improved by a lot. People actually understand and my business is doing well.
I'm pretty sure he only makes his past twitch streams available to subscribers. It's weird they are available on Youtube, maybe he doesn't know that's something he can change.
Not sure about his more recent content but he used to have a policy that the VODs could be uploaded in full as long as they were uncut and not modified. If you go watch some older VODs he says so at the beginning.
>By far the most important aspect is that we need to keep the new codebase as compatible as possible, both in terms of semantics and in terms of code structure. We expect to maintain both codebases for quite some time going forward. Languages that allow for a structurally similar codebase offer a significant boon for anyone making code changes because we can easily port changes between the two codebases. In contrast, languages that require fundamental rethinking of memory management, mutation, data structuring, polymorphism, laziness, etc., might be a better fit for a ground-up rewrite, but we're undertaking this more as a port that maintains the existing behavior and critical optimizations we've built into the language. Idiomatic Go strongly resembles the existing coding patterns of the TypeScript codebase, which makes this porting effort much more tractable.
TLDR: Typescript -> Go is much easier than Typescript -> Rust/Zig/$OTHERNATIVELANG
reply