Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hoodie: very fast web app development

hood.ie

Post reply on HN
Print view View original

141–150 of 155 posts

Re: Hoodie: very fast web app development

#141

Post by janl »

tarabukka wrote: post #123
janl wrote: post #71

Earlier quoted context omitted.

As long as the underlying OS can provide file descriptors, CouchDB can handle the concurrent connections through the magic of Erlang, both persistent and shorter lived. There are obvious limits to this, but the Hoodie architecture allows easy scale out (more DB servers and manual sharding, or a dynamo-like BigCouch, more workers etc.) that we’ll get to making use of once Hoodie apps become that big.

Magic of Erlang? I hate to be cynical, but have you got benchmarks to back that up?

Yeah.

Re: Hoodie: very fast web app development

#143

Post by namdnay »

gr2m wrote: post #130
gbog wrote: post #124

Earlier quoted context omitted.

> [dev speed has] a large impact on the overall probability of getting off the ground I don't know. This seems common sense but it could be a cliché too. If we look at other domains, it is not always true. For instance, if you write novels that are not tied to some evanescent trend like a pop star's private life, then the chance of getting off the ground if not directly linked to the timing of publication. It would b…

Let's say today 1 of 1000 people is able to create an app to solve a problem, let's say time time tracking. Now imagine we change that drastically, to 100 of 1000 or even more. People will start to build their own little apps to solve their own little problems. And if these break, nobody cares, but them. For example, friends of mine like to go climbing. They've build an app in an afternoon, just for their group, to k…

> They've build an app in an afternoon, just for their group, to keep track of what tracks they finished and how they liked it. I think this is fascinating. I wonder what would happen if students would learn to build simple apps like that in school, instead of Excel

To be pedantic, Excel would be the perfect tool for writing an app like this. A few columns, a quick and dirty VBA GUI... Bob's your uncle

Re: Hoodie: very fast web app development

#144

Post by namdnay »

lkrubner wrote: post #131
gr2m wrote: post #130

Earlier quoted context omitted.

Let's say today 1 of 1000 people is able to create an app to solve a problem, let's say time time tracking. Now imagine we change that drastically, to 100 of 1000 or even more. People will start to build their own little apps to solve their own little problems. And if these break, nobody cares, but them. For example, friends of mine like to go climbing. They've build an app in an afternoon, just for their group, to k…

"Now imagine we change that drastically, to 100 of 1000 or even more. People will start to build their own little apps to solve their own little problems. And if these break, nobody cares, but them." This was the old dream of Hypercard, and it worked very well for a long time. http://en.wikipedia.org/wiki/HyperCard Both Danny Goodman and Bill Atkinson have stated publicly that they got programming questions from ever…

It's ironic that the tool that has replaced Hypercard is in fact Excel. Excel makes it amazingly easy for non-programmers to develop simple applications

Re: Hoodie: very fast web app development

#145

Post by rektide »

onemorepassword wrote: post #101

Looks lovely, but I wish people would focus less on fast development and more on something that better maintainability 2 years down the road. When it comes to the lifecycle of most applications, the speed of developing something new has a marginal impact on the overall costs, and most tools and frameworks than enable rapid initial development tend to suck once you have a big app on top of them. This is why we fawn ov…

  I wish people would focus less on fast development and more
  on something that better maintainability 2 years down the road.
Hoodie focuses on the data model, not the application logic or UI. If there's one thing I want to be consistent and maintainable and to have a really solid support stack under it- if there's one area I value maintainability and consistency- it's the data layer, which this very much attempts to provide a consistent development experience for.

An app built with hoodie I could see as being maintainable- even as you gut the entire stack and drag your rails app to flask, or your php app to java, hoodie has defined only the kinds of objects and patterns of accessing them that you'll reuse in whatever your actual app stack is. Hoodie targets the data, which is the thing. Everything else? Who cares. Here's to maintainable data.

Re: Hoodie: very fast web app development

#146

Post by eevee »

andybak wrote: post #126
eevee wrote: post #88

Earlier quoted context omitted.

I run noscript. If I encounter a site that's broken or useless for seemingly no reason (e.g. not an interactive thing like Google Maps), I often don't even whitelist; I just leave. Relatedly, I've stopped clicking on Photobucket or Blogspot links. I kinda resent being expected to run your pile of arbitrary code just to render static text and images on my screen—something that worked just fine without JS twenty years…

