Live data from Hacker News

Hoodie – Fast web app development

hood.ie

31–40 of 147 posts

Re: Hoodie – Fast web app development

#31

>It took less than 15 minutes for a person with no experience in any part of the stack to take an existing single user app and make it a multi-user application with robust security and data storage. […] Bravo, hood.ie, brav-fucking-o. I find that extremely hard to believe.

You should try to head to http://github.com/EGreg/Q and try it out :)

I think you'll find that you can make a multiuser app from a single user app rather straightforwardly in a day. Although 15 mins would be only for a Q expert.

Re: Hoodie – Fast web app development

#34

So let's just deliver all our business logic as JavaScript to an entirely untrustworthy client! Whats the worst that could happen?

Desktop clients have been delivering business logic to clients for a very long time with few problems. Web powered apps are similar. The issues involve protecting data stored in the cloud, communicating over secure channels and client security. JavaScript powered applications running in a browser have many security considerations, but they're manageable if you have security aware engineers building your application. Knowing about OWASP[1] helps.

[1] https://www.owasp.org/index.php/Main_Page

Re: Hoodie – Fast web app development

#35

So let's just deliver all our business logic as JavaScript to an entirely untrustworthy client! Whats the worst that could happen?

Sharing the business logic is less of an issue than the business metrics that get leaked when you include user ID's in your source code.

Re: Hoodie – Fast web app development

#36
post #27

So let's just deliver all our business logic as JavaScript to an entirely untrustworthy client! Whats the worst that could happen?

Hoodie works no different than Gmail. What’s the worst that can happen there?

How is one of the first apps to popularize AJAX, developed on top of a proprietary cross-compiling framework by a top-3 web giant "no different" from Hoodie? Obviously you're getting at some specific point that is completely obscured by the ridiculousness of the comparison. Hopefully it's more than "client-side logic can be useful" because that much is obvious on its face. It's also obvious that the idealized promise of no-backend falls apart pretty quickly for a majority of real world apps. So what is your point exactly?

Re: Hoodie – Fast web app development

#37
post #27

So let's just deliver all our business logic as JavaScript to an entirely untrustworthy client! Whats the worst that could happen?

Hoodie works no different than Gmail. What’s the worst that can happen there?

Well you sure as shit aren't going to see "hoodie.account.signUp(username, password);" in Gmail's client-side code.

Gmail's code base is not a "offline first, mobile first" platform. The API that is exposed to the client-side is fairly light (watch the traffic).

I highly suggest use research "business logic flaws" in web apps. Anything Jeremiah Grossman has said on this topic is good stuff.

Re: Hoodie – Fast web app development

#38
post #27

Earlier quoted context omitted.

Hoodie works no different than Gmail. What’s the worst that can happen there?

How is one of the first apps to popularize AJAX, developed on top of a proprietary cross-compiling framework by a top-3 web giant "no different" from Hoodie? Obviously you're getting at some specific point that is completely obscured by the ridiculousness of the comparison. Hopefully it's more than "client-side logic can be useful" because that much is obvious on its face. It's also obvious that the idealized promise…

Sorry, from “delivering business logic to the client” perspective, Hoodie is no different in concept on that angle. Lots of things are very different, of course :)

Re: Hoodie – Fast web app development

#40
post #27

Earlier quoted context omitted.

Hoodie works no different than Gmail. What’s the worst that can happen there?

Well you sure as shit aren't going to see "hoodie.account.signUp(username, password);" in Gmail's client-side code. Gmail's code base is not a "offline first, mobile first" platform. The API that is exposed to the client-side is fairly light (watch the traffic). I highly suggest use research "business logic flaws" in web apps. Anything Jeremiah Grossman has said on this topic is good stuff.

They have frontend code that will talk to /singup or whatever the route for creating an account is. Hoodie does nothing different.

Thanks for the pointer to Jeremiah, though :)

Post reply on HN