Introduction
In early March of this year, I, @EnZon3, @bddy, and @codingMASTER398 composed a document on why Replit shouldn’t add those pesky deployment restrictions, as well as the nerfing of the free and hacker plans. Then, we posted it on Ask (post located here).
The conversation lasted throughout the month and ended with a one-on-one conversation with the Replit team where we could express more of our concerns. Unfortunately, little to nothing changed.
And once again, we’re back in the same situation. This time, a large portion of the community is worried and opposing the next upcoming change.
QUICK DISCLAIMER
Just like the post from March, this isn’t made to condemn or put down Replit; and is only to address some concerns that the community has. This article will be focusing A LOT on the free plan rather than the paid plans.
On the topic of Deployments
Deployments are great – depending on the situation. Most people opt out of deployments since it doesn’t fit their needs or like the non-costly option. With the new change, only being able to use ‘nerfed’ deployments is bad enough; but when you add the static site restriction and egress, it only gets worse.
Over the past week, I did a StrawPoll which asked the question:
If you don’t plan to use Replit after Jan. 1st (the date of the change), what is the reason?
Out of 43 total responses, over 75% said their problem was with the restrictions that would take place. A result that should not be surprising.
Many of Replit’s active users throughout the community are in the minority age (<18) and might not be able to afford a paid plan or dislike the complexity of other services.
Additionally, most of those people make programs which would not be available after the change, forcing them to move out or buy a subscription.
That same group of people also mostly post them to the Replit Community page (also formerly known as Replit Talk) which is a main source of motivation to code, especially for unemployed and self-taught programmers.
They still can switch to other platforms; but once again many of those people can prefer the simplicity of Replit and not know how to make that important switch.
In the same poll, over 10% said pricing was the problem. Which is also pretty fair. The website https://noreplit.com (made by @codingMASTER398 and @techwithanirudh) does a very good job at comparing and listing alternatives to Replit.
Some free options include:
- Vercel
- Glitch
- GitHub Codespaces
- Cloudflare Pages
and paid options include:
- AWS EC2
- DigitalOcean
- Oracle Cloud
most of which are more cost-friendly and have better performance compared to Replit.
The website also have quotes such as:
“The young aspiring developers that made Replit the company it is today ultimately have been abandoned and kicked to the curb by the platform with rising costs and and restrictions.” - @Zavexeon
or
“So, what? Replit is just not free anymore? Hosting on Replit was already frustrating enough with the slow speeds and the sleepy repls, and now you’re just pulling the plug entirely? Wow.” - @wutadamyt
which just shows a fraction of how much of the community despises this change and the prices.
On the topic of Quality
Lately, there has been a sharp increase in the amount of issues inside Replit including some people actually losing their data during the September 29th outage which at the time of writing, still isn’t fully recovered.
There’s also the topic of many unnecessary changes that affects a user’s workflow or experience.
Like the UI, for example. In the IDE, the Storage meter changed from a bar to a number which decreases consistency and coherency, leading to an unsatisfactory experience for the user.
Conclusion
Many people have turned to brighter, greener pastures after (or even before) the announcement of this change was made. Notable people throughout the community have already changed their choice of platform, and it seems as if that choice is becoming a trend.
Even if Replit changes their mind in a miraculous effort, some people still will not come back. Some are still waiting for that change. And some will never leave the platform.
Let’s end with a quote from a good friend and coder known throughout the Replit community.
“I was a power-user a little while back. Migration would be hell. I have tons of websites to port over, and it won’t be fun. And that’s what was amazing about Replit, you could basically make anything you wanted at any time, at any rate. It’s what kept my motivation super high, Now that motivation has dried up.” - @EnZon3
Sources, or whatchamacallit
- https://noreplit.com
- https://replit.com/pricing
- https://status.replit.com/
- Friends of Replit
- If you don't plan to use Replit after January 1st, what is the reason? - Poll Results - StrawPoll
- https://blog.replit.com/sep-29-read-only-repls
- https://blog.replit.com/hosting-changes
- Changes to Hosting on Replit!
- https://replit.com/@FireDevilX/Do-Not-Make-Hosting-Paid
Appendices
Appendix A: Replit Ask
Yes, there is a post on Replit Ask about this change (see Changes to Hosting on Replit!) and there has been a large discussion about the controversial change there. However, it is much easier to get the point across and expand on the topic on a new post rather than the official one.
Appendix B: The Other Option
On the aforementioned poll, 10%+ voted for another option. The majority of those people said that all of the above were problems with their Replit experience. I am sooooo sorry for not including this in the main article.
Appendix C: The Community does not Like the Change
I’ve said this once and I’ll say it once again. The community does not want this change to happen.
Take this Repl which is trending with just shy 300 likes at the time of writing this.
It is quite literally titled, “Do Not Make Hosting Paid,” and lists the reasons of why you shouldn’t have to pay just to run programs.
Additionally, it has a section showing the amount of times when the Repl was unpublished by moderators; just taken off the platform.
And now, as of 18:58 CST, it has been taken down again from the entire platform.