Echo JS 0.11.0

<~>

tracker1 comments

tracker1 430 days ago. link 1 point
Personally, I don't like using the thenable syntax or response.json() directly with fetch api.  I prefer to use async/await syntax against response.text() then JSON parse directly, keeping a handle to the original request... Then I can return the json body or text body with the error and the result code as part of the error raised.  I'll usually put this directly in a function that will give me more information as part of the error chain.

Using thenables this way makes it a lot harder to do that.
tracker1 468 days ago. link 1 point
Maybe worth mentioning...

    Foo.prototype = Object.create(null);

...to break default inheritance from Object.
tracker1 472 days ago. link 1 point
FYI: Maine and Nebraska aren't winner take all states.
tracker1 498 days ago. link 1 point
It's worth noting that protocol buffers are *NOT* faster in JS than in other languages.  You can often get faster results from compressed json than protobuf and other binary wire formats.

You might be able to use a binary extension/module for Node/Deno that can access the direct sockets to handle the encode/decode in a lower level language (such as rust).
tracker1 498 days ago. link 1 point
It's definitely nice to cover this... that said, if you understand the loose comparisons it can be useful in practice.   Especially when you're dealing with ETL workflows.
tracker1 498 days ago. link 2 points
Yeah... this would be the way... curious on Deno and Bun though... we need a can i use database against the node API for the others.
tracker1 518 days ago. link 2 points
I definitely appreciate these efforts... I kind of wish there was a bit more collaboration between some of these groups.  I mean rspack/rsbuild, biome, and even the typescript, deno, bun and other groups that are duplicating some of these efforts in several ways.

I'd also like to see a bit more integration of TS into these tools as a flag beyond transformations alone.
tracker1 526 days ago. link 2 points
That would definitely be a nice tool... I feel that this will only get more difficult in time though.  Right now it's easy enough to prompt a few popular LLMs to see if you get similar text, but man, what will the cost be in the end.

Both in generated content as well as bot detection and anti-bot tooling.  I'd hate to be github.

I can only say I fully expect that we may wee a return to more niche communities that are self-regulated, similar to BBSes of old.  In only that the popular platforms for social media are already inundated with bot activity.
[more]