3 ms·

Absolutely frontend stuff will burn you out as an individual, it's too high churn and low ROI. Most DBs have triggers now, generally implemented in ways which c

Absolutely frontend stuff will burn you out as an individual, it's too high churn and low ROI. Most DBs have triggers now, generally implemented in ways which can generate a text-stream to be easily parsed. While introspection suffers in a heterogeneous environment, modern Unix does give you free event generation by subsystem (eg. inotify), lists of subscribers (lsof), configurable kernel-level instrumentation if you need more, etc. so it's not all bad. IMHO much of the local maxima are artifacts of too much low-level programming and not enough higher-level codebases. Programmers eschewing the positive aspects of higher level languages and sticking their head in the sand about C-grade portability and nominal efficiency, at least in part. For funds, begin as suggested: define the problem, make a case either in market or in losses, and start pitching.

zackmorris 4y ago
Hey you're right, I agree about problems coming from focusing on the wrong level of abstraction, and thanks for your clarity. I was working on a project and had to install a file watcher for Node.js because the process inside Docker wasn't seeing the file changes from the IDE on the host for some reason, or using too much CPU, can't quite remember. I think it was called Watchman: https://facebook.github.io/watchman/ https://facebook.github.io/watchman/ There are others: https://stackoverflow.com/questions/13695046/watch-a-folder-for-changes-using-node-js-and-print-file-paths-when-they-are-cha https://stackoverflow.com/questions/13695046/watch-a-folder-... They use inotify when possible, but fall back to other methods, including full scan (recursive? bisect? can't remember the term) of the directory and file timestamps. I hadn't put it together that it could be used to implement reactive programming. But I have made toy workflows with folder watchers using AppleScript on macOS. For funding, maybe I could try Reddit or something. I'm realizing that many of my problems come from spending too much time in my own head and not keeping up with trends.

zackmorris 4y ago

Hey you're right, I agree about problems coming from focusing on the wrong level of abstraction, and thanks for your clarity. I was working on a project and had to install a file watcher for Node.js because the process inside Docker wasn't seeing the file changes from the IDE on the host for some reason, or using too much CPU, can't quite remember. I think it was called Watchman: https://facebook.github.io/watchman/ https://facebook.github.io/watchman/ There are others: https://stackoverflow.com/questions/13695046/watch-a-folder-for-changes-using-node-js-and-print-file-paths-when-they-are-cha https://stackoverflow.com/questions/13695046/watch-a-folder-... They use inotify when possible, but fall back to other methods, including full scan (recursive? bisect? can't remember the term) of the directory and file timestamps. I hadn't put it together that it could be used to implement reactive programming. But I have made toy workflows with folder watchers using AppleScript on macOS. For funding, maybe I could try Reddit or something. I'm realizing that many of my problems come from spending too much time in my own head and not keeping up with trends.