Seems like I should've seen this on the latest episode of Silicon Valley.
Hoodie – Fast web app development
81–90 of 147 posts
Re: Hoodie – Fast web app development
#82Earlier quoted context omitted.
would like to know a bit more about comparisons with other realtime & offline-syncable BAAS like: Meteor, Firebase, AngularFire etc - As a non-dev, this looks very appealing, but before I start learning I wanted to know more about the strengths/weaknesses compared to others.
Hoodie is Open Source and more like BYOBAAS (Bring Your Own Backend As A Service), you can host it yourself, or pay someone to host it for you. You are not beholden to single company’s VCs. Meteor is about exposing backend and frontend APIs to the browser. Hoodie hides backend complexity as much as it can. The target audiences are very different. Hoodie aims for more frobtendy/designery types, in the future Hoodie de…
> Meteor is about exposing backend and frontend APIs to the browser
It is the weirdest description of Meteor I have seen so far.
Meteor is all about helping developers to build excellent web apps with ease and spending less time, not providing APIs.
Re: Hoodie – Fast web app development
#83Earlier quoted context omitted.
Hoodie doesn't provide any email privileges in it's core. There is an email plugin that does that, but it's just a showcase and we would not recommend to use that in a production app. The plugin is maybe 10 lines of code, you can easily use that as base and put all the security in it that you would do in a REST API as well. I'd be also very interested in your basic use cases that you think Hoodie couldn't handle. It…
" There is an email plugin that does that, but it's just a showcase and we would not recommend to use that in a production app. " You do realize that by putting it in your documentation, you're encouraging people to use it .
We also encourage people not to use Hoodie in production, yet :)
What @gr2m means: there is no reason Hoodie’s mail feature would work any different from a traditional web app. At some point a server side will validate a client request, and if valid, translate that into sending an email (Gmail comes to mind). Hoodie’s email plugin can do exactly that, except that today’s implementation is a mere sketch of that, like other parts of Hoodie, that show what can be done, but aren’t hardened against production use, yet. None of that means though that Hoodie behaves any differently from a security/abuse/DOS perspective than any other web app :)
Re: Hoodie – Fast web app development
#84Earlier quoted context omitted.
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.…
Are there any e-commerce platforms that trust the client to do all the business logic for an order/checkout? If so how do they prevent client side tampering with the business logic without redoing it on the server side?
An e-commerce platform on Hoodie would also do final validations server-side.
Re: Hoodie – Fast web app development
#85Earlier quoted context omitted.
Hoodie doesn't provide any email privileges in it's core. There is an email plugin that does that, but it's just a showcase and we would not recommend to use that in a production app. The plugin is maybe 10 lines of code, you can easily use that as base and put all the security in it that you would do in a REST API as well. I'd be also very interested in your basic use cases that you think Hoodie couldn't handle. It…
" There is an email plugin that does that, but it's just a showcase and we would not recommend to use that in a production app. " You do realize that by putting it in your documentation, you're encouraging people to use it .
Our goal is to lower the barrier of entry to build fully capable applications. While using the simple email plugin is not a good idea in a production app, there is no problem to use it with an app that runs on your computer only, or in your companie's intranet.
I know this is nightmare to system architects / backend developers at first sight, but trust us, we know exactly what we are doing. We have excellent architects on our team, you just might not be our primary target group here.
But thanks for your feedback, much appreciated!
Re: Hoodie – Fast web app development
#86Earlier quoted context omitted.
Not yet. https://github.com/espy/hoodie-plugin-tutorial "This document describes functionality and features that don't exist yet."
I’m a Hoodie developer, I know what Hoodie does and doesn’t. That disclaimer is just there because some of the things don’t yet work as documented. The particular feature is definitely in existence :)
There, I fixed it :)
Re: Hoodie – Fast web app development
#87Earlier quoted context omitted.
Hoodie doesn't provide any email privileges in it's core. There is an email plugin that does that, but it's just a showcase and we would not recommend to use that in a production app. The plugin is maybe 10 lines of code, you can easily use that as base and put all the security in it that you would do in a REST API as well. I'd be also very interested in your basic use cases that you think Hoodie couldn't handle. It…
" There is an email plugin that does that, but it's just a showcase and we would not recommend to use that in a production app. " You do realize that by putting it in your documentation, you're encouraging people to use it .
To be fair they are still working on 0.x, they probably don't recommend the whole thing to be used in production (although I personally wouldn't mind for some specific projects...). At this stage, I understand they just want to showcase some cool stuff. This being said, we should always be really careful about security when using dependencies, especially when it's in beta, and especially when mostly everything is done client side. It would be also nice if something more explicit was mentioned on the hoodie website. Like the last release version for example (0.x).
Re: Hoodie – Fast web app development
#88Just realized .ie is an excellent TLD for cute website names
It's also notoriously painful to register a .ie domain. You need some connection to Ireland, but even if you do there are restrictions on what you can register (needing to have a company name or registered business name matching the domain, for example). They have loosened up considerably on the discretionary domains, but it still seems to take at least a week to get your registration approved and completed.
Re: Hoodie – Fast web app development
#89So I'm looking at their "Account" api, and I wonder if something similar like that exists for node just for the backend.
Not really the same, but Passport offers easy account authentication.
Re: Hoodie – Fast web app development
#90Earlier quoted context omitted.
" There is an email plugin that does that, but it's just a showcase and we would not recommend to use that in a production app. " You do realize that by putting it in your documentation, you're encouraging people to use it .
We also encourage people not to use Hoodie in production, yet :) What @gr2m means: there is no reason Hoodie’s mail feature would work any different from a traditional web app. At some point a server side will validate a client request, and if valid, translate that into sending an email (Gmail comes to mind). Hoodie’s email plugin can do exactly that, except that today’s implementation is a mere sketch of that, like…
Thanks for confirming my crosspost :) However, as I was just saying, wouldn't it be nice to clearly see that we're talking 0.x directly on the website and not only when we install the npm package?
EDIT: Thanks for your answer, I am going to stop crossposting now :D