Thanks! More than what the application does, its value lies in where it saves the client money. A big part of this is eliminating the need to buy new tools when one simply doens't know where a tool is.
Curious because when sending a .webm video from an Android device to a iOS device, the video file was transcoded on WhatsApp servers and then delivered to the iOS device as H264/mp4 (since iOS can not play .webm files)
I googled for "spotify helper 100 cpu" and there seem to be tons of forum threads of people complaining about it... but the community forum insists that I register an account to even view the threads linked by Google, so, um, maybe I'll just go back to sheer piracy, so I can use open source software that doesn't break my computer.
> There’s a package called isArray that has 880,000 downloads a day, and 18 million downloads in February of 2016. It has 72 dependent NPM packages. Here’s it’s entire 1 line of code: return toString.call(arr) == '[object Array]';
How anyone can deal with JavaScript for more than 5 minutes is absolutely beyond me
Sensationalist stuff. isArray doesn't depend on anything, but lots of other packages depend on it. Why? Because it's actually kind of hard to tell the difference between an array of things and an object with integer keys. The Array.isArray function wasn't added to the language until ES5, so you need a way to shim older tests.
If you're writing only for modern browsers, you don't need it (if you actually visit the code in question you'll see it defaults to Array.isArray - in that sense, it's a polyfill or whatever). But if your code might run on old browsers, it can't hurt to have it, and it cleanly encapsulates a trick that you no longer have to remember the syntax for.
The day there is a Laptop with specs comparable to the Apple MBP (in terms of battery life, build quality, screen resolution etc.) that runs a major Linux distro out of the box with full hardware support and no pain in the ass, i am switching.
I don't think Exchange uses any interface other than LDAP to hit Active Directory, so I'd think there's at least a fighting chance that the AD requirement could be satisfied by other LDAP servers.
I can't speak to the IIS integration anymore-- I quit following that at a low level back in the Exchange '03 timeframe. I would suspect there's a clear line between IIS and Exchange, however, that could be used to facilitate an adapter layer for a flexible HTTP(S) server like nginx. The SMTP, POP, and IMAP services, though, would probably involve a lot of re-implementation.
