"Digitalocean" -> "Digital Ocean", "Openshift" -> "OpenShift", "Openstack" -> "OpenStack". "Apl" -> "APL", "Gdscript" -> "GDScript", "Html/Css" -> "HTML/CSS" (and why are they together? I would have put them separately), "Javascript" -> "JavaScript" (calling just to bug them :P), "Matlab" -> "MATLAB", "Ocaml" -> "OCaml", "Php", "PHP", "Powershell" -> "PowerShell", "Typescript" -> "TypeScript" (again, calling "Vb.Net" -> "VB.NET" (or "Visual Basic (.NET)"?). (I may have missed some) Under "Programming, scripting, and markup language:" What about languages from the Hardware Description family? Ex. Hide questions about C/C++ compilers if the participant hasn't selected that they use C++. These highly language-specific technology categories can be conditionally made visible in the survey when the participant indicates that they are using the relevant contextual technology. I remember when I tried to dip my toes in Flutter, it was quite overwhelming to see the list and try to pick one. I'm kind of interested in what state-management technologies people are using in their Flutter projects. It might be useful to take a look at how other people are conducting similar surveys, such as JetBrains: which does an overall survey, and then ecosystem specific ones. Under "Development Environments:"- no Code::Blocks? The same question goes for C, ECMAScript (related: tsconfig's target field) It would be interesting to know about what C++ language versions people are using in their projects. In the same list where there is GTK and Qt, it would be nice to see other C++ GUI libraries, such as Dear ImGui, FLTK, and WxWidgets.Īnd how could I forget about C++ non-system package managers? Of which they include (but are not limited to): vcpkg, Conan, Spack, Hunter, and build2 (it's also a package manager). I'm also curious about C++ testing libraries- of which some (I pulled the ones I know from the previous link) are: Boost.Test, Catch2, cppunit, doctest, Google Test (see the full list to avoid my bias). Such a list would at the very least include GCC, LLVM's Clang, MSVC, and would do well to also include MinGW, Mingw-w64, Intel C++ Compiler, and some relatively newer blood like Circle. I'm also interested to see what compilers C and C++ devs are supporting in their projects. If this gets given its own category, I'd also like to see IDE-based "buildsystems" in it, such as Xcode, and Visual Studio Solutions. Some form of "what buildsystem tool alternative to CMake do you use" is a frequently rehashed question on r/cmake, so it'd be real nice to get data on this in a survey with as wide a reach as the SO dev survey. Why no C/C++ buildsystem technologies? GNU Make, CMake, Ninja, Meson, build2, MSBuild, QMake, SCons. Why is Maven listed, but not Ant or Gradle? Apache Subversion (SVN), Mercurial)?Īnd why is GitHub listed under Collaboration Tools, but not other similar platforms like BitBucket and GitLab? Why was Git listed last year, but not listed this year (nor other version control software / source control management software? Ex. Why is Homebrew listed, but a bunch of other package managers aren't? Ex. When you say "Bash/Shell", is "Shell" supposed to be a catch-all for shells like the Bourne Shell ( sh), Zsh, C Shell, tcsh, Dash, Fish, etc.? should that section be renamed to "Programming, scripting, query, and markup languages:"? Out of curiosity, do query languages fit within the categories of "programming, scripting, and markup languages"? Or are they different? I.e. We will be collecting feedback until Friday, April 28, 2023. That being said, we are very excited to kick off the survey next month and look forward to hearing from you. Any suggestions will be considered, but we will not necessarily be honoring all suggestions. While we are reviewing your answers here, keep in mind we may not reply to them unless we need clarification. We’re going to experiment with different analyses for this, aiming to remove the emotional attribution while still examining the responses for "Worked With and Want to Work With”. We have also heard your feedback on the Loved, Dreaded, Wanted analysis. If you notice any additional options that should be included, please post an answer below with the name, category, and a brief description or references to why it should be included in this year's survey. It is that time of year again when we ask you all to be our second pair of eyes on the annual Developer Survey! Below you will find the technology choices we would like to include in the 2023 survey. Update on May 3rd, 2023: Thank you for all the comments and suggestions! We have collected your responses and have completed reviewing your suggestions for the survey.
0 Comments
Leave a Reply. |