Earlier quoted context omitted.
Hood.ie is open source, and your code is not. Any chance you can open source your code?
Our client library is entirely open source, but our platform itself is not as it's a commercial no-backend offering. This allows us to offer production-grade hosting for these types of no-backend apps.
Hoodie – Fast web app development
131–140 of 147 posts
Re: Hoodie – Fast web app development
#132>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.
Re: Hoodie – Fast web app development
#133Re: Hoodie – Fast web app development
#134I see you can add , update data to the db using javascript...is it using nodejs?
Re: Hoodie – Fast web app development
#135Earlier quoted context omitted.
Our client library is entirely open source, but our platform itself is not as it's a commercial no-backend offering. This allows us to offer production-grade hosting for these types of no-backend apps.
Many companies offer production-grade hosting for open source applications. The fact that you are keeping your source closed tells me that you are afraid a competitor (or your clients themselves) could achieve an equivalent quality of hosting for less than they would pay you. To a customer like me, this is bad news.
It's still early days for us but we are considering open sourcing reusable parts of our platform or allowing people to host their own if they wish, but we haven't yet decided on which we will pursue yet.
Re: Hoodie – Fast web app development
#136Just realized .ie is an excellent TLD for cute website names
Less than you might think. It's not a trivial matter to get an .ie domain. The IEDR's rules make things difficult if you can't either (a) demonstrate a connection with Ireland the reviewer will accept or (b) demonstrate that you trade in the Irish market. There are ways around some of their rules, such as getting a registered business name from the CRO, but it really is a pain in the backside. I write this as somebod…
Re: Hoodie – Fast web app development
#137Earlier 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.
Re: Hoodie – Fast web app development
#138Earlier quoted context omitted.
Yeah, it’s a document database, uses UUIDs and revisions for identification and does HTTP-based P2P replication. In Hoodie we abstract that away in a simple to use `hoodie.store` object with the usual `add()`, `update(), `find()`, `findAll()` methods for operations. No need to know about the CouchDB/PouchDB specifics, just store your objects :)
Okay, but the key design decision in any data syncing library is how it resolves update conflicts. Is it last-one-wins, report an error and try again, diff merging, or maybe some kind of operational transform? Since that's the heart of the problem being solved, it's weird when the docs leave it out.
Re: Hoodie – Fast web app development
#139Re: Hoodie – Fast web app development
#140Earlier 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?