So whereas biometrics might replace a traditional "password" - we need more systems which aren't vulnerable to the type of 1.8-billion-password-stealing-Russian-problems we see all over the place. I have been a big fan of much of the two-factor stuff, and some of the hashing schemes out there. It will be interesting to see what kind of other solutions could exist - though I don't think anything "static" like biometrics gets us anywhere.
I'd include links - but there are a lot of them depending on what you want (Linux, PAM, Apache, Andoird, iOS, etc) - So, "Just Google it!"
I am very productive with Perl, and I like it. However, with the surge in things using Python, I find myself "needing" to know it. So where I may have a script to write, and I'm more comfortable doing it in Perl, I actually write it in Python just to learn/exercise the (needed) skills. So - even where I'm "productive, comfortable, knowledgeable and not missing features" with Perl, that's why I'd still do it in Python.
That's why at least for me - it's demise is a self-fulfilling prophecy.
(Sorry, had to do it)
Because of the lack of new projects being done with it. I can't remember the last time a [major] web site or web framework was done in Perl. It seems like the whole "ruby on rails" fad is over, but even things like Django (Python),
Well what about as your standard workhorse for script kiddies? Seems like Python has cleaned Perl's clock. For me - I've been a die-hard Perl guy for 10 years. The past couple years, I've worked with many different technologies such as 2d/3d CAD projects, Blender (3d adnimation), Inkscape (2d illustration), GNU Radio, OpenStack (cloud), and even Amazon AWS [libraries]. You know what was the striking commonality to all of these? They were done in Python.
Tiny exception was in the last case (above - Amazon AWS libraries) had several different language options but had *NO* Perl options whatsoever. So the language that was once so revolutionary because of the abundance of CPAN libraries available for it starts to not have newer libraries built/ported to it. Furthermore, binding stuff to Perl can be difficult. So much so that most modern distros will make their own "Perl library" [RPMs] - and one of the reasons being is that a standard CPAN module installation won't work due to problems linking/binding/building across all these different environments with very different prerequisites. Most third party Python stuff I have acquired is most often "native python", and works across all types of exotic platforms - even on iOS and Google App Engine.
As for me - I had to switch away from my beloved Perl over to Python for the aforementioned reasons. There are still several things I miss very much - the abilities to so easily spawn and fork "helper" processes, the ease it which it integrates regular expressions, how it can manipulate files, etc. All these things *can* be done with Python, they're just integrated into Perl much better IMHO.
It seems like Perl 6 was supposed to use something similar to Java's "JVM" microcode interpreter. This could have been a possibility to run Perl in embedded sandbox-type environments (like parking meters and smartphones), but it never happened.
So, I do believe Perl is dead. I miss it for what it was, what it is, and what might have been!
Is it because I am racist, or have a toxic environment, or am biased? No. The reality is that in my entire career, I have only received a single black candidate. (That I know of - some may have failed to get past the resume screening, without having known what their race was).
As for women - we hire them - but a disproportionally smaller percentage of out applicants are women - so that explains the smaller hiring numbers. It's not like we get billions if candidates for the super-skilled positions I hire for. It's not like we have a colossal pool of qualified candidates from which we just pluck-out all the white males. It's a small pool of qualified applicants.
(BTW That one guy? We made him an offer - but his current employer countered it and we lost him. )
Let me count the issues here:
1. This device seems to "do a bit better" than conventional treatments. How much better? A lot or almost none at all?
3. When you eat - it can take (minimum 20 minutes, maximum much longer) for the carbohydrates you eat to be broken down into glucose, detectable by a CGM. This can be MUCH longer for fatty foods which can often result in the liver secreting Glucose. Commercially available insulin can take up to 2 ours to reach peak affect. This means that by the time you eat and your CGM begins to notice it - it is too late to take any meaningful affect and keep your blood sugar under reasonabily control (for the next several ours).
4. There are devices now (by Medtronic) that will shut OFF your Insulin supply if your CGM says your blood glucose is too low - but aside from problems with poor CGM readings, this could be too late. (Furthermore, it's a minor firmware tweak on an existing pump). 5. There have been other project out there for years in which pumps can inject glucogon when BG levels are low. In fact, I credit my 8 year-old daughter for first coming up with the idea a few years ago - at least that't the first time that I personally heard it! Either way - no novily there.
So in short - nothing spectacular here, but I bet if they made a snazzy "solar roadways" type video, made it on a 3D printer and accepted BitCoins for payments, they'd monopolize the front-page headlines for weeks to come!