If it cures cancer, then I would buy it without the headphone jack (just in case it's needed some day).
But it does not : it's a (ugly) phone that will break because of humidity (lots of places on Earth), and has no headphone jack. It's out.
To its credit : it's a flat screen. (Rounded glass sides be damned)
(I'm not personally interested by wireless charging)
That's not the point (but kudos for spending time altering code, sincerely).
Besides installing the default minimal package (Arch), the most I would do with Kodi is
I'm a dev and I have more interesting things to do in my spare time than trying to understand why some modules cannot be removed physically in a trivial manner. It's not worth it. (I prefer to invest my remaining energy into improving something more interesting, e.g. : Wine)
And my slightly paranoid side tells me allowing plugins when none are needed for my use case is inviting trouble a.k.a entry point.
In the base package, simple useless modules are enabled by default and grayed-out for removal.
The easiest access point for the source code is the original sources.
Apparently you have not idea what you are talking about.
AC, Should I be surprised ? I think not.
I'll try to make it simple, even for you. Old XBMC: small, simple, static, good. New Kodi: big, bloated, dynamic, bad.
I liked the old Kodi/XBMC : a light browsing + viewing media application for my legally obtained/home-made content.
Since that time it became bloated with plugins that are looking for your videos on web sites (imdb & cie), and doing "god knows what".
I tried to disable them all, without success.
I tried to recompile from the source, disabling every useless plugin, but the build process is not very clear (and uses cmake, that I find less user-friendly than a well-made autotools chain).
In the end I gave up and now I simply browse to my file and play with the default media player of my current OS.
It took me a few second to remember what it was about.
Because "humans" will end up saying "yes" to about everything.
Free game.
Free browser.
Similar named application.
There is no way to aid "idiots" who do not keep at least one backup of their relevant data.
Now let's see what the "world" will decide about the missing features.
I don't want to wear Bluetooth headphones 5 to 6 hours a day (noise-cancelling, courtesy of that productivity killer fad of open-offices).
As for the arguments for an SD slot : I want to be able to switch storage to another device easily and quickly and to do backups. Even if built-in storage was not so grossly overpriced, I would still choose SD.
For as long as I remember, most companies only care about security a bit after some critical issue happen. Then they act as it was their chief concern.
Doing that is easy. Both keys need to sign records for a while.
A new KSK is published and as such signed in the zone along with the previous KSK.
This new KSK can automatically accepted as valid by resolvers and when, days later, the old KSK is removed, only the new KSK signature remains (or more accurately: is remade, as it covers all DNSKEY records)
DNSSEC is not that complicated (if you ignore the convoluted NSEC3 chains)
Not to forgot Vulkan ?
(I bought one as a X1 test machine)
Did you mean to use "air rushes in" as an euphemism for "implodes" ?
Nothing will happen.
Public money that may have been invested will be lost.
Irresponsible politicians will deflect the damage on someone else.
People will not learn to ignore unwarranted hype.
And what do you exactly mean by "failed".
With my supernatural powers, I predict it will fail to setup a working supersonic (maglev) train running in a vacuum tube between any two (major) cities in the world.
I specifically said "3 lines for emergencies" : life happens (or death, as the case may be).
Taking more than a a minute is where I draw the line.
But maybe you have a different perception of what construes an emergency.
One man's constant is another man's variable. -- A.J. Perlis
