Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://toot.cafe/users/nolan/statuses/113340900722953634">Nolan (nolan@toot.cafe)'s status on Monday, 21-Oct-2024 06:28:36 JST</a><a href="https://toot.cafe/@nolan" title="nolan@toot.cafe"><img src="https://gnusocial.jp/avatar/22381-48-20221110111318.webp" width="48" height="48" alt="Nolan" style="position: absolute; left: 0; top: 0;">Nolan</a><div><a href="https://toot.cafe/@nolan/113340884451613164" rel="in-reply-to">in reply to</a></div></section><article><p>Maybe this is why I'm a little skeptical of the whole "move everything to Rust/Zig/Go/etc" movement in the JS ecosystem. I like JavaScript, I understand JavaScript. If I have to debug some JS tool, I'm well-equipped. Whereas if I have to dip down into some weird error like "libfoo.so.42: cannot open shared object file" then I know I'm gonna get lost.</p><p>Plus I don't think we've come close to exhausting all the ways to optimize JS deps: <a href="https://marvinh.dev/blog/speeding-up-javascript-ecosystem/" rel="nofollow noreferrer">https://marvinh.dev/blog/speeding-up-javascript-ecosystem/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3856285#notice-7540636">In conversation</a><time datetime="2024-10-21T06:28:36+09:00" title="Monday, 21-Oct-2024 06:28:36 JST">about 15 days ago</time> <span>from <span><a href="https://toot.cafe/@nolan/113340900722953634" rel="external" title="Sent from toot.cafe via ActivityPub">toot.cafe</a></span></span><a href="https://toot.cafe/@nolan/113340900722953634">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/3333088">Untitled attachment</a></label><br></li><li><article><header><div>Domain not in remote thumbnail source whitelist: marvinh.dev</div><h5><a href="https://marvinh.dev/blog/speeding-up-javascript-ecosystem/">Speeding up the JavaScript ecosystem - one library at a time</a></h5><div></div></header><div>Most popular libraries can be sped up by avoiding unnecessary type conversions or by avoiding creating functions inside functions.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Nolan (nolan@toot.cafe)'s status on Monday, 21-Oct-2024 06:28:36 JST Nolan
in reply to
Maybe this is why I'm a little skeptical of the whole "move everything to Rust/Zig/Go/etc" movement in the JS ecosystem. I like JavaScript, I understand JavaScript. If I have to debug some JS tool, I'm well-equipped. Whereas if I have to dip down into some weird error like "libfoo.so.42: cannot open shared object file" then I know I'm gonna get lost.
Plus I don't think we've come close to exhausting all the ways to optimize JS deps: https://marvinh.dev/blog/speeding-up-javascript-ecosystem/
In conversationabout 15 days ago from toot.cafepermalink
Attachments
1. Untitled attachment
2. Domain not in remote thumbnail source whitelist: marvinh.dev
  Speeding up the JavaScript ecosystem - one library at a time
  Most popular libraries can be sped up by avoiding unnecessary type conversions or by avoiding creating functions inside functions.

Public

Embed Notice

HTML Code

Corresponding Notice