Same reason I might use tippy.js for popup boxes. I know I could make it myself, and make it just as well as the tippy authors have designed it, but why waste my time doing that when I know they've already thought through all of the problems that I can't even expect until I'm already in the thick of it?
Hey! I want to formally apologize -- the company I heard presenting had a name very, very similar to yours. Definitely was not the same company. Unfortunately it's past the 2 hour mark to delete comments on HN, but consider this my retraction of what I said above. Really sorry about the mix up, and what you have going here seems very impressive. Definitely seems like a fantastic attitude towards workers' health and happiness.
Hey all! I had the chance to see everyone from Fly.io at Hack Arizona -- they gave a presentation before the hackathon began. That presentation displayed the worst work/life balance I think I've ever seen. Every trope was there: "we're not coworkers, we're family", "our developers love to work, they do it out of love", virtue signaling, etc, etc. The whole shebang. Just my two cents, but I really feel that this is a company to avoid.
I wouldn't really call APL/J/K "lost" (or "dead", or "useless", or...). There's an active community on Reddit and there's a pretty active circle of APL'ers on Twitter. It wasn't ever a super mainstream language, but it's definitely not lost its appeal -- maybe even as a fun hobbyists' language.
For memorizing lines? Chew a piece of gum. I've found that it takes the emphasis away from my location in my mind and places some emphasis and connection with the feeling of chewing gum. For extra points, alternate different flavors for different sets of things to memorize.
* Did every OS treat clicking in the blank space above and below the scroll bar the same, like this website seems to suggest?
And,
* Why'd early versions of Apple's OS have the buttons on the bottom? What was the rationale & why'd they give in and move them to the top? I kind of like the bottom buttons.
Right now, the system works on a black and white "I was satisfied with this answer"/"I wasn't satisfied with this answer". If too many users note that they were continually unsatisfied with a particular answerer's answers, then I'm planning on handling that issue myself.
Lyfevest seems more geared towards enterprises, and the subscription will have to be EXPENSIVE to justify all-you-can-post questions. I don't think that's friendly to hobbyists and students -- which both groups that I want Immutable Coffee to be open for.
I've been doing it manually: looking at resumes, code samples, and asking sample questions to judge for myself. Not sure there's any automated way to do that that will work any better.