state_of_js.yml

locale: en-US
namespace: js
translations:
  ###########################################################################
  # General
  ###########################################################################

  - key: general.state_of_js.intro
    t: >
      The JavaScript world could use a bit of classification.


      Since 2016, this survey has collected 
      data from over 20,000 developers each year to identify current and upcoming trends.


      Together, let's find out which libraries developers 
      want to learn next, which have the best retention ratings, and much more.

  - key: general.state_of_js.description
    t: The annual developer survey of the JavaScript ecosystem

  ###########################################################################
  # Sections
  ###########################################################################

  - key: sections.syntax.title
    t: Syntax
  - key: sections.syntax.description
    t: The grammar of JavaScript.

  - key: sections.language.title
    t: Language
  - key: sections.language.description
    t: The vocabulary of JavaScript.

  - key: sections.data_structures.title
    t: Data Structures
  - key: sections.data_structures.description
    t: How you store and manipulate data.

  - key: sections.browser_apis.title
    t: Browser APIs
  - key: sections.browser_apis.description
    t: The features provided by the browser.

  - key: sections.other_features.title
    t: Other Features
  - key: sections.other_features.description
    t: Other technologies and patterns

  - key: sections.patterns.title
    t: Patterns
  - key: sections.patterns.description
    t: How you prefer writing code

  - key: sections.javascript_flavors.title
    t: JavaScript Flavors
  - key: sections.javascript_flavors.description
    t: Languages that compile to JavaScript

  - key: sections.front_end_frameworks.title
    t: Front-end Frameworks
  - key: sections.front_end_frameworks.description
    t: Front-end frameworks and libraries

  - key: sections.datalayer.title
    t: Data Layer
  - key: sections.datalayer.description
    t: Loading and managing data in your app

  - key: sections.rendering_frameworks.title
    t: Rendering Frameworks
  - key: sections.rendering_frameworks.description
    t: Frameworks focused on rendering and serving your application

  - key: sections.back_end_frameworks.title
    t: Back-end Frameworks
  - key: sections.back_end_frameworks.description
    t: JavaScript on the server

  - key: sections.testing.title
    t: Testing
  - key: sections.testing.description
    t: Tools for testing your code

  - key: sections.mobile_desktop.title
    t: Mobile & Desktop
  - key: sections.mobile_desktop.description
    t: JavaScript for mobile devices and desktop apps

  - key: sections.build_tools.title
    t: Build Tools
  - key: sections.build_tools.description
    t: Compiling & bundling code

  - key: sections.monorepo_tools.title
    t: Monorepo Tools
  - key: sections.monorepo_tools.description
    t: Tools used to manage JavaScript monorepos.

  - key: sections.tools.title
    t: Other Tools
  - key: sections.tools.description
    t: Other JavaScript tools

  - key: sections.other_tools.title
    t: Other Tools
  - key: sections.other_tools.description
    t: For these tools & technologies, just check the ones that you use regularly.

  - key: sections.resources_js.title
    t: Resources
  - key: sections.resources_js.description
    t: What JavaScript resources do you consult?

  - key: sections.usage.title
    t: Usage
  - key: sections.usage.description
    t: How you use JavaScript

  ###########################################################################
  # Survey Help
  ###########################################################################

  - key: features.features_intro
    t: >
      Welcome to the survey! This first part is all about figuring out 
      which **features** of the JavaScript language you know about. 
      And if you know about something but haven't yet used it, that's fine too!

  - key: tools.tools_intro
    t: >
      The next couple sections focus on the **libraries** and **frameworks** that make up 
      the JavaScript ecosystem. Let us know what you're excited about!

  ###########################################################################
  # Options
  ###########################################################################

  # JS pain points
  # - key: options.js_pain_points.browser_interoperability
  #   t: Browser Compatibility
  # - key: options.js_pain_points.browser_interoperability.description
  #   t: Differences between Chrome, Safari, Firefox, etc.
  # - key: options.js_pain_points.animations
  #   t: Animations
  # - key: options.js_pain_points.animations.description
  #   t: Managing animations, transitions, etc. using JavaScript.
  # - key: options.js_pain_points.form_handling
  #   t: Form Handling
  # - key: options.js_pain_points.form_handling.description
  #   t: Creating forms, managing their state and errors, and saving their data.
  - key: options.js_pain_points.state_management
    t: State Management
  - key: options.js_pain_points.state_management.description
    t: Managing global data state in complex applications.
  # - key: options.js_pain_points.performance_issues
  #   t: Performance Issues
  # - key: options.js_pain_points.performance_issues.description
  #   t: Bundle sizes, slow loading, and other performance issues.
  - key: options.js_pain_points.managing_dependencies
    t: Managing Dependencies
  - key: options.js_pain_points.managing_dependencies.description
    t: Managing dependencies, package versions and bundle sizes.
  - key: options.js_pain_points.architecture
    t: Code Architecture
  - key: options.js_pain_points.architecture.description
    t: Organizing and maintaining your codebase.
  - key: options.js_pain_points.finding_packages
    t: Finding Packages
  - key: options.js_pain_points.finding_packages.description
    t: Finding and evaluating JavaScript packages.
  - key: options.js_pain_points.writing_modules
    t: Writing Modules
  - key: options.js_pain_points.writing_modules.description
    t: Writing JavaScript modules and publishing them as packages.
  - key: options.js_pain_points.debugging
    t: Debugging
  - key: options.js_pain_points.debugging.description
    t: Identifying and solving issues with your code.
  - key: options.js_pain_points.async_code
    t: Async Code
  - key: options.js_pain_points.async_code.description
    t: Handling asynchronous functions.
  - key: options.js_pain_points.modules_management
    t: Modules Management
  - key: options.js_pain_points.modules_management.description
    t: Writing and importing modules.
  - key: options.js_pain_points.date_management
    t: Date Management
  - key: options.js_pain_points.date_management.description
    t: Handling and manipulating dates and times.
  # - key: options.js_pain_points.xxx
  #   t:
  # - key: options.js_pain_points.xxx.description
  #   t:

  # JS missing features
  - key: options.currently_missing_from_js.static_typing
    t: Static Typing
  - key: options.currently_missing_from_js.static_typing.description
    t: Native types (similar to what TypeScript offers).
  - key: options.currently_missing_from_js.standard_library
    t: Standard Library
  - key: options.currently_missing_from_js.standard_library.description
    t: A standard library of common utilities
  - key: options.currently_missing_from_js.pattern_matching
    t: Pattern Matching
  - key: options.currently_missing_from_js.pattern_matching.description
    t: A new `match` keyword for pattern-matching objects.
  - key: options.currently_missing_from_js.pipe_operator
    t: Pipe Operator
  - key: options.currently_missing_from_js.pipe_operator.description
    t: A new `|>` operator for passing the result of one function to another.
  - key: options.currently_missing_from_js.decorators
    t: Decorators
  - key: options.currently_missing_from_js.decorators.description
    t: Decorators used to metaprogram and add functionality to a value.
  - key: options.currently_missing_from_js.immutable_data_structures
    t: Immutable Data Structures
  - key: options.currently_missing_from_js.immutable_data_structures.description
    t: New deeply immutable data structures such as `Record` and `Tuple`.
  - key: options.currently_missing_from_js.better_date_management
    t: Better Date Management
  - key: options.currently_missing_from_js.better_date_management.description
    t: A new `Temporal` object for working with dates and times.
  - key: options.currently_missing_from_js.observable
    t: Observable
  - key: options.currently_missing_from_js.observable.description
    t: A new `Observable`` type used to model push-based data sources.
  # - key: options.currently_missing_from_js.xxx
  #   t:
  # - key: options.currently_missing_from_js.xxx.description
  #   t:

  # What do you use JS for?
  - key: options.what_do_you_use_js_for.frontend_development
    t: Frontend Development
  - key: options.what_do_you_use_js_for.backend_development
    t: Backend Development
  - key: options.what_do_you_use_js_for.data_analysis
    t: Data Analysis
  - key: options.what_do_you_use_js_for.machine_learning
    t: Machine Learning
  - key: options.what_do_you_use_js_for.desktop_apps
    t: Desktop Apps
  - key: options.what_do_you_use_js_for.mobile_apps
    t: Mobile Apps
  - key: options.what_do_you_use_js_for.embedded_apps
    t: Embedded Apps
  - key: options.what_do_you_use_js_for.game_development
    t: Game Development
  - key: options.what_do_you_use_js_for.data_visualization
    t: Data Visualization
  - key: options.what_do_you_use_js_for.graphics_animation
    t: Graphics & Animation

  # JS App Patterns

  - key: options.js_app_patterns.single_page_app
    t: Single Page Application (SPA)
  - key: options.js_app_patterns.single_page_app.description
    t: Apps that run entirely in the browser
  - key: options.js_app_patterns.multiple_page_app
    t: Multi-Page Application (MPA)
  - key: options.js_app_patterns.multiple_page_app.description
    t: Apps that run entirely on the server, with minimal client-side dynamic behavior
  - key: options.js_app_patterns.static_site_generation
    t: Static Site Generation (SSG)
  - key: options.js_app_patterns.static_site_generation.description
    t: Pre-rendered static content, with or without a client-side dynamic element
  - key: options.js_app_patterns.server_side_rendering
    t: Server-Side Rendering (SSR)
  - key: options.js_app_patterns.server_side_rendering.description
    t: Dynamically rendering HTML content on the server before rehydrating it on the client
  - key: options.js_app_patterns.partial_hydration
    t: Partial Hydration
  - key: options.js_app_patterns.partial_hydration.description
    t: Only hydrating some of your components on the client (e.g. React Server Components)
  - key: options.js_app_patterns.progressive_rehydration
    t: Progressive Hydration
  - key: options.js_app_patterns.progressive_rehydration.description
    t: Controlling the order of component hydration on the client
  - key: options.js_app_patterns.islands_architecture
    t: Islands Architecture
  - key: options.js_app_patterns.islands_architecture.description
    t: Isolated islands of dynamic behavior with multiple entry points in an otherwise static site (Astro, Eleventy)
  - key: options.js_app_patterns.progressive_enhancement
    t: Progressive Enhancement
  - key: options.js_app_patterns.progressive_enhancement.description
    t: Making sure an app is functional even without JavaScript
  - key: options.js_app_patterns.incremental_static_generation
    t: Incremental Static Generation
  - key: options.js_app_patterns.incremental_static_generation.description
    t: Being able to dynamically augment or modify a static site even after the initial build (Next.js ISR, Gatsby DSG)
  - key: options.js_app_patterns.streaming_ssr
    t: Streaming SSR
  - key: options.js_app_patterns.streaming_ssr.description
    t: Breaking down server-rendered content in smaller streamed chunks
  - key: options.js_app_patterns.resumability
    t: Resumability
  - key: options.js_app_patterns.resumability.description
    t: Serializing framework state on the server so the client can resume execution with no duplicated code execution.
  - key: options.js_app_patterns.edge_rendering
    t: Edge Rendering
  - key: options.js_app_patterns.edge_rendering.description
    t: Altering rendered HTML at the edge before sending it on to the client

  ###########################################################################
  # Features
  ###########################################################################

  # syntax
  - key: features.destructuring
    t: Destructuring
  - key: features.spread_operator
    t: Spread operator
  - key: features.arrow_functions
    t: Arrow Functions
  - key: features.nullish_coalescing
    t: Nullish Coalescing
  - key: features.optional_chaining
    t: Optional Chaining
  - key: features.private_fields
    t: Private Fields

  # language
  - key: features.proxies
    t: Proxies
  - key: features.async_await
    t: Async/Await
  - key: features.promises
    t: Promises
  - key: features.decorators
    t: Decorators
  - key: features.decorators.description
    t: >
      In its simplest form, a decorator is simply a way of 
      wrapping one piece of code with another — literally “decorating” it.
  - key: features.dynamic_import
    t: Dynamic Import

  # patterns
  - key: patterns.object_oriented_programming
    t: Object-Oriented Programming
  - key: features.functional_programming
    t: Functional Programming
  - key: features.reactive_programming
    t: Reactive Programming

  # upcoming features
  # - key: features.static_typing
  #   t: Static Typing

  # - key: features.standard_library
  #   t: Standard Library

  # - key: features.pattern_matching
  #   t: Pattern Matching

  # - key: features.pipe_operator
  #   t: Pipe Operator

  # - key: features.immutable_data_structures
  #   t: Immutable Data Structures

  # slider
  - key: options.js_ts_balance.0
    t: 100% JS
  - key: options.js_ts_balance.4
    t: 50%/50%
  - key: options.js_ts_balance.8
    t: 100% TS

  ###########################################################################
  # Tools
  ###########################################################################

  - key: tools.angular.description
    t: >
      Note that this question only targets [Angular](https://angular.io/) experience,
      and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/).

  ###########################################################################
  # Other Tools
  ###########################################################################

  - key: tools.runtimes
    t: JavaScript Runtimes
  - key: tools.runtimes.question
    t: Which engines/runtimes/execution environments do you regularly use?
  - key: tools.runtimes.others
    t: Other Runtimes
  - key: tools.runtimes.others.description
    t: Other answers (freeform field).

  - key: tools.package_registries
    t: Package Registries
  - key: tools.package_registries.question
    t: Which package registries do you regularly fetch packages from?
  - key: tools.package_registries.others
    t: Other Package Registries
  - key: tools.package_registries.others.description
    t: Other answers (freeform field).

  - key: tools.form_factors
    aliasFor: environments.form_factors
  - key: tools.form_factors.description
    aliasFor: environments.form_factors.question

  - key: tools.backend_as_a_service
    t: Backend-as-a-Service Providers
  - key: tools.backend_as_a_service.question
    t: Services that host your data and offer a client API to access it.
  - key: tools.backend_as_a_service.others
    t: Other BaaS Providers

  - key: tools.date_management
    t: Date Management
  - key: tools.date_management.question
    t: Libraries that help with date and timezone management.
  - key: tools.date_management.others
    t: Other Date Management Libraries

  - key: tools.data_visualization
    t: Data Visualization
  - key: tools.data_visualization.question
    t: Libraries that help with charts and other data visualizations.
  - key: tools.data_visualization.others
    t: Other Data Visualization Libraries

  - key: tools.graphics_animation
    t: Graphics & Animations
  - key: tools.graphics_animation.question
    t: Libraries dedicated to graphcis and animation.
  - key: tools.graphics_animation.others
    t: Other Graphics & Animations Libraries

  - key: tools.data_fetching
    t: Data Fetching
  - key: tools.data_fetching.question
    t: Libraries that manage data fetching and caching.
  - key: tools.data_fetching.others
    t: Other Data Fetching Libraries

  - key: tools.backend_frameworks
    aliasFor: sections.back_end_frameworks.title
  - key: tools.backend_frameworks.description
    t: Frameworks for generating APIs and managing back-ends
  - key: tools.backend_frameworks.others
    t: Other Back-end Frameworks

  ###########################################################################
  # Usage
  ###########################################################################

  - key: usage.js_app_patterns
    t: Application Patterns
  - key: usage.js_app_patterns.question
    t: Which of the following architecture and rendering patterns have you used **in the last year**?
  - key: usage.js_app_patterns.others
    t: Other App Patterns

  - key: usage.what_do_you_use_js_for
    t: What do you use JavaScript for?
  - key: usage.what_do_you_use_js_for.others
    t: Other JavaScript Use Cases

  - key: usage.js_ts_balance
    t: JavaScript/TypeScript Balance
  - key: usage.js_ts_balance.question
    t: Assuming you use TypeScript, how do you divide your time between writing JavaScript and TypeScript code?

  - key: tools.edge_runtimes
    t: JavaScript Edge/Serverless Runtimes
  - key: tools.edge_runtimes.question
    t: Which edge or serverless runtimes do you regularly use?
  - key: tools.edge_runtimes.others
    t: Other Edge Runtimes

  - key: usage.usage_type
    t: JavaScript Usage
  - key: usage.usage_type.question
    t: In what context do you use JavaScript?
  - key: usage.usage_type.others
    t: Other Usages

  - key: usage.pick_of_the_year
    t: Your “Pick of the Year”
  - key: usage.pick_of_the_year.description
    t: The name of a feature, library, framework, company, person, blog post, etc. you want to highlight this year.

  ###########################################################################
  # Opinions
  ###########################################################################

  - key: opinions.js_moving_in_right_direction
    t: JavaScript is moving in the right direction

  - key: opinions.building_js_apps_overly_complex
    t: Building JavaScript apps is overly complex right now

  - key: opinions.js_over_used_online
    t: JavaScript is over-used online

  - key: opinions.enjoy_building_js_apps
    t: I enjoy building JavaScript apps

  - key: opinions.would_like_js_to_be_main_lang
    t: I would like JavaScript to be my main programming language

  - key: opinions.js_ecosystem_changing_to_fast
    t: The JavaScript ecosystem is changing too fast

  - key: opinions_others.missing_from_js.others
    t: What do you feel is currently missing from JavaScript?
  - key: opinions_others.missing_from_js.others.description
    t: Features you'd like to see in JavaScript one day.

  - key: happiness.front_end_frameworks
    t: How happy are you with the state of front end frameworks?
  - key: happiness.back_end_frameworks
    t: How happy are you with the state of back end frameworks?
  - key: happiness.testing
    t: How happy are you with the state of testing tools?
  - key: happiness.mobile_desktop
    t: How happy are you with the state of mobile & desktop frameworks?
  - key: happiness.build_tools
    t: How happy are you with the state of build tools?
  - key: happiness.monorepo_tools
    t: How happy are you with the state of monorepo tools?

  - key: happiness.state_of_the_web
    t: How happy are you with the general state of web technologies?

  - key: happiness.state_of_js
    t: How happy are you with the general state of JavaScript?

  # Pain Points
  - key: opinions.js_pain_points
    t: JavaScript Pain Points
  - key: opinions.js_pain_points.description
    t: For each matchup, pick the aspect of JavaScript you struggle with the most.

  - key: opinions_others.js_pain_points.others
    t: Other JavaScript Pain Points

  # Missing Features
  - key: opinions.currently_missing_from_js
    t: What do you feel is currently missing from JavaScript?
  - key: opinions.currently_missing_from_js.description
    t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today.
  - key: opinions_others.currently_missing_from_js.others
    t: Other Missing Features

  # pain points/currently missing (results)
  - key: js_pain_points.js_pain_points_wins
    t: JavaScript Pain Points
  - key: js_pain_points.js_pain_points_wins.description
    t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won.

  - key: js_pain_points.js_pain_points_matchups
    t: JavaScript Pain Points (Matchups)
  - key: js_pain_points.js_pain_points_matchups.description
    t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item.

  - key: currently_missing_from_js.currently_missing_from_js_wins
    t: Features Missing From JavaScript
  - key: currently_missing_from_js.currently_missing_from_js_wins.description
    t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won.

  - key: currently_missing_from_js.currently_missing_from_js_matchups
    t: Features Missing From JavaScript (Matchups)
  - key: currently_missing_from_js.currently_missing_from_js_matchups.description
    t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item.

  ###########################################################################
  # Resources
  ###########################################################################

  - key: resources.first_steps_js
    t: First Steps With JavaScript
  - key: resources.first_steps_js.description
    t: When first starting out, how did you initially learn JavaScript?