Comments (7)
People should rather create bug reports for their tools instead.
Most people don't do this. As a maintainer of a couple of dev tools I am always surprised at how many people tweet about a thing being broken vs. actually open an issue.
Same experience here.
A lot of the questions related to tooling read like a popularity contest. With few exceptions like : https://2021.stateofcss.com/en-US/technologies/pre-post-processors/#pre_post_processors_happiness
This (in my opinion) is not very interesting as it isn't actionable.
Maybe my original proposal isn't ideal and better, more specific questions can be found that focus on tools and IDE's?
Maybe there should be a question about which tools people use to author their CSS, in the first place. And a second question could ask how happy they are in general with their tools.
Then there could still be a way to ask for specific pain points or incompatibilities to new CSS features.
Sebastian
from surveys.
That's interesting but it may be a bit too niche to ask about?
from surveys.
In which way is this niche?
Just a repeat of the compat issues question but focussed on developer tools would already be very valuable.
from surveys.
I assume @SachaG means "niche" in a way that the answers would be very specific and only target specific tools. So the outcome of that question might not overlap much.
People should rather create bug reports for their tools instead.
The collected data would only be valuable if the editors of those tools actually see the answers and take action on them. For IDE developers this probably isn't the case most of the time.
Though I still see some value in that for tools strictly tied to CSS like pre- and post-processors, CSS frameworks and CSS-in-JS libraries.
Sebastian
from surveys.
means "niche" in a way that the answers would be very specific and only target specific tools. So the outcome of that question might not overlap much.
This I understand. The question and options will need to be carefully picked for this to be valuable in any way. Any maybe we do not find the right question or options, that would be fine.
People should rather create bug reports for their tools instead.
Most people don't do this.
As a maintainer of a couple of dev tools I am always surprised at how many people tweet about a thing being broken vs. actually open an issue.
From my perspective it seems that there is a barrier for most developers between having a problem with a tool and reporting this problem.
- do you have a GitHub account?
- do you feel you have agency to open an issue?
- do you feel confident about your ability to explain the issue?
- are you able to pinpoint the tool or library causing the issue?
- are you discouraged after having seen a lot of "won't fix" + close in one project
The collected data would only be valuable if the editors of those tools actually see the answers and take action on them. For IDE developers this probably isn't the case most of the time.
I am here, I would see the results and I will do my absolute best to make sure answers are brought to the attention of maintainers in an actionable way.
I co-maintain the polyfill-library and postcss-preset-env and contribute to countless other projects. Because I use VSCode, this includes the bits that relate to CSS. There are others like me.
A lot of the questions related to tooling read like a popularity contest.
With few exceptions like : https://2021.stateofcss.com/en-US/technologies/pre-post-processors/#pre_post_processors_happiness
This (in my opinion) is not very interesting as it isn't actionable.
Maybe my original proposal isn't ideal and better, more specific questions can be found that focus on tools and IDE's?
from surveys.
Maybe there should be a question about which tools people use to author their CSS, in the first place. And a second question could ask how happy they are in general with their tools.
I am unsure how this can be asked without just measuring the popularity of tools and IDE's.
I want to avoid pitting tools against each other in a question.
In the previous survey there was only one question (that I could find) that listed different browsers and this was without making this competitive : https://2021.stateofcss.com/en-US/environments/#browsers
from surveys.
which features are causing the most issues in popular editors and tools?
"popular editors and tools" This I meant as one group without specifying it as individual items.
Not a matrix of features and tools, but just a list of features and "does it work in your stack". Whatever "stack" might be.
from surveys.
Related Issues (20)
- Higher Education Degree - or Degrees?
- [Copy edit] [Subjective] Section: Why are there JS questions in an HTML Survey? HOT 1
- Bad copy for `alt` question HOT 4
- State of JS 2023 Feedback HOT 17
- State of Node.js/State of Back-end JavaScript 2024 Suggestions HOT 39
- State of JS 2024 Suggestions HOT 9
- Inconsistent result for the Most Adopted Feature award in State of CSS 2023
- Broken link for the Ratios Over Time heading in State of CSS 2023
- How to help with data normalization
- I wonder when I will know the results of the survey HOT 2
- [Comment Report] Exclusive Accordion / hKZyC4UOLMe1jryB0hdHQ
- [Comment Report] Popover API / JznsTrWdydxePZABVgSPm HOT 1
- [Comment Report] Form Pain Points/<code><input type="date"></code> / MhVWkGitKH0gAy82JObuI
- State of HTML 2024 Suggestions HOT 2
- [Comment Report] Solid / 060GbLVX4zvRMYovErSoR
- [Comment Report] React / 8OJHpE5Bfao_KrI3mfHgD
- State of JS 2024 Suggestions
- [Comment Report] Solid / 060GbLVX4zvRMYovErSoR
- [Comment Report] Browser APIs Pain Points/Dates / FgK5P_M-bfwfDD4Zrj31w
- [New Questions]
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from surveys.