v1.0 Roadmap?

[isbee]

@jondot claims Loco is production ready. (source: reddit)

I believe this is likely true because Loco is not written from scratch—it leverages Axum, SeaORM and other well maintained open sources.

But we don't have v1.0 yet. I’m curious about the factors holding back v1.0. My assumption is that it might be due to some missing features compared to Rails. If this is the case, a feature comparison table along with a detailed roadmap would be highly valuable.

Also, if there are other exciting features planned, it would be great to see a comprehensive list and a clear roadmap outlining their development and release timeline.

[schungx]

IMHO, missing features can be progressively added in 1.x versions. What's missing right now is polish... and "Just Works" SOP's

[jondot]

That is correct. Part of working on polish is our rewrite of all generator aspects into loco-gen and advanced new app wizard into loco-new.

[jondot]

Regarding version policy - we see using 0.x as "we may still break interface", but we're production ready nevertheless. Take for example Axum which is at 0.8, and people use it in production, wide spread.

I believe once we make it into 1.x, that will mean "we will not break interface untill 2.x" with your current app, which may take a long time and give you some peace of mind of not needing code changes for upgrades.

Historically in the 0.x series, there may be 1-2 code changes every 2 versions we released, we work hard on trying to minimize this anyway, but sometimes it's a must to improve the overall experience.

I agree with the need for roadmap and showing what's next, we'll work on something like that, in addition people can use this thread to say what they need the most to be added to the roadmap.