Steven Luscher

```shell npm dist-tag rm @solana/addresses latest npm dist-tag rm @solana/assertions latest npm dist-tag rm @solana/codecs-core latest npm dist-tag rm @solana/codecs-data-structures latest npm dist-tag rm @solana/codecs-numbers latest npm dist-tag rm @solana/codecs-strings...

> What would reimplementing the legacy API to call the ideal API help us do? Back when Relay was completely reimplementing _everything_, the library forked into ‘classic,’ ‘modern,’ and ‘compat.’...

> Building the solana-sdk for wasm to avoid re-writing all the transaction packing logic/etc in web3.js would be splendid. Thanks for bringing this up! I've heard this a few times....

> …great choice of word in the current climate & state of affairs. 🤦‍♂️ where is the media & pr communications filter Oh? What's the cultural context that you're referring...

> principle 5 sounds like dependency hell. Thankfully we're on the same team! I meant _ES_ Modules, not _NPM_ modules. I'll update the text.

> I don't know what you mean by principle 5, but I do like how lodash is structured… 100%. Underscore and lodash were the inspiration for principle 5.

> In principle 8, it would be really useful for me to have makeSubscription and the abortable callbacks to match the [TC39 Observable spec](https://github.com/tc39/proposal-observable). I've used `Observables` in the context...

> keep the function inputs as concrete as possible (for ex; codeblock1 requires a provider, which requires a wallet, but it never uses it... I know this is an anchor...

> Please please please, improve the overall debugging process for this library. Absolutely. I'm elevating this to principle 10.

> If we can automate generating TypeScript types for all of the endpoints it will lower the maintenance burden quite a bit. If you could see my screen right now,...