4 ms·
> There is a trend toward devices that are programmable from user space and the kernel is simply used as a conduit to carry proprietary code and data between us
by matheusmoreira 6y ago
> There is a trend toward devices that are programmable from user space and the kernel is simply used as a conduit to carry proprietary code and data between user space and the device; only the device maker has any real view into what is actually happening inside it.
They just keep coming up with new ways to take away the user's control...
- grawprog 6y agoEvery bit of control taken away from the user is just another avenue that can be used to make money from them. More than that though, it's a way to ensure only select people can be creators, the rest must be delegated to consumers. Computers as they've been for the last few decades has enabled more people to create so many things than any other time in history. For one of the first times in history, the last 30 years or so has allowed any single person on this planet, with enough money for a computer to do amazing things. But, this upsets the status quo. Businesses and I guess the 'powers' for lack of a better word, that profited off society as it was have been threatened and in many cases overturned in a short time. However, they're catching up faster than the average person and through a combination of marketing and just market control, companies are closing hardware platforms faster than what it's taken for most people to begin to utilize all this amazing technology. And it's sad, I know my kids won't have the experience of booting up an atari computer and laughing as they use their first loop to make a bunch of random things appear on their screen over and over. They won't have that experience cobbling computers together from spare parts and getting on the internet for the first time and just being amazed at all the things out there. They'll never get that feeling of really being free to do anything because they have a computer. As a kid, even when everything else was really shitty, being able to just turn on a computer and do anything, whether I was supposed to or not, just really helped me through so much and honestly, I don't know how my life would have turned out if I couldn't have done that. By the time I have kids and they're old enough, unless I buy some retro computers and set it up or something, everything they end up using or seeing will be a locked down device the sole purpose of which is to constantly track them and market to them. The internet is corporate, sanitized, and locked away in these little bubbles provided by platforms. So much has been lost and slowly but surely, the ability to just pick up a computer and create anything we want is being stripped away by hardware vendors and these huge dominating platforms that control every aspect of the computing experience and feel the need to profit off of and dictate everyone's computer use.
- imtringued 6y agoWhy would you want to buy them a retro computer? The reality would look closer to something like Windows S being installed on every PC and you'd have to shell out $2000 for an expensive Windows license to be able to run unsigned applications. Also, the raspberry pi is pretty much the epitome of giving children access to a programmable computer. My personal fear is that people will think that they have to explicitly decide to invest into becoming a software developer by buying developer tools the same way you have to invest into dedicated wood working tools to become a carpenter.
- rowanG077 6y agoIt's already happening. Look at the tablet/mobile market. These devices are easily capable of providing a development environment but it's essentially impossible to use them like that. The IPad Pro being the worst of the worst. It even markets itself as a "real" computer.
- an_opabinia 6y agoIt’s complicated. The drivers are probably riddled with security bugs. For the at-home consumer security through diversity and obscurity is sufficient, their adversary is not the government but malware authors. Malware authors can and do use source code as their starting point for exploits. Especially vendored known-bad code, the main thing that is hiding in these drivers. The manufacturer’s adversary isn’t consumers. It’s not even other small time manufacturers making knockoffs. It’s Google, Microsoft, Amazon and Apple, who are obviously the biggest violators of the spirit, technological and economic, of open source. As soon as you open source your pathetic network driver, if it happens to benchmark the best in some niche way a Google team needs, it’s not like they go and buy your hardware. It’s just some guy who looks at your source and copies-via-rewriting it internally at Google for the hardware they already own and have source access to. Like how are you going to prove that copyright violation happens? People can barely get GPL judgements against random, low money defendants. Look at how many businesses they are in. Google is making WiFi routers. Apple makes its own GPUs now. What will they start with? Open source code. It’s not just the AppGet guy, or some niche feature. It’s literally everything, top to bottom. It is the core of the trillion dollar market cap culture. Nobody has or will ever succeed in a source code copying lawsuit against Google. Apple is going out there and using your shit until they copy it too. Your chips, your wireless stack, your graphics stack, every little thing. They will copy it. Amazon and Microsoft have far flung offices loaded up with people just violating the spirit of open source and legal force of EULAs via copying all day. That is how some guy survives, gets enough work for a year that matters to the bottom line of a multi billion dollar corporation, far out of sight of the compliance culture at HQ. Every giant company does this. Engineers make careers out of copying open source stuff into some other language, making it seem like it’s clean room implemented when of course it is not. They are the adversaries, not users.
- g_p 6y agoOn the point about riddled with bugs, the Qualcomm proprietary drivers absolutely are riddled with them. Even in their closed source and proprietary incarnation, take a skim through Google's monthly android security bulletins, specifically for the Qualcomm closed source components. It's a long time since I did it, but I analysed the frequency and severity of identified vulnerabilities, looking at QCOM open and closed components... The results were fairly easy to predict and guess - the closed components had many more critical vulnerabilities, occuring at a far greater rate. One reason Qualcomm wants to keep these closed is because of IP and the fact they often buy in third party IP (especially in imaging for example). The other reason is because they sell their proprietary userspace drivers to manufacturers as a "board support package", and they need to select the length of time they want updates for. In the old days before treble, when Google changed the HAL every release of android, this meant not being able to run using the old binaries, or having to write shim drivers to wrap old (closed, but exported) function calls with the new expected ones. Post-Treble, the Swiss cheese nature of their driver code means OEMs need these updates to avoid their phones being compromised, ensuring further recurring revenue. The best thing that could happen for Android security would be the opening of the entire Qualcomm userspace drivers, so they could be maintained by some competent developers, and eventually unified into an equivalent project akin to the mainline kernel, so that common code could be shared between generations, and therefore security patches can be applied to past devices' components. And then the next best thing would be for QCOM to open source their modem and RIL (Radio interface layer), because both of those are vulnerability ridden messes of legacy code - I believe their radio baseband firmware is compiled using an utterly ancient compiler still, and lacks even basic secure coding principles. Occasionally you'll see some black box vulnerability research looking into these basebands and they tend to validate the above findings quite nicely.