kicad-developers team mailing list archive

[Henner Zeller <h.zeller@xxxxxxx>]

Thanks for your humble introduction. Send a link once you have code. You
are in for years of work. If you choose to not positively contribute to
KiCAD with patches or suggestions then why are you here?

All software has issues, and the only way to fix them is to get involved
and contribute code. Spewing vitriol does _not_ fix code and also makes it
hard to retain developers once you do consider leading a project, just
saying.

As for technology, I am glad that EDA tools are not running in the browser,
JavaScript is a mess to maintain. So if you go that route, make sure to
have only the presentation in  "web technology"; still 95% of your code
will be in the backend and be C, C++, Go or whatever you choose.


Good luck
H

On Dec 25, 2017 08:03, "Cerem Cem ASLAN" <ceremcem@xxxxxxxxxxxx> wrote:

> Hello everyone,
>
> I'm the founder and project engineer of my current company. We are
> developing open source web based realtime SCADA solutions with or without
> custom open source hardware. We are using Kicad for our hardware
> development, and thank you for your hard work.
>
> Before the main subject, let me clear an issue:
>
> There are a few problems between Kicad and us (me). First, you developers
> are too arrogant. And your software, Kicad, sucks in many aspects. I can
> build my own EDA, better than yours, there is no need for Kicad.
>
> Yeah, that was what I was thinking for the last 1.5 years and that's
> corrected a few days ago: https://forum.kicad.info/
> t/kicad-from-scratch-with-web-technologies/8962 I realized that "those
> people" were not developers at all, so there was a total misunderstanding
> on my side. "Kicad sucks"? Nope, every application might have problems. I'm
> a developer, an engineer, I know that. Sending bug reports and/or sending
> patches is one of our responsibility as a user (and this is what I did for
> our workflow: https://github.com/aktos-io/kicad-tools, https://
> github.com/aktos-io/kicad-install) .
>
> Real problem between Kicad an me:
>
> There is a "lost" 1.5 years for me because of the above misunderstanding
> and I have a long wish list. Plus, I don't write C++ applications, which
> will force me diverging my own effort if I want to dive into Kicad codes.
> In addition, I feel like a web application might be useful in many cases.
> Additionally, such a drawing ability will be used for our SCADA product.
> That's why I've initiated the following project: https://github.com/
> ceremcem/aecad
>
> Above forum thread is too long to be read easily, but I would like to
> quote one of my thoughts from there:
>
> I have a question: Is KiCAD a tool, or an idea with a physical evidence?
>> If it's a tool, you are justified "defending" it to the end. If it is an
>> idea with physical product, then the physical product may change slightly.
>> Like an airplane. It's an idea about flying. There are many different
>> airplanes. They share the same knowledge, but these teams can not work on
>> the same plane. Important part is to keep these teams in touch to let them
>> chat and share their experiences.
>>
>
> Based on this logic, I would like to get your opinions. What design
> decisions should be taken into account in this step? What would you do
> differently if you were at the time you started coding Kicad? What are the
> dead valleys? What would you expect from such a project?
>
>
> Regards.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>