houseinthewoods

TLDR if you don't want to stick around for my ramble: if you have experience inspecting JSON logs, what's your workflow?

I'm working on a project of a very small scale where monitoring is important. I'm biased to just stick with text files and SSH rather than log software (such as ELK stack or Grafana Loki), so as to not have to learn/install/maintain a heavy tool for my toy needs. I'm also biased towards JSON as a format because I learned programming too late in life to be a Unixy regexy text wizard, though I admire people of that ilk from afar.

For improvised analysis, I'm using jq on the terminal. For less flexible human-readable text summaries, I wrote a Deno script. Ergonomically, jq on the terminal feels lacking. Whoever made jq is doing God's work, to be clear, but I could possibly use a more intuitive language (with an emphasis on more tersely expressing groupings/filters). And independently of using jq or not, the terminal is slow and ephemeral: I would love something sort of like the Acme text editor (where you can build yourself an interface on the fly with text), but without the three-button mouse dependency. Right now I just keep a cheatsheet of jq commands that have been useful. I've been daydreaming about making a local webapp to fulfill this need (that just eval()s Javascript, since it would only ever be local).

Lately I've been yearning to make simple multiplayer Javascript games with as much ease as simple single player games, for the sake of prototyping with friends. I have a sneaking suspicion that for discrete (turns or timers) match-based games, you could have a Firebasey store synchronized between clients and an authoritative server built on top of web sockets, such that the programmer doesn't have to design a new protocol for every game. The reason I don't reach for Firebase immediately is partly due to lock-in/pricing concerns, and because I imagine there would be a simpler tool with the above constraints in mind.

I've stumbled across https://colyseus.io/, but it doesn't look like it quite fits my needs.

Does anyone know of a library out there with the mission of Colyseus, the behavior of Firebase, and simpler than both? Alternatively, has anyone had a pleasant experience building a discrete game with Firebase?

Is is safe to say that 99+% of program bugs are software-related rather than hardware-related bugs?

I should note that I don't have actual experience from Erlang, just docs/talks/etc.

From what I can tell, Erlang treats asynchronous messaging as a language primitive, and to do a synchronous request/response, you send a unique reference, and wait for an ACK back.

I've been fantasizing about what kind of programming language I would write (I don't need to be scolded for hubris, just daydreaming ;) ). It would be statically typed, functional in a pipe-ish way rather than in the pure sense, and have processes/messaging inspired by Erlang.

I'm not sure why I would use asynchronous messages as the foundation rather than synchronous. I'm thinking I would go in a more Promise-y direction, but without Promises explicitly ("message" function calls always return a Union(error,...), and always have either a default or configured timeout).

Are there enough cases for wanting to send a message without knowing at the very least that it was received, in the context of a high-level language?

Thanks in advance for considering this silly question <3