Very soon you might realize, that Twitter is good not bcoz of frontend but the major tech expertise is in the backend systems to handle super high traffic and dispatching messages quickly.
Twitter, but without code
31–40 of 68 posts
Re: Twitter, but without code
#32Don't post on HN of all places and claim we don't need programmers... On a serious note, cool product but we've seen many many many of these sorts of platforms before. They never work outside a niche market simply because programming isn't about typing, but assembling logic.
I think lots of people on HN are programmers, so probably a good place to post it, no? Good to get the people that will be 'replaced' in 20 years or whatever to start thinking about other ways to use their knowledge or at least thinking about how the industry could evolve in the future!
Re: Twitter, but without code
#33This may very well be a cool product - I like the idea of people being able to build things without code (how do they architect a DB?). Of course, as a lot of people are pointing out, this approach doesn't scale very well. To be fair, neither did the original Twitter, and it was built on Rails. They're different levels of scale, but if all you really need is a proof of concept this could solve the "How do I find a CT…
I totally agree with you, the website is really slow, most likely because it ended here...
If the resulting sites can't handle a traffic spike, it's not that great a tool, is it? No one wants a hammer that shatters if you swing it too hard...
Being optimistic, it might just be a hosting problem.
Re: Twitter, but without code
#34I've been using Zoho Creator for years (http://creator.zoho.com) as a tech-savvy non-developer. Anyone had any experience with both Creator and Bubble and can compare the two?
Re: Twitter, but without code
#35I honestly don't think I will ever use something like this because you have to stick to the resources provided. Also they might have released it too soon. I tried signing up and this is the message I get "Sorry, we ran into a temporary bug and can't complete your request. We'll fix it as soon as we can; please try again in a bit!"
Re: Twitter, but without code
#36The whole thing is built using bubble.is
If any of the site's devs are browsing the comments, you might want to address this problem I found while navigating the site: http://imgur.com/h0iUIVw
Re: Twitter, but without code
#37It's seriously slow and it lost my user account picture and status after I clicked away.
Maybe this could be a good thing in the future for simple prototyping (to show off to investors, not a general public kind of thing) but the bubble.is pricing advertises "Grow" "Scale" and "Flourish" plans for $460, $1700, and $4200 respectively.[1] I would definitely wait until the architecture here becomes more advanced before trusting them with your entire app.
I noticed their architecture was built on JS. JS is a pain in the butt when it comes to sandboxing. Either you run multiple contexts in a V8 engine that can crash each other if one OOMs, or you start up a new process for every instance. Single-threadedness is also not fun to deal with, in terms of efficiency.
(Yes, I've explored building a service like this on Node.js. I summarily discovered that it's probably not the best plan.)
Re: Twitter, but without code
#38I went to bubble.is and every link I clicked asked if I was sure I wanted to leave the page without saving my changes.
Re: Twitter, but without code
#39I got a good laugh out of this- definitely very creative and a good idea. I'd just be careful about the whole "please don't sue us" line. Companies like Twitter take these things very seriously.
Re: Twitter, but without code
#40Earlier quoted context omitted.
I totally agree with you, the website is really slow, most likely because it ended here...
If the resulting sites can't handle a traffic spike, it's not that great a tool, is it? No one wants a hammer that shatters if you swing it too hard... Being optimistic, it might just be a hosting problem.
Ya, to be fair I've seen Wordpress blogs go down under an HN spike, as well as a lot of stuff using socket connections for each user. Not many people build products expecting 100+ people to simultaneously use the site on day one.