I feel like calling this a downside implies there's an alternative, but there's no way that `innerHtml`'s behavior could be changed. There are a lot of valid reasons for arbitrary HTML to be set, and changing that would break so many things.
There could be a better name for it? like `innerSanitizedHTML` or something, that makes it clear what the difference between the two calls are. There is nothing in the wording of setHTML that makes it clear it sanitizes where innerHTML doesn't.
They are not referring to a WhatsApp specific UX issue, but to the cognitive load of having multiple apps that you have to remember who to use which for, and their different interfaces.
Not the author, but I have heard the criticism that it is trying to monopolize blogging. Oh, and it is hosting "white-supremacist, neo-Confederate, and explicitly Nazi" content. [1]
NTA but there are some people who see Substack as an enabler / platformer of the ultra-right. I don't personally feel this way since I've seen just as many lefty things hosted there. Seems like a fairly neutral platform.
I do dislike Substack for other reasons though, but they have more to do with disliking content aggregators and seeing them as parasites. Substack, and (worse) Medium are magazines with unpaid or under-paid writers. They bait people in with ease-of-use and free hosting and then paywall their content and if they allow author monetization they take a very large cut. The general trend on all these platforms is progressive enshittification.
Patreon remains probably the least objectionable one.
> they allow author monetization they take a very large cut
It could definitely change in the future, but Substack's cut seems to be 10% minus credit card fees. That definitely seems pretty reasonable in comparison to other platforms (Most app stores tend to be around 30%.)
Maybe there are other creator-hostile elements, but most of the creators I follow that have started on or switched to Substack don't seem to have an adversarial relationship with it.
ES6 modules make it straightforward to reform great piles of unstructured JS hackery into hierarchical dependency-controlled units for which you can actually reliably draw a block diagram. Hmm, or maybe get Claude to draw it for you ...
The article really should be "Everything Is Chrome + Safari", the "Firefox on the brink?"[1] article even shows that Safari has ~37% market share (Although the underlying site[2] currently shows me ~34%.)
I think the format here is pretty brilliant, because you can look at what's outside of the brackets to try to fill in a reasonable answer. The Brady Bunch one was followed by ]orian, which made for a useful hint.
But there are few of those that are so cleanly nested. I know where it’s going, but the requirement to solve every individual step slows you down.
Of course, I’ve been a steady cruciverbalist for 35+ years, so learning a new puzzle style will always take a while. Do agree that until OP settles into a smoother rhythm, adding the length of the solvable answers would help.
reply