What I Learned from State of JS 2024

Поділитися
Вставка
  • Опубліковано 2 гру 2024

КОМЕНТАРІ • 12

  • @shrutikapoor08
    @shrutikapoor08 День тому +3

    I love that you were taking notes as you went along

  • @CourtneyR_dev
    @CourtneyR_dev 3 години тому

    Timestamps (Powered by Merlin AI)
    00:03 - Participating in the 2024 State of JavaScript survey enhances community engagement and knowledge.
    02:10 - Exploring non-mutating array methods and browser APIs for JavaScript.
    06:31 - Browser APIs face inconsistency, impacting developer experiences across frameworks.
    08:49 - Overview of experiences with various meta frameworks and testing tools.
    13:17 - Testing and development in React Native has inherent challenges.
    15:45 - Exploring various JS tools and frameworks with mixed feelings.
    20:20 - Overview of frequently used libraries and frameworks in daily development.
    22:53 - Discussion on favorite runtimes and AI tools for coding.
    27:36 - The challenges of modern JavaScript package management and emerging TC39 proposals.
    29:53 - Exploring potential additions and concerns in JavaScript's evolving landscape.
    34:19 - The speaker shares personal background and experiences related to the State of JS survey.
    36:37 - Encouragement to engage with the channel's content.

  • @noahwinslow3252
    @noahwinslow3252 День тому +1

    I really love sets for figuring out what elements of an array (really a set as an array in this context) are in my array but not in another since doing so with arrays only involves a combination of .filter and .find (or.some) whereas setDifference makes this much more readable.

  • @eliasepg
    @eliasepg День тому +2

    27:45 Oh man, I didn't know that, I've stopped using npm trends but I really liked that feature where they recommended several packages as alternatives, and i just checked it out, oh no it's really dissapointing..

  • @alvingultiano7513
    @alvingultiano7513 9 годин тому +1

    What really side are you in Nextjs or Tanstack ?

    • @jherr
      @jherr  6 годин тому

      Neither. I think both are good. Although comparing the two, the API surface of NextJS is a lot more settled than TanStack Start. So if you go with TanStack today, IMHO, you are in for a bumpier ride than NextJS.

    • @alvingultiano7513
      @alvingultiano7513 4 години тому

      ​@@jherrI agree with your perspective. Both have their strengths, but you're right about the stability factor. Next.js has a more mature and established API, which often translates to smoother development and fewer unexpected changes. TanStack Start is promising, but its evolving nature might mean more adjustments down the road. IMHO, for a production project, Next.js currently offers a more predictable experience. Speaking streamlined and performance Nextjs good

  • @MicahIsaiahAtnadu
    @MicahIsaiahAtnadu День тому +2

    Great🔥

  • @joaosaraiva1998
    @joaosaraiva1998 День тому +1

    React shirt

  • @greendsnow
    @greendsnow День тому +5

    what's the point. all questions should be like 'Is your AI using ....this and that...? '

  • @DiscipleofYah777
    @DiscipleofYah777 9 годин тому +2

    Selenium sucks to use imo and would not recommend