One of the problems with examples like this is that it gives an unrealistic expectation to non-technical people that large & complex sites are actually quite basic. There is a lot of functionality that a typical user never sees and is often where the complexity lies. And as the "app too busy" error message proves, there is a lot more to a site than it's front end alone and cloning a front end does not clone performan…
Great point. There's certainly much more that goes into building a site like Reddit than what goes into building a clone in two weeks. The purpose of this is to show the potential of what can be done in no-code. No-code is still in it's very early days, and I think that a lot of its capabilities will improve over time. Also, it's very possible that a lot of the inefficiencies in no-code apps are a result of the build…
Show HN: Reddit clone built in no-code in two weeks
171–176 of 176 posts
Re: Show HN: Reddit clone built in no-code in two weeks
#172Earlier quoted context omitted.
Just use old reddit. It's fast. On mobile https://www.reddit.com/.compact (with a dot before compact) still works.
On mobile web, you can also select an option from the hamburger menu to tell it to give you the desktop interface (which persists until you clear your cookies), and in your user settings you can set your default desktop interface as old reddit. Call me crazy for using the desktop site on mobile, but I find it far more usable to pinch and zoom than to navigate the redesign.
Re: Show HN: Reddit clone built in no-code in two weeks
#173Earlier quoted context omitted.
It does handle many orders of magnitude more users than this thing does though. As a site that is the source of many hugs of death, it's serving a hell of a lot of traffic, mostly successfully. It could serve even more traffic if it was less bloated of course. EDIT: Some random stats from 2019 suggest that they're handling ~1000 pageviews a second on average over a month, and a view can take >100 requests to load. Co…
Over 100 requests per load? That has to be static files like images, right? Do they not have a cache system for that (like what Cloudflare provides)?
Re: Show HN: Reddit clone built in no-code in two weeks
#174One of the problems with examples like this is that it gives an unrealistic expectation to non-technical people that large & complex sites are actually quite basic. There is a lot of functionality that a typical user never sees and is often where the complexity lies. And as the "app too busy" error message proves, there is a lot more to a site than it's front end alone and cloning a front end does not clone performan…
Re: Show HN: Reddit clone built in no-code in two weeks
#175One of the problems with examples like this is that it gives an unrealistic expectation to non-technical people that large & complex sites are actually quite basic. There is a lot of functionality that a typical user never sees and is often where the complexity lies. And as the "app too busy" error message proves, there is a lot more to a site than it's front end alone and cloning a front end does not clone performan…
Great point. There's certainly much more that goes into building a site like Reddit than what goes into building a clone in two weeks. The purpose of this is to show the potential of what can be done in no-code. No-code is still in it's very early days, and I think that a lot of its capabilities will improve over time. Also, it's very possible that a lot of the inefficiencies in no-code apps are a result of the build…
Of course, maybe someone will solve that problem. (Or computers will get so powerful efficiency ceases to matter). It also doesn’t change that things like no-code could be great for people less programming focused to prototype ideas, or create scripts to run over data much like people have used excel for ages. It might just remain necessary to eventually pass the implementation onto a non-visual programmer when scaling the solutions up for production.
Re: Show HN: Reddit clone built in no-code in two weeks
#176There was a badly documented plugin for twitter and it could do a subset of what the API was capable of, but I didn't see how I could extend it meaningfully.
I really wished API usage and low-code would get a bit more love.