While I admire your principled stand - you are in a dwindling minority so there isn't much reason to factor in people such as yourself when making technical decisions. The SEO issue is a stronger argument but Googlebot now seems to be executing javascript in some cases so even that might cease to be an issue.

It's not just people like myself; it's people writing one-off scrapers, people writing new search engines or browsers (Google is not the entire universe), everyone when you forget a brace and break all of your JS, etc. The Web is not and has never been merely human beings sitting at a keyboard and using one of three known GUI browsers.

Re: Hoodie: very fast web app development

#147

Post by eevee »

Ecio78 wrote: post #121
eevee wrote: post #88

Earlier quoted context omitted.

I run noscript. If I encounter a site that's broken or useless for seemingly no reason (e.g. not an interactive thing like Google Maps), I often don't even whitelist; I just leave. Relatedly, I've stopped clicking on Photobucket or Blogspot links. I kinda resent being expected to run your pile of arbitrary code just to render static text and images on my screen—something that worked just fine without JS twenty years…

that's your choice, but don't pretend devs will change all their stack/development approach to take into account your refusal of using a technology that has been around for 15 years.

You say that like I'm the one missing out when I don't use your new social cat 2.0 viewer. Do you not want me as a user? How many of me are there?

Re: Hoodie: very fast web app development

#148

Post by jjsz »

gr2m wrote: post #15
RaphiePS wrote: post #10

Earlier quoted context omitted.

A lot of my Angular code is glue for the backend, so this would be an absolute godsend.

I've made a backbone adapter a while a go: https://github.com/hoodiehq/hoodie.js/blob/master/stuff/back... shouldn't be hard to make one for Angular. Happy to help

I'm looking for someone to translate this into an angular adapter and combine it with Yeoman's 1.0b4's AngularJS generator, among other things to test out hoodie. If you were already going to do it, might as well do it sooner than later and get payed for it! :-)

I posted the job on Elance, Freelancer, and Odesk if anyone is interested.

Elance: https://www.elance.com/job/40077787/proposals Freelancer: http://www.freelancer.com/projects/Javascript-Software-Archi... ODesk: https://www.odesk.com/jobs/Create-Hoodie-AngularJS-adapter-w...

Re: Hoodie: very fast web app development

#149

Post by gr2m »

namdnay wrote: post #143
gr2m wrote: post #130

Earlier quoted context omitted.

Let's say today 1 of 1000 people is able to create an app to solve a problem, let's say time time tracking. Now imagine we change that drastically, to 100 of 1000 or even more. People will start to build their own little apps to solve their own little problems. And if these break, nobody cares, but them. For example, friends of mine like to go climbing. They've build an app in an afternoon, just for their group, to k…

> They've build an app in an afternoon, just for their group, to keep track of what tracks they finished and how they liked it. I think this is fascinating. I wonder what would happen if students would learn to build simple apps like that in school, instead of Excel To be pedantic, Excel would be the perfect tool for writing an app like this. A few columns, a quick and dirty VBA GUI... Bob's your uncle

yeah, but they could access the tool all from their own mobile devices, with their own user accounts ;-)

Re: Hoodie: very fast web app development

#150

Post by pjbrunet »

Lazare wrote: post #102
pjbrunet wrote: post #89

Earlier quoted context omitted.

If my phone has no signal I'd rather see an error message. I don't want the app to pretend everything is fine when that's not the case. If I press "Delete" in the app, don't pretend the thing is deleted if it's not really deleted yet, that's deceptive. What if I take off on my boat and I press "Send" and your app says "Sent!" but it's really not sent because now I've left the coast--your app just lied to me.

With all due respect, I think you're wrong. If I'm writing an email in the Gmail app on Android, what I want when I hit send is for the app to save the email locally, and then do its best to try and deliver it. Ditto for, basically, every other app on the phone that talks to a remote server. If I try and send a tweet, I want it to go "sure", and then be able to go on about my business while it works in the background…

You think I'm wrong but you wholeheartedly agree? Funny. Every situation is unique but bottom line: you can't receive content without a connection. Most apps NEED a connection to function. So an error message "No Connection, Retry?" is both common and expected behavior.
Post reply on HN