If journals are going to rehash Facebook blah word by word, syllable by syllable, then I expect free endorsements to alternatives. It's a small public service in exchange for the free content and clicks.
I tried putting in verified users and they were all "probably bots". By definition is that not the only type of user publicly acknowledged as "not a bot"?
Not married to the syntax, just wanted to highlight the absence of this syntax form. The syntax used was mainly meant to mirror the existing Rust pattern syntax.
As for partial matching, other languages give warnings or errors if a pattern doesn't cover all cases.
There is a whole style of programming dedicated to tail-recursion called Continuation Passing Style. It is not usually useful for programmers directly to use, because it is so complicated to read/write, but it is very useful for compilers to generate code in CPS.
If you wanted to, for example, write a new experimental functional language and reuse part of the Rust compiler to sanity check and generate the executable, then tail-recursion would be really important.
Similarly, if you create something like a parser generator and don't have tail recursion optimization, then you are going to run out of stack space before being able to parse stuff. So, there are lots of practical applications that depend on this feature too.
There is something disconcerting to me about titles containing the author's name. I don't care if you are famous or not, that format is for tweets, not full articles.
So he thinks everyone's potential kids should commit suicide, and recommends preempting that choice. Why do philosophers have to be so damn arrogant and grandiose about everything they propose?
Keyword there I think is "runs of phrasing content". That means that you can "nest" different tags but not those of the same tag. The nesting <b> inside <b> like op is causing the parser to ignore the depth of nesting of <b> elements and just closes the bold content on first </b>.
Some html elements are containers, others aren't. <b> can only contain text, so there is a bunch of ignored <b>'s and </b>'s. Then comes the <em> which is followed by an unexpected closing </b>. Use div's or span's if you want to put something inside and have nesting work normally.
This isn't climate science, we could see the economic effect immediately. That is simple enough for most people to draw a connection. I think the problem is more that some people want to hurt the US IT industry for political gain.
I used to do development for a company with mainly government clients. The director of Operations (devops), had a policy of taking down the site every week for "maintenance" because it makes the customers trust you more.
It's like the story of the janitors that were too good: the executives decide that the office is clean enough, so they cut the budget and then everythings a mess... that's just how bureaucracy works at the high level.