227 karma · joined January 25, 2016
The biggest difference I have seen is reasonable defaults for a new user. I have lots of friends and coworkers who use Sublime because dropping into vim/emacs is like entering an alternate dimension. They expect to click around and edit text similar like any other program on the computer (which vim lacks) and have a sensible menu system (which emacs lacks). Sublime uses standard system keybindings, so that e.g on a mac Cmd-S saves the current file like you would expect. This is possible to do on both vim/emacs, but not the default. It is really difficult to convince a brand new user that the first step they need to take is opening some random hidden file and customizing their entire editor in a custom configuration language just to get the system default behavior.
It is absolutely infuriating that it fails at even keeping track of the songs you have added to your library. That should be one of the most basic features possible.
Also, saying that NN are easy with a library like tensorflow is akin to saying that Sudoku solvers are easy with Prolog. Of course they are! The library/language does the vast majority of the heavy lifting.
I would absolutely recommend Plex Media Server as a backend. It is very powerful and has great support by the community (see PlexPy). It makes it very easy to store all my media on my home NAS and watch it from any device, even outside of my house. There isn't really anything like this for Kodi that I have found.
For frontends, Plex Media Player is alright but you can also use Kodi with the Plex plugin. This is especially useful since there are no linux builds of Plex Media Player available. I don't really have a preference for one or the other.
[1] https://www.sosy-lab.org/~dbeyer/verification-witnesses/
There is some danger of control over the interface, but the interface does not specify any control operations beyond resetting diagnostic codes. The vulnerabilities in the interface stem from automakers repurposing the protocol, and are model/maker specific.
It seems like another protocol would only help if it defined control mechanisms so that carmakers would stop abusing OBD2.
It's not a set law, but more expressive type systems almost always increase the class of properties that can be "easily" proved in a language. I work on a verification tool for C/C++ programs and we constantly struggle with the languages. Pointer arithmetic and aliasing dramatically complicate any possible analysis, and these problems are only exacerbated at a lower level IR/ASM level.
It's up to you whether you trust it for large products, but so far it has been fairly magical for me.
(I love LaTex, but it is still one of the most frustrating pieces of software ever conceived.)