I may not see the tree in the forest here. My latest article [Microfrontends - From Zero to Hero](https://www.codeproject.com/Articles/5251628/Microfrontends-From-Zero-to-Hero) was (to my eye) correctly released (in the web section). However, I do not see it on the homepage (not in All, nor in Following or "Web"). Maybe I am missing something? Thanks! :rose: Update: The article was also not in *The Daily Build*. I am quite confused.

> The details of exactly how and when the shutdown will take place are not clear yet, but will be communicated soon, probably tomorrow. I guess it will be tomorrow your time, but 1st of April his time. :rose:

"devs" don't hate JavaScript. Also don't blame someone else for your mistakes (you use a style of JS that was written like 10 years ago; TypeScript is out there since 2012 and you are still not using arrow functions, `let`, strict mode, and other goodies that are there to help you to avoid such mistakes). I am not sure why you "compile" at all when you essentially write ES3 code.

Hehe, thanks for mentioning me - yes and no. Yes, always makes me happy to share my thoughts (otherwise I would not blog), however, no I would rather wish for ASP.NET Core to become a little bit more lightweight (and the tooling to become better). Anyway, I think with VS 2019 (at least after a couple of sessions) it seems that tooling is now definitely on the right track and .NET Core 3 was also a good step in the right direction. Let's see where this is going...

VS Code is just a text editor. No dotnet core or any other distribution is installed. So there is nothing to prompt about.

This is quite old. JS was brought in as a first-class language with Windows 8 (WinRT apps) already. Microsoft just continued it with UWP. UWP does not need to implement the browser control - it is directly using Chakra + Trident. This was one of the reasons why WinJS was formed ([GitHub - winjs/winjs: A UI toolkit for modern browsers](https://github.com/winjs/winjs)) in the first place.

Are we talking relative or absolute here? It makes a huge difference. Example: If, e.g., JS is used 10x as much as X and X is liked by 100% of its developers, while JS is only liked by 20% of their developers, its still twice as popular. Of course you are right, but JS *is* popular and *is* most used. There are only two kinds of programming languages: Those that aren't used and those that people complain about.

While there is certainly a valid point in your statement the overall outcome is utter bs (sorry). Tiobe is really a joke benchmark especially when compared to StackOverflow. Just compare the top spot: Java? JavaScript not even in top 5 (the most used PL running on essentially all devices and platforms)? As every of these benchmarks is a lie (strongly depending on the sources, custom metrics, and attitudes of the creators) a survey across *all* developers seems to be the most reliable indicator about the *popularity* of PL.

We use it actively and are very happy with it. Its Git integration is superb, issue management is top notch (as you know it from TFS 2015) and the CI/CD capabilities are outstanding. Best thing is the Azure integration. We also heavily use the dashboards, test management, private package feeds, and the team collaboration tools (e.g., calendar). All in all you get the product you know already / love (TFS 2015+) in a (even) more modern design and always up-to-date mode incl. even better Azure / cloud integration. On the downside you may have downtimes / unexpected behavior from time to time (e.g., our Azure deployments sometimes "fail" out of no reason, VSTS makes some unstable updates, useful features are removed / redesigned).

How is this determined? Is it random? I ask because I also submitted a code like on the first day of the challenge and never heard back (no confirmation, no error, ...). Anyway congrats!

Protractor seems indeed quite nice - I'll put that on my list for future considerations with any Selenium-based tests. Thanks! And yes, I do agree - JS suffers a lot from the rushed implementation which left no time for in-detail design discussions. Generally (not only talking about initial design choices, but taking all factors into account), I consider it the "best and worst language" available. It's a paradox.

What you describe is rather a community problem than a language problem. Also unless you want to use a task runner you could also just add it your test automation script to your package.json scripts section - problem solved. I'm not opposed to what you wrote (I also think that the JS community is developing new tools for solved problems too often instead of making the existing solutions better), but some parts of it sound a little bit unjustified / unfair to me.

Yes, sure. Any reason for not using constructor initializer? Such direct assignments are where they shine!

Actually, I found it much better than anticipated. The Oculus team really did a great job there :wtf:.

One should always be happy to make such experiences: Seeing how dumb the world is can be sad - but can also make one happy to realize one isn't as stupid as one might feel from time to time. Still frustrating. Be glad they did not make a better impression and you took it - you would have ended up in hell!

That is true. But keep in mind that the Min and Max functions have nothing to do with C# - they are written in C#; yes, but they are part of the LINQ / the .NET Framework. The difference in both is that Max excludes NaN, while Min will take NaN exclusively. You can see the difference here (Min)[^] and here (Max)[^]. That is different to some JS functions (such as everything in Math), which are defined by the same specification as the language.

Nope, it does not imply this. Comparing anything with NaN always yields false as NaN is "not a number" and cannot be compared by definition. Thus it behaves such as if NaN would be the smallest number for Min and excludes NaN for being the largest number in any other set containing numbers. See floating point - What is the rationale for all comparisons returning false for IEEE754 NaN values? - Stack Overflow[^]

This has nothing to do with C#. I refer you to IEEE 754.

Looks awesome! Always wanted to built a cluster with 2^n of single-board computers ... (especially, the RPi Lego cluster was inspiring here: http://www.newrisingmedia.com/all/2012/9/18/engineers-build-supercomputer-using-raspberry-pi-and-lego.html[^])