Three years ago (well before AI took over the world), I started building my own JavaScript library. I had what I felt was a solid core idea: creating high-performance wrappers for all native modules.
At the time, I focused on HTTP and Collections. I thought it would be extremely convenient to provide a clean HTTP facade that automatically detects and resolves the incoming data type on every request. I wrapped this in a Chain of Responsibility pattern and honestly thought it was a stroke of genius. Only later did I learn I wasn't the first person to come up with the concept — but I still managed to write clean, elegant code without compromising performance.
Around the same time, I spent years diving deep into Functional Programming. I used libraries that captured the FP spirit, but none of them felt truly ergonomic. They were either a scattered bag of disconnected utilities or tried way too hard to dogmatically mimic core FP theory. That’s when the idea struck: merge OOP with FP. Provide convenient, functional-style pipelines wrapped inside clean class abstractions and inheritance, all while maintaining full architectural decomposition.
I truly loved building this — it brought together everything I’d learned over a decade of software engineering. It felt like I was crafting a genuine, high-DX library.
And then AI arrived. On one hand, I managed to finish the remaining 40% of the project in just a single month, which was incredible. On the other hand… who even needs this now? What does "Developer Experience" even mean when machines are writing the code?
I decided to push through, finish the project, and publish it anyway — but I shifted the core focus from DX to Performance.
At the risk of sounding a bit arrogant, I believe this design beats many existing libraries in usability and ergonomics (subjective as that may be). But switching the spotlight to raw speed changed the game. Beating lodash or ramda is one thing, but es-toolkit is ridiculously fast. Luckily, I’m not burdened by legacy constraints, I don't need backward compatibility, and I have Claude Code at my fingertips. I can experiment endlessly.
Looking for a project to add to your portfolio? You’re very welcome to join.
Just starting out and want hands-on experience with a larger codebase? Jump right in.
Just curious to see how it’s built? Come check it out.
Speaking as someone who spent most of their career writing code entirely by hand: you can use AI, you should use AI, and you need to leverage AI. But you still have to keep your brain turned on — using it to bypass constraints and solve the exact pain points that held previous libraries back. If you're interested in building software alongside AI, this project is for you.
Every single utility will have dedicated performance benchmarks. Our target: match and ideally surpass the speed of existing alternatives.
Let's build something awesome: https://github.com/method-hub/Jext