Echo JS 0.11.0

<~>

tracker1 comments

tracker1 495 days ago. link 1 point
Wish theses were up on the YouTube channel... looks like the live streams are there, but separated videos would be nice.  Hopefully TBD.  I generally watch stuff like this in the Living Room via YT or other services.
tracker1 509 days ago. link 1 point
Pricing, seems out of line with other, similar books.  It's more expensive than some of the larger, more comprehensive books from O'Reilly.  Haven't read the book, and at the price, not sure that I'm willing to be the first with no existing reviews on Amazon.
tracker1 535 days ago. link 1 point
Seems to be a marketing gimmick more than a useful resource.
tracker1 544 days ago. link 1 point
Would be cool to see something like this integrated with Squoosh
tracker1 549 days ago. link 1 point
Not surprised that for-loop was fastest followed by reduce.
tracker1 549 days ago. link 1 point
Kinda weird in the comparison section... Would probably compare this with Caddy and Nginx, and no detail in terms of throughput or perf, where I think either of the mentioned would outdo this server.
tracker1 549 days ago. link 1 point
Just came across this... seems to be relatively API compatible with node, with a much lower cold start and latency time compared to Node/Deno.  It's being developed to target Lambda at Amazon, but should work with other environments.
tracker1 745 days ago. link 1 point
Would work on expanding the test harness... the application breakdown may not lead to good testing structure.  Also, I would recommend having the test next to the module being tested as a general rule.

On the latter part, some projects (looking at you ASP.Net) will break up structure into mirrored trees... you'll have a controller, view, js, etc all with the same name sitting in different directories... the same for tests (in this case), where you wind up hunting across directories looking for things that are the same contextual concern.  I prefer to see a structure based on the context/feature concern where the different types of files are next to each other in the directory, so they're easy to navigate between when working in that context and this includes tests imo.

I didn't dig into the code, so can't comment much on what is or isn't in place.  I'm generally not a big fan of ORMs in general, especially in a scripted language, as you can usuaally do type inference from a simpler mapping from direct SQL. With a taggeed template string processor in the case of JS.

As for Joi, tend to prefer Zod myself, as it has *much* better TS inference imo.
[more]