101–110 of 115 posts
Earlier quoted context omitted.
[deleted]
Well I'll sheepishly raise my hand and say I don't have a bloody clue what the sentence is trying to say. Individually, the words make sense, but after trying to parse the combination I feel like I have less information than when I started.
> FOAM is a full-stack Reactive MVC Meta-Programming framework. 5 years ago I would have thought that this would have been the title of the tech section of Onion article ...
These links (below) are a bit clearer, imho. The project actually looks pretty interesting, but the readme in the repo isn't as convincing:
http://foam-framework.github.io/foam/about/
http://foam-framework.github.io/foam/tutorial/0-intro/
Edit: formatting
One thing you notice right off the bat: Its very slow. It takes about 2s on my machine to load the TodoMVC example. Thats about as long as it takes to load my GMail inbox. Thats pretty horrible for whats supposed to be the "Hello World" of JS frameworks. I didnt dig in what actually takes so long, but it seems like it has still some way to go. I find it interesting that after Angular this would the second (3rd if you…
What do I see? It's language centric, that's good and bad. The good bit is you can with a very small JS lib write code to generate a dynamic page. The bad bit: as the language grows and rusts, you have to chase down the removed features. Much easier to grasp in concept and execution than Angular.
Loved this bit in the calc demo source, testing: https://github.com/foam-framework/foam/blob/master/apps/acal...
Q. Is foam an attempt to create a framework for Mobile Apps?
Earlier quoted context omitted.
I'd love to see a mature app written this way (and I mean that genuinely, without sarcasm) and look at their project timeline, war stories, etc. My gut feeling is that the 'frameworks are for prototypes, libraries are for production' camp is closest to the money, but (a) I have no actual data and (b) different approaches to frameworks will have different outcomes.
Just compare number of well-known production apps written using React & Angular.
> FOAM is a full-stack Reactive MVC Meta-Programming framework. Inevitably reminds me of this: http://html9responsiveboilerstrapjs.com/ I understand MVC, but what is reactive meta-programming exactly?
Simplifying - Reactive: The display automatically changes when some data changes eg http://foam-framework.github.io/foam/foam/index.html?model=f... the one clock moves when you move the other Meta-programming: The writing of computer programs with the ability to treat programs as their data. Examples of meta-programming include Lisp-macros and C++ Templates. FOAM does this through code-generation, but for Javascript,…
This is a bold take on a problem that a lot of people have written away as reinventing the wheel. But color me impressed! Unlike almost every other Javascript framework we've so far seen, FOAM makes the data model the primary entity in the system, which is a good idea. In the typical UI-driven development of web applications, the data model often gets modified without much thought and causes cascading complexity acro…
I'd love to see a mature app written this way (and I mean that genuinely, without sarcasm) and look at their project timeline, war stories, etc. My gut feeling is that the 'frameworks are for prototypes, libraries are for production' camp is closest to the money, but (a) I have no actual data and (b) different approaches to frameworks will have different outcomes.
> a mature app written this way
I've added links a number links to FOAM apps for you at the bottom of http://foamdev.com.
We have a number of mature apps. QuickBug, which is a codesite issue tracker, is about two years old. MBug is a mobile version, is about a year old. The ChromeOS calculator was written last summer as a demo but went into production just recently. There's also a rough but working GMail client. The Chrome App Builder is also in production, but, unlike the other apps, isn't open-sourced. We also have a couple very large internal Google apps that I can't talk about.
> project timeline FOAM was started in 2011, and generated its first production code, in C++ and JS for Chrome, in early 2012.
> war stories
Here's one: https://docs.google.com/presentation/d/139TUw8tLtqRzFSHGoLTQ...
I have several others as well, but I would need to scrub them before making them public.
Earlier quoted context omitted.
Bold, and beautiful!! Quick everyone, scrap all your existing frameworks and jump on the flavor of the week! Seriously though, I think it's borderline negligent to contribute any kind of hype to new javascript frameworks considering they are spraying out into the ecosystem like a broken fire hydrant. New javascript frameworks should be met with extreme skepticism, if not indifference, if we want this industry to be a…
It looks like this framework goes back ~3 years. So, why would you consider it the 'flavor of the week'? Because someone posted it to HN? That doesn't seem to be much of a threshold. Also, it looks like this framework could be of use in other languages aside from javascript.
I lead the FOAM project at Google.