Live data from Hacker News

Show HN: Reddit clone built in no-code in two weeks

reggit.bubbleapps.io

141–150 of 176 posts

Re: Show HN: Reddit clone built in no-code in two weeks

#141

Content provider built in no-code in 2 weeks without content

While amusing... the value of most of those sites is not the site themselves. But the people network that is there. Why is everyone using it? Because everyone is using it. Then suddenly the 'crowd' will move to the next one. There will be a few holdouts that stick but it will be a zombie site that lumbers on. For example myspace, digg, and fark are still around.

I think you will always find a core that stays and a core that leaves.. the reason is that people don't feel heard so they look for other places to voice themselves. I went from slashdot to reddit to HN. Even now HN doesn't feel satisfactory.

Re: Show HN: Reddit clone built in no-code in two weeks

#143
post #43

I love no code! Wait. Wait. Hear me out... Building software is easy. Changing people's minds is damned near impossible. As an engineer: - I'm constantly handed shitty (or a complete lack thereof) requirements from non-technical people. No code lets people figure out that they haven't thought something out nearly as much as they think they have. I no longer am the bearer of bad news. - I constantly see business peopl…

Can you elaborate on the list of problems with no-code? Of course I'm not denying there are problems with no-code, I'd like to learn about other developers' issues, particularly with larger, longer-term projects.

I think there's an interesting analogy to be drawn with Lego. You can build interesting and useful things out of Lego, more than you may even realize. It can be fast & effective, it's certainly easy, especially if you imagine we've abstracted away the question of what bricks you have so you have as many as you need of any kind & color.

However, you end up with two sorts of problems if you start letting people just build solutions to whatever they like with Lego:

1. The solutions may work, but they aren't really that good. You can only do what there's Lego bricks for. When it comes time to solve the problem at the next level, the Lego stuff can be less helpful than it looks even as a prototype, as even at small scales a lot of the engineering in the Lego was solving around the limitations of Lego in the first place, rather than solving the problem per se.

2. Eventually you get people trying to build sheds and houses out of legos, struggling to put up shelves, all kinds of silly things that the solution isn't really suitable for. And there's a variety of pathologies here, too, like how they don't understand why their Lego solution isn't good enough, and why you can't just buff up their shelf since it's just that the shelf is falling over, and explaining to them that they basically just built a shed that is made out of code violations may not be very easy, etc.

There are advantages, too, like letting them get their hands on some engineering and stuff, and there are a lot of problems in the world where a Lego solution is no big deal. I don't know if I've got anything right now, but I've done it before; I had a lego setup for holding tablets & phones for charging that was better than anything I've bought, because it actually had the correct sizes for things, for instance. But there's limits.

Re: Show HN: Reddit clone built in no-code in two weeks

#145

Nocode/lowcode is excellent for company internal apps & GUIs. Imagine things like barcode/QRcode scanner app for warehouse that just needs to send an HTTP call somewhere. Stakeholders/business people might be able to complete some smaller apps & views & GUIs themselves an no need to wait for engineering support. It's likely never going to produce production quality web UIs for sites that have millions of consumer use…

Sure, it won't be used for millions of users, but I am already seeing plenty of startup MVPs built entirely from no code.

I can see a near future where no code offers the ability to take the model as built and start hand optimizing the code once things start to get off the ground.

Re: Show HN: Reddit clone built in no-code in two weeks

#146
post #127
post #43

I love no code! Wait. Wait. Hear me out... Building software is easy. Changing people's minds is damned near impossible. As an engineer: - I'm constantly handed shitty (or a complete lack thereof) requirements from non-technical people. No code lets people figure out that they haven't thought something out nearly as much as they think they have. I no longer am the bearer of bad news. - I constantly see business peopl…

Thank you. HN is one of the few places where no-code is discussed at length, and it's frustrating how many programmers default to replying with "I would never use this in production." You don't have to. The no-coder is building a prototype, safely sandboxed away from your precious CI/CD pipeline. The benefit of building a robust prototype is that the idea-haver person doesn't bother developers with unfinished require…

No-code is going to be used in production for sure. It's not something only for sandboxing and prototypes.

Re: Show HN: Reddit clone built in no-code in two weeks

#148

Earlier quoted context omitted.

Ironically, it seems this clone does a great job of cloning the performance of reddit, at least when I tried it (bunch of unnecessary requests that takes multiple seconds each, sometimes just returning errors)

Hard to meet a person that doesn't at least dislike reddit, but at least old.reddit.com is quite an efficient page. I had an internet outage that left me with a few kilobytes/s upstream/downstream. Most of the modern web was plainly unusable, often requests got terminated before all data was transmitted. But reddit among few other sites did work quite well. Of course not for pictures and media, but the text and comme…

I will only ever use old.reddit.

If they take that away, I will kill my account. My account is 15 years old on Reddit, with near daily use.

Re: Show HN: Reddit clone built in no-code in two weeks

#150
post #127

Earlier quoted context omitted.

Thank you. HN is one of the few places where no-code is discussed at length, and it's frustrating how many programmers default to replying with "I would never use this in production." You don't have to. The no-coder is building a prototype, safely sandboxed away from your precious CI/CD pipeline. The benefit of building a robust prototype is that the idea-haver person doesn't bother developers with unfinished require…

No-code is going to be used in production for sure. It's not something only for sandboxing and prototypes.

My point is that the conversation about such tools is derailed by HN programmers who automatically jump to the conclusion that these products are the wet dreams of non-technical CEOs, who will force their org to go no-code exclusively.

If no-code tools are used in production, that implies that it will have to pass QA and code review, just like anything else.

Post reply on HN