Comments by "Manuell" (@manuell3505) on "TechAltar" channel.

@bracco23 - They always say that... Problem: smartphones are crippled computers. The user I/O is hijacked by a high-level softwarestack called "ecosystem" Ever wondered why USB-keyboards and mice don't work with smartphones but do with a $5 single board computer? Or why smartphones ONLY will accept their internal storage volume as initial boot device? Or a question as another example: what is a smartphone boot-ROM? Read only? Then how is it posibble to overwrite it? Luckily at least, I didn't notice people arguing this with terrorism, pedophiles and computer-users being a treat to themselves by nature, which ofcourse all requires an enclosed user-level operating environment that fully consists of software and lacks any option for alternatives.
5
Beware of ecosystems. They aren't "open" but a narration of user abilities and a infrastructure that demands personal identification for anything that involves profit. Proof of that: try to download and play 1 mp3 file on your Android or iOS device's local storage. Now compare the requirements to do this 20 years ago on a computer with capabilities that were far less than a cheap smartphone of today... There's a giant difference and nobody seems to have noticed it. But where are our admin permissions? Face the commercial playground. Computers today are way beyond this...
3
@bracco23 Again: they always say that. PC's and smartphones both are personal computers. While a PC runs all hardware-compatible binary code, the smartphone only runs a "Android kernel" with "apps". You don't notice an at least a little bit suspicious problem here? Without it, I could play Counterstrike and Unreal in a emulated 32bit/386 windows XP on my phone, booted from SD-card. It works on ALL PC's (and even most Mac's) with sufficient resources and a alternative boot device option. It works on not a single smartphone.
2
@tarkfarhen3870 Blablabla. Have any substance? (Except your biased and childish political bullshit) You're internet pollution...
2
@igorgiuseppe1862 - Instruction sets can be emulated. You need a emulated x86 system on your ARM hardware. This points to the same problem: hardware-compatibility is only about hardware. Software declines that barrier. It can manifest the required computing logic by itself, abstracted from the physical hardware, at the cost of a defined amount of resources.
2
@DopePhizh Android is open source. But the hardware capable of compiling, installing and running this source, controlled by the owner of the system, without the need of anything else doesn't exist.
2
@DopePhizh I think the problem can be found at where the Android kernel is not a Linux kernel, while it lacks a real technical requirement to be different. It's why Ubuntu Phone never made it, at least not while staying "Linux" reasonably. Canonical required a dirty deal with hardware manufacturers and a few crucial proprietary components to keep Debian, Slack and all the others away. As a OSS-supporting company, you can't sell that. So they didn't, resulting in distrust of all manufacturers by this "infiltration attempt". No production deal for any pure Linux-based system. It makes too much possible...
2