<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I prefer to think that we aren’t topping our drinks off often enough.<div class=""><br class=""></div><div class="">I wonder what it would take for KiCad to move closer to Eagle in capabilities? Would we do better for ourselves by promoting/contributing to KiCad? </div><div class=""><br class=""><div class="">
<div class=""><div class=""><font face="Menlo" color="#011373" class=""><b class="">Tadd / KA2DEW</b></font></div><div class=""><font face="Menlo" color="#011373" class=""><b class=""><a href="mailto:tadd@mac.com" class="">tadd@mac.com</a></b></font></div><div class=""><font face="Menlo" color="#011373" class=""><b class="">Raleigh NC FM05pv</b></font></div><div class=""><font face="Menlo" color="#011373" class=""><b class=""><br class=""></b></font></div><div class=""><font face="Menlo" color="#011373" class=""><b class="">“Packet networking over ham radio": <a href="http://tarpn.net/t/packet_radio_networking.html" class="">http://tarpn.net/t/packet_radio_networking.html</a></b></font></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jan 20, 2017, at 1:52 PM, Jesse Griggs via TriEmbed <<a href="mailto:triembed@triembed.org" class="">triembed@triembed.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi John,
<div class=""><br class="">
</div>
<div class="">This has been a very interesting journey. Your response has been a common one. I find it interesting that people often assume that my intentions are to cheat software developers out of making money for their blood, sweat, and tears - I know you're not
directly implying this, but I want to make clear that’s not my intention. I fully support a maintenance release based model where I have to pay for significant software releases so long as the license is perpetual. I do understand that software developers
are entitled to change their licensing but I whole hardly disagree with a third-party controlled gate that can cut me off from something I purchased.</div>
<div class=""><br class="">
</div>
<div class="">I appreciate your thoughtful reply and I look forward to meeting you in person. I’m much more interesting and less annoying than my emails may imply in person. :-)</div>
<div class=""><br class="">
</div>
<div class="">Forever an internal optimist… just kidding… the glass is never half full, it’s simply twice as large as it needs to be.<br class="">
<div class=""><br class="webkit-block-placeholder">
</div>
<div class="">
<div class=""><b class="">Jesse Griggs</b></div>
<div class=""><a href="mailto:jesse.griggs@outlook.com" class="">jesse.griggs@outlook.com</a></div>
<div class=""><br class="">
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
<div class="">
<div class="">On Jan 20, 2017, at 1:36 PM, John Vaughters via TriEmbed <<a href="mailto:triembed@triembed.org" class="">triembed@triembed.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<div style="background-color: rgb(255, 255, 255); font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px;" class="">
<div id="yui_3_16_0_ym19_1_1484833362300_177177" class=""><span class="">Jessie, </span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" class=""><span class=""><br class="">
</span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" class=""><span id="yui_3_16_0_ym19_1_1484833362300_177266" class="">Not trying to discourage your effort, but I do want to point out that it is quite common to change licensing and those that put the effort into the software certainly
have the right to try and reap rewards for their efforts. I think it's great that Eagle has given us such a great tool. I do not think they ever had any other intentions than to create a class of user willing to pay in the future and I am quite sure they have
accomplished their task. The open source world is one where many will switch when projects go dark. It often times motivates the alternatives to increase their users and therefore improve their products. </span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" class=""><span class=""><br class="">
</span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" dir="ltr" class=""><span id="yui_3_16_0_ym19_1_1484833362300_177649" class="">It will probably break like this. If you make money on eagle, you pay the price and move on. If you make enough money that Eagle is not worth your time,
you pay the price and move on. If you have the time but not the money, you just move on.</span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" dir="ltr" class=""><span class=""><br class="">
</span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" dir="ltr" class=""><span class="">My 2 cents worth half a pence on a good day.</span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" dir="ltr" class=""><span class=""><br class="">
</span></div>
<div id="yui_3_16_0_ym19_1_1484833362300_177177" dir="ltr" class=""><span class="">John Vaughters</span></div>
<div class="qtdSeparateBR"><br class="">
<br class="">
</div>
<div class="yahoo_quoted" style="display: block;">
<div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12px;" class="">
<div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" class="">
<div dir="ltr" class=""><font size="2" face="Arial" class="">On Friday, January 20, 2017 12:33 PM, Brian via TriEmbed <<a href="mailto:triembed@triembed.org" class="">triembed@triembed.org</a>> wrote:<br class="">
</font></div>
<br class="">
<br class="">
<div class="y_msg_container">On 01/20/2017 12:01 PM, Pete Soper via TriEmbed wrote:<br class="">
Where I sit this moment I'm expecting to<br class="">
> buckle down and get past a lot more of the KiCad learning curve while<br class="">
> coughing up $100 for Autodesk for the next year.<br class="">
><br class="">
<br class="">
Don't cough up for Eagle. If you keep Eagle around, you'll be tempted <br class="">
to just use it each time you run into a hiccup with KiCAD. Just grit <br class="">
your teeth and plow through the KiCAD curve.<br class="">
<br class="">
Maybe my boards are simpler than yours, but I've always had much better <br class="">
luck (and been much more pleased with the results) routing entirely by <br class="">
hand. Maybe that's just a matter of me not knowing how to set up the <br class="">
autorouter to get the best results.<br class="">
<br class="">
Anyhoo, I made the switch to KiCAD a year or two ago, when I developed <br class="">
some designs that simply could not be routed effectively in two layers. <br class="">
The scramble up the KiCAD learning curve was painful, but now that <br class="">
I've got my head around it, I haven't looked back. Plus I can sell my <br class="">
work if I want to, and I've already done some tinkering with the KiCAD <br class="">
source to add RDBMS component and footprint libraries.<br class="">
<br class="">
Go get 'em!<br class="">
<br class="">
-B<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Triangle, NC Embedded Computing mailing list<br class="">
<a ymailto="mailto:TriEmbed@triembed.org" href="mailto:TriEmbed@triembed.org" class="">TriEmbed@triembed.org</a><br class="">
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" target="_blank" class="">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br class="">
TriEmbed web site: <a href="http://triembed.org/" target="_blank" class="">http://TriEmbed.org</a><br class="">
<br class="">
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
Triangle, NC Embedded Computing mailing list<br class="">
<a href="mailto:TriEmbed@triembed.org" class="">TriEmbed@triembed.org</a><br class="">
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" class="">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br class="">
TriEmbed web site: <a href="http://TriEmbed.org" class="">http://TriEmbed.org</a><br class="">
</div>
</div>
<br class="">
</div>
</div>
_______________________________________________<br class="">Triangle, NC Embedded Computing mailing list<br class=""><a href="mailto:TriEmbed@triembed.org" class="">TriEmbed@triembed.org</a><br class="">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org<br class="">TriEmbed web site: http://TriEmbed.org<br class=""></div></blockquote></div><br class=""></div></body></html>