6 ms·
Flatironjs: an unobtrusive framework initiative for node.js
- franze 15y agounobtrusive framework is an oxymoron
- netghost 15y agoI see a list of libraries, but no links. Where's the source, the docs, etc?
- netlemurde 15y agohttps://github.com/flatiron https://github.com/flatiron
- jsight 15y agoI found the layout of the website extremely obtrusive. I'd have preferred a much more basic layout, without so much fixed text/graphics.
- munaf 15y agoAgreed. I'd prefer to discuss the pros/cons of the framework, but honestly the content on the left was enough to make me stop reading. It's unfortunately very common to miss out on interesting content because of UI pickiness.
- lclarkmichalek 15y agoThere was a link posted on reddit about this framework, however it linked to a nodejitsu blog post, and iirc, nodejitsu links cannot be submitted to hackernews.
- SeoxyS 15y agoI'm viewing this on an iPhone via the news.yc app, and the website is impossible to view on a mobile browser. Op might want to look into that.
- jeromeparadis 15y agoSame problem on my iPad but I found the solution: use 2 fingers to scroll.
- firefoxman1 15y agoViewing this on a netbook is a nightmare. On another note, when will they launch? I got an email a while ago announcing the beta but never let me sign up.
- jokull 15y agogithub link? Some radical ideas in this framework! Quite close to what I've predicted in the merging of frontend and backend frameworks (think Brunch with backend DOM awareness). EDIT: [github link](https://github.com/flatiron/flatiron https://github.com/flatiron/flatiron)
- funthree 15y agoSpeaking of backend DOM awareness, have you seen this? https://github.com/tblobaum/nodeQuery https://github.com/tblobaum/nodeQuery
- jokull 15y agoSeems like quite a feat has been accomplished. But it also feels like it was simply done for the sake of it, instead of creating a framework that addresses real problems. Will have a close look however, correct me if my 2 second impression is completely off.
- funthree 15y agoYou are right, at first I did do it just to see if it was possible. I've been meaning to write in more detail about some of the implications, clean up some of the code, etc. I've also experimented with the API to feel out how it could work with other client side stuff in an isomorphic way, url routes, and other frameworks (https://gist.github.com/1336381 https://gist.github.com/1336381), but havent released any of that.
- maratd 15y ago> instead of creating a framework that addresses real problems. If you need to protect code that is currently client-side while retaining responsiveness, this will solve that problem. In my opinion, the price for that is too high. You are significantly increasing the traffic between the server and the client. On top of that, you are forced to do all your work on the server, which to me feels like a step back to the way we used to do things a decade ago. Beefy servers handling a few clients, rather than light servers handling thousands of clients.
- AlexC04 15y agoI'd like a simpler explanation of how it all works. With colorful flow charts and graphs. I'm really interested in how it compares to what express does. How is it the same, how different? However since I'm reading this from the office between doing actual work I've not got time to read this version. I may or may not remember to come back and check it out after work. Anyways, all of that is intended as a round of constructive criticism. At the end of the day, it is what it is.
- akavlie 15y agoIf you want colorful flow charts, there are plenty at the "Isomorphic" link: http://blog.nodejitsu.com/scaling-isomorphic-javascript-code http://blog.nodejitsu.com/scaling-isomorphic-javascript-code The proposed Resource-View-Presenter model is a bit of a brain bender. Anyway, that aside, I agree -- this is described as a framework "initiative", and that page has no links to actual code, making it sound like a mere proposal. However, looking back at Nodejitsu's blog, it looks like they have a post with a more cogent explanation... and github links: http://blog.nodejitsu.com/introducing-flatiron http://blog.nodejitsu.com/introducing-flatiron
- AlexC04 15y agoThanks so much for this! The graphs are exactly the kind of "conceptual flow" I like to have to give me a 1000 meter view of what's going on.
- mcantelon 15y agoExpress is quite low level, with many frameworks built on top of it. This appears to be higher level.
- justatdotin 15y agoyeah, but, it's not immediately clear to me why they built sugarskull instead of a client library to match connect's routing (I've used sammyjs for that purpose) and while I do appreciate the philosophy of plates (I've done something similar), I wonder why wasn't that implemented as an express 'template engine'. I'm sure there's good reasons: I'd like them spelled out ;{)} looking good.
- jonpaul 15y agoAwesome! I had a similar on building something like this. One thing is for certain, members of the community lean more towards a simplistic, minimal, and clean toolset. Express.js delivers, and this seems to as well. I've dedicated myself completely to Node.js for the last month, and I'm sold!