//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileHeaderAlt
by @jakesimonds.com
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
Profile
Loading...
#FDJT. He/Him JavaScript In Depth - https://www.manning.com/books/javascript-in-depth
James Snell
Loading...
I have to say... reviewing Rust code to me feels a lot like sitting in a room full of people scratching their nails on a chalkboard while babies cry uncontrollably. Definitely not my favorite syntax.
11d
Heh, seems like some folks don't appreciate my opinions on responsible AI use... I've been blocked by more people in the past two days than I have in months
When Amazon picks up on the fact we have dogs that like to chew on things....
Ahem.. you mean the Tem Poral cake.
Happy to report that WinterTC/TC55 has accepted the "new streams" / stream-iter as an incubating spec stream-iter.jasnell.me The impl for @nodejs.org is coming along nicely (github.com/nodejs/node/...) and showing great results. Up to 90% less memory usage, up to 30% faster than Node.js streams,
... At least 2x faster than web streams, with with a much less complicated implementation and API surface. Whether stream-iter stays at WinterTC long term has yet to be determined but incubating it there will provide a good home for developing the ideas further.
James Snell