Community

ivue grew out of shipped products, and it keeps growing through the conversations below. Bring questions, bug reports, wild ideas, or a benchmark you don't believe — there's no ticket queue on the other end, just the people who write the code. Welcome in.

Get help, talk shop

Each channel has a job — picking the right one gets you answered fastest:

GitHub

Source Code

Browse ivue, its tests, examples, and benchmarks.

Discussions

"Is this the right pattern?" questions, ideas, and show-and-tell.

Issues

Bugs and defects. A minimal reproduction turns a report into a fix.

Community

Discord

Live chat — quick questions, work-in-progress, and community help.

Socials

Follow on X

Updates from Evgeny: releases, benchmarks, examples, and new ideas.

Connect on LinkedIn

Professional background, writing, and work beyond ivue.

Feedback

The best feedback is public — others can +1 it, refine it, and watch it become a change:

If something in the docs is wrong, unclear, or missing — that's a bug too. Every page's source is available in the v2 docs on GitHub.

Start a GitHub discussion →Anonymous feedback form →

Follow the work

New posts, releases, and measured numbers land on the Blog, on X, and in GitHub Releases.

Blog Newsletter

The whole blog, delivered in 114 days — one post every other day, at your local morning:

Get the blog as a newsletter

Who's behind ivue

AuthorEvgeny KalashnikovLead Software Engineer@Blackline, Adhoc Studio

XGitHubLinkedInEmail

ivue was not designed in theory. It was reduced out of a production application — where deep class graphs, fields, grids, and stores had to stay coherent under real load. The examples are descendants of that system. v2 carries the same conclusion in its smallest form: plain classes, full reactivity, one kilobyte.

Credits

Nothing here was built alone. A few people and projects permanently rewired how I think about software — ivue carries their fingerprints on every page, and naming them is a pleasure:

Evan You — Vue

Creator of Vue. The reactivity engine ivue rides on — refs, effects, and the scheduler that makes a 1 kB class layer possible at all.

Taylor Otwell — Laravel

The standing proof that developer experience is a feature — API elegance practiced as an engineering discipline, not a garnish.

MobX

Transparent reactive objects, years ahead of the field — the prior art that showed plain-looking classes could be fully observable.

Pete Heard — UI Academy

Framework-agnostic UI architecture and model–view separation, taught as a testable discipline — the school of thought behind the model layer.

Blackline

Where ivue works for a living — the first version was implemented and battle-tested here, in production, before it was ever a library.

Adhoc Studio

The studio where ivue's ideas were shaped against real client work — every pattern on this site survived a shipping deadline first.