Skip to main contentblog
back to blog

learning frontend in 2025: the ai confusion

21 oct 2025, 07:14 utc+8·4 min read
share:

too many choices, too much help

learning frontend development right now feels different. maybe harder. maybe easier. honestly? i'm confused.

we have AI assistants like claude code. we have models like sonnet 4.5 that can write entire components. we have frameworks multiplying faster than we can learn them.

react? vue? svelte? which one should you actually learn?

the framework paradox

five years ago, the answer was simple: learn react. everyone used it. jobs wanted it.

today? it's complicated:

  • react - still the biggest. app router, server components, new hooks. feels like learning react again every year.
  • vue - cleaner syntax, easier to start. vue 3 composition api looks suspiciously like react hooks.
  • svelte - "no virtual dom" they said. "truly reactive" they said. svelte 5 runes just dropped. more syntax to learn.

each framework has its own:

  • state management story
  • routing solution
  • build tools
  • ecosystem

you can't learn them all. but choosing one feels like fomo.

the ai assistant dilemma

here's the weird part: claude code can write components in any framework.

// me: "build a todo app in svelte"
// claude: *generates perfect svelte code*
 
<script lang="ts">
  let todos = $state<Todo[]>([])
 
  function addTodo(text: string) {
    todos.push({ id: Date.now(), text, done: false })
  }
</script>

it looks perfect. it works. but did i learn anything?

the question: should you learn frameworks deeply, or just learn enough to guide AI?

learning with vs learning from ai

i've noticed two approaches:

learning from ai (the traditional way):

  • ask claude to explain concepts
  • ask it to write example code
  • study the output
  • try to recreate it yourself

learning with ai (the new way):

  • have a project idea
  • pair program with claude
  • learn patterns as you build
  • iterate quickly, make mistakes faster

the second one feels more real. you're building actual things. but there's a trap: you might not understand what you're building.

the depth vs breadth problem

sonnet 4.5 is scary good. it knows:

  • react server components
  • vue composables
  • svelte runes
  • solid.js signals
  • qwik resumability

it can explain trade-offs. suggest optimizations. refactor your code.

but here's the thing: understanding trade-offs requires context that only comes from experience.

you can ask "react or vue?" but the answer depends on:

  • team size
  • project complexity
  • performance needs
  • developer experience
  • ecosystem requirements

ai can list these factors. it can't tell you what matters for your specific situation.

what i'm doing about it

honestly? still figuring it out. but here's my current approach:

  1. pick one framework, go deep - for me it's react. not because it's the best, but because choosing anything is better than choosing nothing.

  2. use ai as a pair programmer - not as a teacher. build things together, but make sure i understand each piece.

  3. read the source code - when claude generates something clever, i dig into why it works. what patterns is it using?

  4. build without ai sometimes - force myself to struggle. that's where real learning happens.

  5. learn fundamentals, not just frameworks - javascript, typescript, browser apis, http, state management patterns. these transfer across frameworks.

the uncomfortable truth

maybe the confusion is the point.

frontend development has always been about adapting. new tools, new patterns, new best practices every year.

AI doesn't change that. it just makes the pace faster.

the developers who thrive won't be the ones who memorize every framework api. they'll be the ones who:

  • understand core concepts deeply
  • adapt to new tools quickly
  • know when to use ai and when to think for themselves
  • build things consistently

so... which framework?

still confused? here's my honest take:

  • react - if you want jobs and a huge ecosystem
  • vue - if you want developer happiness and gradual learning
  • svelte - if you want to understand reactivity deeply

or you know what? pick the one that excites you most. build something real with it. use claude code to help when you're stuck.

the confusion will always be there. might as well build stuff while confused.

what's your experience learning frontend with AI? confused too? figured it out? let me know.

contents
  • too many choices, too much help
  • the framework paradox
  • the ai assistant dilemma
  • learning with vs learning from ai
  • the depth vs breadth problem
  • what i'm doing about it
  • the uncomfortable truth
  • so... which framework?