I do understand why some don't like JS/TS... and I really do get it.
That said, I think a lot of complaints are from a combination of ignorance and conflating the DOM with the language.
As to numbers, it's an IEEE 64-bit floating point, the precision issues are there in any language if you use float64 for all number logic... Math.round() against any number that fits in a safe integer range will work roughly the same as int32 will, though max safe integer is around 52 bits, not 32 or 64.
Coersion issues often come from sloppy/jr devs who don't understand how it works, or even if/when you should rely on it.
Nice, this and tabbed view are preferred for doc/comment edits in apps for me these days. I did some work to adapt a Medium-like editor that loads/saves as markdown through some filters, but that was a lot of painful work.
One suggestion, for those using this, would be to use an async loader so that it's not loaded until it's needed in your application. Markdown libraries tend to be relatively big.
I think a lot of it is the time involved... I'm not at all familiar with the codebase, and the backend is iirc Ruby.
May be worth taking a loot at a refresh for a few things... I've often thought it would be cool to rewrite as-is to node (maybe deno?) and from there work on feature enhancements.
I am someone with a real name that is relatively common first+last name, iirc about 1:50000 or so in the US, there are lots Michael Ryan's out there, I've met a couple unrelated to me. And a handle (tracker1, azTracker1, xTracker1) on various social media, and a *lot* of them are not me.
While interesting at best, this is dangerous at worst. As long as you're only testing for actual indicated names on other social platforms, then this *might* be okay. If you want real verification, most of them have some sort of OAuth interface that you can use for only name/email identification matching. If you're using a self-registered interface for what is "public" you may be violating TOS (which can be interpreted as a crime in the US.
I'm not the one who down-voted, but can completely understand why one would.
edit: Just an example of how mangled things get, the main image/job title is not me, but other pieces of information are me. https://rocketreach.co/michael-ryan-email_25502930
I was on vacation this past week, so wasn't active, but generally do a sweep at *least* once a day of all new posts... on busier days, I tend to concentrate on those that look spammy by title, have comments or are downvoted...
If you don't want to downvote a comment is usually the best option for getting attention. While it's not as quick/active as it could be, there are usually not *that* many new posts each day.
And, no, I don't always delete downvoted posts... which is again why even if downvoting, a comment helps understanding why it was downvoted.
Interresting... The following might be slightly cleaner: ``` import {App, Static, Router, Get, Post, Put, Delete, Patch} from 'react-express'; ```