That is why I thought there should be sound but I missed the point it seems as others have commented something to do with modifying the visuals based on a function.
Thank you Grimm for beating me to the punch. Being working with a company dealing with sensitive data. who are concerned about the security of the npm package system, especially with the recent rc/roc exploits. Have any company actually moved from node to deno successfully in production? Would really appreciate some links and references to stories like that as we are also considering moving node -->>> deno.
> streaming media today is usually encapsulated in small frequent chunks over the same https channels as the rest of the page are delivered as that's what's available in JS/native
>You might think this is trivial -- but SERIAL creates an "owned" (by a certain user) sequence behind the scenes, and so you run into massive headaches if you try to move things around.
Maybe it is because I'm too old, but making id grow by sequence is the way how things 'ought' to be done in the old skool db admin ways. Sequences are great, it allows the db to to maintain two or more sets of incremental ids, comes in very handy when you keeping track of certain invoices that needs to have a certain incremental numbers. By exposing that in the CREATE statement of the table brings transparency, instead of some magical blackbox IDENTITY.
However, it is totally understandable from a developer's perspective that getting to know the sequences is just unneeded headache. ;-)
