# Dev Diary 85 - We Hit 1,000 Subscribers! What's next? **URL:** \ **Category:** Elements\ **Created:** [June 3, 2025, 12:11pm UTC](https://forums.realmacsoftware.com/t/dev-diary-85-we-hit-1-000-subscribers-whats-next/47893 "2025-06-03T12:11:23Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![pumpkin](https://avatars.discourse-cdn.com/v4/letter/p/ccd318/32.png) [@pumpkin](https://forums.realmacsoftware.com/u/pumpkin)\ **Post date:** [June 3, 2025, 5:43pm UTC](https://forums.realmacsoftware.com/t/dev-diary-85-we-hit-1-000-subscribers-whats-next/47893/3 "2025-06-03T17:43:24Z")
> [@jccdebruin](#): > > Do I need [Elements](https://elementsapp.io/) instead Rapidweaver? Do you need [Elements](https://elementsapp.io/) instead of RW classic? No. > [@jccdebruin](#): > > Does it have advantages for me as single user? Tons. No matter if you’re doing a private website just for yourself or if you’re a seasoned professional doing client work. And it’ll get better everyday. I used RW classic for years, invested a lot (!) of money in frameworks, cms solutions and 3rd party stacks which all had a different way to name or sort their settings. That already drove me nuts. There’ll sure be some 3rd party additions to [elements](https://elementsapp.io/), but even in it’s current state it can do more than I was able to do with RW classic + Foundry + easyCMS + lots of 3rd party stacks or even Blocs. Yes, there’ll be a learning curve, but it’s worth it. I could’ve stayed with classic, but being forced into the terrible UI/UX from Stacks to create a website… no way. And even more so if you switch back from [elements](https://elementsapp.io/) (or blocs, where I now come from) to RW classic and stacks. I can’t imagine that for the life of it. Give it a try. You won’t be disappointed, and the forums and especially the developers offer a ton of help if you get stuck. --- _[View the full topic](https://forums.realmacsoftware.com/t/dev-diary-85-we-hit-1-000-subscribers-whats-next/47893)._