Index: trunk/doc-rnd/devlog/20162601/gencsv.sh =================================================================== --- trunk/doc-rnd/devlog/20162601/gencsv.sh (nonexistent) +++ trunk/doc-rnd/devlog/20162601/gencsv.sh (revision 987) @@ -0,0 +1,3 @@ +#!/bin/sh +sed "s@\t@,@g" < poll.tsv > poll.csv +tr "\n" "," < header > header.csv Property changes on: trunk/doc-rnd/devlog/20162601/gencsv.sh ___________________________________________________________________ Added: svn:executable ## -0,0 +1 ## +* \ No newline at end of property Index: trunk/doc-rnd/devlog/20162601/genhtml.sh =================================================================== --- trunk/doc-rnd/devlog/20162601/genhtml.sh (nonexistent) +++ trunk/doc-rnd/devlog/20162601/genhtml.sh (revision 987) @@ -0,0 +1,9 @@ +#!/bin/sh +( +echo '' +echo "" +sed "s@^@
@" < header +sed "s@^@
@;s@\t@@g" < poll.tsv +echo '
' +) > poll.html + Property changes on: trunk/doc-rnd/devlog/20162601/genhtml.sh ___________________________________________________________________ Added: svn:executable ## -0,0 +1 ## +* \ No newline at end of property Index: trunk/doc-rnd/devlog/20162601/header =================================================================== --- trunk/doc-rnd/devlog/20162601/header (nonexistent) +++ trunk/doc-rnd/devlog/20162601/header (revision 987) @@ -0,0 +1,11 @@ +1. How many of your boards REQUIRE burried or blind vias? [percentage] +2. How many of your boards could BENEFIT burried or blind vias? [percentage] +3. When your board REQUIRED them, do you more often find a workaround to stick with pcb instead of switching to another design tool? [yes/no] +4. When your board could BENEFIT using them, do you more often find a workaround to stick with pcb instead of switching to another design tool? [yes/no] +5. Have you ever tried pcb-rnd? [yes/no] +6. Would you try pcb-rnd if it offered blind/burried vias? [yes/no] +7. Would you consider switching to pcb-rnd if it offered blind/burried vias? [yes/no] +8. Approximately how many boards have you done so far with pcb (pcb mainline/branches/forks included, using gschem/gnetlist not required)? "1 board done" means you had one or more physical copies of the board. [rough estimation, positive integer] +9. Approximately how many boards have you done with other packages? [rough estimation, positive integer] +10. What OS would you prefer to do your pcb layouts on (assuming your favorite layout tool is/would be available on it)? [one of: (GNU/)Linux, *BSD, OSX, windows, other; if you like more, select the one you would spend most time on!] + Index: trunk/doc-rnd/devlog/20162601/header.csv =================================================================== --- trunk/doc-rnd/devlog/20162601/header.csv (nonexistent) +++ trunk/doc-rnd/devlog/20162601/header.csv (revision 987) @@ -0,0 +1 @@ +1. How many of your boards REQUIRE burried or blind vias? [percentage],2. How many of your boards could BENEFIT burried or blind vias? [percentage],3. When your board REQUIRED them, do you more often find a workaround to stick with pcb instead of switching to another design tool? [yes/no],4. When your board could BENEFIT using them, do you more often find a workaround to stick with pcb instead of switching to another design tool? [yes/no],5. Have you ever tried pcb-rnd? [yes/no],6. Would you try pcb-rnd if it offered blind/burried vias? [yes/no],7. Would you consider switching to pcb-rnd if it offered blind/burried vias? [yes/no],8. Approximately how many boards have you done so far with pcb (pcb mainline/branches/forks included, using gschem/gnetlist not required)? "1 board done" means you had one or more physical copies of the board. [rough estimation, positive integer],9. Approximately how many boards have you done with other packages? [rough estimation, positive integer],10. What OS would you prefer to do your pcb layouts on (assuming your favorite layout tool is/would be available on it)? [one of: (GNU/)Linux, *BSD, OSX, windows, other; if you like more, select the one you would spend most time on!],, \ No newline at end of file Index: trunk/doc-rnd/devlog/20162601/poll.csv =================================================================== --- trunk/doc-rnd/devlog/20162601/poll.csv (nonexistent) +++ trunk/doc-rnd/devlog/20162601/poll.csv (revision 987) @@ -0,0 +1,10 @@ +0,50,yes,yes,no,no,no,1,2,Linux +10,40,no,n/a,no,yes,n/a,20,2,Linux +0,5,n/a,no,no,no,no,20,4,Linux +5,20,no,no,no,yes,no,5,20,Linux +0,0,n/a,n/a,no,no,no,10,0,Linux +0,80,yes,yes,no,no,no,15,0,Linux +50,80,no,no,no,yes,n/a,30,100,OSX +20,75,no,no,no,yes,yes,15,3,Linux +0,8,yes,yes,yes,yes,no,2,1,Linux +0,2,yes,yes,no,no,no,8,4,Linux Index: trunk/doc-rnd/devlog/20162601/poll.html =================================================================== --- trunk/doc-rnd/devlog/20162601/poll.html (nonexistent) +++ trunk/doc-rnd/devlog/20162601/poll.html (revision 987) @@ -0,0 +1,24 @@ + + +
1. How many of your boards REQUIRE burried or blind vias? [percentage] +2. How many of your boards could BENEFIT burried or blind vias? [percentage] +3. When your board REQUIRED them, do you more often find a workaround to stick with pcb instead of switching to another design tool? [yes/no] +4. When your board could BENEFIT using them, do you more often find a workaround to stick with pcb instead of switching to another design tool? [yes/no] +5. Have you ever tried pcb-rnd? [yes/no] +6. Would you try pcb-rnd if it offered blind/burried vias? [yes/no] +7. Would you consider switching to pcb-rnd if it offered blind/burried vias? [yes/no] +8. Approximately how many boards have you done so far with pcb (pcb mainline/branches/forks included, using gschem/gnetlist not required)? "1 board done" means you had one or more physical copies of the board. [rough estimation, positive integer] +9. Approximately how many boards have you done with other packages? [rough estimation, positive integer] +10. What OS would you prefer to do your pcb layouts on (assuming your favorite layout tool is/would be available on it)? [one of: (GNU/)Linux, *BSD, OSX, windows, other; if you like more, select the one you would spend most time on!] + +
050yesyesnonono12Linux +
1040non/anoyesn/a202Linux +
05n/anononono204Linux +
520nononoyesno520Linux +
00n/an/anonono100Linux +
080yesyesnonono150Linux +
5080nononoyesn/a30100OSX +
2075nononoyesyes153Linux +
08yesyesyesyesno21Linux +
02yesyesnonono84Linux +
Index: trunk/doc-rnd/devlog/20162601/poll.tsv =================================================================== --- trunk/doc-rnd/devlog/20162601/poll.tsv (nonexistent) +++ trunk/doc-rnd/devlog/20162601/poll.tsv (revision 987) @@ -0,0 +1,10 @@ +0 50 yes yes no no no 1 2 Linux +10 40 no n/a no yes n/a 20 2 Linux +0 5 n/a no no no no 20 4 Linux +5 20 no no no yes no 5 20 Linux +0 0 n/a n/a no no no 10 0 Linux +0 80 yes yes no no no 15 0 Linux +50 80 no no no yes n/a 30 100 OSX +20 75 no no no yes yes 15 3 Linux +0 8 yes yes yes yes no 2 1 Linux +0 2 yes yes no no no 8 4 Linux Index: trunk/doc-rnd/devlog/20162601.html =================================================================== --- trunk/doc-rnd/devlog/20162601.html (nonexistent) +++ trunk/doc-rnd/devlog/20162601.html (revision 987) @@ -0,0 +1,59 @@ + + +

