-
Notifications
You must be signed in to change notification settings - Fork 8
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
Comments
Reintroduce Utilities question?
|
This wording is confusing since "Types as comments" is the old name for "type annotations". So a better set of options could be:
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) |
Add question: Why did you take the survey?
|
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. |
Clarify "Native Apps" label: |
The text was updated successfully, but these errors were encountered: