well, I havebeen coding for a good long while, I wouldn't know the
first thing about CNC Linux, but
would be interested in doing something with sensors, or those quadrature
encoders... BUT it's pretty hard to find any info
about details like that, and how it would fit in (for example, I assume
you can't 'steal' too many cycles.)
But I agree, there are tons of people that work on it, there are a lot
more that work with it, so just saying, create your own fork/branch is
saying the same as "no, go away..." besides, what is the point of
having dozens of distros?
I like it, I like the work that's done, I don't know much about CNC
machining (that is an overstatement actually), and it probably does a
lot more then I ever use, or have the time to understand.
so.. uhm.. thanks for those that do the work...
Ron
On 9/8/20 7:38 PM, andy pugh wrote:
On Mon, 7 Sep 2020 at 22:31, Rafael Skodlar <ra...@linwin.com> wrote:
IMO it's extremely bad to attack those who come up with "it would be
nice to have this or that" in existing product. Saying, "it's open
source, go fork and write your own code" is plain STUPID! We are not all
programmers! [1]
The problem is that not enough of us are programmers. ( I am not a programmer )
When folk say "you want it, you code it" this isn't a rejection of the
idea, it is just that they know that they can't do it.
The Machinekit fork wasn't a high point of the LinuxCNC story. But MAH
wanted to re-work NML to use a 0MQ as he was keen to make the GUI /
Realtime split that some are asking for. He took more than a whole
year off work to make that happen. It didn't happen (in LinuxCNC _or_
Machinekit as far as I know)
An analysis of the 2.8 release:
LinuxCNC contains 2,294,176 lines of code. 55% of those were touched
during 2.8 development.
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
