Even internally across different teams.
With all the other technologies falling back to json, modern web dev only thinks about SQL as a store for CRUD operations, and not as an integral part of the stack. At least that’s how it seems to me.
If there's a way in which sqlite is underrated by data scientists, it's as a storage format - it's a lot more reliable than passing around csv files.
In your case the rules engine would keep track of the login attempts and automatically expire the records once they are old enough that they won’t trigger any rules.
It boggles my mind that nobody has tried making a JavaScript framework based on them; they would be particularly good for the cases where people get burned in React, such as when there are several pieces of information which go into a computation that updates the UI. Rather than having to implement updates for all the cases the compiler figures out all the ways in which a change could force a UI update and makes it happen.
At the uni where I work there is a lot of work on social robots, many of these could be prototyped with no moving parts, only sensors.
HHAST and LibCST are notable examples in the right direction.
Not so interested in GPGPU, which is something I have more experience with. If you aren't guaranteed to have the latest and greatest hardware, GPGPU isn't always worth the trouble.
Barriers are:
• skills (software, artistic, ...)
• Android, Intel GPU and other bad hardware
My third side project in the queue might involved WebGL but I gotta finish one and make progress on #2 before I start on #3.
Legit. Art for NFTs. Meh. Securing data transfers w peer hosted ledgers and code as unchangeable nft assets. Yes pls.