Hacker News new | ask | show | jobs
by Ao7bei3s 3851 days ago
Favorably.

Obviously, it's free and open source, with no board size / layer limitations. On the other hand, Eagle is still much more widely used in the DIY community, and most my-first-PCB-like tutorials are Eagle-based. Kicad has for years suffered from the binary release being really, really outdated. Kicad development feels pretty fast-paced.

It has most or all of Eagles features, and some nice advanced features Eagle doesn't have. Especially it's PCB routing support is much better. For example, it supports push shove routing[1] and automatic trace length matching. It also shows the netname on pads (in Eagle you have to use "show" all the time). On the schematic side, It has had hierarchical sheets for many years now, whereas Eagle only gained hierarchical design support earlier this year in version 7. Things like that.

There are minor workflow differences in some places. For example, it uses key combinations instead of typed commands. There's a netlist generation step between schematic editing and board editing, so going back and forth between the two isn't as straightforward as it is in Eagle.

[1] If you're used to Eagle, this may blow your mind: https://www.youtube.com/watch?v=C02D0_kNQeM

3 comments

The hobbyist community has been switching over to KiCAD, to the point where I believe KiCAD has a significant majority over Eagle in OSHPark orders. A lot of people switched with the new Eagle licensing model, which they put on hold due to backlash.
I'm on support at OSH Park and we're still seeing a sizable majority of Eagle boards, but KiCad is definitely on the rise. I've got the impression that a lot of folks have been turned off by having to get the daily builds, so I'm incredibly excited to see the stable release. I'm expecting we'll see KiCad come to parity with Eagle over the next year or two.

We're also working on being able to take .kicad_pcb files directly, in the same way we take Eagle .brd files now. In the meantime, I wrote up a page with some KiCad screenshots and instructions for how to generate the gerbers and drill files we need. [1]

The major issues we see can be solved by checking the Protel naming format option so we can detect layers correctly, and by putting the board outline by itself on the Edge Cuts layer.

[1] http://docs.oshpark.com/design-tools/kicad/

Laen mentioned on the amp hour podcast a couple of years ago that kicad was the majority at the time. Later on he said that it was just a blip at the time for some reason and eagle became much more dominant.

I wish I could upvote your post more for the middle paragraph. Direct kicad_pcb input in to OSH Park will be fantastic!

Do you see a lot of cloud based boards (Upverter, Altium's cloud component, etc) coming through?
We do! They're way behind Eagle and KiCad, but they're a fair and growing number. Our current challenge is to keep expanding our ability to automatically detect the default gerber naming scheme so it doesn't matter which CAD package you're using. I know we've recently really nailed down the Altium variants (Designer, CircuitMaker) but I'm less sure about Upverter.

One of the downsides of accepting gerber files is that a lot of folks rename to match our suggested naming pattern to be sure the files work, so it can be tough to determine which CAD package was originally used. Plus, we still get gerbers from some rare ones like TraxMaker 2000 or Ranger 3.

FWIW the old lead dev had a philosophy of "everybody should just compile the most recent source" which is why there hasn't been a stable release in a long time.

The new lead dev wants to do stable releases much more often than in the past. We'll see how it goes. KiCad ended up in a "feature freeze" since ~May which slowed down dev for the last six months.

Can you comment on the situation with component libraries for kicad? How does it compare to Eagle?

I've recently tried Fritzing but keep finding that some components aren't available. Defining my own is kind of tedious.

I generally end up using an online tool [1] for high pin count parts. It's not the best though, someday I will write something better.

BTW, in most professional contexts, parts are all created by the engineer - vendor part libraries are pretty rare. I know Altium is trying to change that, maybe soon we will see something similar happen with KiCAD.

[1] http://kicad.rohrbacher.net/quicklib.php

Thanks for the link: very useful!
This release of kicad supports using eagle footprints, but not schematic symbols.

There are quite a handful of component libraries, but you'll probably have to do a bit of digging.