Comment by Moral_ 7 days ago
This is the exact reason why they bought Arduino... So now startups have a way to buy say 1,000 devices for prototyping. Qualcomm gets used to supporting smaller developers/startups/tinkerers and will hopefully push different types of chips into the Arduino product lines.
This was very much my experience going through an acquisition like that. I was working at a company that served big customers. We bought a smaller company, with one of the goals being to expand to serving smaller customers.
What actually happened was that our management very quickly started telling the people who came along with the acquisition that they were doing everything wrong. The salespeople were selling wrong, the marketing people were marketing wrong, the customer support people were supporting customers wrong. Everything that the company we acquired did differently was seen as a problem.
Within about a year, anyone they hadn't pressured to adopt our practices had left and been replaced with a transplant from the Mothership. Another year later, the customers we picked up in the acquisition were rapidly leaving for other vendors. They simply couldn't work with us in a way that worked for their business anymore. Last I heard, pretty much the only remaining vestiges of the company we acquired were trademarks, and we were back to only having very large customers.
Here's how I like to think about it. Tech salesmen (especially enterprise software salesmen) are just like car salesmen. Now which commission would you like to receive: mattel matchbox car or BMW? This makes sense, because it's often the same sales effort per-sale for each possibility.
> This is the exact reason why they bought Arduino... So now startups have a way to buy say 1,000 devices for prototyping. Qualcomm gets used to supporting smaller developers/startups/tinkerers
For this, Qualcomm does not have to buy Arduino for a big amount of money: Qualcomm could simply offer this option on their own and save the acquisition cost.
Addendum: For the acquisition cost, Qualcomm could do a lot of marketing of their offering towards makers.
> Qualcomm could simply offer this option on their own and save the acquisition cost.
No they can't. That's like suggesting "the aircraft carrier could simply turn around." The cheap and simple way for a multi-billion-dollar secretive semiconductor manufacturing behemoth that doesn't know how to write a contract for less than a million dollars or to publish documents for the public is not to just change that. It's to write a contract for millions of dollars to buy someone else that can already do that.
https://www.reddit.com/r/WarshipPorn/comments/140oahc/japane...
You picked an unfortunate analogy.
More importantly, if Qualcomm management is just unable to do this, why would they suddenly be able to do this with a different brand under their umbrella?
> the aircraft carrier could simply turn around.
Pretty sure it can turn 180 degrees fairly quickly.
Seems like a corporate version of the "buy vs build" question. If it's true that the goal is to become more approachable to students and hobbyists (which personally I think would be a good idea) - then Qualcomm must've evaluated both options and decided "buy".
The problem is that massive semiconductor companies like Qualcomm rarely follow through. They want their lottery ticket to be included in the next smartphone revolution but won't care about random under 5k unit Kickstarter. Everyone knows that those are two sides of the same coin, but they always choose to wait for the bankruptcy trustees to show up.
Seems like a similar play to what Broadcom did with Raspberry Pi— create a new entity/brand that could resell their chips on hobby boards and be stewards of a "community" support framework but largely without distracting the company from its enterprise customers or risk cannibalizing those relationships.
That said, interesting that Qualcomm would buy twenty years of Arduino legacy for this rather than launching something new in the space.
Broadcom wasn't really a driver behind Raspberry Pi. They acquiesced and let them have chips, once the product took off, they continued supplying chips for the Pi. And of course supported the community by refusing to supply non-propriety firmware blobs to this day ;)
Other than that, Broadcom never really had any community involvement, nor any involvement in the Raspberry Pi Foundation that runs it. However, some broadcom engineers were part of the foundation, which isn't quite the same.
> interesting that Qualcomm would buy twenty years of Arduino legacy for this rather than launching something new in the space
I wouldn't minimise the effect of people just googling around and finding the name Arduino all over the place. It would be very hard for an entirely new platform to get critical mass while esp32 is not standing still.
As other have pointed out, that doesn't make any sense. Qualcomm doesn't want anyone buying their products at 1k quantities for prototyping. They want huge customers that place huge orders consistently. The return for supporting those small orders is miserable and doesn't align with their business objectives
Qualcomm has bought plenty of companies that serviced small customers, and what happed is exactly what the person you’re replying to described. You can’t even get a quote many times.
What I expect short term is what happened to Eagle in the PCB space when Autodesk bought it (best thing that happened to kicad).
Longterm Arduino goes into the periphery of the maker market, similarly to beaglebone.
Qualcomm did not need to buy Arduino in order to do that.
It's cheaper and easier to just spin your own boards at that point. Arduinos are not complex or special in any way. Even if you did need a ton of off the shelf boards, there are countless clones that will sell you as many as you want for next to nothing.
Plus the market you're implying exists is so small as to be utterly worthless to Qualcomm. They are in no way interested in individuals or small businesses
The issue is that their corporate culture does not support it. Arduino will be too small to matter. This is the same issue as with Coral, the Google TPU. They are not refreshed as they are too small. They are too small cause they are not updated or supported widely.
People need mainline kernel support and regular refreshes to reliably build projects based on it. This will require some level of building their BSPs in open and providing APIs for people to take advantage of the QCOM specific features. A QCOM that won't talk to anyone without an NDA cannot adapt to this.