As an integrated environment to get going quickly on a large-scale single page app this looks nice. I'm wondering though who this is suited for. An experienced web developer who has a few frameworks under their belt will have a preferred toolbox, and likely won't be interested. Meanwhile, a beginner will have a really steep learning curve figuring all these tools out at the same time, instead of one by one, and I suspect will fall off the mountain before they reach the summit. I suppose this toolbox is best suited for the mid-level, experienced enough to know some of the tools, but not so experienced as to have decided which tools they want.
Introducing Rec Room
11–20 of 65 posts
Re: Introducing Rec Room
#12Re: Introducing Rec Room
#13That's the first time I've seen someone mention Grunt since Gulp became the new hotness. Wonder why they chose to go with that instead?
Re: Introducing Rec Room
#14I see no clock at this time: http://worldclock.tofumatt.com/
fails for me in private browsing mode because firefox can't remember history, works in normal mode
Re: Introducing Rec Room
#15I'm very curious as to why this is diverging from the "Ember Way" and not using http://www.ember-cli.com/
It's an officially supported approach that is under very active development and (at least ostensibly) covers what this tool does and more. The use of globals over ES6 modules is the most glaring omission.
Re: Introducing Rec Room
#16That's the first time I've seen someone mention Grunt since Gulp became the new hotness. Wonder why they chose to go with that instead?
Probably because next week Gulp will stop begin the new hotness and there will be something else.
Re: Introducing Rec Room
#17I'm very curious as to why this is diverging from the "Ember Way" and not using http://www.ember-cli.com/ It's an officially supported approach that is under very active development and (at least ostensibly) covers what this tool does and more. The use of globals over ES6 modules is the most glaring omission.
Maybe it's the active development part of it? Things are changing fast and it's still not even at 0.1.0.
From the docs:
Although potentially exciting, this is still really a WIP, use at your own risk.
Re: Introducing Rec Room
#18At the end of this road, I foresee a full IDE baked into Firefox. I can't wait.
It would so great if you could just open the App Manager, click "Create New App", check the boxes of the libraries you want to include by default (jQuery, Ember, etc.), and it would then generate a Hello World app folder with all those files included.
Heck, Firefox Developer Tools is practically already an IDE. All that really remains for it is a "Resources" tab with text editing ability.
EDIT: Additionally, being beginner-friendly would be a huge advantage to Firefox OS because its target market is the developing world. Only requiring an installation of Firefox to develop apps would significantly lower the barrier for who could learn to develop apps. Locals could quickly learn to make an app that caters specifically to their local community (what farms are hiring, where the cleanest water is, etc.).
Re: Introducing Rec Room
#19At the end of this road, I foresee a full IDE baked into Firefox. I can't wait. It would so great if you could just open the App Manager, click "Create New App", check the boxes of the libraries you want to include by default (jQuery, Ember, etc.), and it would then generate a Hello World app folder with all those files included. Heck, Firefox Developer Tools is practically already an IDE. All that really remains for…
If you are running Aurora, you can have almost all of this: go to about:config, search for "webide.enabled" and change the value to true
It won't download and install the js libraries for you, but it does let you click "Create New App" and sets a bunch of stuff up for you.
You can even install a Firefox OS simulator to test your app with.
Re: Introducing Rec Room
#20As an integrated environment to get going quickly on a large-scale single page app this looks nice. I'm wondering though who this is suited for. An experienced web developer who has a few frameworks under their belt will have a preferred toolbox, and likely won't be interested. Meanwhile, a beginner will have a really steep learning curve figuring all these tools out at the same time, instead of one by one, and I sus…
You're right on the money. I think people who already know their tools well and have a system that works are covered and are NOT the target audience.
In the future I'd like to sort of ween new users into using recroom by abstracting away a lot of things (we are largely proxying to other commands in grunt/yeoman right now, but the user doesn't need to know these tools to use recroom at a very basic level).
But for me, I feel like an intermediate/experienced developer who has just always wanted an end-to-end idiomatic way to write apps without me knowing all the tools inside-out. I'm hoping recroom will be that most of all, so you're right :-)