Nick Johnson

Member Since: March 12, 2011

Country: United States

  • Well, it’s your code - there’s nothing stopping you from offering it under multiple licenses. Beerware or WTFPL for the hackers, and MIT for the corporate suits.

  • Yup! I met some of the bare conductive folks on a trip to Shenzhen! They were in well before the current Arduino foofarah.

    Even now I’d probably be happy to sign up - if they’d just answer my emails.

    My project is called the Tsunami, and it’s currently up on KS: https://www.kickstarter.com/projects/nickjohnson/tsunami/

  • Has anyone had success with the Arduino@Heart program recently? I was 95% of the way there - I had a contract only waiting on Massimo’s signature - when the person I was dealing with at Arduino left, and they stopped answering all my emails. In the end, I had to launch my product without arduino@heart branding.

  • “Finally, and perhaps most importantly, when you alter an open-­source design you are obligated to share your improvements with the rest of the community under the open-­source licenses.”

    Untrue - you’re only obliged to provide the source to your modified design to anyone you provide the ‘compiled’ product to. If you’re modifying it for your own use, for instance, you have no obligation to distribute the changes.

    Whether or not a 3d printed object is the compilation of a design is an interesting question, though.

  • I really want to see a masterchef style elimination show based on the premise of challenges like these. Nicely done!

  • The actual choice I face, though, is to pick an FTDI chip and risk this happening - which I’m sure will be educational for everyone, but that’s not much comfort - or to pick a competitor’s chip, which removes that risk. Why would I take the additional risk of using an FTDI product?

  • If you’ve ever manufactured anything in China, you’ll know that nobody there can guarantee 100% that nobody on their supply chain is going to make a bit on the side by swapping some parts out.

    And “you’ve helped the world counterfeiting problem” isn’t particularly comforting news when you’ve just gone out of business. Nor is it a compelling reason not to switch to an alternate part that I can be sure won’t suffer from this issue.

  • The maintainer of the subsystem works at TI, not FTDI. It’s a joke.

  • Yes, I would - because I don’t have control over my entire supply chain, and if alternatives exist, switching them is one way to mitigate the risk that counterfeit parts could get substituted, and I get lumped with a bunch of devices that get bricked by FTDI’s drivers.

  • The “FTDI cable interface” is actually just a bidirectional UART with a particular 0.1" male header pinout. Making an “FTDI cable” with another usb to UART chip that works in all the places an FTDI one works would be trivial.

No public wish lists :(