pcb-rnd devlog

+ +

Burried/blind via poll

+ +

Results

+ +I received 10 full answers to the poll - thanks everyone who +answered. This is a small sample, but this is the best I could get +(I can't reach more pcb users). +

+Raw results are available in html, tsv and +csv format. + +

My interpretation

+ +(User obviously means "those users who answered the poll") + + + +

My conclusions

+Because of 1. and 2., pcb-rnd doesn't seem to need blind/burried vias. The +purpose of question 7 was to find out whether users value this feature high +enough to actually consider investing time/effort in return, compared to +question 6. This pair of questions was designed to avoid noise that comes +from the fact that we, on the list tend to express our opinions in vast +crowds while only a few invest more time than talking and do actual work. +According to the result of line 7, my conclusion is that it's absolutely +not blind/burried vias that potential pcb-rnd users need. Thus +my decision is that I won't spend time on this feature in the near future. +

+The situation for pcb might be different, tho. I worded the first 4 questions +to find out how strong the need is among the users of mainline pcb and whether +they are devoted to pcb or choose the tool according to the design requirements. +There seems to be a correlation between having to use blind/burried vias +and using other layout tools. Or in other words: those who are happy with pcb +usually don't need or want blind/burried vias anyway and those who do have +already switched to another tool. +

+This suggests mainline pcb could benefit from burried/blind vias. However, +the demand is much lower than "every new design needs this" or "no new +user would consider pcb because of this missing feature". +

+Linux: it seems pcb power users mostly use Linux. I am not sure if it's +because PCB works well on Linux and is a bit harder to compile on +anything else - or the other way around (Linux users are more attracted +to PCB). + + + + + +