JavaScript Is Evolving Faster Than Ever — And JSConf Spain Made It Impossible to Ignore
There’s something powerful about stepping away from your day-to-day work and being surrounded by people asking the same questions you’ve been thinking about:
- What’s actually changing in JavaScript?
- What should we be paying attention to right now?
- And more importantly — where is all of this going?
At JSConf Spain, those answers don’t come from a single talk. They emerge from patterns — ideas that repeat across different speakers, different companies, and different perspectives.
And this year, one thing became very clear:
JavaScript is no longer just evolving — it’s expanding into intelligence, infrastructure, and decision-making systems.
From AI running directly in the browser and at the edge, to real conversations about ethical AI in production, to a growing shift away from framework obsession — the ecosystem is going through a deeper transformation than it might seem on the surface.
But beyond the talks, something else stood out:
Being there — in person — changes how you understand all of this.
Because conferences like JSConf aren’t just about content.
They’re about seeing what other teams are actually building, hearing what’s working (and what’s not), and connecting ideas in a way that’s hard to replicate anywhere else.
This is not a recap.
It’s a reflection on the patterns that emerged — and what they mean for how we build, think, and evolve as developers today.
JavaScript is becoming a runtime for intelligence
One of the clearest signals of where things are heading came from Erick Wendel’s talk.
This wasn’t about calling AI APIs.
It was about running AI directly in JavaScript.
From genetic algorithms and reinforcement learning to Transformers.js at the edge, and even local RAG powered by SQLite in WebAssembly — all running in:
- the browser
- Node.js
- edge environments
The shift is clear:
AI is moving from being a service → to becoming part of the runtime.
This means:
- no per-request costs
- privacy by default
- no vendor lock-in
But more importantly:
JavaScript is no longer just coordinating systems — it’s becoming where intelligent systems run.
And that changes everything about how we build.
From writing code to building with agents
In Gisela’s talk, the shift wasn’t abstract — it was practical.
AI is no longer just helping us autocomplete code.
It’s starting to work alongside us.
Using agents to build applications with tools like Astro, Vue, or any frontend framework, the idea becomes clear:
We’re moving from writing every line → to collaborating with systems that help us build.
This changes the developer experience:
- less focus on manual implementation
- more focus on defining intent
- faster iteration loops
And maybe the most interesting part:
Programming is becoming more interactive, more dynamic — and even more fun.
But underneath that shift, there’s something deeper:
The value is no longer just in writing code —
it’s in knowing how to guide, structure, and collaborate with these systems effectively.
We’re finally moving past framework obsession
In Fernando Herrera’s talk, something the entire community has felt for years was finally put into words:
We’ve been optimizing for the wrong thing.
For too long, JavaScript conversations have been dominated by:
- Which framework to use
- What’s trending
- What to switch to next
But none of that solves the real problems.
Because in production:
- performance issues don’t care about your framework
- memory leaks don’t care about your stack
- complexity doesn’t disappear with a new tool
What actually matters is:
- understanding how your system behaves
- knowing where it breaks
- being able to reason about it under pressure
Which leads to a simple but powerful shift:
Frameworks change.
Fundamentals don’t.
And maybe that’s where the ecosystem is finally maturing:
Less focus on tools — more focus on understanding.
AI in production is not just technical — it’s a responsibility
In Anna Vía’s talk, the focus wasn’t on what AI can do — but on what it should do.
Using real examples from InfoJobs, the message was clear:
Building AI in production means dealing with real consequences.
These systems:
- influence job opportunities
- make recommendations that affect people
- and can introduce bias if not carefully designed
Which leads to a critical shift:
Not everything that can be automated should be automated.
Instead of full automation, the approach is:
- keep humans in the loop
- design for explainability
- define clear boundaries
Because in the end:
You’re not just building intelligent features — you’re building systems people need to trust.
Final Thoughts
If JSConf Spain made something clear, it’s that we’re not just going through another wave of tools or trends.
We’re going through a shift in how we build.
- AI is no longer something we call — it’s something we run
- Frameworks are no longer the center — systems are
- Writing code is no longer the only skill — understanding behavior is
But maybe the most valuable part of all of this wasn’t any single talk.
It was the perspective you gain when you step into a space where everyone is building, experimenting, and questioning the same things.
Because seeing what others are doing — in real conversations, not curated demos — helps you recalibrate your own direction.
It helps you understand not just what’s possible, but what actually matters.
And that’s the real power of conferences like JSConf.
They don’t just give you answers.
They help you ask better questions.
JavaScript isn’t slowing down.
It’s expanding — into intelligence, into infrastructure, into everything.
The real question is:
Are we evolving with it? 🚀
🎥 Watch the talks
If you’d like to explore the full conference and dive deeper into the talks:
🙌🏼 Acknowledgements
A huge thank you to the organizers, speakers, and the entire community behind JSConf Spain for creating such a meaningful space to learn, connect, and share.
Events like this remind us that beyond the code, what truly moves the ecosystem forward is the people behind it.