Ultra Librarian joins Flux to take the hard out of hardware • Hacker News Board

Re: Ultra Librarian joins Flux to take the hard out of hardware

#21

Post by buescher » Wed, Mar 06, 2024, 11:53 PM UTC

peteforde wrote: post #11

swamp40 wrote: post #8

Earlier quoted context omitted.

I don't see how it's possible to beat companies like Altium that have been continually improving the sch and pcb design experience for the last 30 years. The AI is a cool idea. Maybe as an add-on? An import? A library? Collaboration? IDK, but details like via tenting properties on layer 3 are best left to the experts.

I think it's a huge mistake for any ecosystem to be impenetrable to new players with fresh ideas. We see this in the web browser engine space with Chromium. That's why I find the glee with which prominent EE community types appear to condemn Flux really frustrating. Yes, Flux has big problems and a huge mountain to climb. To me, that's why we should encourage them. There are a million easier things those folks could…

Altium has only recenty started adding the features it needs to compete with Allegro and Xpedition. It's historically been oriented towards small-team efforts in the same niche as OrCAD and PADS.

The argument I see for Flux is the "FAE in a box" sorts of features for educating hobbyists and early-career design engineers while keeping them out of trouble. The person I imagine would otherwise not done a PCB at all. Someone who instead would have wired up up a bunch of prefab Arduino-type dev boards or bought small power supplies, DIN mount relays, and so on. Those features put a lot of things within the reach of technicians, panel designers, and systems integrators.

Re: Ultra Librarian joins Flux to take the hard out of hardware

#22

Post by delfinom » Thu, Mar 07, 2024, 1:20 AM UTC

peteforde wrote: post #4

I spent several months working with Flux, and while I actually generally enjoyed the UI and web-based approach, I had to switch back to KiCAD because there were so many dealbreaking bugs in fundamental features. The realtime collaboration was just straight up broken; as in, my collaborator would make changes that would not manifest until I refreshed. This is unacceptable. The PCB tracing was unusable because you coul…

Entry into the domain is hard because EE is incredibly mature in western countries.

By that I mean most work is heavily regulated, either defense, aerospace or industrial goods that must meet safety certs. Schematic and PCB design flow are heavily impacted and you can't go all tech startup go fast and break things on it.

Anything that's mass market consumer goods these days is outsourced to a shop in Asia or even Eastern Europe to design. At that point their labor is cheap that you don't care what they use.

Re: Ultra Librarian joins Flux to take the hard out of hardware

#23

Post by rgovostes » Thu, Mar 07, 2024, 5:48 AM UTC

bsder wrote: post #7

peteforde wrote: post #4

I spent several months working with Flux, and while I actually generally enjoyed the UI and web-based approach, I had to switch back to KiCAD because there were so many dealbreaking bugs in fundamental features. The realtime collaboration was just straight up broken; as in, my collaborator would make changes that would not manifest until I refreshed. This is unacceptable. The PCB tracing was unusable because you coul…

Partnering with Ultra Librarian is simply going to make me more inclined to shit on Flux, though. And I don't even know anything about Flux. These "library managers" like Ultra Librarian and SnapEDA are a pox upon the ecosystem. The symbols and footprints have non-open source licenses, so you nominally can't share them. They simply want to get in the middle of your design so that they can monetize you.

I looked into this the other day. SnapEDA says their symbols are CC licensed, though their FAQ reference some kind of license addition that tries to discourage mass redistribution—at the time I couldn’t find the actual text of this addition. Ultra Librarian did not publish any license I could locate.

Re: Ultra Librarian joins Flux to take the hard out of hardware

#24

Post by RF_Savage » Thu, Mar 07, 2024, 6:50 AM UTC

rgovostes wrote: post #23

bsder wrote: post #7

Earlier quoted context omitted.

Partnering with Ultra Librarian is simply going to make me more inclined to shit on Flux, though. And I don't even know anything about Flux. These "library managers" like Ultra Librarian and SnapEDA are a pox upon the ecosystem. The symbols and footprints have non-open source licenses, so you nominally can't share them. They simply want to get in the middle of your design so that they can monetize you.

I looked into this the other day. SnapEDA says their symbols are CC licensed, though their FAQ reference some kind of license addition that tries to discourage mass redistribution—at the time I couldn’t find the actual text of this addition. Ultra Librarian did not publish any license I could locate.

Is the license CC 4.0 or one of the older flawed ones?

That part is very important when it comes to CC licenses. Make a mistake in attribution for pre-4.0 CC license and you are open to being sued by the rights holder.

Cory Doctrow has an article about the background and the industry that sprang up to make use of this. https://pluralistic.net/2022/01/24/a-bug-in-early-creative-c...

