Ok thanks, I thought the above was pointing to resources as well but they're just roadmaps.
Great work then! Offering pointers to resources sounds like a great addition onto these learning roadmaps.
I'm curious, have you tried opening a PR / adding them onto the super popular roadmaps repo?
I've been thinking quite a bit about the value of sharing such roadmaps and resources in the past, even pondered working on such things but decided not to in the end. Hence my interest and 2-cent ideas.
A history that dates back to its very origins, AFAIK they were first created to manage the piles of money generated from the opium sold by British into China
Very surprised by the no value you attach to Knex, I'm curious to get your view on the values I see in using it for a few years now.
I feel at ease with SQL and like to get as close to it as possible in my Node service. But Knex still appears to be highly valuable to me to, for instance, not care about managing DB connections, at least until they become critical for my use-case.
Not care about sanitising inputs and protecting myself from SQL injections.
Have more readable and maintainable code in my repositories than SQL in plain strings as a default. Yes I have some raw queries but 98% of my queries are easy to follow knex chains.
Not care about creating and maintaining code for migrations. Running them in transactions, keeping track of and running only the ones needed, ... so happy I didn't have to re-invent that and be the responsible of it never ever failing in production.
> not care about managing DB connections, at least until they become critical for my use-case.
That's something the db driver usually does. E.g. when using Postgres, the pg library already comes with the connection pooling. Haven't looked into the implementation in Knex but i'd suspect they just use the Pool class of pg (https://node-postgres.com/features/pooling).
> Not care about sanitising inputs and protecting myself from SQL injections.
That's also not that much of a concern when just binding parameters.
> Have more readable and maintainable code in my repositories than SQL in plain strings as a default. Yes I have some raw queries but 98% of my queries are easy to follow knex chains.
Comes with the cognitive cost of maintaining another abstraction for SQL.
> Not care about creating and maintaining code for migrations.
That's actually the one feature which made me use Knex for years (just for the migration part of course :) ). I didn't use the schema builder functions mostly, just a bunch of `knex.raw` calls in the migration files.
But for the benefits you mentioned (transactions, bookkeeping) it is really useful.
"The boreal forest, or taiga, supports a relatively small range of animals due to the harshness of the climate. Canada's boreal forest includes 85 species of mammals, 130 species of fish, and an estimated 32,000 species of insects."
No you don't, there might be one I dowloaded in there but most of them were definitely not downloaded by me (and no one in my house). I guess that's a good side of getting a very dynamic IP from my ISP...
And yes I know, that doesn't mean I'm protected from getting into trouble if I did something wrong since my ISP could probably link an IP and timestamp to me if asked by a lawyer.
I'd be curious to see if the Odoo one fits, though it might be for the wrong reasons. I had to try and understand it a few years back and it looked like a complete mess to me.
Looks great, from looking at the use cases and examples.
What scares me is the requirement to have ffmpeg and ffprobe installed and available of course. Had a painful experience installing ffmpeg on Jessie Light on a rpi in the past.
If you know a good and easy way, or have a link to such a way, to install these on Mac / Windows / Ubuntu I think adding it to your readme could help you gain traction outside of people who already have some of the capacities needed to do such edits.
Edit: precised that I'm not looking for a way to install ffmpeg, I was just suggesting that pointing to a way in the README would be an improvement IMHO.
I might add the ffmpeg-static npm package, then no need for system ffmpeg. But that package does not work on raspberry pi, so yeah.. Downloading and installing static ffmpeg builds from ffmpeg.org is pretty easy these days
From skimming through their website, it looks like they target business applications with bigger displays (Health Care, Transportation, Industrial & Packaging, ...) which I would assume are high margin contracts.
So maybe another reason would be that offering lower prices for big displays would reduce profits from these business clients more than it would increase profits from the additional low-margin mass-market volumes.
