Notices by Aral Balkan (aral@mastodon.ar.al)

@djsundog Cool. I’ve already fixed it in dev so that you can now access `db` from global scope in a route file. It will be in the next release. Tracking it here: https://source.small-tech.org/site.js/app/-/issues/241

@djsundog Are you accessing it from outside the route? It won’t be defined there. I’ve been wondering if we need an initialisation method for global stuff for a while; this might be the use case to implement it so tables can be initialised with default values outside of routes.

Site.js version 15.2.2 released

Updates JavaScript Database (JSDB) to version 1.1.3 (improves query security).

https://sitejs.org

#SiteJS #SmallWeb #SmallTech

JSDB version 1.1.3 released

This release improves query security by failing faster during sanitisation of disallowed characters and on syntax errors (the latter by using the function constructor instead of eval.)

To install: npm i @small-tech/jsdb

Introductory blog post/tutorial: https://ar.al/2020/10/20/introducing-jsdb/

Source code: https://github.com/small-tech/jsdb

#JSDB #JavaScriptDatabase #JavaScriptQueryLanguage #JSQL #SmallTech #SmallWeb #JavaScript #database #security

@zens @mewmew Oh yeah, PS. It’s here: https://github.com/small-tech/jsdb

@zens @mewmew JSDB will happily handle ten times that :) But I wouldn’t recommend it for 100 times that (it can do it but you’d have to raise the memory allocated to Node, etc., and – really ­– why is your database that big, hmm? *stares in surveillance capitalism*) :P

@aral @laura That's such a great tip! Thank you.

There's also https://justbuyirish.com/

@gadonias @laura Neat + thanks for the link :)

@jums @laura Actually, just sent them an email to ask them. Will update you if/when they respond :)

@jums @laura It doesn’t look like it. But these are the folks who built it: https://hustleandpraise.com – perhaps get in touch and ask them. I can see how it would be useful to have a free/open framework that other folks could use in other countries.

Here’s one quick way to test for timing/load-related/exotic issues in your Node code: run your tests on a loop and keep doing some work on your machine. See if they fail at any point.

while npm test; do :; done

#NodeJS #testing

Live in Ireland? Don’t want to make Jeff Bezos any richer and instead support your local businesses and communities?

Check out this excellent site:

https://shoplocalonline.ie/

#ShopLocal #BuyLocal #Ireland

HT @laura

@zens Again, important to know what the limitations are and how it can be used safely. Scalpels are dangerous and will cut you every time if you pick them up using the blade. An oven will burn you if you don’t use a mitten, etc. :)

If you have time/the inclination, I’d love it if you can break https://ar.al/2020/10/24/why-i-wrote-152-extra-lines-of-code-just-to-do-the-same-thing-and-why-id-do-it-again-today/ for me so I can improve it if necessary :)

@peter It’s for a very specific purpose: to create Small Web sites and apps (https://ar.al/2020/08/07/what-is-the-small-web/) so the folks who need Big Tech tools are not who this is for to begin with. It will become even clearer once small-web.org is ready and I’ve published more Small Web protocols. These are necessary infrastructure right now and I’m trying to share every brick of the bridge we’re trying to build from surveillance capitalism to a place where individuals have ownership and control :)

@gid Thank you :) Please do let me know if you have any thoughts if you get to play with it at any point :)

@K0nrad Exactly. (And also keep those tests.) ;)

Also, another interesting observation:

Run the first loop and then run it again. Notice anything? Times go from ~100+ms to ~30-40ms

Do the same with the second loop. Notice exactly the same thing.

So both get optimised during reuse also.

Just try and understand your problem domain and understand the limitations of your tools and design/implement accordingly. Doesn’t mean you’ll get it right but at least you’ll be going from observation and experimentation instead of dogma.

So much mis/outdated information is taken as gospel… Something isn’t just true because someone said it in 2009 and no one’s bothered to reevaluate it since.

Case in point: “eval is slow”

OK, run these two lines in a recent version of Node.js:

t=performance.now(); for (i = 0; i < 10000; i++) { eval(`x=${i}`); }; console.log(performance.now()-t);

t=performance.now(); for (i = 0; i < 10000; i++) { (new Function(`x=${i}`))(); }; console.log(performance.now()-t);

On mine: ~107ms vs 169ms