Re: Ultra Librarian joins Flux to take the hard out of hardware

#25

Post by RF_Savage » Thu, Mar 07, 2024, 6:51 AM UTC

peteforde wrote: post #9

bsder wrote: post #7

Earlier quoted context omitted.

Partnering with Ultra Librarian is simply going to make me more inclined to shit on Flux, though. And I don't even know anything about Flux. These "library managers" like Ultra Librarian and SnapEDA are a pox upon the ecosystem. The symbols and footprints have non-open source licenses, so you nominally can't share them. They simply want to get in the middle of your design so that they can monetize you.

Damn, I am apparently woefully ignorant of this. As someone who is somehow both intimidated and fatigued of having to track down multiple assets for every item in my BOM, DigiKey's downloadables have been huge win... or so I thought? How does the licensing issue actually manifest in a practical sense? By what mechanism(s) could this monetization occur? Is this sabre rattling or are small hardware designers actually g…

I do like the DigiKey symbols, but the quality and style is all over the place with them.

Re: Ultra Librarian joins Flux to take the hard out of hardware

#26

Post by SnappyCM » Thu, Mar 07, 2024, 4:07 PM UTC

RF_Savage wrote: post #24

rgovostes wrote: post #23

Earlier quoted context omitted.

I looked into this the other day. SnapEDA says their symbols are CC licensed, though their FAQ reference some kind of license addition that tries to discourage mass redistribution—at the time I couldn’t find the actual text of this addition. Ultra Librarian did not publish any license I could locate.

Is the license CC 4.0 or one of the older flawed ones? That part is very important when it comes to CC licenses. Make a mistake in attribution for pre-4.0 CC license and you are open to being sued by the rights holder. Cory Doctrow has an article about the background and the industry that sprang up to make use of this. https://pluralistic.net/2022/01/24/a-bug-in-early-creative-c...

Hello there, this is Carlos from SnapMagic (formerly SnapEDA) writing, thanks for bringing this up. The Creative Commons License we use is CC4.0, with a Design Exception that allows for fair use of our content. For more information, please go to this link: https://support.snapmagic.com/en/articles/2957814-what-is-th...

Re: Ultra Librarian joins Flux to take the hard out of hardware

#27

Post by SnappyCM » Thu, Mar 07, 2024, 4:18 PM UTC

rgovostes wrote: post #23

bsder wrote: post #7

Earlier quoted context omitted.

Partnering with Ultra Librarian is simply going to make me more inclined to shit on Flux, though. And I don't even know anything about Flux. These "library managers" like Ultra Librarian and SnapEDA are a pox upon the ecosystem. The symbols and footprints have non-open source licenses, so you nominally can't share them. They simply want to get in the middle of your design so that they can monetize you.

I looked into this the other day. SnapEDA says their symbols are CC licensed, though their FAQ reference some kind of license addition that tries to discourage mass redistribution—at the time I couldn’t find the actual text of this addition. Ultra Librarian did not publish any license I could locate.

Hi, this is Carlos from SnapMagic, thanks for sharing this. We have a CC4.0 license which allows for fair use on commercial and non-commercial manufactured designs without attribution or other license restrictions.

When sharing the exact CAD content or any derived works publicly, please make sure to provide proper attribution to the sources. The credited sources must include Snapmagic and the community author, if applicable. For more information, please check: https://support.snapmagic.com/en/articles/2957814-what-is-th...

Re: Ultra Librarian joins Flux to take the hard out of hardware

#28

Post by rgovostes » Thu, Mar 07, 2024, 11:43 PM UTC

SnappyCM wrote: post #27

rgovostes wrote: post #23

Earlier quoted context omitted.

I looked into this the other day. SnapEDA says their symbols are CC licensed, though their FAQ reference some kind of license addition that tries to discourage mass redistribution—at the time I couldn’t find the actual text of this addition. Ultra Librarian did not publish any license I could locate.

Hi, this is Carlos from SnapMagic, thanks for sharing this. We have a CC4.0 license which allows for fair use on commercial and non-commercial manufactured designs without attribution or other license restrictions. When sharing the exact CAD content or any derived works publicly, please make sure to provide proper attribution to the sources. The credited sources must include Snapmagic and the community author, if app…

Thanks for the clarification, and thanks for going with a permissive license.

I think the link to the Design Exception was broken previously. Also in the definition it's called the Design Exclusion, might want to fix that.

It would just be easiest if every page where you download the design has a copyable license with correct attribution, and a LICENSE file in the download bundle, just like a typical open source project. As is, the license information is kind of buried in not one but two different FAQ parts of your website.