Haskell / Scotty
Care to give anymore details? Tips on using this approach? Problems? Advantages? What do you think of mflow?
Poll: For your startup, do you use Django, Rails, PHP or Other?
81–90 of 96 posts
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#82[deleted]
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#83Mongodb/ExpressJS/AngularJS/NodeJS
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#84glad to see i'm not the only one using PHP. reading HN sometimes give you the impression that PHP is only used by dinosaurs
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#85Haskell / Yesod
Care to go into more detail? How are you handling storage, deployment, frontend. How useful are Shakespearean templates?
Well, I've a couple projects on Yesod, with some variation, but I'll focus on the one that has users outside my family.
Storage is Postgres; deployment is some overly specific (and slightly too manual) scripts I put together before Keter was mature (and haven't touched since); front end is mostly flat HTML generated from Hamlet (or markdown, through pandoc), gussied up with some JS where appropriate, but definitely more of a progressive-enhancement approach than a single page app.
With regards to Shakespearean templates, the languages for JS and CSS (Julius and Cassius/Lucius) are - in practice - of only mild use on their own. Hamlet is a bigger win - and, in particular, the ability to package up all three into a single widget to be embedded in arbitrary Hamlet, is great. And all the type safety is a nice bonus. One thing it does need is more exhaustive documentation - I don't think there's anywhere that actually specifies the "embed tag attributes from this list" or "generate a URL with parameters" sigils, save the source and mailing list. What documentation does exist is pretty solid, mind you, there's just some omissions.
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#86Earlier quoted context omitted.
Care to go into more detail? How are you handling storage, deployment, frontend. How useful are Shakespearean templates?
Well, I've a couple projects on Yesod, with some variation, but I'll focus on the one that has users outside my family. Storage is Postgres; deployment is some overly specific (and slightly too manual) scripts I put together before Keter was mature (and haven't touched since); front end is mostly flat HTML generated from Hamlet (or markdown, through pandoc), gussied up with some JS where appropriate, but definitely m…
Thanks for the reply. I've done a cursory run through of the "book", and wondered how close it was to an actual use of the framework in development.
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#87Earlier quoted context omitted.
Node.js / Express / Postgres / React & Fluxxor Really enjoying the Flux design pattern + declarative nature of React. I've been applying the Flux pattern to other applications (iOS) with great successful. The goal of one-way data flow and a single touch point for application events is a radical tool for complexity reduction.
Are you using any ORM for PostgreSQL in Node? Haven't found anything as good as ActiveRecord yet...
Check out bookshelf and knex
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#88Go / Postgres / React & Fluxxor Edit: forgot to mention go-tigertonic. :)
I just looked at Fluxxor and AngularJS. They use the exact same TodoList example in their quickstart guides. Turns out that AngularJS is simpler and easier to understand.
As someone who uses Angular.js every single day on some very large front-end apps, yeah, Angular seems simpler to understand, until your app gets large; Those small examples don't really show the benefit of the Flux architecture, as when it's that small something like Angular or other MVC frameworks with their magic and libraries really shine.
Heck, Angular is still excellent for large apps as well, as long as there is discipline in your development technique. The issue arises when you have a large team with varying skill levels, all working on the same front-end, with things stuck in the $scope when they shouldn't be, over-use and abuse of $watch, and a stack of other gotchas that make debugging an absolute nightmare, as tracing the execution flow is nigh on impossible.
That's where Flux is trying to do things differently. By having one way of passing data between the various components (and plugged directly into React, which also is built around a "componentized" architecture) you know exactly where to look when things go wrong, you give up a bit of dynamism and magic for explicitness, which in my experience is not a bad thing. That's my two cents anyway!
Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#89Re: Poll: For your startup, do you use Django, Rails, PHP or Other?
#90Java Rest backend FTW! (No Spring!)