@Das_Geek For sending messages from the chat input, yes. I routinely have a desire to post multiple messages one after the other. I use it for sending commands to SD, primarily !!/watch and !!/blacklist-* commands. In addition, I tend to be ... a bit verbose and regularly write things that are both significantly longer than is permitted in a single post with Markdown formatting, and that need Markdown formatting at the same time. While you can send longer messages, they can't use Markdown.
So, I added code to my personal SE chat adjustments to add an additional "multi-part" button to the chat input interface, along with a counter for the remaining characters in each message. Each message that will be sent is separated by a soft-return. I then can click the "multi-part" button and all the individual messages contained in the chat input textarea are sent one after the other as fast as the chat interface permits (there's throttling, so there's some delay between messages).
As to the individual regexes, those I currently compose by hand and then copy into the chat input textarea and click the "multi-part" button, or compose in the chat input, depending on convenience.
Fairly high on my list of things to do is to modify FIRE so that it will, upon command, create !!/watch and !!/blacklist-* commands with appropriate regexes for the common things we watch/blacklist in a message. That is, however, only at the planning stage at this point.
For example, all of the messages in this batch were composed together and I will be clicking "multipl-part".
@ArtOfCode Oh I believe it. Unfortunately, the main project I work on is legacy PHP code (barf), so I don't use JS enough to really warrant charging for learning TS
It's worse than that. The original developers weren't trained as developers. It was really only intended to be an internal tool for their personal use...then managers heard of it and suddenly it became a high-priority thing that had a bunch of feature requests
And let me tell you, they REALLY took advantage of PHP's loose typing
Can't tell you how many errors I chased down that were caused by random type conversions
@Das_Geek Well, my use of JavaScript grew out of a desire to have things work the way I wanted them. It helped that JavaScript syntax is C-like and similar to many other the languages descended from C, which I already had experience with. If there is something you want changed, you can always jump in and change it. :-) You could start with just small changes for things that almost work the way you want, but not quite.
@Das_Geek As to TypeScript, I'd generally choose not to use it for a userscript. One of the things about userscripts is that people are routinely seeing the source code when installing. A reasonable number of those people will be inspecting the code to verify it's not doing anything nefarious. That's quite a bit easier to do when the code isn't compiled or transformed from what it's originally written in.
In addition, my expectation is that JavaScript is the lower common denominator wrt. what people know. Thus, using Typescript lowers the number of people that are able to easily contribute to a project. Or, at least, that's what I've assumed, so far.
