| Re: [ide-dev] Survey results |
The case that the ignore settings are an explicit choice is weak. Undoubtedly, some fraction is an explicit choice, but we don’t have the data to show how big of a fraction. Consider a fairly common usecase where developers go mucking with these properties… Some problem is configured as warning by default and it is annoying someone. They go and flip that one to ignore. What can we conclude about their preference for another problem that defaults to ignore. No much. - Konstantin From: ide-dev-bounces@xxxxxxxxxxx [mailto:ide-dev-bounces@xxxxxxxxxxx] On Behalf Of Sebastian Zarnekow Why should we ignore that? The users that share their settings may have chosen to set the important flags to warning / error and leave the unimportant validations as ignore. I would say that's an explicit decision and should not be ignored. - Sebastian On 10.12.2013, at 16:10, Konstantin Komissarchik wrote: If I am not mistaken, JDT does not use sparse storage for these settings, so when a user changes any problem severity setting at project level, all are persisted. The 1061 set as warning and 230 set as error are then valid data as these are not defaults, but we can’t use this data to tell how many actually prefer to ignore. - Konstantin From: ide-dev-bounces@xxxxxxxxxxx [mailto:ide-dev-bounces@xxxxxxxxxxx] On Behalf Of John Arthorne Sven's queries only capture the users with custom settings - the people who are *not* just using defaults. While it is true this is only a fraction of all users, it still gives us some interesting data about what settings Java devlopers find useful.
What happened to the idea of scraping github for data ? This seemed like a great idea to me when it first came up and may provide further insight into our users 'real' preferences. Do you, as a user, commit your preferences to GitHub? _______________________________________________ |