Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

State of JS 2025 Suggestions #255

Open
SachaG opened this issue Nov 14, 2024 · 8 comments
Open

State of JS 2025 Suggestions #255

SachaG opened this issue Nov 14, 2024 · 8 comments

Comments

@SachaG
Copy link
Member

SachaG commented Nov 14, 2024

  • Biome is not a build tool
  • vue_news is discontinued
@SachaG
Copy link
Member Author

SachaG commented Nov 14, 2024

#85 (comment)

@SachaG
Copy link
Member Author

SachaG commented Nov 28, 2024

Reintroduce Utilities question?

Tools like eslint, prettier, dprint, stylelint, Babel, Biome, swc, etc. are all developer tools that don't get to be listed, and some of them are huge

@SachaG
Copy link
Member Author

SachaG commented Dec 9, 2024

Screenshot 2024-12-09 at 15 15 33

This wording is confusing since "Types as comments" is the old name for "type annotations". So a better set of options could be:

  • Runtime types
  • Type annotations
  • JSDoc
  • No types
  • Other…

The only issue is that I assume the vast majority of people who want types do so because they like TypeScript. And they might only know that they want something like that, without really knowing the details of which implementation they prefer…

See also: #62 (comment)

@SachaG
Copy link
Member Author

SachaG commented Dec 10, 2024

Add question: Why did you take the survey?

  • To learn about the ecosystem
  • To help figure out trends
  • To help with representation
  • I find it fun
  • other…

@autonome
Copy link

A challenge with understanding platform-level feature gaps is that developer decisions are rarely framed in the context of alternatives.

For example, the question "What's missing from the web" will likely yield very different answers than "What capabilities force you to choose a native platform over the web platform?".

Would need separate questions for mobile vs desktop, since the capabilities and use-cases are different when making choice of Electron vs web for desktop, or Swift vs web on iOS for example.

Also, this question implies that native platform developers are taking the survey. A risk is that the question would not be getting answers from non-JS native platform devs. A mitigation is that JS-based toolkits for native (or native-like) development like React Native and Electron are popular enough that it would likely still result in high-signal feedback.

Could also mitigate with a gating question first like "Do you use JS toolkits for native platform development, or develop for native platforms in their non-JS languages?" which unlocks the mobile/desktop feature gap questions.

@SachaG
Copy link
Member Author

SachaG commented Dec 17, 2024

Screenshot 2024-12-17 at 9 01 14

@SachaG
Copy link
Member Author

SachaG commented Dec 17, 2024

Clarify "Native Apps" label:

Devographics/Monorepo#472

@SachaG
Copy link
Member Author

SachaG commented Dec 18, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants