Could EU force hardware manufacturers to make working drivers for Linux?(old.reddit.com)
old.reddit.com
Could EU force hardware manufacturers to make working drivers for Linux?
https://old.reddit.com/r/linux/comments/16wv53f/could_the_eu_force_hardware_manufacturers_to_make/
313 comments
I like this idea because it’s incredibly American. If we’re going to go full on free-market, we might as well live up to those principles.
There is precedent for this idea, in 1948 the Supreme Court forced the film studios to give up exhibition (theaters) with the paramount decision. This enabled the rise of independent film, and audiences benefited from more choice.
If you try to do this legislatively the Apples and the NVidias of the world will hire an army of lobbyists and storm Capitol Hill. But it might be to their benefit. After the breakup of Standard Oil, John Rockefeller became richer because competition forced out the less efficient portions of his old business from the market.
It’s true that it could temporarily degrade the user experience of some people, but that’s a small price to pay. People who give up liberty for safety, deserve neither liberty nor safety.
There is precedent for this idea, in 1948 the Supreme Court forced the film studios to give up exhibition (theaters) with the paramount decision. This enabled the rise of independent film, and audiences benefited from more choice.
If you try to do this legislatively the Apples and the NVidias of the world will hire an army of lobbyists and storm Capitol Hill. But it might be to their benefit. After the breakup of Standard Oil, John Rockefeller became richer because competition forced out the less efficient portions of his old business from the market.
It’s true that it could temporarily degrade the user experience of some people, but that’s a small price to pay. People who give up liberty for safety, deserve neither liberty nor safety.
There are so many flawed analogies here it’s hard to know where to start. How will it make my everyday experience better as an Apple customer without the integration of software and hardware between my Mac, iPads Watch, Airpods and phone?
Windows laptops are worse in every vector than MacBooks. No consumer is asking for this.
So you want to degrade the user experience for “freedom” by giving the government more power???
Windows laptops are worse in every vector than MacBooks. No consumer is asking for this.
So you want to degrade the user experience for “freedom” by giving the government more power???
> How will it make my everyday experience better as an Apple customer without the integration
Perhaps you should ask the inverse - how good would your experience with Apple be, if there were no open standards paid for by someone else, and fought for by someone else?
You wouldn't even have GPS and navigation. You would not have HTML or the open web. Before we fought for video codecs compatibility you could not even get a video that was recorded on a Device A to reliably play on Device B. The phone would be almost useless.
The people that argue this, they only take from the commons and never give back.
Perhaps you should ask the inverse - how good would your experience with Apple be, if there were no open standards paid for by someone else, and fought for by someone else?
You wouldn't even have GPS and navigation. You would not have HTML or the open web. Before we fought for video codecs compatibility you could not even get a video that was recorded on a Device A to reliably play on Device B. The phone would be almost useless.
The people that argue this, they only take from the commons and never give back.
I think you should look up the history of h.264 and see who is in the patent pool…
You should go even further and check the video playback experience on apple machines, when divx was all the rage and apple had just a sorrenson video 3. And yeah, full-screen playback was a qt pro feature, paid extra.
Or you can go even further back when Microsoft was caught stealing QT code because they couldn’t do video competently themselves and Apple could (circa 1995).
And every Mac geek knew how to work around it either via free third party software or just using AppleScript
https://osxdaily.com/2007/01/30/play-quicktime-movies-full-s...
And every Mac geek knew how to work around it either via free third party software or just using AppleScript
https://osxdaily.com/2007/01/30/play-quicktime-movies-full-s...
Nah, they didn't, when Jobs said someone has stealing his code, he meant that someone did something similar. Like "stealing his ideas".
Also in 90's, there was no applescript support on macos classic qt, and third party players like vlc didn't exist yet either (not that they ever ran on classic). I know, I was mac user back then and I remember.
Also in 90's, there was no applescript support on macos classic qt, and third party players like vlc didn't exist yet either (not that they ever ran on classic). I know, I was mac user back then and I remember.
No, Microsoft actually stole QuickTime code.
https://thisdayintechhistory.com/12/06/apple-sues-over-quick...
Someone doesn’t know their history…
Also, the look and feel lawsuit happened before Jobs came back and within a few months after he came back, he settled all of the claims.
Your memory is spotty
https://thisdayintechhistory.com/12/06/apple-sues-over-quick...
Someone doesn’t know their history…
Also, the look and feel lawsuit happened before Jobs came back and within a few months after he came back, he settled all of the claims.
Your memory is spotty
I see you don't know how presumption of innocence works. I'm not a fan of Microsoft, but the same applies to them as anyone else.
You can be sued for anything, whether true or not. In the court, it must be proven that you did what you are sued for. So it is either proven, or not, and then the court issues the verdict. If it is not, like in Microsoft's case, they are still innocent. It does not matter whether it was impossible to prove or Apple stopped pursing the case; the court said they are guilty. If you continue say they did it, it is a defamation.
Even without regarding the above, the case was really shaky. Microsoft using the same vendor through a chain (via Intel) as Apple does not mean they are "stealing". That vendor might learn something from working with them, but that does not imply what you said. Nevermind, that Video for Windows had somewhat different scope (video subsystem), than Quicktime (multimedia subsystem). For Apple, it was simply a negotiation card.
Look & feel lawsuit was literally the oh noes, they do similar thing as we do case.
You can be sued for anything, whether true or not. In the court, it must be proven that you did what you are sued for. So it is either proven, or not, and then the court issues the verdict. If it is not, like in Microsoft's case, they are still innocent. It does not matter whether it was impossible to prove or Apple stopped pursing the case; the court said they are guilty. If you continue say they did it, it is a defamation.
Even without regarding the above, the case was really shaky. Microsoft using the same vendor through a chain (via Intel) as Apple does not mean they are "stealing". That vendor might learn something from working with them, but that does not imply what you said. Nevermind, that Video for Windows had somewhat different scope (video subsystem), than Quicktime (multimedia subsystem). For Apple, it was simply a negotiation card.
Look & feel lawsuit was literally the oh noes, they do similar thing as we do case.
Again you don’t know your history. Microsoft paid Apple a settlement fee as part of the overarching deal they made with Apple back in 1997.
The 1997 settlement was about making peace between these two companies. It had nothing to do with the 1994 lawsuit.
Btw, the result was that "Apple cannot get patent-like protection for the idea of a graphical user interface, or the idea of a desktop metaphor [under copyright law].."
If you want to know how it looks when Microsoft did stole something, look at Stacker. Entirely different evidence, entirely different result, including entirely punishment.
Btw, the result was that "Apple cannot get patent-like protection for the idea of a graphical user interface, or the idea of a desktop metaphor [under copyright law].."
If you want to know how it looks when Microsoft did stole something, look at Stacker. Entirely different evidence, entirely different result, including entirely punishment.
I just notice you said AppleScript didn’t exist then. It was introduced in 1993.
I corrected myself; being introduced in 1993 does not mean it was supported by all the Apple utilities since start, at once.
Also, it is not an user friendly solution. Do you know, how it really worked? Mac users were sharing QT pro keys. Most had zero interest in the pro features, except full screen playback.
It took Apple almost two decades to fix this.
Also, it is not an user friendly solution. Do you know, how it really worked? Mac users were sharing QT pro keys. Most had zero interest in the pro features, except full screen playback.
It took Apple almost two decades to fix this.
It was very well supported. I had a Mac LC II back then.
And your previous comments about the history of Apple makes me think that your memory or experience during that time is spotty.
And your previous comments about the history of Apple makes me think that your memory or experience during that time is spotty.
Well supported? Outside of Apple-only SVQ3 and QDM2, it was deserted wasteland. All the videos you could play on PC, it was pita on a Mac. Even if you eventually had divx codec, you had to convert avis to movs.
But it is already established in this thread by others, that you have your own, RDF-like experience of what happened; no point in trying to discuss any further.
But it is already established in this thread by others, that you have your own, RDF-like experience of what happened; no point in trying to discuss any further.
> * How will it make my everyday experience better as an Apple customer without the integration of software and hardware between my Mac, iPads Watch, Airpods and phone?*
"Open Standards" - There is no reason that your Mac or iPhone should only work with other Apple products through closed and proprietary standards. With adoption of open standards, all devices (irrespective of their manufacturer) can offer a decent integrated experience.
"Open Standards" - There is no reason that your Mac or iPhone should only work with other Apple products through closed and proprietary standards. With adoption of open standards, all devices (irrespective of their manufacturer) can offer a decent integrated experience.
It is a great idea, but with a caveat: communism is a great idea too, and pretty much in the same sense. I can say that about most of the propositions in this thread.
I, as a user (and a vim-user, may I add), would like it very much if all the software and hardware in the world would be fully open, customizable, community-maintained. I, as a manufacturer, am less keen on that idea. So, to make it happen, every manufacturer has to be forced to make that happen. So, literally, we are stepping farther from the open market and killing some personal freedom under a promise of a bright happy future.
And the realness of that promise is as questionable, as the means necessary to achieve the goal. As I've said, personally, I'm very excited about that promise. But it really is just a promise, and if it can be fulfilled is a very, very big question.
Ultimately, nobody really sells hardware or software. Everybody sells user-experience. It is very obvious in Apple's case, but it is always true. It's easy to forget that when you are choosing the cheapest light bulbs on the market, because the user-experience of having electric light in your house has been sold to you so long ago, there are so many basically identical products that the only apparent difference to you is the price. Now you perceive GPUs (or bluetooth, or whatever) as light bulbs. But at some point selling a GPU or a light bulb was quite similar to selling a novel iSomething. The seller had to explain to you, not so much what iSomething is, but how iSomething makes your life better. And if the technology that makes this promise of the user-experience a reality is hardware, software or just exceptional marketing — really is just details.
So, as much as I hate that my fitness-watch is basically a spying device and I don't even own the data it produces (and I mean, I really hate that), I don't feel like forcing Garmin to open-source the firmware is the right thing to do. Maybe I would support some more forceful moves to make the generated data my property, but even here the line is blurry. But forcing them (and better think: you, as a manufacturer) to make something other than you wanted to make — …why the fuck should I? Who decides what is that common standard I don't want in my product, but I have to, to be legally allowed to sell that? I think, I just like the idea of personal freedom a bit too much to support that. I'd much prefer Garmin just losing to competition that chooses open firmware, than legally forcing them to produce anything they didn't want to produce.
I, as a user (and a vim-user, may I add), would like it very much if all the software and hardware in the world would be fully open, customizable, community-maintained. I, as a manufacturer, am less keen on that idea. So, to make it happen, every manufacturer has to be forced to make that happen. So, literally, we are stepping farther from the open market and killing some personal freedom under a promise of a bright happy future.
And the realness of that promise is as questionable, as the means necessary to achieve the goal. As I've said, personally, I'm very excited about that promise. But it really is just a promise, and if it can be fulfilled is a very, very big question.
Ultimately, nobody really sells hardware or software. Everybody sells user-experience. It is very obvious in Apple's case, but it is always true. It's easy to forget that when you are choosing the cheapest light bulbs on the market, because the user-experience of having electric light in your house has been sold to you so long ago, there are so many basically identical products that the only apparent difference to you is the price. Now you perceive GPUs (or bluetooth, or whatever) as light bulbs. But at some point selling a GPU or a light bulb was quite similar to selling a novel iSomething. The seller had to explain to you, not so much what iSomething is, but how iSomething makes your life better. And if the technology that makes this promise of the user-experience a reality is hardware, software or just exceptional marketing — really is just details.
So, as much as I hate that my fitness-watch is basically a spying device and I don't even own the data it produces (and I mean, I really hate that), I don't feel like forcing Garmin to open-source the firmware is the right thing to do. Maybe I would support some more forceful moves to make the generated data my property, but even here the line is blurry. But forcing them (and better think: you, as a manufacturer) to make something other than you wanted to make — …why the fuck should I? Who decides what is that common standard I don't want in my product, but I have to, to be legally allowed to sell that? I think, I just like the idea of personal freedom a bit too much to support that. I'd much prefer Garmin just losing to competition that chooses open firmware, than legally forcing them to produce anything they didn't want to produce.
> ... literally, we are stepping farther from the open market and killing some personal freedom...
No, we are democratically balancing consumer rights with the rights of entrepreneurs to make money. Consumers need the right to repair and not be limited with closed, proprietary standards. That entrepreneurs may take take a slight hit on their profit due to this is acceptable as protecting the consumer enhances the well being of the overall society that both entrepreneurs and the consumers are part of. (And note that right to repair and open standards can also foster more competition in the "free market" and reduce monopolistic abuses - so it is really a win-win for both sides).
No, we are democratically balancing consumer rights with the rights of entrepreneurs to make money. Consumers need the right to repair and not be limited with closed, proprietary standards. That entrepreneurs may take take a slight hit on their profit due to this is acceptable as protecting the consumer enhances the well being of the overall society that both entrepreneurs and the consumers are part of. (And note that right to repair and open standards can also foster more competition in the "free market" and reduce monopolistic abuses - so it is really a win-win for both sides).
> democratically balancing consumer rights
Right. By stepping farther from the open market and killing some personal freedom. (Also, word "democratically" is absolutely meaningless in this context, but that's the usual mode it is used in in western politics.)
Right. By stepping farther from the open market and killing some personal freedom. (Also, word "democratically" is absolutely meaningless in this context, but that's the usual mode it is used in in western politics.)
> "democratically" is absolutely meaningless in this context
No, it isn't. When a law / regulation / policy is made all stakeholders are consulted and their views sought on it. Consumers are one of the stakeholders in context of what we are talking about. Politicians than work out a compromise that balances everyone's concerns. That's basically democracy at work.
No, it isn't. When a law / regulation / policy is made all stakeholders are consulted and their views sought on it. Consumers are one of the stakeholders in context of what we are talking about. Politicians than work out a compromise that balances everyone's concerns. That's basically democracy at work.
So when did entrepreneurs have “the right” to make money?
Depending on the country, it is not an absolute right, but still recognized as an essential one.
See Article 16 - Freedom to conduct a business - http://fra.europa.eu/en/eu-charter/article/16-freedom-conduc... and the article The 16th of all EU-r rights: the right to conduct a business and how the Charter contributes - https://www.eurac.edu/en/blogs/eureka/the-16th-of-all-eu-r-r... - for the European perspective of it.
See Article 16 - Freedom to conduct a business - http://fra.europa.eu/en/eu-charter/article/16-freedom-conduc... and the article The 16th of all EU-r rights: the right to conduct a business and how the Charter contributes - https://www.eurac.edu/en/blogs/eureka/the-16th-of-all-eu-r-r... - for the European perspective of it.
If only there were some company that made a watch that stored your health data e2e encrypted and didn’t use it to spy on you…
Yeah and that works out well with Android and Bluetooth.
Isn't that literally the point. Crappy drivers and no hardware documentation?
Yeah, it did. Your point?
You can seamlessly share standard Bluetooth devices between 5 devices just by pairing it to one like I do with my iPhone, iPad, Watch, MacBook and AppleTV and it automatically switches?
"seamlessly". I've had trouble between just an Apple-branded mobile phone and their branded all-in-one computer when it comes to the Apple-branded wireless headphones. The ping-pong between active sound channel/device had me disable the "seamless" handover, as it were a subpar experience for me. Better to manually decide which device that actively "owns" the channel.
Yeah. Multipoint connection has been a part of the Bluetooth spec since 4.0. Compatible devices will connect to anything available nearby and negotiate audio to whichever device pressed 'play' last. No iCloud mumbo-jumbo required, it was smoother than the Airpods experience when I was using it.
And how many “multipoint” devices support an unlimited number of devices? I currently have 2 AppleTVs, a MacBook, iPad, an iPhone and an Apple Watch all paired to my AirPods .
What’s the pairing process like? Mine is just - sign into iCloud and my AirPods show up.
What’s the pairing process like? Mine is just - sign into iCloud and my AirPods show up.
I have JBL headphones currently paired with Samsung phone, tablet, Intel NUC running Ubuntu and MacBook Pro running macOS. No problem, no cloud login necessary.
That’s still less than the 6 devices I have..
Next you're going to ask how high into the air I can piss?
>How will it make my everyday experience better as an Apple customer without the integration of software and hardware between my Mac, iPads Watch, Airpods and phone?
Perhaps that's the wrong question. Perhaps "making my everyday experience better as a customer" is not the be all end all.
Perhaps that's the wrong question. Perhaps "making my everyday experience better as a customer" is not the be all end all.
So now you want the government to pass laws that make consumer experience worse?
Maybe that will cause the “Year of Linux on the Desktop” to happen.
Maybe that will cause the “Year of Linux on the Desktop” to happen.
Mandating open standards is not the same thing as 'making consumer experience worse'.
So everything that any company designs should go through a committee before it’s introduced and become parts of a standards body?
That is your benevolent interpretation of the post you are answering to? Or is this just your hyperbolic example of the black-and-white fallacy to show how not to conduct a civil discussion?
I know, the point you are trying to make is buried beneath somewhere but it is really hard to make out. All I see is pettiness. So sad.
I know, the point you are trying to make is buried beneath somewhere but it is really hard to make out. All I see is pettiness. So sad.
Sure, why not? Except for some religous allegiance to "free market" (as it hasn't produced disasters aplenty itself) or some knee jerk rection to the notion of a committee?
[deleted]
Ah, I see the new marketing slogan for the FOSS movement is finally ready.
Thinking you know better than customers is a classic.
What if by letting this anti-competitive monopolies survive, we are getting future better ‘everyday experiences’ killed in their cribs?
Large companies routinely buy out startups, kill their products, and absorbs the teams.
Large companies routinely buy out startups, kill their products, and absorbs the teams.
Well, we have three examples of well resourced companies that weren’t able to compete in the smart phone market - Microsoft, Amazon and Facebook.
You really think a little startup is going to be able to do hardware at scale?
Was it big bad Apple that killed all of those phones or maybe it is just consumers made a choice using their own free will?
You really think that the startups didn’t have “being bought by a big company” as an exit strategy in the first place?
Out of all the companies that YC has funded (1000+) only six have ever gone public.
Were all the little companies that Apple acquired to integrate into their phone in an alternate universe going to create a phone?
You really think a little startup is going to be able to do hardware at scale?
Was it big bad Apple that killed all of those phones or maybe it is just consumers made a choice using their own free will?
You really think that the startups didn’t have “being bought by a big company” as an exit strategy in the first place?
Out of all the companies that YC has funded (1000+) only six have ever gone public.
Were all the little companies that Apple acquired to integrate into their phone in an alternate universe going to create a phone?
> Windows laptops are worse in every vector than MacBooks.
Plainly not true. Some are better hardware/quality wise. All are better when it comes to freedom with what you can actually do with the device.
Plainly not true. Some are better hardware/quality wise. All are better when it comes to freedom with what you can actually do with the device.
Is there one Windows laptop that can get 14 hours of battery life, fanless and that runs at a decent speed?
There are windows laptops that advertise over 20 hours of battery life with top current or last gen Intel and AMD processors.
Care to name a laptop with the performance, size, weight, and battery life running x86 chips like the MacBook Air - and that won’t fry my nuts when on my lap or sound like a 747 from the fans running?
The Dell XPS 13 inch series was a great pick, and then there was an Asus series, I think the 'B' series, that weighed less than a macbook air, had much longer battery, and had far more ports. Also could be charged with only a usb c cable, no special adapter.
Why would you doubt there are better options? The whole thing about the PC market is it has a much greater diversity of choices. It's silly to think Apple simply makes the best machine for a price point out of all available PC and Mac models.
Why would you doubt there are better options? The whole thing about the PC market is it has a much greater diversity of choices. It's silly to think Apple simply makes the best machine for a price point out of all available PC and Mac models.
All USB C MacBooks have always been able to be charged via USV C or MagSafe for the ones that come with it.
Was this the best you could do - worse performance, loud, poor battery life, poor display, poor audio?
The very first review I found
https://www.theverge.com/23674395/dell-xps-13-2022-intel-rev...
I’ll do the bottom line up front
In the past, the XPS 13 was a hands-down contender for the best laptop on the market. But the Apple-silicon MacBook has since barrelled onto the scene, and it wipes the floor with most of the ultraportable Windows laptops that cross my desk on a daily basis. This XPS is no exception. Compared to the M2 MacBook Air, battery life is worse. Benchmark performance is worse. Screen, while good, is worse. Port selection is worse.
And the rest.
So anyway, I’ve been using the regular XPS 13 for the past few weeks. And, like, it’s fine. It’s just fine. It’s worse than its 2020 predecessor in some ways and better in others. It continues to bring some of the best build quality in the 13-inch space. The display is fine. The speakers are fine. There’s an off-purple color option! It’s certainly one of the best Windows laptops you can buy, and it also doesn’t come close to the performance or efficiency that today’s MacBooks can provide, which says a thing or two about the current state of the Windows laptop space.
And the resolution is worse
Specifically, you’re limited to a 1920 x 1200 60Hz IPS panel
A similarly configured M2 MacBook Air is currently selling for $1,699, which makes Dell’s pricing attractive — though the performance benefits Apple delivers for that extra price aren’t insignificant, as we’ll soon discuss.
One thing to note about the XPS 13, though — the fans get going very easily. They were audible with a couple Chrome tabs and Slack open
Speaking of things that have improved: battery life. I averaged six hours and 42 minutes of consistent use around
Was this the best you could do - worse performance, loud, poor battery life, poor display, poor audio?
The very first review I found
https://www.theverge.com/23674395/dell-xps-13-2022-intel-rev...
I’ll do the bottom line up front
In the past, the XPS 13 was a hands-down contender for the best laptop on the market. But the Apple-silicon MacBook has since barrelled onto the scene, and it wipes the floor with most of the ultraportable Windows laptops that cross my desk on a daily basis. This XPS is no exception. Compared to the M2 MacBook Air, battery life is worse. Benchmark performance is worse. Screen, while good, is worse. Port selection is worse.
And the rest.
So anyway, I’ve been using the regular XPS 13 for the past few weeks. And, like, it’s fine. It’s just fine. It’s worse than its 2020 predecessor in some ways and better in others. It continues to bring some of the best build quality in the 13-inch space. The display is fine. The speakers are fine. There’s an off-purple color option! It’s certainly one of the best Windows laptops you can buy, and it also doesn’t come close to the performance or efficiency that today’s MacBooks can provide, which says a thing or two about the current state of the Windows laptop space.
And the resolution is worse
Specifically, you’re limited to a 1920 x 1200 60Hz IPS panel
A similarly configured M2 MacBook Air is currently selling for $1,699, which makes Dell’s pricing attractive — though the performance benefits Apple delivers for that extra price aren’t insignificant, as we’ll soon discuss.
One thing to note about the XPS 13, though — the fans get going very easily. They were audible with a couple Chrome tabs and Slack open
Speaking of things that have improved: battery life. I averaged six hours and 42 minutes of consistent use around
You realize there are multiple XPS laptop models, right? Not to mention you are overexaggerating the alleged negative aspects quite a lot . Are you really that addicted to the Apple kool-aid?
Go look at some of the Asus models than if you think an XPS can't compete. Weighed less than a macbook air, more port including ethernet (via a HDMI port), something like 21 hours of battery life, weight was slightly under a pound IIRC.
There's plenty of other models/companies.
The biggest benefit? It's not Apple locking you into their ridiculous ecosystem. But I suspect you're fine with that. Pretty funny in another comment you talk about governments restricting geeks, yet you advocated for the most locked down nannyed device you can hand over money to buy.
Go look at some of the Asus models than if you think an XPS can't compete. Weighed less than a macbook air, more port including ethernet (via a HDMI port), something like 21 hours of battery life, weight was slightly under a pound IIRC.
There's plenty of other models/companies.
The biggest benefit? It's not Apple locking you into their ridiculous ecosystem. But I suspect you're fine with that. Pretty funny in another comment you talk about governments restricting geeks, yet you advocated for the most locked down nannyed device you can hand over money to buy.
So, now you’re going to find the Asus or Dell that has
- 16 hours battery life
- fanless
- doesn’t scorch my nuts
- performance?
- a decent display
- and doesn’t weigh a ton?
So please tell me how the Mac keeps you from running the software you want.
But you named how great the objectively shitty Dell is.
You’ve already struck out with the Dell, care to try again with Asus? Can you cite a review of an Asus that compares?
Even though the Dell sucks in every dimension, at least you have “freeduhm”
- 16 hours battery life
- fanless
- doesn’t scorch my nuts
- performance?
- a decent display
- and doesn’t weigh a ton?
So please tell me how the Mac keeps you from running the software you want.
But you named how great the objectively shitty Dell is.
You’ve already struck out with the Dell, care to try again with Asus? Can you cite a review of an Asus that compares?
Even though the Dell sucks in every dimension, at least you have “freeduhm”
Yeah. I already told you there was an Asus that meets that criteria and has longer battery life.
Again, it's ridiculous to think Apple makes the very best lightweight powerful laptop given how diverse the PC market is. You're really durnk on that Apple kool-aid huh.
I didn't strike out with Dell at all. You found one review of one model and then exaggerated it.
You're the exact type of person that required coining the concept of an apple reality distortion field.
Again, it's ridiculous to think Apple makes the very best lightweight powerful laptop given how diverse the PC market is. You're really durnk on that Apple kool-aid huh.
I didn't strike out with Dell at all. You found one review of one model and then exaggerated it.
You're the exact type of person that required coining the concept of an apple reality distortion field.
I rather have Windows laptops that can replace a graphics workstation. a gaming PC on the go, or HPC on the go.
Markets Apple decided weren't worth their time.
Markets Apple decided weren't worth their time.
It's amazing how many people are just loyal to Apple even when it doesn't make sense.
There was a time when PCs started having vastly better graphics cards, and Adobe started prioritizing development for PCs, but still graphic designers were buying Apple because 'it's what creatives use'.
There was a time when PCs started having vastly better graphics cards, and Adobe started prioritizing development for PCs, but still graphic designers were buying Apple because 'it's what creatives use'.
You see this on the last bastion of people still hoping that Mac Pro desktop makes a proper comeback, instead of a Mac Studio in a bigger case.
Creatives buying Apple has always been mostly a North American phenomen, in Europe Apple only started being market relevant after the NeXT reverse acquisition, with iPod and iMacs rescuing it from insolvency.
Creatives buying Apple has always been mostly a North American phenomen, in Europe Apple only started being market relevant after the NeXT reverse acquisition, with iPod and iMacs rescuing it from insolvency.
Yeah the US has a weird fascination with Apple in particular. Just look at iphone users looking down on Android users because their text messages come as green instead of blue.
In every single market, the people who an afford iPhones, overwhelmingly by them. You see the same in the EU and especially China.
That's completely made up.
I'm in the UK, and working in IT, I can assure you that everyone in my team can afford and iPhone.
Only one does.
The cashier at the supermarket have them, you can see them in the back pockets of folks stacking shelves. It's not a device that requires people to be wealthy to own, just a desire.
I'm in the UK, and working in IT, I can assure you that everyone in my team can afford and iPhone.
Only one does.
The cashier at the supermarket have them, you can see them in the back pockets of folks stacking shelves. It's not a device that requires people to be wealthy to own, just a desire.
That is why they manage 20% world market share on mobile devices, and about 10% across desktop and laptop devices.
Not everyone can buy a Bentley.
Not everyone can buy a Bentley.
That's a fantastic random fact that has absolutely no bearing on the point I made.
>Windows laptops are worse in every vector than MacBooks. No consumer is asking for this.
"Not being Apple" was a very major part of my choice to buy a Windows laptop.
Some other consumers share my opinion of Apple.
>So you want to degrade the user experience for “freedom” by giving the government more power???
Having open standards is not "giving the government more power".
"Not being Apple" was a very major part of my choice to buy a Windows laptop.
Some other consumers share my opinion of Apple.
>So you want to degrade the user experience for “freedom” by giving the government more power???
Having open standards is not "giving the government more power".
How in the world is your everyday experience "better" today as a result of Apple's vertical integration?
Spoiler: it isn't.
Spoiler: it isn't.
Really?
I have a silent fanless MacBook Air running an Apple designed chip, with an Apple written OS where I can move my cursor between it and my iPad sitting right besides it and my keyboard and mouse can control both seanlessly. It also gets 16 hours of battery life.
And then I have a Windows laptop with piss poor battery life, sounds like a 747 at idle and runs hot enough that if I actually put it in my lap , it would endure that I don’t ever have any little Scarface’s
On the phone side, the day that Apple releases a new version of iOS, it’s immediately available worldwide for every iPhone that was introduced in the last four years. Is the same true for Android devices?
I have a silent fanless MacBook Air running an Apple designed chip, with an Apple written OS where I can move my cursor between it and my iPad sitting right besides it and my keyboard and mouse can control both seanlessly. It also gets 16 hours of battery life.
And then I have a Windows laptop with piss poor battery life, sounds like a 747 at idle and runs hot enough that if I actually put it in my lap , it would endure that I don’t ever have any little Scarface’s
On the phone side, the day that Apple releases a new version of iOS, it’s immediately available worldwide for every iPhone that was introduced in the last four years. Is the same true for Android devices?
Apple would still be able to do all of that.
The main reason Windows sucks is that Windows sucks. No specialized hardware can change that. The second reason is that hardware manufacturers make shitty drivers; because it shouldn't be their job in the first place.
And why is OS X so good? They scrapped the original MacOS, and started fresh with a fork of BSD. None of that has anything to do with monopolizing hardware.
It's also absurd to compare Apple's limited selection of exclusively flagship devices against every existing Android device. Compare them with their direct competition, and your point is moot.
If Apple's hardware division was broken off into a separate company, Apple's software division would be able to do everything they do today as a customer of that hardware company. The only difference would be that everyone else could too.
The main reason Windows sucks is that Windows sucks. No specialized hardware can change that. The second reason is that hardware manufacturers make shitty drivers; because it shouldn't be their job in the first place.
And why is OS X so good? They scrapped the original MacOS, and started fresh with a fork of BSD. None of that has anything to do with monopolizing hardware.
It's also absurd to compare Apple's limited selection of exclusively flagship devices against every existing Android device. Compare them with their direct competition, and your point is moot.
If Apple's hardware division was broken off into a separate company, Apple's software division would be able to do everything they do today as a customer of that hardware company. The only difference would be that everyone else could too.
So none of the fact that my MacBook Air runs quiet and fast running Apple designed processors, using an Apple designed OS, and integrating with other Apple hardware has anything to do with Apple being integrated?
And it shouldn’t be the company’s responsibility that made the hardware to make drivers and they should depend on who to do it then?
And it shouldn’t be the company’s responsibility that made the hardware to make drivers and they should depend on who to do it then?
Whoever writes the OS is in a much better position to write drivers. This is the reason Linux drivers are (usually) very good.
This is also why the current vertically integrated Apple is able to write good drivers: it isn't an isolated hardware manufacturer writing a driver. Because it's all one company, the OS team can be involved with driver development.
The solution for everyone would be to simply publish the hardware spec such that Apple, Microsoft, and Linux devs are able to write their own drivers.
The notion that hardware specs must be kept secret (because driver development is integrated with hardware development) is harming everyone, except the select few who have their own seats in the backroom.
Vertical integration is creating the very problem that you see Apple solving with vertical integration. Unfortunately, Apple is solving it exclusively for Apple, while hanging everyone else out to dry.
This situation is not unique to Apple, which is why we have shitty NVidia drivers in Linux, and why Android hardware support ends.
This is also why the current vertically integrated Apple is able to write good drivers: it isn't an isolated hardware manufacturer writing a driver. Because it's all one company, the OS team can be involved with driver development.
The solution for everyone would be to simply publish the hardware spec such that Apple, Microsoft, and Linux devs are able to write their own drivers.
The notion that hardware specs must be kept secret (because driver development is integrated with hardware development) is harming everyone, except the select few who have their own seats in the backroom.
Vertical integration is creating the very problem that you see Apple solving with vertical integration. Unfortunately, Apple is solving it exclusively for Apple, while hanging everyone else out to dry.
This situation is not unique to Apple, which is why we have shitty NVidia drivers in Linux, and why Android hardware support ends.
> Whoever writes the OS is in a much better position to write drivers. This is the reason Linux drivers are (usually) very good.
You really think that Linux developers would know how to squeeze better performance out of Nvidia hardware than the Nvidia even with the design specs? Nvidia has the foremost experts in designing GPUs and software around it (Cuda).
The software and the hardware teams know the intricacies of their hardware better than anyone and they work in concert to design a better product.
How long would it take the hypothetical Apple Hardware company to release products that the hypothetical Apple Software company wrote drivers for if they were split up?
Could the new Apple hardware company say release the AirPods that paired seamlessly with multiple products just by pairing with one device signed into your account and release a new version of MacOS, iOS, TvOS, etc at the same time? Apple, Google and even AWS (in the server space) design hardware and processors in tandem with their software teams. They don’t just throw designs over the fence with documentation.
> This situation is not unique to Apple, which is why we have shitty NVidia drivers in Linux, and why Android hardware support ends.
That’s a poor excuse. The fact is that Google is just a shitty platform caretaker. Microsoft has the same business model where they make the OS and license it to OEMs yet they support hardware for years if not decades.
Google doesn’t support its own phones as long as Apple. There is no excuse.
You really think that Linux developers would know how to squeeze better performance out of Nvidia hardware than the Nvidia even with the design specs? Nvidia has the foremost experts in designing GPUs and software around it (Cuda).
The software and the hardware teams know the intricacies of their hardware better than anyone and they work in concert to design a better product.
How long would it take the hypothetical Apple Hardware company to release products that the hypothetical Apple Software company wrote drivers for if they were split up?
Could the new Apple hardware company say release the AirPods that paired seamlessly with multiple products just by pairing with one device signed into your account and release a new version of MacOS, iOS, TvOS, etc at the same time? Apple, Google and even AWS (in the server space) design hardware and processors in tandem with their software teams. They don’t just throw designs over the fence with documentation.
> This situation is not unique to Apple, which is why we have shitty NVidia drivers in Linux, and why Android hardware support ends.
That’s a poor excuse. The fact is that Google is just a shitty platform caretaker. Microsoft has the same business model where they make the OS and license it to OEMs yet they support hardware for years if not decades.
Google doesn’t support its own phones as long as Apple. There is no excuse.
> You really think that Linux developers would know how to squeeze better performance out of Nvidia hardware than the Nvidia even with the design specs?
Yes. Even more importantly, they would be able to keep it stable alongside Mesa and Wayland/Xorg updates.
> Nvidia has the foremost experts in designing GPUs and software around it (Cuda).
And breaking up the company wouldn't make those people disappear! On the contrary, it would liberate their work. They would suddenly be free to start making CUDA compatible with AMDGPU! It would be wonderful.
Even if those people kept their work closed-source, just having an open hardware spec would do wonders for nouveau development. Last I checked, nouveau can't even set the GPU clock speed!
> Google doesn’t support its own phones as long as Apple. There is no excuse.
And that's my entire point! Google is bad at handling this responsibility, so let's take it off their hands! The reality is that Google doesn't want us to, because long term support is bad for their bottom-line!
Yes. Even more importantly, they would be able to keep it stable alongside Mesa and Wayland/Xorg updates.
> Nvidia has the foremost experts in designing GPUs and software around it (Cuda).
And breaking up the company wouldn't make those people disappear! On the contrary, it would liberate their work. They would suddenly be free to start making CUDA compatible with AMDGPU! It would be wonderful.
Even if those people kept their work closed-source, just having an open hardware spec would do wonders for nouveau development. Last I checked, nouveau can't even set the GPU clock speed!
> Google doesn’t support its own phones as long as Apple. There is no excuse.
And that's my entire point! Google is bad at handling this responsibility, so let's take it off their hands! The reality is that Google doesn't want us to, because long term support is bad for their bottom-line!
> And breaking up the company wouldn't make those people disappear! On the contrary, it would liberate their work. They would suddenly be free to start making CUDA compatible with AMDGPU! It would be wonderful.
The chip designers at NVidia work alongside the software people iteratively. They don’t just design the perfect chip and throw it over the fence.
Cuda isn’t just great (I’m not in that space, it might suck. I honestly don’t know) software that could be ported to any architecture. Cuda is written to work on a specific architecture both the hardware and the software inform each other.
The chip designers at NVidia work alongside the software people iteratively. They don’t just design the perfect chip and throw it over the fence.
Cuda isn’t just great (I’m not in that space, it might suck. I honestly don’t know) software that could be ported to any architecture. Cuda is written to work on a specific architecture both the hardware and the software inform each other.
Colleagues of mine aren't able to use their Macs for work since they're unable to target the hardware we're working on.
Perhaps with Asahi Linux they could. But even then, support isn't great.
Perhaps with Asahi Linux they could. But even then, support isn't great.
Well that world would suck immensely, with horrible integration between hardware and software like exists right now outside of the Apple world. Case in point: can you copy text on your phone, and paste in your computer (and vice versa), seamlessly as if it were the same device, without any configuration, hacks or programs needed? Things like that are amazing and I'd never give up. And I'm sure most people wouldn't want to give this up either just because Linux fanboys want to.
> Well that world would suck immensely, with horrible integration between hardware and software like exists right now outside of the Apple world.
Why? The hardware people at companies like NVIDIA or Apple already have to write detailed documentation for their stuff anyway so that the software people can do their side.
Assuming they do a good enough job at writing documentation and testing their hardware, it should not be a problem for Linux developers to write appropriate drivers. Hell there are a very few select people able to write high quality drivers even with zero documentation (see Asahi Linux).
The only ones in trouble would be the vendors of crap SoCs who ship extremely buggy hardware and make up for the lack of QA in software quirks instead.
Why? The hardware people at companies like NVIDIA or Apple already have to write detailed documentation for their stuff anyway so that the software people can do their side.
Assuming they do a good enough job at writing documentation and testing their hardware, it should not be a problem for Linux developers to write appropriate drivers. Hell there are a very few select people able to write high quality drivers even with zero documentation (see Asahi Linux).
The only ones in trouble would be the vendors of crap SoCs who ship extremely buggy hardware and make up for the lack of QA in software quirks instead.
1. Hardware companies need some software to test their product, so this will be wasting their effort.
2. Good documentation and testing is probably not as common as you think.
3. It takes a huge amount of effort to write high quality drivers by reverse engineering. The thing about Asahi Linux is that the hardware does not have many variants, but there are a lot more different hardware for PCs.
2. Good documentation and testing is probably not as common as you think.
3. It takes a huge amount of effort to write high quality drivers by reverse engineering. The thing about Asahi Linux is that the hardware does not have many variants, but there are a lot more different hardware for PCs.
> 1. Hardware companies need some software to test their product, so this will be wasting their effort.
They can also open source their testing bench code. The only ones who have to be afraid are those who don't care about quality. "Sunlight is the best disinfectant" also applies here - I'd really like to be able as a consumer to choose the product that demonstrates the better engineering!
> 2. Good documentation and testing is probably not as common as you think.
Oh, I'm aware of that, and the consequences of that are becoming more and more dire as electronic waste from defunct companies or unsupported and unsecure devices piles up, together with hacked IoT devices causing mayhem on the wide Internet in botnets.
It's high time for that to stop.
> 3. It takes a huge amount of effort to write high quality drivers by reverse engineering. The thing about Asahi Linux is that the hardware does not have many variants, but there are a lot more different hardware for PCs.
So what? Ordinary PC hardware at its core still conforms to decades old standards that can be used as a fallback. Given a sufficient supply of beers, coffee and pizza, every CS student worth their money can throw up a basic graphical OS that runs on any mainstream (i.e. non-embedded) x86 system. Input, output (video, serial, audio, keyboard, mice, accessories) and storage all have standardized interfaces - the only thing that does not is networking.
There is no reason at all to say that the ARM world can't standardize on basic components or at least interfaces. Apple can - their UART implementation, according to rumors, dates back to the early iPod/iPhone days, while Samsung has something like five or six completely different implementation, and Mediatek and all the other SoC vendors run their completely own stuff.
They can also open source their testing bench code. The only ones who have to be afraid are those who don't care about quality. "Sunlight is the best disinfectant" also applies here - I'd really like to be able as a consumer to choose the product that demonstrates the better engineering!
> 2. Good documentation and testing is probably not as common as you think.
Oh, I'm aware of that, and the consequences of that are becoming more and more dire as electronic waste from defunct companies or unsupported and unsecure devices piles up, together with hacked IoT devices causing mayhem on the wide Internet in botnets.
It's high time for that to stop.
> 3. It takes a huge amount of effort to write high quality drivers by reverse engineering. The thing about Asahi Linux is that the hardware does not have many variants, but there are a lot more different hardware for PCs.
So what? Ordinary PC hardware at its core still conforms to decades old standards that can be used as a fallback. Given a sufficient supply of beers, coffee and pizza, every CS student worth their money can throw up a basic graphical OS that runs on any mainstream (i.e. non-embedded) x86 system. Input, output (video, serial, audio, keyboard, mice, accessories) and storage all have standardized interfaces - the only thing that does not is networking.
There is no reason at all to say that the ARM world can't standardize on basic components or at least interfaces. Apple can - their UART implementation, according to rumors, dates back to the early iPod/iPhone days, while Samsung has something like five or six completely different implementation, and Mediatek and all the other SoC vendors run their completely own stuff.
> 2. Good documentation and testing is probably not as common as you think.
Not to mention that documentation != the actual behavior of the card. both nvidia and AMD release a ton of day-one driver fixes for new games being released that provide stability and sometimes double-digit performance gains over a pre-patched driver. The only way this works in a disintegrated ecosystem is if game devs become pros at creating driver bug workarounds.
Not to mention that documentation != the actual behavior of the card. both nvidia and AMD release a ton of day-one driver fixes for new games being released that provide stability and sometimes double-digit performance gains over a pre-patched driver. The only way this works in a disintegrated ecosystem is if game devs become pros at creating driver bug workarounds.
> The only way this works in a disintegrated ecosystem is if game devs become pros at creating driver bug workarounds.
They already are, they have to because that is the reality on mobile games. IIRC the devs of Real Racing (or another Android car race game) made a blog post on that.
They already are, they have to because that is the reality on mobile games. IIRC the devs of Real Racing (or another Android car race game) made a blog post on that.
Every year, Apple releases new hardware and software in tandem. How long does it take Android manufacturers and Windows manufacturers to take advantage of the latest OS features?
How are those Android updates working out compared to iPhones?
How are those Android updates working out compared to iPhones?
> How long does it take Android manufacturers
Way way too long, but to be fair a huge part of the issue are carriers and their insistence to pack the phones full of bloatware that needs to be tested against each update.
> and Windows manufacturers to take advantage of the latest OS features?
Windows device manufacturers tend to do what Microsoft demands of them.
> How are those Android updates working out compared to iPhones?
Samsung is fairly decent, although I'd be happier if they'd ... consolidate their lineup a bit and instead offer longer availability for spare parts.
Way way too long, but to be fair a huge part of the issue are carriers and their insistence to pack the phones full of bloatware that needs to be tested against each update.
> and Windows manufacturers to take advantage of the latest OS features?
Windows device manufacturers tend to do what Microsoft demands of them.
> How are those Android updates working out compared to iPhones?
Samsung is fairly decent, although I'd be happier if they'd ... consolidate their lineup a bit and instead offer longer availability for spare parts.
Fairly decent? The iPhone 5s from 2013 just got an update and it’s the carriers is a poor excuse. Apple runs on the same carriers.
Google’s first party phones don’t have third party bloat ware and still have a piss poor history of updates
Google’s first party phones don’t have third party bloat ware and still have a piss poor history of updates
And guess why? Because ~3-ish years used to be what the SoC vendors provided as BSP support timeframe, and there was no mandate that they open up their specifications. Most don't even care about following the legal minimum aka provide the kernel and bootloader source code, especially not all these fly-by-night gongkai "brands".
So it’s what happens when hardware and software is not integrated…
No, it's what happens when there is no competition in the SoC vendor area. Apple and Samsung don't sell to external customers, NVIDIA doesn't do much with Tegra outside of the Switch and automotive, Broadcom doesn't do much in mobile SoCs (and from what the Raspberry Pi community learned hard, their chips are utter dogshit which is how RPi got started after all - they used surplus crap that Broadcom wasn't able to sell), which leaves Qualcomm as a sole supplier for the "high end" and Mediatek/Rockchip for bottom-of-the-barrel crap. There used to be Annapurna Labs as well, QNAP used their SoCs for a while, but I think they stopped selling to externals as well as they were bought up by Amazon and now only do Graviton which are Amazon exclusives.
And yet Apple uses Qualcomm chips and manages to update 10 year old phones.
It couldn’t possibly be your premise is flawed could it?
It couldn’t possibly be your premise is flawed could it?
> And yet Apple uses Qualcomm chips and manages to update 10 year old phones.
For modems, yes, but only because there's even less competition in that area (which is why they bought Intel's mobile modem business, but failed to produce a viable design in all the years since).
They've been running their own SoC designs since the iPhone 4 era in 2010.
For modems, yes, but only because there's even less competition in that area (which is why they bought Intel's mobile modem business, but failed to produce a viable design in all the years since).
They've been running their own SoC designs since the iPhone 4 era in 2010.
So now it’s the severe lack of competition that allows Apple to support phones for a decade but stops Android manufacturers?
Lame excuses, Google could do the same as Microsoft with PC standards and OEM legal obligations.
They have chosen not to.
They have chosen not to.
Agreed. Google has gone down the drains just as well on all fronts... the thing is, once again, there is no viable competition left since Microsoft gave up. The various Linux phone projects are extremely niche stuff, Blackberry and Symbian are long gone, and Google seems to be happy coasting along on mediocrity and billions of dollars in Play Store revenue.
That wouldn't change at all. The newly separated software company would get appropriate hardware specs and prototypes during the same timeline they do today (as a vertically integrated branch of Apple).
So instead of working together , the software team would work in isolation and then when they are finished they deliver to the hardware company and keep going back and forth? Yeah that’s going to work out real well. Let’s just look how well it work for Android.
> the software team would work in isolation
Only if the hardware company refuses to share info with them, which - as you clearly laid out - is not in their interest.
Only if the hardware company refuses to share info with them, which - as you clearly laid out - is not in their interest.
You really don’t see how that would slow things down compared to the hardware and software company working together?
I bet you also think that a company should set up a DevOps “department” to increase efficiency
I bet you also think that a company should set up a DevOps “department” to increase efficiency
Are you telling me that Apple doesn't have a separate hardware division? I sincerely doubt that.
I am saying that Apple has a software and hardware division that work in concert.
Chris Lattner, the inventor of the Swift programming language and the open source LLVM was once interviewed on the Accidental Tech Podcast and he was asked whether bytecode could be used to allow Apple to switch architectures without forcing them to require developers to recompile and still have native compilation. He made up some half truth about whether that would be possible.
Years later when the S chips in the Apple Watch became 64 bit, he admitted that at the time of the interview, he knew that the 64 bit S chip was on the roadmap internally and he designed the LLVM with that in mind.
That’s what happens when you have software and hardware teams working together. The same is true with Nvidia and the their software developers who design Cuda and Intel and the compiler makers.
There were also reports that the software team responsible for the JS engine in WebKit worked with the processor team and the processor team did some design work around Apple’s ARM variants to make JS pre compilation faster.
This is also the whole idea of VLIW architectures where the processor manufacture depends on a team of compiler makers to ring out efficiencies and they work closely together.
Heck even back in the Apple // days, Woz a developer, designed hardware and software together.
Chris Lattner, the inventor of the Swift programming language and the open source LLVM was once interviewed on the Accidental Tech Podcast and he was asked whether bytecode could be used to allow Apple to switch architectures without forcing them to require developers to recompile and still have native compilation. He made up some half truth about whether that would be possible.
Years later when the S chips in the Apple Watch became 64 bit, he admitted that at the time of the interview, he knew that the 64 bit S chip was on the roadmap internally and he designed the LLVM with that in mind.
That’s what happens when you have software and hardware teams working together. The same is true with Nvidia and the their software developers who design Cuda and Intel and the compiler makers.
There were also reports that the software team responsible for the JS engine in WebKit worked with the processor team and the processor team did some design work around Apple’s ARM variants to make JS pre compilation faster.
This is also the whole idea of VLIW architectures where the processor manufacture depends on a team of compiler makers to ring out efficiencies and they work closely together.
Heck even back in the Apple // days, Woz a developer, designed hardware and software together.
Have you wrote drivers? Writing a driver off documentation is: a) very hard, how do you debug anything without JTAG ports and simulators? and b) not correct on principle because the documentation is not the hardware, there are errata in the hardware so what documentation says is not always what the hardware does and there are mistakes in the documentation for the same outcome.
>The only ones in trouble would be the vendors of crap SoCs who ship extremely buggy hardware and make up for the lack of QA in software quirks instead.
I.e. the every single vendor currently on the market...
>The only ones in trouble would be the vendors of crap SoCs who ship extremely buggy hardware and make up for the lack of QA in software quirks instead.
I.e. the every single vendor currently on the market...
> Writing a driver off documentation is: a) very hard, how do you debug anything without JTAG ports and simulators? and b) not correct on principle because the documentation is not the hardware, there are errata in the hardware so what documentation says is not always what the hardware does and there are mistakes in the documentation for the same outcome.
I agree with you, no system (particularly not something as complex as an entire SoC) is free of bugs.
> I.e. the every single vendor currently on the market...
And yet, we have Apple, whose hardware quality alone is good enough for a dedicated team to reverse engineer and write drivers for, with almost zero documentation available.
The problem, as I expanded below, is the complete lack of competition in the SoC space. Everyone gets away with mediocrity because the largest players in town (Apple and Samsung) refuse to sell their chips to externals. The result is that the mobile ecosystem as a whole suffers, because that is what happens in markets where entities get too large.
I agree with you, no system (particularly not something as complex as an entire SoC) is free of bugs.
> I.e. the every single vendor currently on the market...
And yet, we have Apple, whose hardware quality alone is good enough for a dedicated team to reverse engineer and write drivers for, with almost zero documentation available.
The problem, as I expanded below, is the complete lack of competition in the SoC space. Everyone gets away with mediocrity because the largest players in town (Apple and Samsung) refuse to sell their chips to externals. The result is that the mobile ecosystem as a whole suffers, because that is what happens in markets where entities get too large.
>And yet, we have Apple, whose hardware quality alone is good enough for a dedicated team to reverse engineer and write drivers for, with almost zero documentation available.
Apple own software is pretty janky, my current MacBook cannot bring up GPU after sleep about once a month and needs a reboot to begin drawing GUI correctly again, used to be dying completely waking up before it was fixed couple OS updates back. My previous MacBook could not stay on WiFi for more than a couple hours straight, never had been fixed.
Also, reversing an existing working driver is different from writing a driver from scratch. In one case you just need to repeat the functionality, produce the same outputs for the same inputs, the quality of hardware is orthogonal here since it's already worked around in the existing driver. It's orders of magnitude easier than writing the thing from scratch.
Apple own software is pretty janky, my current MacBook cannot bring up GPU after sleep about once a month and needs a reboot to begin drawing GUI correctly again, used to be dying completely waking up before it was fixed couple OS updates back. My previous MacBook could not stay on WiFi for more than a couple hours straight, never had been fixed.
Also, reversing an existing working driver is different from writing a driver from scratch. In one case you just need to repeat the functionality, produce the same outputs for the same inputs, the quality of hardware is orthogonal here since it's already worked around in the existing driver. It's orders of magnitude easier than writing the thing from scratch.
Documenting this in detail is neigh impossible. Ashai Linux has the benefit of having working code to RE - this wouldn't work for silicon or board bring up.
> Case in point: can you copy text on your phone, and paste in your computer (and vice versa), seamlessly as if it were the same device, without any configuration, hacks or programs needed?
I am guessing that AirDrop, Sidecar, etc have absolutely nothing to do with hardware-software integration, and have ≥ Layer 3 implementations. KDE Connect and Microsoft My Phone are competitors.
I am guessing that AirDrop, Sidecar, etc have absolutely nothing to do with hardware-software integration, and have ≥ Layer 3 implementations. KDE Connect and Microsoft My Phone are competitors.
Exactly. Apple could have made this work across other platforms (Windows, Android, Linux), but chose not to. KDE Connect, for example, runs on quite a few platform, including all popular ones. https://kdeconnect.kde.org/download.html
Why should Apple be forced to write software for competing platforms?
I generally think any company with a >10 billion (2023 US) dollar valuation should be forced to do things that may not directly benefit them but benefit society. Having to publish open specifications for all their proprietary integrations is a pretty easy, relatively low-cost example.
How to make this work in practice is a really interesting question. Community and employee representatives on the board would be a good start. But I think just having the requirement that open specifications be made available, and writing that into legislation, would be great.
How to make this work in practice is a really interesting question. Community and employee representatives on the board would be a good start. But I think just having the requirement that open specifications be made available, and writing that into legislation, would be great.
Oh god, talking about design by committee. Why not just cut out the middle man and let the government take it over and come up with “5 year plans”
If a company doesn't want at least some element of that, the solution is very simple: drop below a USD $10B valuation by spinning off parts of the company. Note that I said TEN BILLION DOLLARS. A "decacorn". That is an unfathomable amount of money. If you've created a company worth that much you've won at capitalism.
If governments had a good track record I'd advocate for that. No need for strawmen like five year plans, I think competition is a wonderful thing.
My underlying, strong belief is that corporations are legal fictions created primarily to benefit society, Milton Friedman's philosophy notwithstanding.
If governments had a good track record I'd advocate for that. No need for strawmen like five year plans, I think competition is a wonderful thing.
My underlying, strong belief is that corporations are legal fictions created primarily to benefit society, Milton Friedman's philosophy notwithstanding.
Your suggestion makes a ton of sense. It's astounding how many HN people are so hardcore capitalists to be against such a simple suggestion.
It’s not hard core capitalism. It’s that geeks hate when people make their own choices without government interference because normal people don’t care that they can’t run Linux on the Apple Pencil.
It’s also naiveté to think that government power isn’t the most dangerous kind of power imaginable even though almost every law proposed by the government with regards to tech is roundly criticized by the same people.
It’s also naiveté to think that government power isn’t the most dangerous kind of power imaginable even though almost every law proposed by the government with regards to tech is roundly criticized by the same people.
> It’s also naiveté to think that government power isn’t the most dangerous kind of power imaginable
That's only true if the market isn't free. If private businesses are not kept in check, they can (and have) overthrown government power. Ask me how I know!
That's only true if the market isn't free. If private businesses are not kept in check, they can (and have) overthrown government power. Ask me how I know!
Yes I’m sure Apple and Google are secretly conspiring to overthrow the government.
The suggestion was simply that companies that make more than 10 billion should be forced to give back to society. That's it. To be against that is indeed hard core capitalism, bordering on religious fervor.
They do give back to society - they provide jobs, pay taxes, and mobile has created millions of jobs and put computers in billions of people’s pockets.
Design-by-committee doesn't sound half-bad if it can standardize a single serial cable that doesn't have licensing fees. Doesn't resemble an unreasonable use of government power at all.
I don’t think that’s the argument you think it is. Thought experiment, grab a random USB C cable, now tell me:
1. What speed can you transfer data through it?
2. How much power can it deliver?
3. Can it support video over USB C?
4. Say a random device comes with a USB-A cable on one side and a USB-c on the other. Now take a standard usb c/usb c cable, will it always charge the device?
Also when that same government first wanted to “standardize”. They wanted to standardize on micro-USB.
1. What speed can you transfer data through it?
2. How much power can it deliver?
3. Can it support video over USB C?
4. Say a random device comes with a USB-A cable on one side and a USB-c on the other. Now take a standard usb c/usb c cable, will it always charge the device?
Also when that same government first wanted to “standardize”. They wanted to standardize on micro-USB.
> Thought experiment, grab a random USB C cable, now tell me
Oh, easy. Apple already solved this one; if it has the Thunderbolt logo, it's maxed out. If it's anything else, you're usually getting at least 5w charging and USB 2.0 speeds. In other words, the worst-case scenario is usually slightly better than Lightning.
Oh, easy. Apple already solved this one; if it has the Thunderbolt logo, it's maxed out. If it's anything else, you're usually getting at least 5w charging and USB 2.0 speeds. In other words, the worst-case scenario is usually slightly better than Lightning.
It’s not that simple. A cable has to support video which is separate from the speed.
So your solution to making sure that you get the most compatibility is to buy Apple cables for Apple devices…meet the new boss.
I’m slightly trolling. I have these….
https://www.amazon.com/dp/B093YVRHMB
I travel with a portable monitor that gets power and video from one USB-c cable. It works with both my personal MacBook Air and my work Windows laptop.
So your solution to making sure that you get the most compatibility is to buy Apple cables for Apple devices…meet the new boss.
I’m slightly trolling. I have these….
https://www.amazon.com/dp/B093YVRHMB
I travel with a portable monitor that gets power and video from one USB-c cable. It works with both my personal MacBook Air and my work Windows laptop.
> So your solution to making sure that you get the most compatibility is to buy Apple cables for Apple devices…meet the new boss.
I was hoping you'd bite the hook, but not like this...
Intel actually designed the spec, drivers and IC controllers for Thunderbolt. Apple consulted on it with USB-IF, but they don't own the spec like they do with Lightning. They're less of a new boss, and more subsuming their rightful position as a valued consultant on a shared standard. It's a good (albeit old) example of Apple doing the right thing through the right channels.
I was hoping you'd bite the hook, but not like this...
Intel actually designed the spec, drivers and IC controllers for Thunderbolt. Apple consulted on it with USB-IF, but they don't own the spec like they do with Lightning. They're less of a new boss, and more subsuming their rightful position as a valued consultant on a shared standard. It's a good (albeit old) example of Apple doing the right thing through the right channels.
It doesn't - it only needs to support open standards.
So does that mean Apple can’t release anything until it goes through a standards body?
Scarface, Apple doesn't love you back.
Well neither does the government. At least Apple doesn’t have guns to force me to do what it wants.
How hard is it for you not to use Apple products? Are you incapable of using your own free will?
Between Apple and the government, guess which one has the power to take away your free will?
How hard is it for you not to use Apple products? Are you incapable of using your own free will?
Between Apple and the government, guess which one has the power to take away your free will?
What open standard covers shared clipboards across devices?
If it doesn't exist, then obviously the standard body has to work with the stakeholders and create one.
Are you suggesting that Apple shouldn’t create any new feature without going through a standards body?
No. Apple can create a working solution and submit it to the standards body. That's what being "open" means.
And then if the standards body doesn’t accept their solution because low end Android manufacturers don’t want to spend an extra 20 cents on a build of materials?
That’s why PC OEMs didn’t support FireWire before USB 3 came out except for Sony and Dell on some of their high end offerings.
If you don’t like Apple’s offerings you are free to choose Android/Windows
That’s why PC OEMs didn’t support FireWire before USB 3 came out except for Sony and Dell on some of their high end offerings.
If you don’t like Apple’s offerings you are free to choose Android/Windows
That's where regulation comes in - when it is mandated that devices have to support standards, all will have to support it.
I suppose that loops back to the premise of the linked article (which is IMO absurd).
KDEConnect lets you sync your phone keyboard, even with Windows. And Apple could let you sync your clipboard to non-iOS devices too, they just block arbitrary features unless you buy into their entire ecosystem.
I did mention without installing a program, and without any configuration.
Is the implicit "… not written by the original OS vendor" at the end of your sentence intentional? There is obviously a program and/or configuration, just done by Apple. Nothing precludes building such a system in other systems.
Yes, the whole discussion is about vertical integration, achieved best so far by Apple. I'm sure it can be done in other systems, but for whatever reason other systems haven't made it as simple and seamless. I wonder why. Could it have something to do with the lack of vertical integration maybe?
> Well that world would suck immensely
Maybe.
> Case in point
But this does not really support your statement no? What you described seems to me SW only functionality no? And if in requires any special HW (BT? I have no idea how it works under the hood), why does it need tight integration? I do not see a technical reason why Android and Windows could not provide the same feature out of the box, despite neither the Google nor Microsoft making the HW.
Maybe.
> Case in point
But this does not really support your statement no? What you described seems to me SW only functionality no? And if in requires any special HW (BT? I have no idea how it works under the hood), why does it need tight integration? I do not see a technical reason why Android and Windows could not provide the same feature out of the box, despite neither the Google nor Microsoft making the HW.
the most probable cause is patents
Sounds like we clear abuse of patent law.
> Non-obvious is a requirement for patent protection that literally means your invention is not obvious to someone who is in the same industry. A new invention needs to be unexpected or surprising and cannot be anticipated by looking at the existing technology or prior art.
> Non-obvious is a requirement for patent protection that literally means your invention is not obvious to someone who is in the same industry. A new invention needs to be unexpected or surprising and cannot be anticipated by looking at the existing technology or prior art.
Really your example serves as disproving your point, without the hardware walled garden there could be nothing to prevent apple to distribute the software to copy-paste from-to multiple devices
Ah just forgot to add to the point, its possible to copy paste from mobile/desktop with kconnect that is open source, its not that bit of a deal that requires special hardware
What is KDE Connect? Which incidentally runs equally well on other desktops and even windows.
https://userbase.kde.org/KDEConnect
Also gsconnect can provide integration with gnome.
https://extensions.gnome.org/extension/1319/gsconnect/
KDE Connect is a project that enables all your devices to communicate with each other. Here are a few things KDE Connect can do:
Firefox and I presume chrome let you push tabs from one machine to the other or with forefox simply pull up a list of tabs currently open on the other device.
Unified remote also gives you a great remote for our multimedia pc.
Basically every email service abd chat app has good integration between desktop and phone.
Mpd and mafa lets me easily listen to my music
Calibre and calibre companion let's me easily sync my books
I doubt one person making these things would make them better
https://userbase.kde.org/KDEConnect
Also gsconnect can provide integration with gnome.
https://extensions.gnome.org/extension/1319/gsconnect/
KDE Connect is a project that enables all your devices to communicate with each other. Here are a few things KDE Connect can do:
Receive your phone notifications on your desktop computer and reply to messages
Control music playing on your desktop from your phone
Use your phone as a remote control for your desktop
Run predefined commands on your PC from connected devices. See the list of example commands for more details.
Check your phones battery level from the desktop
Ring your phone to help finding it
Share files and links between devices
Browse your phone from the desktop
Control the desktop's volume from the phone
Firefox and I presume chrome let you push tabs from one machine to the other or with forefox simply pull up a list of tabs currently open on the other device.
Unified remote also gives you a great remote for our multimedia pc.
Basically every email service abd chat app has good integration between desktop and phone.
Mpd and mafa lets me easily listen to my music
Calibre and calibre companion let's me easily sync my books
I doubt one person making these things would make them better
KDE Connect requires both devices to be connected to the same network, which means you have to connect your devices to the same VPN if you're on a wifi network with client isolation (most public wifi). If you're away from wifi, you'll have to configure one of the devices to be an access point and join everything else to that device.
Apple's clipboard/handoff/continuity automatically works as long as the devices are within wifi/bluetooth range.
Apple's clipboard/handoff/continuity automatically works as long as the devices are within wifi/bluetooth range.
This is a good point and a good reason to propose an improvement to KDE Connect but users point was that integration would be awful if not done by the same party and it seems to my eyes to be pretty good despite one being created by a party with literally a billionth of the resources of the other.
For what it's worth, Connect does have a Bluetooth backend that supposedly works: https://invent.kde.org/network/kdeconnect-kde/-/tree/master/...
It doesn't seem to be enabled by default though. I'm not totally familiar with the situation, but I'd assume it's a problem with multi-device handling and switching to the best backend. For most people/situations, the Wifi Direct option will be faster and lower-latency.
It doesn't seem to be enabled by default though. I'm not totally familiar with the situation, but I'd assume it's a problem with multi-device handling and switching to the best backend. For most people/situations, the Wifi Direct option will be faster and lower-latency.
It also wont magically stop working 30 feet away if you want to use the multimedia remote functionality. Graceful degradation seems like a useful feature but if you aren't careful the result might be flaky
> Case in point: can you copy text on your phone, and paste in your computer (and vice versa), seamlessly as if it were the same device, without any configuration, hacks or programs needed?
Circumstantially, yes. I am a KDE user though, on GNOME you do have to install a little app for it.
Circumstantially, yes. I am a KDE user though, on GNOME you do have to install a little app for it.
Yes, that works if I want it to, e.g by running KDE Connect (which works outside of KDE). Works on Linux, Android, Windows and even on Apple-things in case you need to escape the walled garden...
Sounds like it needs a special program and configuration, which is not needed on Apple devices. Also, KDE Connect needs both devices to be in the same network - which is not needed for Apple devices. My phone can be on 5G, and my Mac can be on wifi. Or they don't have to connected to a network at all.
> Sounds like it needs a special program and configuration, which is not needed on Apple devices
How else would it work across different devices? Apple devices can not connect to e.g. Android devices without a 'special program and configuration' nor can they do so with Linux or Windows or whatever other devices.
> Also, KDE Connect needs both devices to be in the same network - which is not needed for Apple devices
KDE Connect and other similar tools work fine over a VPN which is the preferred solution for such setups. You can choose which VPN you want to use, OpenVPN and Wireguard are two popular choices. Here again that VPN can be used to connect disparate devices - Linux, Windows, Android, Apple-things, whatever. Apple devices only talk to other Apple devices which is far more restrictive.
If you are a happy camper in the walled garden then things are good for you. I prefer the freedom of camping in the wild even if that means I may have to build my own fire and cook my own food since it enables me to go where I please without being held back by that wall and without having to pay the ferryman. To each his own I guess?
How else would it work across different devices? Apple devices can not connect to e.g. Android devices without a 'special program and configuration' nor can they do so with Linux or Windows or whatever other devices.
> Also, KDE Connect needs both devices to be in the same network - which is not needed for Apple devices
KDE Connect and other similar tools work fine over a VPN which is the preferred solution for such setups. You can choose which VPN you want to use, OpenVPN and Wireguard are two popular choices. Here again that VPN can be used to connect disparate devices - Linux, Windows, Android, Apple-things, whatever. Apple devices only talk to other Apple devices which is far more restrictive.
If you are a happy camper in the walled garden then things are good for you. I prefer the freedom of camping in the wild even if that means I may have to build my own fire and cook my own food since it enables me to go where I please without being held back by that wall and without having to pay the ferryman. To each his own I guess?
> How else would it work across different devices? Apple devices can not connect to e.g. Android devices
I was talking about Mac and iPhone having seamless integration - something I have not noticed of any other ecosystem. I have not been able to share clipboards with an android and a PC (Win and Linux) without installing an app, or doing some other hacky things. The integration, while possible, doesn't exist by default. It's not seamless. It doesn't _just work_.
> KDE Connect and other similar tools work fine over a VPN
I don't want to use a VPN? I want to use my regular home wifi or phone network, like a normal person.
I was talking about Mac and iPhone having seamless integration - something I have not noticed of any other ecosystem. I have not been able to share clipboards with an android and a PC (Win and Linux) without installing an app, or doing some other hacky things. The integration, while possible, doesn't exist by default. It's not seamless. It doesn't _just work_.
> KDE Connect and other similar tools work fine over a VPN
I don't want to use a VPN? I want to use my regular home wifi or phone network, like a normal person.
> I have not been able to share clipboards with an android and a PC (Win and Linux) without installing an app, or doing some other hacky things
How else would this type of interchange work between disparate systems other than by equipping all systems with a piece of software to bridge the gap? In what way is this a problem and what makes it 'hacky'? When you want to use your Apple-device to interact with something non-Apple you install a piece of software to enable this interaction - that was the premise of a 'smart phone' after all, a device which' functionality can be extended by installing software? This in contrast to a 'feature phone' where all functionality has been baked in by the manufacturer/distributor. You seem to be using your Apple devices more in the way of the latter - using only manufacturer-provided functionality.
> I don't want to use a VPN? I want to use my regular home wifi or phone network, like a normal person.
I do not want to use 'the cloud' and Bluetooth in ways I do not have control over [1] - as I said, to each his own?
[1] https://www.forbes.com/sites/zakdoffman/2020/02/26/simple-ap...
How else would this type of interchange work between disparate systems other than by equipping all systems with a piece of software to bridge the gap? In what way is this a problem and what makes it 'hacky'? When you want to use your Apple-device to interact with something non-Apple you install a piece of software to enable this interaction - that was the premise of a 'smart phone' after all, a device which' functionality can be extended by installing software? This in contrast to a 'feature phone' where all functionality has been baked in by the manufacturer/distributor. You seem to be using your Apple devices more in the way of the latter - using only manufacturer-provided functionality.
> I don't want to use a VPN? I want to use my regular home wifi or phone network, like a normal person.
I do not want to use 'the cloud' and Bluetooth in ways I do not have control over [1] - as I said, to each his own?
[1] https://www.forbes.com/sites/zakdoffman/2020/02/26/simple-ap...
Not only copy/paste, but have notifications shared both ways, use your computer as a phone laptop, use the phone as a trackpad/mouse, and much more. It just works.
[deleted]
Why would this be an issue? Under the proposed model, the vendor for phone software can be the same vendor for desktop software.
With those preconditons, it doesn't even work on Apple devices.
What do you mean? This is what Universal Clipboard does.
Pretty sure you had to configure both devices for it to work.
No, just sign into both of them with your iCloud account
It obviously uses "a program, a hack, or configuration" (taking these from the original reply), just that they are written and pre-installed by Apple, and work seamlessly.
But from the end-user perspective it doesn't really. Nobody consciously sets the universal clipboard up, it comes as part of the cohesive whole of the Apple ecosystem. That's my point. Whether or not you want to dive deep into nerdland of if it's a program or not is besides the point, because for the end-user none of it matters, and that's why the vertical integration is nice.
Probably true. The whole vertical integration does rub me the wrong way though, it's just uncomfortable to have one company own so much of my personal computing infrastructure, especially one that is so unfriendly to "tinkerers" like me.
Yes because the 10% market share that Apple has in computers is really worrying…
If I buy an Apple phone, tablet, and computer, that will be 100% of my computing infra, which is all that matters to me.
Then don’t buy a device that doesn’t meet your needs? I don’t go shopping in the big and tall store expecting to find something that meets my needs when I am five foot five.
Literally never needed to copy text from smartphone to pc (or viceversa). At best anyone needs to sync between photos, docs or stuff like that. For that you just need a sync on the cloud like Dropbox, Drive, Box, and so on (also never heard of bluetooth for small files?)
moreover, apple's software is generally very buggy.
moreover, apple's software is generally very buggy.
Never typed a 2FA code from the phone to the computer?
Just copying them on the iPhone and pasting them on the mac is super convenient.
Just copying them on the iPhone and pasting them on the mac is super convenient.
I never felt like syncing my devices besides steam cloud saves. Too much convenience makes me uncomfortable. Especially if it means mixing corporate and personal stuff.
On android you can view your sms messages at messages.google.com allowing you to easily copy and paste it
Yeah, can also view email on both phone and computer since forever ago - this is not even remotely similar to the shared clipboard of an iPhone and Mac, where you don't need to open any links or programs, install anything, configure anything - you just copy on phone/computer and then instantly are able to paste on phone/computer.
Have you ever wanted to copy anything from A->B that wasn't a 2fa text, a password, or a url? I certainly haven't. An android phone out of the box supports syncing tabs and passwords and provides a trivial way to copy 2FA codes with a built in feature.
So your argument is that because the things to copy are few, this feature doesn't matter? Or what? I fail to see how what you say contributes to the discussion of vertical integration in any way.
Not few none. People need to share files, tabs, messages, mails. If you can share the things people actually want shared then sharing the clipboard itself has zero value.
Your response is completely irrelevant to the discussion of vertical integration. Whether or not you find use in it is up to you, and I don't really care.
This is completely impossible with any hardware made in the last 20 years or so.
The problem is that you cannot make a hard distinction between hardware and software. An Intel CPU simply isn't going to run without microcode, and having to get rid of microcode would easily set back chip design by a decade.
Even something as trivial as a USB cable isn't pure hardware anymore. It has a programmable eMarker in order to advertise its capabilities, so it is also a combination of hardware and software. Everything but completely trivial chips has some kind of computation embedded in it, requiring some firmware.
Chips are complicated and weird. Pretty much nobody writes code which directly interacts with hardware. Even people who write code for embedded microprocessors will use an SDK provided by the chip manufacturer to smooth out the nastiest details. How's that supposed to work when the hardware vendor can no longer provide any software?
And then there's the question of what exactly constitutes "firmware". Is code in a separate programmable flash chip okay if they hardwire the Write Protect pin? What if the exact same code is stored in programmable space in the MCU itself? Is it fine to place that code in One-Time-Programmable memory? Bake it into the chip during wafer manufacturing? If anything, being able to update the firmware in the field is better for the consumer when it comes to fixing bugs.
The problem is that you cannot make a hard distinction between hardware and software. An Intel CPU simply isn't going to run without microcode, and having to get rid of microcode would easily set back chip design by a decade.
Even something as trivial as a USB cable isn't pure hardware anymore. It has a programmable eMarker in order to advertise its capabilities, so it is also a combination of hardware and software. Everything but completely trivial chips has some kind of computation embedded in it, requiring some firmware.
Chips are complicated and weird. Pretty much nobody writes code which directly interacts with hardware. Even people who write code for embedded microprocessors will use an SDK provided by the chip manufacturer to smooth out the nastiest details. How's that supposed to work when the hardware vendor can no longer provide any software?
And then there's the question of what exactly constitutes "firmware". Is code in a separate programmable flash chip okay if they hardwire the Write Protect pin? What if the exact same code is stored in programmable space in the MCU itself? Is it fine to place that code in One-Time-Programmable memory? Bake it into the chip during wafer manufacturing? If anything, being able to update the firmware in the field is better for the consumer when it comes to fixing bugs.
> The problem is that you cannot make a hard distinction between hardware and software. An Intel CPU simply isn't going to run without microcode, and having to get rid of microcode would easily set back chip design by a decade.
Yes you can make the distinction, and no it doesn't require getting rid of the microcode: https://news.ycombinator.com/item?id=37731829
Simply put, if the microcode can be updated by the user or remotely by Intel, then it count as "software", and Intel should stop shipping it. But if those update are either impossible or require a factory recall, then it's "hardware", and Intel can happily continue to ship it.
The same logic applies to the USB cable, and even FPGA: if the bitstream is locked into the NVCM, that's hardware. If it's merely written in the rewritable SPI flash, that's software. It's not a property of the bitstream itself, it's a property of how it is stored.
Obviously the cost of micro-code bugs will sharply increase. That's kind of a feature though: now hardware vendors must be really careful.
Yes you can make the distinction, and no it doesn't require getting rid of the microcode: https://news.ycombinator.com/item?id=37731829
Simply put, if the microcode can be updated by the user or remotely by Intel, then it count as "software", and Intel should stop shipping it. But if those update are either impossible or require a factory recall, then it's "hardware", and Intel can happily continue to ship it.
The same logic applies to the USB cable, and even FPGA: if the bitstream is locked into the NVCM, that's hardware. If it's merely written in the rewritable SPI flash, that's software. It's not a property of the bitstream itself, it's a property of how it is stored.
Obviously the cost of micro-code bugs will sharply increase. That's kind of a feature though: now hardware vendors must be really careful.
Can you imagine the nightmare alternate universe of waking up to hear that Rowhammer is raging uncontrolled in the world, and the only way to fix it is to either return a data center full of affected products to the manufacturer or pay a specialist (who would probably be booked out for a long time to come) to come onsite?
Last I checked Rowhammer is raging uncontrolled in the world, and the only way to fix it is to swap the RAM with something that actually works. I’m not aware of any configurable firmware residing on RAM chips.
Yikes, lol. Way to put my foot in my mouth. For some reason I was thinking it was fixed with software, but that was just a taxing mitigation that only lowered the chance of success. I stand corrected, we do in fact live in that nightmare world.
> Force hardware vendors to only sell hardware. If any software that can be changed remotely or by the user is off limits. Even firmware. Conversely, software vendors can only sell (or freely distribute) software.
So, I would go buy a smartphone at a shop, and then buy an OS to run on it at another shop? Or would it be allowed for a third party to integrate the two and sell me a working phone?
Also, would “any software that can be changed remotely or by the user is off limits” mean Intel/Samsung/… couldn’t sell CPUs with microcode installed, or even write microcode? It may be hard to legally define where the border between “software that’s part of the hardware” and “software.” lies.
> You'll get the necessary specs required to make it work on all OSes
I don’t see how that follows. Software company C could pay hardware company H to build hardware according to specs they give, with the specs under NDA, possibly even forbidding H to sell that hardware design to others than C.
I think banning trade secrets (https://www.wipo.int/tradesecrets/en/tradesecrets_faqs.html) on the interface between software and hardware, rather than splitting companies into hardware and software parts is the way to achieve your goals.
So, I would go buy a smartphone at a shop, and then buy an OS to run on it at another shop? Or would it be allowed for a third party to integrate the two and sell me a working phone?
Also, would “any software that can be changed remotely or by the user is off limits” mean Intel/Samsung/… couldn’t sell CPUs with microcode installed, or even write microcode? It may be hard to legally define where the border between “software that’s part of the hardware” and “software.” lies.
> You'll get the necessary specs required to make it work on all OSes
I don’t see how that follows. Software company C could pay hardware company H to build hardware according to specs they give, with the specs under NDA, possibly even forbidding H to sell that hardware design to others than C.
I think banning trade secrets (https://www.wipo.int/tradesecrets/en/tradesecrets_faqs.html) on the interface between software and hardware, rather than splitting companies into hardware and software parts is the way to achieve your goals.
> So, I would go buy a smartphone at a shop, and then buy an OS to run on it at another shop?
Good point, by default you would. Perhaps allowing some third party to bundle the two could be a nice convenience, but then we must make absolutely sure that they never sell the bundle for less than the separate parts, that would be anti-competitive.
Also, I'm sick of paying for a Windows copy I never use. I'd very much like to see the OEM deals Microsoft make with laptop vendors just die.
> Also, would “any software that can be changed remotely or by the user is off limits” mean Intel/Samsung/… couldn’t sell CPUs with microcode installed, or even write microcode?
Depends whether that microcode can be changed by the user or remotely, or if doing so basically means returning the CPU to the factory. If it can conveniently be changed, that's software, and the actual interface to the CPU is not the final ISA, but how to encode that micro-code to make the final ISA. If however the microcode is etched or locked, then it's part of the hardware.
Another example would be an FPGA implementation of a RISC-V core: if the bitstream is locked into the NVCM it can no longer be modified, and thus counts as hardware. But if it's in the easily rewritable SPI flash, then it's software, and it can't be bundled with the FPGA itself.
While I'm not absolutely certain my border is the right one, I believe it's at least one that can be fairly easily delimited.
> Software company C could pay hardware company H to build hardware according to specs they give, with the specs under NDA, possibly even forbidding H to sell that hardware design to others than C.
Correct, some trade secrets need to be banned. Even further, I would void all ISA related patents and copyright. Specifically, cloning the functionality of any piece of hardware should be allowed, similar to how the IBM PC was cloned.
Note thought that splitting the activities is still worth it: when software is bundled with the hardware, we still need exploitable specs. Banning trade secrets doesn't force vendors to disclose them, and even if they do disclose them, nothing forces them to make especially readable beyond regulatory mandate, and nothing forces them to simplify their hardware interfaces. Exposing hardware interfaces to the competition however may provide very strong incentive to improve not only the hardware, but it's programming interfaces as well.
Good point, by default you would. Perhaps allowing some third party to bundle the two could be a nice convenience, but then we must make absolutely sure that they never sell the bundle for less than the separate parts, that would be anti-competitive.
Also, I'm sick of paying for a Windows copy I never use. I'd very much like to see the OEM deals Microsoft make with laptop vendors just die.
> Also, would “any software that can be changed remotely or by the user is off limits” mean Intel/Samsung/… couldn’t sell CPUs with microcode installed, or even write microcode?
Depends whether that microcode can be changed by the user or remotely, or if doing so basically means returning the CPU to the factory. If it can conveniently be changed, that's software, and the actual interface to the CPU is not the final ISA, but how to encode that micro-code to make the final ISA. If however the microcode is etched or locked, then it's part of the hardware.
Another example would be an FPGA implementation of a RISC-V core: if the bitstream is locked into the NVCM it can no longer be modified, and thus counts as hardware. But if it's in the easily rewritable SPI flash, then it's software, and it can't be bundled with the FPGA itself.
While I'm not absolutely certain my border is the right one, I believe it's at least one that can be fairly easily delimited.
> Software company C could pay hardware company H to build hardware according to specs they give, with the specs under NDA, possibly even forbidding H to sell that hardware design to others than C.
Correct, some trade secrets need to be banned. Even further, I would void all ISA related patents and copyright. Specifically, cloning the functionality of any piece of hardware should be allowed, similar to how the IBM PC was cloned.
Note thought that splitting the activities is still worth it: when software is bundled with the hardware, we still need exploitable specs. Banning trade secrets doesn't force vendors to disclose them, and even if they do disclose them, nothing forces them to make especially readable beyond regulatory mandate, and nothing forces them to simplify their hardware interfaces. Exposing hardware interfaces to the competition however may provide very strong incentive to improve not only the hardware, but it's programming interfaces as well.
You know, computers that aren't smartphones do exist..
Nearly every non-Apple PC on the planet is sold with Windows preinstalled, yet Microsoft didn't manufacture them.
Nearly every non-Apple PC on the planet is sold with Windows preinstalled, yet Microsoft didn't manufacture them.
I really like this. Other than an upvote I would very much like to express my support for this idea and I hope someone with connections to the halls of power passes it on, there is a lot of merit to this. It would immediately result in hardware manufacturers having to document each and every input and output of their hardware if they expect any sales at all and it would also do an end run around various monopolies.
Check out the idiocy around Broadcomm's WiFi/Bluetooth drivers on the Mac, it's absolute insanity, there are so many of them that to install Linux on one of the machines with such a chipset you need to copy your drivers from the Mac operating system (if you still have it installed...) in order to give Linux the ability to load firmware onto the devices so that they can work. Three different files iirc.
Check out the idiocy around Broadcomm's WiFi/Bluetooth drivers on the Mac, it's absolute insanity, there are so many of them that to install Linux on one of the machines with such a chipset you need to copy your drivers from the Mac operating system (if you still have it installed...) in order to give Linux the ability to load firmware onto the devices so that they can work. Three different files iirc.
rather than "disallow vertical integration", start with "disallow lock-out". By all means, vertically integrate as much as you want but it should not be illegal for someone to take your hardware and use it for another purpose that you have no say in, or write and run software using your hardware without you having a say in that.
It would be more prudent indeed to just force hardware vendors to release the specs, and it would be even more prudent still to just disallow lock-out. I would start there like you suggest.
I do suspect however that we'd miss out on many benefits if we don't go all the way the way to disallowing vertical integration eventually. It's also something I rarely see spoken of.
I do suspect however that we'd miss out on many benefits if we don't go all the way the way to disallowing vertical integration eventually. It's also something I rarely see spoken of.
Yeah, someone on that Reddit thread said it right - force the companies to publish documentation for the interfaces. Let the hackers write the drivers without painful, slow and error-prone reverse engineering.
I wouldn't even go that far: by all means, don't publish your interfaces, but if someone reverse engineers them: legalize that. And don't offer tax cuts to companies that don't publish their schematics and interfaces.
terrible idea.
people buy apple products precisely because of how integrated they are. this idealism and desire to force companies to support everything (as much as i want gaming on mac/linux and drivers for things supported) is the single most dangerous idea that would completely ruin the user experience for millions.
people buy apple products precisely because of how integrated they are. this idealism and desire to force companies to support everything (as much as i want gaming on mac/linux and drivers for things supported) is the single most dangerous idea that would completely ruin the user experience for millions.
> this idealism and desire to force companies to support everything
I'm sorry, where did I proposed we do that? As far as I am aware my proposal would only force Apples to split itself in 2: a hardware company that sells top notch hardware (so top notch in fact that even the hardware interfaces are as clean and slick as an iPad's case), and a software company that sells a top-notch integrated software suite on whatever hardware they chose to support (and no other hardware).
This idea that Apple's hardware is somehow better because they don't publish their spec sounds incoherent to be honest. As is the idea that their software is better because it runs on company hardware. If there's still a company selling good hardware, one can still write good software for that particular hardware.
So… forcing hardware companies to support all software? Nope, though publishing their spec does automatically provide some level of support for arbitrary software. Forcing software companies to support all hardware? No more than they do now, possibly even less: hardware vendors will be incentivised to harmonise their respective interfaces to appeal to a maximum number of software vendors, so software vendors will be incentivised to support a relatively limited set of interfaces.
I'm sorry, where did I proposed we do that? As far as I am aware my proposal would only force Apples to split itself in 2: a hardware company that sells top notch hardware (so top notch in fact that even the hardware interfaces are as clean and slick as an iPad's case), and a software company that sells a top-notch integrated software suite on whatever hardware they chose to support (and no other hardware).
This idea that Apple's hardware is somehow better because they don't publish their spec sounds incoherent to be honest. As is the idea that their software is better because it runs on company hardware. If there's still a company selling good hardware, one can still write good software for that particular hardware.
So… forcing hardware companies to support all software? Nope, though publishing their spec does automatically provide some level of support for arbitrary software. Forcing software companies to support all hardware? No more than they do now, possibly even less: hardware vendors will be incentivised to harmonise their respective interfaces to appeal to a maximum number of software vendors, so software vendors will be incentivised to support a relatively limited set of interfaces.
Why split the company? What does that do?
I'm not proposing that we split companies. I proposing that no company that sells hardware be allowed to distribute software, and no company that distributes software be allowed to sell hardware. The Apple split is only a consequence of that. As would be the likely end of locked down game consoles, now that I think of it.
What I'm hoping to accomplish with this is: reduced or eliminated vendor lock-in, harmonisation and simplification of ISAs, the ability to support any hardware in any OS, and maybe even the the ability to actually write new OSes and see some real competition in this space.
Note one important component I haven't mentioned: ISA patents should be rendered null and void. Anyone should be allowed to design, make, and sell an ARM or x86 CPU without asking anyone's permission. Or a GPU clone, or a network card clone, etc. Without that we'll just strengthen monopolies, or maybe allow new ones to arise.
What I'm hoping to accomplish with this is: reduced or eliminated vendor lock-in, harmonisation and simplification of ISAs, the ability to support any hardware in any OS, and maybe even the the ability to actually write new OSes and see some real competition in this space.
Note one important component I haven't mentioned: ISA patents should be rendered null and void. Anyone should be allowed to design, make, and sell an ARM or x86 CPU without asking anyone's permission. Or a GPU clone, or a network card clone, etc. Without that we'll just strengthen monopolies, or maybe allow new ones to arise.
This is a rather amazing comment, I'm astonished by the bald-faced lie that you open your first paragraph with:
> I'm not proposing that we split companies.
Also you, only a couple comments up:
> As far as I am aware my proposal would only force Apples to split itself in 2: a hardware company that sells top notch hardware (so top notch in fact that even the hardware interfaces are as clean and slick as an iPad's case), and a software company that sells a top-notch integrated software suite on whatever hardware they chose to support (and no other hardware).
Which is it, split companies or don't split companies? You can't have it both ways. If you aren't proposing that we split companies then you can't propose we split Apple unless you want to be a pedantic twit and point out that that's just one company and not companies.
> I'm not proposing that we split companies.
Also you, only a couple comments up:
> As far as I am aware my proposal would only force Apples to split itself in 2: a hardware company that sells top notch hardware (so top notch in fact that even the hardware interfaces are as clean and slick as an iPad's case), and a software company that sells a top-notch integrated software suite on whatever hardware they chose to support (and no other hardware).
Which is it, split companies or don't split companies? You can't have it both ways. If you aren't proposing that we split companies then you can't propose we split Apple unless you want to be a pedantic twit and point out that that's just one company and not companies.
Listen to any pro-gun advocate: the goal is not to kill the bad guy, the goal is to stop the bad guy… though unfortunately sometimes this means reducing their blood pressure to zero.
The law as I propose it would not legally force Apple to split. They would have 3 alternatives: stop selling software, stop selling hardware, or split. They could fire half the company, but we all know what they would actually do. Same deals with banks: enforcing the separation between deposit and investment wouldn't force the banks to split, but we all know that in practice they would.
Understand here that splitting Apple is not my goal. My goal is to separate the activities, in the hope of fostering more competition and personal freedom.
The law as I propose it would not legally force Apple to split. They would have 3 alternatives: stop selling software, stop selling hardware, or split. They could fire half the company, but we all know what they would actually do. Same deals with banks: enforcing the separation between deposit and investment wouldn't force the banks to split, but we all know that in practice they would.
Understand here that splitting Apple is not my goal. My goal is to separate the activities, in the hope of fostering more competition and personal freedom.
But how would that actually work? Two companies have an agreement to work together and share specs between themselves?
Actually no that would defeat the point. There are a couple thing we need to do beyond separating hardware and software: the first is forbidding NDAs around hardware interfaces. If you sell hardware to someone, you cannot force them not to publish the manual.
The second is an interoperability mandate: reproducing the functionality of existing hardware (a CPU ISA, a GPU clone…) must be authorized, and all relevant copyright and patents ignored.
This doesn’t mean that we would end all partnerships. The hardware company can still send prototypes to the software company, so driver development can begin before the hardware gets production-ready. That kind of workflow is common today.
The second is an interoperability mandate: reproducing the functionality of existing hardware (a CPU ISA, a GPU clone…) must be authorized, and all relevant copyright and patents ignored.
This doesn’t mean that we would end all partnerships. The hardware company can still send prototypes to the software company, so driver development can begin before the hardware gets production-ready. That kind of workflow is common today.
So...why bother with the separation? Why not just publish the specs and let people copy your hardware work and be done?
> people buy apple products
People used to buy cocaine toothache drops and give them to children to get them to shut up. People used to send babies by post. Just because people like something doesn't mean it doesn't have terrible effects. [1]
> single most dangerous idea
I mean, sure after guns, drugs, superbugs, global nuclear war, climate change, super-plague produced by synthetic biology...
1 - https://www.irishtimes.com/life-and-style/health-family/coca...
People used to buy cocaine toothache drops and give them to children to get them to shut up. People used to send babies by post. Just because people like something doesn't mean it doesn't have terrible effects. [1]
> single most dangerous idea
I mean, sure after guns, drugs, superbugs, global nuclear war, climate change, super-plague produced by synthetic biology...
1 - https://www.irishtimes.com/life-and-style/health-family/coca...
the second is in reference to technology and customer experience, don’t be obtuse.
comparing apple’s integrated approach to cocaine drops for kids tells me all i need to know about your bias; consumers like apple products, they are privacy focused more then any commercial competitor and their chips and OS are better than anything else precisely because of their integration.
and people want those devices.
comparing apple’s integrated approach to cocaine drops for kids tells me all i need to know about your bias; consumers like apple products, they are privacy focused more then any commercial competitor and their chips and OS are better than anything else precisely because of their integration.
and people want those devices.
I get you in principle, but the company should still be allowed to sell hardware with some default software installed, because if I had to search for someone on the internet that wrote software for my specific smart TV, washing machine or whatever this becomes much more painful.
I would rather see a 'right to repair' extended to software bundled. Any device or software that can connect to a network or can be interfaced with in any way is prone to security (or any other) bugs, which the customer should have the right to fix themselves, because they bought it, and in order to do so, the company needs to hand out the source code and documentation for all their devices.
Also about vendor writing Linux drivers, you probably don't want them too, there are already vendor board support packages (BSP) out there that enabled their hardware on Linux, but those are overwhelmingly abysmal in quality.
What you rather want is for vendors to upstream their driver into the kernel, so that it is properly integrated, doesn't break the hardware of others and has a high quality, but that process is not something you can regulate and force.
I would rather see a 'right to repair' extended to software bundled. Any device or software that can connect to a network or can be interfaced with in any way is prone to security (or any other) bugs, which the customer should have the right to fix themselves, because they bought it, and in order to do so, the company needs to hand out the source code and documentation for all their devices.
Also about vendor writing Linux drivers, you probably don't want them too, there are already vendor board support packages (BSP) out there that enabled their hardware on Linux, but those are overwhelmingly abysmal in quality.
What you rather want is for vendors to upstream their driver into the kernel, so that it is properly integrated, doesn't break the hardware of others and has a high quality, but that process is not something you can regulate and force.
Of course your hardware would come with software installed! That software would simply be written by a separate company.
We already do this! HP didn't write Windows, but they sure as hell sell laptops with Windows preinstalled.
We already do this! HP didn't write Windows, but they sure as hell sell laptops with Windows preinstalled.
I still don't get how that would solve the issue of having no linux drivers.
Lets say I create a new GPU IP core, i give it to a third-party chip manifactorer to produce it, then that delivers it to a fourth-party to burn a privat key into the fuses, then a fifth party signs its firmware with that key, which contains checks that Windows is running in secure boot mode with Microsoft keys. And then it is sold to the end user via a distributor, which did't do any other work on it.
How would preventing a 'vertical' integration forbid that?
I would rather just regulate that users should be given the full specs and possibility to use their own keys, to allow them to run their own software on/with it without any feature gates to the hardware. This can be argued for as a right to repair or as giving devices a second life and thus reducing electronic waste.
Your rule would likely make the work of smaller companies and startups more difficult, if they have to hire a third-party to write the software. A solo dev might has to create two companies in order to create one product, that seems painful. I guess a lot of OSH projects would not be possible with that rule.
Lets say I create a new GPU IP core, i give it to a third-party chip manifactorer to produce it, then that delivers it to a fourth-party to burn a privat key into the fuses, then a fifth party signs its firmware with that key, which contains checks that Windows is running in secure boot mode with Microsoft keys. And then it is sold to the end user via a distributor, which did't do any other work on it.
How would preventing a 'vertical' integration forbid that?
I would rather just regulate that users should be given the full specs and possibility to use their own keys, to allow them to run their own software on/with it without any feature gates to the hardware. This can be argued for as a right to repair or as giving devices a second life and thus reducing electronic waste.
Your rule would likely make the work of smaller companies and startups more difficult, if they have to hire a third-party to write the software. A solo dev might has to create two companies in order to create one product, that seems painful. I guess a lot of OSH projects would not be possible with that rule.
vendor sw (hp, samsung, htc, gateway, dell) is some of the worst sw i’ve ever experienced.
i want safari, mail, and messages tyvm
i want safari, mail, and messages tyvm
Vendor software is the result of hardware companies attempting vertical integration.
Get rid of vertical integration, and the software job will be given to someone capable.
Get rid of vertical integration, and the software job will be given to someone capable.
Trying to leverage right to repair to apply to software, as a way to demand source for commercial apps is a huge stretch.
We live with such an extreme amount of vertical integration today that people actually believe it is benefiting them.
Every time I see an Amazon delivery truck, part of me dies inside.
Every time I see an Amazon delivery truck, part of me dies inside.
> either they only sell hardware in the EU, or they only sell software. Intel and microsoft would have no problem.
Intel has microcode.
Microsoft has Xbox which I'd guess would have issues getting game releases if excluded from a decent-sized market.
Also. My phone (hardware) came with an OS (software) already installed. As do other pre-assembled computers.
Intel has microcode.
Microsoft has Xbox which I'd guess would have issues getting game releases if excluded from a decent-sized market.
Also. My phone (hardware) came with an OS (software) already installed. As do other pre-assembled computers.
Microcode can be non-configurable.
I'm willing to sacrifice the business model of game consoles.
I hate OEM deals, it just propagates the current monopolies and oligopolies. I'm okay with forcing everyone to buy their phone or laptop separately from the OS.
I'm willing to sacrifice the business model of game consoles.
I hate OEM deals, it just propagates the current monopolies and oligopolies. I'm okay with forcing everyone to buy their phone or laptop separately from the OS.
> Microcode can be non-configurable.
Some of the Spectre bugs were patched via microcode.
That seems like a rather useful ability to have.
Some of the Spectre bugs were patched via microcode.
That seems like a rather useful ability to have.
It is a useful ability, and I’m still willing to sacrifice it. I’m afraid that allowing updatable firmware to be part of the hardware will just allow hardware companies to get sloppy, not to mention the freedom we could lose if that firmware is proprietary. If hardware is (by law) immutable, then it’s pretty clear it’d better work from day one. No last minute patch, it has to work, or it won’t sell.
This will drive up the costs, as well as the selling price, but if it means hardware will work out of the box more often than it does now I’m willing to pay that cost.
This will drive up the costs, as well as the selling price, but if it means hardware will work out of the box more often than it does now I’m willing to pay that cost.
So your saying apple would have to stop making operating systems?
Or are you saying Qualcomm would be required to not provide drivers?
This is a super dumb take, like beyond stupid, and I get that it’s directed at apple.
Here’s the thing: since day 1 apple has been a hardware company, and what makes hardware good or bad is often the software that drives runs it. That goes for every product apple makes.
The idea that you can remove one half of that from the other is beyond stupid.
Or are you saying Qualcomm would be required to not provide drivers?
This is a super dumb take, like beyond stupid, and I get that it’s directed at apple.
Here’s the thing: since day 1 apple has been a hardware company, and what makes hardware good or bad is often the software that drives runs it. That goes for every product apple makes.
The idea that you can remove one half of that from the other is beyond stupid.
The same people who are currently working on hardware for Apple would be working for a new company that makes hardware, and the new Apple Software Co. would continue to work with those people just as closely as they always have.
The only difference is that Microsoft Windows, Linux kernel devs, etc. would also be able to work with that hardware company to get their OS working on that hardware.
The hardware company would not be allowed to keep secrets between itself and Apple.
The only difference is that Microsoft Windows, Linux kernel devs, etc. would also be able to work with that hardware company to get their OS working on that hardware.
The hardware company would not be allowed to keep secrets between itself and Apple.
> * So your saying apple would have to stop making operating systems?*
No. That's only 1 of 3 alternatives, the other 2 being stop making hardware, or split in 2.
> Or are you saying Qualcomm would be required to not provide drivers?
Yes. They'd have to provide an actual manual for a change.
> This is a super dumb take, like beyond stupid, and I get that it’s directed at apple.
It's not. Many more would have to rethink their entire business model.
No. That's only 1 of 3 alternatives, the other 2 being stop making hardware, or split in 2.
> Or are you saying Qualcomm would be required to not provide drivers?
Yes. They'd have to provide an actual manual for a change.
> This is a super dumb take, like beyond stupid, and I get that it’s directed at apple.
It's not. Many more would have to rethink their entire business model.
This would be terrible for specialized hardware, such as assistive technology. Open source software doesn’t really exist for it because there is simply no interest.
We could carve out exceptions for specific niches. Ugly, but could work.
Who says the software has to be open? It would be better for sure, but companies may be interested in selling software for assistive technologies.
Interest may go up if the barrier to entry lowers. Undocumented hardware is quite the turn off.
Who says the software has to be open? It would be better for sure, but companies may be interested in selling software for assistive technologies.
Interest may go up if the barrier to entry lowers. Undocumented hardware is quite the turn off.
You can't really sell software for running a braille display on its own, for example. As for interest going up, I doubt that very much, as linux is still lacking good vision accessibility, such as a screen reader that doesn't brake with every update to the gnome desktop. windows and macOS figured that one out years ago, and the only decent open source screen reader is windows only.
Braille displays were precisely on my mind: there is a sizeable community of blind programmers out there. And realistically: how hard could it be to operate such a device? The thing is basically a super-low resolution screen with an abysmal refresh rate. A sufficient design could be a serial interface where you send all the pixels in a single packet. Or perhaps we could go fancy with modifying single characters or shifting the display left or right… done right, writing a driver for this thing is nearly trivial, to the point of being possible in user-space.
One reason for the blight of the blind here is the ludicrous complexity of the software, much of it comes from the ludicrous complexity and diversity of hardware interfaces, such that there is no competition and everything is terrible.
Most people however sharply underestimate the mountain of avoidable complexity we've accreted over the decades. I would situate it between 99% and 99.9% for personal computing. No silver bullet perhaps, but I know almost for a fact that there's enough silver dust around to gather 2 or 3 bullets.
One reason for the blight of the blind here is the ludicrous complexity of the software, much of it comes from the ludicrous complexity and diversity of hardware interfaces, such that there is no competition and everything is terrible.
Most people however sharply underestimate the mountain of avoidable complexity we've accreted over the decades. I would situate it between 99% and 99.9% for personal computing. No silver bullet perhaps, but I know almost for a fact that there's enough silver dust around to gather 2 or 3 bullets.
What if we allow hardware manufacturers to create software to run their hardware but open the schematics and make the hardware hackable such that others can run software they want? That seems like a decent compromise because there’s very little margin in hardware alone and if you force hardware makers to go that route pretty soon there won’t be any because they’ll all have gone out of business.
Hardware manufacturers can’t all go out of business. We need hardware at some point. Some might, but what I’m proposing would drive up costs for everyone. Most likely, prices will just go up a little bit.
Allowing hardware manufacturers to ship their own software, even if that software must be free, even if the hardware specs must be released, will still allow them to ship crappy hardware interfaces and compensate that with bloated software. I’m also afraid some manufacturer would try to game the system, with, say, tweaking the instruction set of every new GPU so third party drivers can’t really keep up.
Allowing hardware manufacturers to ship their own software, even if that software must be free, even if the hardware specs must be released, will still allow them to ship crappy hardware interfaces and compensate that with bloated software. I’m also afraid some manufacturer would try to game the system, with, say, tweaking the instruction set of every new GPU so third party drivers can’t really keep up.
But if it’s open installing your own, open, on-bloatware software would be easy. That’s not the case now … but it could be.
Hardware vendors then that install the vanilla, non-bloatware software will be seen as a feature. You can see this now: Google ships vanilla Android whereas some of the Android phone manufacturers ship it with their own crapware. Or on the other end of the spectrum Apple ships MacOS without advertising garbage but vanilla Windows ships games and ads in the start menu.
So I don’t really see how your argument stands.
Hardware vendors then that install the vanilla, non-bloatware software will be seen as a feature. You can see this now: Google ships vanilla Android whereas some of the Android phone manufacturers ship it with their own crapware. Or on the other end of the spectrum Apple ships MacOS without advertising garbage but vanilla Windows ships games and ads in the start menu.
So I don’t really see how your argument stands.
Yeah, the part about gaming the system may not actually apply.
Now, bloated software is still bloated software, even if it's open. I guess that with the sources the community can make it better, but there's still a limit to how well they can do: the hardware interface itself. It's a long tradition in hardware design to ship crappy interfaces and just say the software folks will make it nice. But if all you ship is the hardware, the interfaces have to be nice, else it will be harder to program for, and that definitely influences the ultimate success of the platform. See game consoles, I believe those who have a reputation of being hard to program tend to sell less (because they have fewer or worse games).
Now, bloated software is still bloated software, even if it's open. I guess that with the sources the community can make it better, but there's still a limit to how well they can do: the hardware interface itself. It's a long tradition in hardware design to ship crappy interfaces and just say the software folks will make it nice. But if all you ship is the hardware, the interfaces have to be nice, else it will be harder to program for, and that definitely influences the ultimate success of the platform. See game consoles, I believe those who have a reputation of being hard to program tend to sell less (because they have fewer or worse games).
> Now the complicated part is how to define a company. We don't want a single company to just split itself into 2 legal entities
HN routinely seems unaware that this is a totally solved problem in the tax law of virtually every industrialized country.
In the US, for example, the phrase is "Common Control": https://www.law.cornell.edu/cfr/text/26/1.414(c)-2
All sorts of modern tax schemes would have truck-sized loopholes without a rigorous definition of Common Control. It's already in the tax code of every industrialized country (possibly under a different name). All you have to do is reference it. The necessary definitions have been in the tax codes since the 1980s.
I'm kind of annoyed at how often this "but but but two companies with overlapping owners yadda yadda" comes up. Go ahead try that on the IRS and see how it works out for you.
HN routinely seems unaware that this is a totally solved problem in the tax law of virtually every industrialized country.
In the US, for example, the phrase is "Common Control": https://www.law.cornell.edu/cfr/text/26/1.414(c)-2
All sorts of modern tax schemes would have truck-sized loopholes without a rigorous definition of Common Control. It's already in the tax code of every industrialized country (possibly under a different name). All you have to do is reference it. The necessary definitions have been in the tax codes since the 1980s.
I'm kind of annoyed at how often this "but but but two companies with overlapping owners yadda yadda" comes up. Go ahead try that on the IRS and see how it works out for you.
I should have thought of those issues, thank you. I’ll look up this "Common Control".
An alternate paradigm? 20 years ago I mused over a law called the "Operating System Fairness Act", designed to level the playing field, mostly for smaller OS's. It's nowhere as revolutionary as separating hw development from sw development, but may thus be more realistic. One clause (of maybe six) concerned "Forced licensing of must-have drivers, algorithms, codecs, file formats, etc. to any viable OS, and for a price that market can bear".
At the time I was thinking of technologies like the Unisys GIF patent, Flash, various audio and video codecs, and peripheral drivers. If not having a technology makes an OS vitally less useful and appealing to a user then there's potentially a path to developer documentation. Who decides? I think the current system for DMCA exemptions works pretty well (noting that I despise the DMCA), so maybe a branch of the US Copyright Office or another government's similar branch? A viable OS is one with a notable following and which can use the technology. If I write RadiumOS for myself, that doesn't count. Likewise Widevine for the Atari 800 is out. But Linux anything would, the BSD family, and Amiga, BeOS/Haiku, etc. would have a fair shot. Making a free, public developers kit is always better, but offering an NDA to a developer representing each OS family would likely be common. No, it wouldn't be an instantaneous process, yes, there would be paperwork and maybe a lawyer involved, but the burden has to be bearable for each OS/developer. If you're Apple wanting the MS Office file formats, MS is allowed to charge a not insignificant amount, but if you're a free, open source OS, then the cost would be either free or nearly so. Not every vendor in a field would be cracked open. If AMD is very friendly to developers, then Nvidia could keep their video drivers proprietary. With all the OSS available today vs. 20 years ago, something like this is maybe a bit less useful, but IMHO still a significant step forward, and a hedge against companies suddenly taking their specs private.
At the time I was thinking of technologies like the Unisys GIF patent, Flash, various audio and video codecs, and peripheral drivers. If not having a technology makes an OS vitally less useful and appealing to a user then there's potentially a path to developer documentation. Who decides? I think the current system for DMCA exemptions works pretty well (noting that I despise the DMCA), so maybe a branch of the US Copyright Office or another government's similar branch? A viable OS is one with a notable following and which can use the technology. If I write RadiumOS for myself, that doesn't count. Likewise Widevine for the Atari 800 is out. But Linux anything would, the BSD family, and Amiga, BeOS/Haiku, etc. would have a fair shot. Making a free, public developers kit is always better, but offering an NDA to a developer representing each OS family would likely be common. No, it wouldn't be an instantaneous process, yes, there would be paperwork and maybe a lawyer involved, but the burden has to be bearable for each OS/developer. If you're Apple wanting the MS Office file formats, MS is allowed to charge a not insignificant amount, but if you're a free, open source OS, then the cost would be either free or nearly so. Not every vendor in a field would be cracked open. If AMD is very friendly to developers, then Nvidia could keep their video drivers proprietary. With all the OSS available today vs. 20 years ago, something like this is maybe a bit less useful, but IMHO still a significant step forward, and a hedge against companies suddenly taking their specs private.
In practice, what fines would hardware manufacturers be held liable for for any bugs in their specifications? How do we conclude that, yes, a hardware manufacturer hasn’t lived up to the regulation? Perhaps the operating system is “using it wrong”. Do governments have entire departments running tests on these devices?
That's in part why I didn't propose that we force manufacturers to specify their products, but simply make sure that if they don't, nobody would want to use their product. Who would buy a CPU they don't know the ISA of?
Forcing the separation between software and hardware companies may be more stringent, but it may be simpler to enforce, and likely even more effective at making sure the hardware is humanely specified than direct regulation would be.
Forcing the separation between software and hardware companies may be more stringent, but it may be simpler to enforce, and likely even more effective at making sure the hardware is humanely specified than direct regulation would be.
[deleted]
It's a cool idea, but where do you draw the line? Where do you place something like microcode? Depending on how you design a computer, you can have software almost all the way down.
https://news.ycombinator.com/item?id=37731829
I draw the line at "can it be updated without returning to the factory?"
If microcode can be updated by the user (or remotely by Intel), it’s software. If it’s immutable then its hardware. If an FPGA bitstream (say a RISC-V soft core) is locked into the FPGA’s NVCM, then it can no longer be modified, and it counts as hardware. If however it is merely stored in the SPI flash and can be modified, then it’s software.
I draw the line at "can it be updated without returning to the factory?"
If microcode can be updated by the user (or remotely by Intel), it’s software. If it’s immutable then its hardware. If an FPGA bitstream (say a RISC-V soft core) is locked into the FPGA’s NVCM, then it can no longer be modified, and it counts as hardware. If however it is merely stored in the SPI flash and can be modified, then it’s software.
I know no other way to say this. But this idea is just dumb. The entire value proposition would be worse for everyone. Software and hardware integration is what makes a product better.
> Software and hardware integration is what makes a product better.
... Except for the times when it makes things worse.
... Except for the times when it makes things worse.
And when would that be?
I suppose I should say forced integration; ex. see the recent nonsense with Hue deciding you need an account to control your local lightbulbs, which isn't a problem with third party apps. I'm generally skeptical of vertical integration because of lock in, but if it's not forced it's less obviously bad.
If only adults had agency to make their own decisions about lightbulbs without depending on the government…
What decision would those adults make? The vendor changed the deal after the sale.
If only adults had the agency to make their own decision about how to deal with corporate malfeasance.
Like back in the good old days when lynching was an option. /s
Like back in the good old days when lynching was an option. /s
Yes because choosing which light bulb to use is analogous to lynching.
You realize it was the government that enforced Jim Crow laws, against miscegenation, and “sodomy” (ie non heterosexual sex).
Not to mention the “War on Drugs”, civil forfeiture and using eminent domain to take away private property to give to another company.
I can much easier choose which corporation to use than the government.
And looking at some of the ideas on this submission, I damn sure don’t want some internet geeks deciding what products I can use and how they are made.
You realize it was the government that enforced Jim Crow laws, against miscegenation, and “sodomy” (ie non heterosexual sex).
Not to mention the “War on Drugs”, civil forfeiture and using eminent domain to take away private property to give to another company.
I can much easier choose which corporation to use than the government.
And looking at some of the ideas on this submission, I damn sure don’t want some internet geeks deciding what products I can use and how they are made.
The lightbulbs were changed after sale, consumer choice is irrelevant here.
You realize that said lynching was very often institutionalized and encouraged by local authorities? Do you think corporations were the ones doing the lynching?
Even in the context of the extreme hyperbole of this entire comment chain, your analogy is pretty extreme and does not make sense. Jim Crow laws weren't stopped by regulation, they were stopped by dismantling government enforced rules.
And yes, it might sound crazy but individuals can actually decide what light bulb to buy or what computer to buy. And thinking so isn't even remotely libertarian or hyper capitalist. We aren't talking about labor rights or healthcare or other very asymmetric power imbalances. People just like to buy computers and devices that nerds and euh, let's say, activists dislike or ideologically disagree with. It doesn't make them sheep, or stupid, or ignorant.
Even in the context of the extreme hyperbole of this entire comment chain, your analogy is pretty extreme and does not make sense. Jim Crow laws weren't stopped by regulation, they were stopped by dismantling government enforced rules.
And yes, it might sound crazy but individuals can actually decide what light bulb to buy or what computer to buy. And thinking so isn't even remotely libertarian or hyper capitalist. We aren't talking about labor rights or healthcare or other very asymmetric power imbalances. People just like to buy computers and devices that nerds and euh, let's say, activists dislike or ideologically disagree with. It doesn't make them sheep, or stupid, or ignorant.
Yes, and I'd also like hardware and software companies to not have access to my data. E.g. Google should be split into hardware, software, and data companies.
You'd have to define "hardware" in a rather interesting way for that to have any hope of working.
Consider any sort of user-facing device (say, an electronic toy, or a music performance device, or for that matter, even a phone). These are all aggregates of hardware made by other companies. Yet they are also hardware. Being unable to develop such devices along with the firmware that runs them would make it more or less impossible to develop them at all. So where does "hardware" stop and "device" start?
Consider any sort of user-facing device (say, an electronic toy, or a music performance device, or for that matter, even a phone). These are all aggregates of hardware made by other companies. Yet they are also hardware. Being unable to develop such devices along with the firmware that runs them would make it more or less impossible to develop them at all. So where does "hardware" stop and "device" start?
Let's say one wants to make hardware made of 3 pieces of hardware that talk to each other. They may need to write firmware to do that. At a first approximation, I would say one of the following should apply:
Either the firmware can be modified by the user, or remotely, in which case it should not be shipped.
Or it is an implementation detail of the communication between the 3 pieces of hardware, not reasonably modifiable without returning the whole thing to the factory, in which case that firmware is actually part of the 3-piece hardware, and can be shipped.
Either the firmware can be modified by the user, or remotely, in which case it should not be shipped.
Or it is an implementation detail of the communication between the 3 pieces of hardware, not reasonably modifiable without returning the whole thing to the factory, in which case that firmware is actually part of the 3-piece hardware, and can be shipped.
But it is often both. Just because it is essential for proper operation and therefore an implementation detail, doesn't mean it cannot be updated.
Even a device as trivial as a keyboard, mouse, or SSD drive has firmware which can be updated. Shipping them without firmware would be completely ludicrous, and you'd basically buy a fancy brick. Hell, you need to flash firmware onto it in the factory to make future updates by the user possible!
Even a device as trivial as a keyboard, mouse, or SSD drive has firmware which can be updated. Shipping them without firmware would be completely ludicrous, and you'd basically buy a fancy brick. Hell, you need to flash firmware onto it in the factory to make future updates by the user possible!
The prudent manufacturer makes sure that some of the firmware is truly immutable, to prevent bricking the device if some firmware version is botched enough.
I'm not proposing that no hardware ships with firmware. I'm proposing the hardware manufacturer choses: enable updates and don't ship the parts that can be updated, or disable updates entirely.
I'm not proposing that no hardware ships with firmware. I'm proposing the hardware manufacturer choses: enable updates and don't ship the parts that can be updated, or disable updates entirely.
interesting premise, but i ultimately think this would be worse for the tech by forcing them to play in a limited playing field that doesn't have parallel in other businesses, does it?
Oh but it does have parallel in other businesses. Splitting oil companies being one of the oldest examples. Rockefeller reportedly became richer as a result, so it wasn't even a socialist move.
Another feature of forbidding vertical integration is that is prevents companies from competing with their own customers.
Another feature of forbidding vertical integration is that is prevents companies from competing with their own customers.
i don't think your examples are great examples
but i immediately disagreed with myself after posting because i don't think hospitals can make their own drugs. or rather, if a drug manufacturer owned a hospital and a health insurance company this might be considered a conflict of interest
i still don't think its a great example given this one comes from an ethical basis but this is more apt
but i immediately disagreed with myself after posting because i don't think hospitals can make their own drugs. or rather, if a drug manufacturer owned a hospital and a health insurance company this might be considered a conflict of interest
i still don't think its a great example given this one comes from an ethical basis but this is more apt
I have yet to really flesh out my proposal, but ethics does come into play. Walled gardens for instance, are in part enabled by hardware/software bundles.
[deleted]
Sounds great - there’s just one problem: The desktop applications will still almost entirely be written for Windows. Or MacOS. Or Android.
So yay, you can buy a device… and 99% of people will install the same OS on it that it would have originally come with anyway. What’s the point here?
You’d have to say desktop apps must support all competing operating systems. But, hah, good luck with that.
So yay, you can buy a device… and 99% of people will install the same OS on it that it would have originally come with anyway. What’s the point here?
You’d have to say desktop apps must support all competing operating systems. But, hah, good luck with that.
The hope is that hardware interfaces harmonise to the point where writing a new OS becomes actually possible. Right now it's not, there simply is too much diversity, and that's before we talk about all the quirks in hardware APIs vendors currently hide under the software rug. Then maybe, just maybe, we could start some real competition on the OS space.
Even if that doesn't happen I would be happy with the end of vendor lock-in.
Even if that doesn't happen I would be happy with the end of vendor lock-in.
More likely they would require companies to publish specs suitable for driver authors. I’ve always thought that companies treating their register configuration and I/O offsets as a trade secret is ridiculous.
This. Linked post is a misconception of how EU actually work. They will never "hardcode" something like "linux drivers" into the law. But, in theory, they could write a law like "If you want to sell your device in the EU, you must publish a freely available technical spec with enough level of detail to write a functioning driver".
This would not even be something completely new.
It would just revert the market for computer peripherals and interfaces to how it was before the launch of MS Windows 95.
In the MS-DOS days everything was provided with detailed technical information, so you could write your own device drivers, for any operating system.
This ended in 1995, after which most hardware vendors stopped providing documentation and replaced it with MS Windows device drivers.
It would just revert the market for computer peripherals and interfaces to how it was before the launch of MS Windows 95.
In the MS-DOS days everything was provided with detailed technical information, so you could write your own device drivers, for any operating system.
This ended in 1995, after which most hardware vendors stopped providing documentation and replaced it with MS Windows device drivers.
The days spent trying to get drivers to work and deal with their bugs and conflicts were seriously grim.
Do you realize how much the PC ecosystem sucked back then?
Do you have any point of substance to make here? What do you mean by it sucked, and how does that relate to publishing driver specs?
Yes, it’s a dumb idealistic idea that never worked in practice. Geeks spent forever trying to get crappy drivers working IRQ conflicts fixed, etc.
It wasn’t until Windows 95 and WinHec and “Plug and Play” that x86 based PCs became usable for the mass market
It wasn’t until Windows 95 and WinHec and “Plug and Play” that x86 based PCs became usable for the mass market
That was largely hardware issues. In particular without a way to negotiate between drivers conflicts were doomed to happen regardless of who was writing the driver, especially with the relatively small number of resources to pull from.
And yet, Apple’s integrated solution didn’t have those issues with the Apple // in 1977 yet alone the Mac II with Nubus in 1987.
Yeah, PC clones were a right mess. The ISA bus was extremely primitive, even by the standards of the day. There is a reason the PCI bus was such a breath of fresh air.
Maybe, but that's a separate matter from publishing specs that would let someone write a driver.
How well did that work in the past when for profit companies had a motivation to write good drivers? You think it’s going to be a seamless mass market experience this time?
I don't see the connection. Two things appear to be true: 1. In the past, it was common to publish actual specs for talking to hardware. 2. In the past, drivers often sucked. You appear to be claiming that the first thing caused the second, but I can't see any reason for that to follow. It's not like hardware manufacturers couldn't, or indeed didn't, write their own official drivers, and on the other hand there's no reason to believe that a 3rd-party driver written using proper hardware docs wouldn't work well. In fact, it's quite reasonable to suggest that the improvement in quality is entirely tied to overall architecture improvements, mostly (as cousin comments point out) device enumeration standards and possibly OS improvements (preemptive multitasking and memory protection).
And how slow was the evolution of both Windows and the entire ecosystem compared to Apple that could release an OS, the hardware and the drivers simultaneously? When Apple releases new hardware it can upgrade everything in tandem. It’s especially apparent now that everything Apple sells runs some variant of the same processor from the AirPods, Watches, tablets, TV set top boxes, phones and even monitors?
And what would stop Apple from doing that while also having to publish documentation?
And the ability to use such a driver. Hell, even the spec wouldn't be such a strong requirement as people can reverse them. The issue is usually the firmware and signature checks.
This sounds much more reasonable to me. Banning unnecessary hardware DRM and requiring specs to get published would be a much more effective way to stimulate the market. Forcing manufacturers to publish Linux drivers would probably just end up in low-effort support on either side. The last person I want writing my Linux drivers is someone who doesn't care.
Yeah, you know it would end up with the manufacturers just releasing a binary driver for exactly one point release of the kernel and calling that box checked. Might even just be some NDIS thing where they wrap the Windows driver to get it mostly working.
This would be my expectation too. Though I’d think you’d need to go one further - hardware manuals AND a license to redistribute any necessary firmware binaries - the latter has been an issue with Nouveau for example.
In fact I think manuals are probably better in a lot of cases, OEM drivers are routinely terrible.
In fact I think manuals are probably better in a lot of cases, OEM drivers are routinely terrible.
Intel publish datasheets which describe their network interface cards to this level. It's fantastic, literally anybody can write a driver for an Intel NIC for any OS. You can also debug existing drivers when you get strange hardware issues, which is part of my job. No other networking vendor does this.
Why should EU give preference to Linux over any other operating system?
A much more EU "style" directive would be to force the companies to release enough of the specs so anyone can write the driver if they want to.
A much more EU "style" directive would be to force the companies to release enough of the specs so anyone can write the driver if they want to.
A much more EU style directive would be to force all operating systems to use the Linux 5.1 kernel.
A much more EU style directive would be to force all operating systems to ask on every boot: Do you consent for this OS to store files on your hard drive?
No, the EU version of that would be requiring OSs to ask before using a disk, and certain proprietary OSs deciding to spam the user with requests on every boot until they consent - at which point suddenly the OS can magically remember that preference - and then pretending that the law forced them to do that even though it said no such thing.
That's also fine.
> Could EU force hardware manufacturers to make working drivers for Linux?
> Why are these companies like intel, Razer, nvidia or AMD..
The question makes no sense. As one of the Reddit comment says: Intel and AMD are among the biggest contributors to the Linux kernel.
The real-world is pretty much powered by millions of Linux machines running on Intel or AMD hardware (for the most part). Try replacing that with Windows servers and their "working drivers" and then we talk.
> Why are these companies like intel, Razer, nvidia or AMD..
The question makes no sense. As one of the Reddit comment says: Intel and AMD are among the biggest contributors to the Linux kernel.
The real-world is pretty much powered by millions of Linux machines running on Intel or AMD hardware (for the most part). Try replacing that with Windows servers and their "working drivers" and then we talk.
What could work well is forcing manufacturers to release hardware documentation that is sufficiently detailed to allow developing drivers without reverse engineering.
Perhaps forcing them to do so a couple of years after hardware release, so that it does not interfere too much with trade secrets.
This would avoid perfectly functional hardware to go to the landfill because of no further software support, and it would also prevent incredibly time-consuming reverse engineering efforts.
Perhaps forcing them to do so a couple of years after hardware release, so that it does not interfere too much with trade secrets.
This would avoid perfectly functional hardware to go to the landfill because of no further software support, and it would also prevent incredibly time-consuming reverse engineering efforts.
what about releasing the source code of drivers/firmware after the official support ended
Azure, and all the games being emulated on Proton as means to make SteamDeck a viable product.
Remember how old electrical appliances used to come with full circuit diagrams to help repair them? That's one way to go about this is - force hardware manufacturers to provide complete device and technical specification (e.g. https://datasheets.raspberrypi.com/rp2040/rp2040-datasheet.p... (PDF)) for every hardware they manufacture. This should enable any competent system developers to create the drivers for it, for any software system. (After all, realistically, we cannot force hardware manufacturers to create drivers for every OS in the world).
One major objection we can expect is that sometimes hardware manufacturers deliberately cripple their products through their drivers. This enables them to sell a cheaper version, that is crippled, and a costlier one that isn't. One example of this is Intel and AMD manufacturing a quad-core processor, but selling the same processor as dual-core and quad-core (remember how AMD allowed you to "unlock" extra cores on their processors?). I think NVIDIA also limits some of their graphic card with their drivers, to sell the same hardware at different prices.
One major objection we can expect is that sometimes hardware manufacturers deliberately cripple their products through their drivers. This enables them to sell a cheaper version, that is crippled, and a costlier one that isn't. One example of this is Intel and AMD manufacturing a quad-core processor, but selling the same processor as dual-core and quad-core (remember how AMD allowed you to "unlock" extra cores on their processors?). I think NVIDIA also limits some of their graphic card with their drivers, to sell the same hardware at different prices.
Drivers… I don’t know if I could sign on for that for the following reasons:
1. The burden it would put on smaller manufacturers and companies (every little regulation adds up), especially difficult considering the comparative lack of qualified developers
2. Drivers != Quality, Upstreamable Drivers. Making the judgements of Linux maintainers legally binding is a bad idea. Case in point: Apple has Linux drivers internally, they’re just not complete or upstreamable. You would be forced to fight the Linux maintainers (and the power trips they already have!) in order to legally sell your product.
3. If we can force companies to support Linux, why not force all websites to support Firefox? Why not force all desktop programs like Adobe to support Linux? Etc…
4. What about poor FreeBSD? Serenity OS? That guy who still loves OS/2?
1. The burden it would put on smaller manufacturers and companies (every little regulation adds up), especially difficult considering the comparative lack of qualified developers
2. Drivers != Quality, Upstreamable Drivers. Making the judgements of Linux maintainers legally binding is a bad idea. Case in point: Apple has Linux drivers internally, they’re just not complete or upstreamable. You would be forced to fight the Linux maintainers (and the power trips they already have!) in order to legally sell your product.
3. If we can force companies to support Linux, why not force all websites to support Firefox? Why not force all desktop programs like Adobe to support Linux? Etc…
4. What about poor FreeBSD? Serenity OS? That guy who still loves OS/2?
> 3. If we can force companies to support Linux, why not force all websites to support Firefox? Why not force all desktop programs like Adobe to support Linux? Etc…
...Although I agree that there are questions about required effort and breadth of support and burden to smaller companies, every one of those sound like wonderful outcomes to me.
...Although I agree that there are questions about required effort and breadth of support and burden to smaller companies, every one of those sound like wonderful outcomes to me.
Don't forget TempleOS, lest you be religiously intolerant.
As others have pointed out why single out linux? Why not BSD? And second which linux? 4.14? 5.10? 6.2? Can they release it for linux 2.7 and call it a day afterwards? Supporting linux requires effort and money. How would you go about defining "reasonable effort" at supporting linux. If it breaks every month? every year? Enforcing this simply would turn out to become a nightmare. I think a better approach would look like what jandrese said in this thread. Force them to publish the specs so other companies or individuals can write open source drivers for the hardware.
> being forced to make drivers that work equally in linux, windows and even macOS
That is almost a recipe for drivers built on hardware abstraction layers (HALs), so vendors can use literally the same code on every platform. That, of course, results in a bunch of unnecessary HAL code being added -- unnecessary from the OS point of view, which already has perfectly good hooks for all the stuff a driver needs. That's the reason Linux does not accept HALs into the mainline kernel.
What often happens on Linux is vendors will then move their HAL and drivers into userspace, interfacing with the kernel via a shim instead. This has the side effect of no longer needing to open-source the driver code at all, since it's not linked into the kernel. Look how that works out!
In case of Android, it was literally Google that did the HAL/shim work, giving vendors a pass on open sourcing or mainlining their drivers.
That is almost a recipe for drivers built on hardware abstraction layers (HALs), so vendors can use literally the same code on every platform. That, of course, results in a bunch of unnecessary HAL code being added -- unnecessary from the OS point of view, which already has perfectly good hooks for all the stuff a driver needs. That's the reason Linux does not accept HALs into the mainline kernel.
What often happens on Linux is vendors will then move their HAL and drivers into userspace, interfacing with the kernel via a shim instead. This has the side effect of no longer needing to open-source the driver code at all, since it's not linked into the kernel. Look how that works out!
In case of Android, it was literally Google that did the HAL/shim work, giving vendors a pass on open sourcing or mainlining their drivers.
> What often happens on Linux is vendors will then move their HAL and drivers into userspace, interfacing with the kernel via a shim instead. This has the side effect of no longer needing to open-source the driver code at all, since it's not linked into the kernel. Look how that works out!
It doesn't stop anyone else from writing better drivers (i.e. the thing they already do) but decouples things so that people can at least update their kernel while keeping their drivers. So, win-win.
It doesn't stop anyone else from writing better drivers (i.e. the thing they already do) but decouples things so that people can at least update their kernel while keeping their drivers. So, win-win.
I've swung over the last few years from thinking it's manufacturers' fault to realising that most of the fault here lies with the linux project itself. They're the ones who have normalised constant churn and thus needing to keep drivers for hardware, sometimes many years old, up to date year after year or even month after month. After seeing the churn mentality affect everything mainly spreading from web dev circles to the rest of the ecosystem, it's hard not to identify that trend as having been the norm in the kernel for decades.
I've only come to realise that blaming manufacturers for failing to keep up to date with a constantly moving target was totally unfair.
I've only come to realise that blaming manufacturers for failing to keep up to date with a constantly moving target was totally unfair.
> I've only come to realise that blaming manufacturers for failing to keep up to date with a constantly moving target was totally unfair.
The intention of keeping the kernel moving and unstable at the inner layer is intentional: it is a negative incentive to make people at least publish documentation, if not outright publish driver source code, in the open.
The userspace-facing layer of Linux has remained very VERY stable over the decades, no matter the consequences [1].
[1] https://archive.fosdem.org/2016/schedule/event/design_linux_...
The intention of keeping the kernel moving and unstable at the inner layer is intentional: it is a negative incentive to make people at least publish documentation, if not outright publish driver source code, in the open.
The userspace-facing layer of Linux has remained very VERY stable over the decades, no matter the consequences [1].
[1] https://archive.fosdem.org/2016/schedule/event/design_linux_...
> They're the ones who have normalised constant churn and thus needing to keep drivers for hardware, sometimes many years old, up to date year after year or even month after month.
That's exactly why you should mainline your code. Then people refactoring other subsystems will fix your code for you.
That's exactly why you should mainline your code. Then people refactoring other subsystems will fix your code for you.
Sorry but your claim is that Linux is the driver of churn?! That’s a wild thought.
Hard for me to imagine how Linux could be more responsible that the incentives of capitalism, eg planned obsolescence, the race to the bottom, and consumer demand for more and better cameras, storage, etc.
Hard for me to imagine how Linux could be more responsible that the incentives of capitalism, eg planned obsolescence, the race to the bottom, and consumer demand for more and better cameras, storage, etc.
I didn't claim that it birthed it but that the same issue I see in the unsustainability in software today is literally the norm in the kernel. If it's bad in one domain, perhaps it's reasonable to question its value in the other.
Yes, ideology has a price.
Please no.
The idea is rooted in idealism, but absolute crap will be produced in reality.
The idea is rooted in idealism, but absolute crap will be produced in reality.
I don't think the law being Linux-specific would be right.
But making them release comprehensive documentation / specs and forbidding them from requiring signed firmware would be something.
But making them release comprehensive documentation / specs and forbidding them from requiring signed firmware would be something.
What I want should be a right and someone forced to provide it to me?
Cool, until I'm the one forced to do something, then it's exploitation.
Of course they could. Will they? Probably not. Should they? Maybe. Do I want them to? Hell yeah. Let's light this firecracker.
Any "vendor lock in" practices should be considered as monopoly practices. And anti-monopoly laws are already here in EU. Just a matter of interpretation of what falls to monopoly.
This is why society is screwed.
All these people don't understand the dangers of socialism. History is bound to repeat itself.
The cost of the EU forcing everyone to adopt a standard is that next time a new manufacturer need to enter the market, it will have to cater to the need of the 1% (of which I am part, I'd love to have drivers for linux for everything).
Who is going to benefit from this regulation? The existing players who can afford to support linux: it will be peanuts for them and it will make or break a new broke manufacturer.
All these people don't understand the dangers of socialism. History is bound to repeat itself.
The cost of the EU forcing everyone to adopt a standard is that next time a new manufacturer need to enter the market, it will have to cater to the need of the 1% (of which I am part, I'd love to have drivers for linux for everything).
Who is going to benefit from this regulation? The existing players who can afford to support linux: it will be peanuts for them and it will make or break a new broke manufacturer.
I can get behind this. It'd definitely be great to see VoiceOver, the screen reader on Mac, get some competition. Maybe then blind Mac users could do their work on Mac, even in Salesforce and Google Docs and Sheets and such, and not hear "Safari not responding" at the slightest sign of overused JavaScript. There's a reason most blind people either use Windows, or don't use a desktop or laptop at all.
That would be amasing, and should happen. If you sell hardware you should include all documentation, code and support needed to use it.
facepalm
Whoever asked this have not considered for one second what would it mean in a way that can be put into legislation to "make drivers that work equally in linux, windows and even macOS". This is an incredibly, incredibly difficult topic. How would you phrase and likely measure "equality" here? I have no clue how to answer this even in layman terms. Perhaps someone would need to create and maintain a test suite covering all class of peripherals covered by the legislation and mandate this test suite passes. But even that would not cover performance. Much good does it to you if the video card tests pass unaccelerated.
And then the way this question is put forward also shows this person is not at all familiar with how the EU works. The EU does not have laws in the very first place. It does not. But that aside, the amount of study and coordination that goes into creating or amending an existing directive is just monumental. You would need a strong, compelling need to go through a multi year process, costing many millions of euros. In this case, the need was crystal clear: "these new obligations will lead to more re-use of chargers and will help consumers save up to 250 million euro a year on unnecessary charger purchases. Disposed of and unused chargers account for about 11 000 tonnes of e-waste annually in the EU". How many EU consumers are even affected? Because mobile phone chargers, these days, affect everyone (above the age of three or some such).
Here's a quote from the relevant USB C legislation:
Stakeholder consultations
The following consultation activities were conducted between May 2019 and April 2021 in order to assess potential areas for revision and the impacts of the suggested policy option in various areas:
– an inception impact assessment (2018-2019) targeted citizens, consumer associations, non-governmental organisations (NGOs), manufacturers’ associations, and individual manufacturers;
– a public consultation (2019) targeted member states, citizens, consumer associations, NGOs, manufacturers’ associations, and individual manufacturers;
– two consumer surveys (2019 and 2021) targeted citizens;
– a stakeholders survey (2020-2021) targeted Member States, citizens, consumer associations, and manufacturers;
– targeted interviews (2021) targeted consumer associations, environmental associations, market surveillance authorities, NGOs, manufacturers’ associations, and manufacturers;
– expert group meetings targeted consumer associations, Member States, market surveillance authorities, NGOs, manufacturers’ associations, and manufacturer
And all of that was to survey compelling to use an existing, well understood, already ubiquitous standard.
Whoever asked this have not considered for one second what would it mean in a way that can be put into legislation to "make drivers that work equally in linux, windows and even macOS". This is an incredibly, incredibly difficult topic. How would you phrase and likely measure "equality" here? I have no clue how to answer this even in layman terms. Perhaps someone would need to create and maintain a test suite covering all class of peripherals covered by the legislation and mandate this test suite passes. But even that would not cover performance. Much good does it to you if the video card tests pass unaccelerated.
And then the way this question is put forward also shows this person is not at all familiar with how the EU works. The EU does not have laws in the very first place. It does not. But that aside, the amount of study and coordination that goes into creating or amending an existing directive is just monumental. You would need a strong, compelling need to go through a multi year process, costing many millions of euros. In this case, the need was crystal clear: "these new obligations will lead to more re-use of chargers and will help consumers save up to 250 million euro a year on unnecessary charger purchases. Disposed of and unused chargers account for about 11 000 tonnes of e-waste annually in the EU". How many EU consumers are even affected? Because mobile phone chargers, these days, affect everyone (above the age of three or some such).
Here's a quote from the relevant USB C legislation:
Stakeholder consultations
The following consultation activities were conducted between May 2019 and April 2021 in order to assess potential areas for revision and the impacts of the suggested policy option in various areas:
– an inception impact assessment (2018-2019) targeted citizens, consumer associations, non-governmental organisations (NGOs), manufacturers’ associations, and individual manufacturers;
– a public consultation (2019) targeted member states, citizens, consumer associations, NGOs, manufacturers’ associations, and individual manufacturers;
– two consumer surveys (2019 and 2021) targeted citizens;
– a stakeholders survey (2020-2021) targeted Member States, citizens, consumer associations, and manufacturers;
– targeted interviews (2021) targeted consumer associations, environmental associations, market surveillance authorities, NGOs, manufacturers’ associations, and manufacturers;
– expert group meetings targeted consumer associations, Member States, market surveillance authorities, NGOs, manufacturers’ associations, and manufacturer
And all of that was to survey compelling to use an existing, well understood, already ubiquitous standard.
If the hardware is not too insanely complex, until there is a maintained and properly written open source driver with public hardware programming documentation for some OS, a working linux driver will probably follow if this hardware has a pertinent meaning.
I'd rather they force them to release documentation instead, documentation which they certainly already have, and which hardware manufacturers used to freely provide.
If they're worried about IP, that's what the patent system is for.
If they're worried about IP, that's what the patent system is for.
A lot of the innovation in the GPU space and competition between Nvidia and AMD happens at the driver level.
This could be an
This could be an
There's absolutely no legal basis for it. EC technically may risk it and then lose in court.
The USA could also do some work...
Two words: regulatory capture.
[deleted]
Force hardware vendors to only sell hardware. If any software that can be changed remotely or by the user is off limits. Even firmware. Conversely, software vendors can only sell (or freely distribute) software. For vendors from abroad, don't go extra-territorial, just force them to chose: either they only sell hardware in the EU, or they only sell software. Intel and microsoft would have no problem. NVDIA might complain very loudly. Apple would likely have to split itself.
Now the complicated part is how to define a company. We don't want a single company to just split itself into 2 legal entities that work so closely together they might as well be the same company.
Do that, and you'll get much better than device drivers for one free OS. You'll get the necessary specs required to make it work on all OSes. Even better, the user-facing hardware interface will start to matter, and there will be some selection pressure to drive the more complex ones, or the non-standard ones, out of the market. (Won't be ideal, I can see a particular over-complex architecture win out, similar to x86, but at least there won't be that many left, so writing a driver for most devices will actually be possible).