NXP do own Mifaire technology that is what is used in most door opening scenarii. But, NFC (aka ISO/IEC 1809 & ECMA-340 ) are standardized Open (read Open Standard) solution. Although most chipset do support both, on lot of phones (say Samsung for instance), only NFC is enabled because of royalties disputes between the manufacturer and NXP. Most Mifaire standards are known for security issues. But you know, most people still use pin-based lock which most of them can be oppenned in a bunch of minutes with innexpensive tools. So ... Anyway, in all the application I've designed that required NFC, our customer decided to either drop the feature (because iOS lacked NFC support) or simply dropped the iOS application. In most cases it was a casus belli that ends the iOS device predominancy at the corp.

There is almost only one country that does not use the SI meter system and there is almost only one country that thinks pluto is a planet. USA is sometime ridiculous in its fights. All the rest of the world knows why USA does not want the title of "planet" to be removed from Pluto ... ;-) (Spoiler alert : It is the only planet of the solar system discovered by a US citizen as far as we know) If you plan to call it a planet, what about Eris or Makemake, etc ? Where do we stop ? That is why there were rules defined to set the limit. As a consequence of those rules, Pluto is no more a planet of the solar system but a dwarf planet such as Eris or Makemake ... If you don't like it you can try to change the classification in the next conference. But doing so, we might end up with tens or hundreds of new "planets" because of the removal of rule 3 that block Pluto from beeing a planet. I don't think pupils from the world would be glad of this change when they will have to learn a lot more of planets because of a USA caprice :P

This is too late as WebOS is almost a dead ecosystem : no updates, little applications ... #whatelse WebOS is mainly used on highend LG's TV. The hardware is fine, but the software is ... emmm... is somehow useless : - Bad user experienced browser even if you own a keyboard ... why can't it keep my keyboard layout scheme ?!? No way to get plugin working (a browser plugin can be handy to fix some website issues on big screen). Look at youtube on it to get my point here. - Stupid guide application : open it and try to simply change the chanel from it or go back to the chanel you were coming from ... you will get my comment ;-) - Miracast not stable : anybody tested this at LG's ? - Almost no application : I don't understand why they did not bring Android application compatibility to revive the WebOS world - Bad support of some codec (think TruHD audio or some advanced MKV) I own one of them, I don't regret the hardware (an OLED UHD), but I do regret the software. And WAF is low too on it. People expect updates nohttps://news.slashdot.org/story/18/03/20/1437240/lg-releases-open-sourced-version-of-webos-in-hopes-to-push-it-beyond-tvs-and-smart-refrigerators#wadays (and more specifically when there are bugs).... but LG don't do it. I barelly had 2 or 3 updates in 3 years ... and major bugs are not fixed (such as putting always on the subtitle at anytime, and you can not remove it unless you reset the settings to factory level). Next time, I have to buy a device, I will not buy a WebOS featured one.

Seriously, the only issue I see with Flash beeing deprecated is accessing to some legacy site. I was more concerned with Java applet beeing deprecated, because there are usecases where applet have no replacement solution. For instance, if you need access to smartcard to get decent two form factor identity level for signature. Web crypto is not moving much and not covering those areas AFAIK. And alternative such as WebUSB are limited to Chrome only. Applet were working on all the desktop browsers.

The article is posted by a guy that "have since switched entirely to R" ... even him agrees that Python is not good enough (say versatile if you preffer) to suits his datascientist requirements. Python is nice (it brought some interresting way of doing things & al), but feel like it was designed as a non-mainstream language in mind. Take Java, why did it succeed at the time ? Legacy synthax of the C, rock solid object grounds from SmallTalk but with some lighter ingredients (simple types) to make it "real world" and a by default huge standard library to do what was suitable back in the day. From day one, people with little knowledge could read Java code and understand it. It was simple and enjoyable : you writes, it compiles and run as expected. So long coredumps & heloworld debug sessions ! Actually, I tend to think that all the languages that were succussfull have that same things in common : obvious synthax (reading is cristal clear and writing is not too complex) & nice core library (enjoy it from minute 1). Look at Cobol, even if you have never learn Cobol, you can read it and understand what a program is doing. What does Python offer ? Dedicated synthax, not so versatile library by default, thousands of not no so well seamed libraries ... Sure if you are an expert : you write things with much less fewer lines than say Java or even Cobol. But if you are not an expert, try to read those same lines .... you will end up puzzeled. Python was maybe one of the best contender to phase out Java of its pole position (lots have tried to do it and are now in the limbo of IT history)... but I now don't think, it would be the new king to come. Next contender please...

Actually C# (which name does not sound like it is written ... unless you don't know how a sharp sign is written), was only a reaction to the story known as "RNI vs JNI battle". Sun had a native interface designed called JNI that is way too much complex. And MS decided to make something much more straightforward: RNI. This approach led to the JDirect way and was reused for the PInvoke grounds of .net was a much more easy way to call existing code. MS evey pushed a whole library name Windows Foundation Classes (WFC) which were actually there by default and would let you call all the Direct API to interract with Windows. MS tried to push Sun to accept RNI/JDirect as another way ... but Sun feared balkanization of Java in an "embrace an extend" known strategy from MS. When MS failed to convinced them, they did the more that could to prevent Java to enter in ISO and ECMA standard body (lobying thru known member or country representatives). At a given point of time, they just decided to build their own improved clone solution getting rid at the same time of the DNA, MFC & al stacks ... which could be still used in the "unmanaged" scenario but were no more "gout du jour" de facto. Actually, Java and .net only were competitors at the very beggining of .net when it was IBM stack (WAS+WSAD) vs MS ... once Eclipse was pushed in a smartmove against Sun (hence the name), game was over : full opensource & free stack on oneside ... the only option for MS was to try to follow. But remember where MS was gaining money from at that time ? Windows ! Now, the goal is to move to Azure only as a milking cow ... .net is of no use in that strategy if you compare it to Windows Linux Subsystem. with WSL, you simply run Linux (yes JVM included) directly ! Hence, they can provide direct linux container support. Since about 15years, I've seen no C# running in production outside a Windows host and nobody to MS zealot to even push the idea such an architecture has any point toward the competition. Noting, that at this time we are in a NodeJS trend, that is sucking most of the PHPs ... .net only remain because of the MS ecosystem (tools & solution like sharepoint) and the customer legacies. I don't see quite often new .net application. None of them are public sites. Only internal sites/backend ... Embrace and extend again ?

Since almost 20 years, there are so much "Java Killer" touted languages that died and other that are dead-alive experiencing NDE. Meanwhile, Java is still there and kicking ... even though Oracle is doing so much little for it, even though Google tried to escape from it several time. Obviously, people do not use Java like 5 years before, as the app fundations has evolved ... but evolution means you are alive. Sure there are better features in this or that languages, but aside TypeScript I see little competition for yet another 5 years. Btw, Oracle did not even noticed something called IoT that Java was suited, for instance by repackaging JavaCard & J2ME ecosystem and bringing direct I/O API. Ceylon was nice, but it has "no killer" feature. I've never seen anybody outside a lab test case pushed Ceylon (outside Red Hat of course !). R.I.P. Ceylon ...