Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Rec Room

hacks.mozilla.org

Post reply on HN
Print view View original

21–30 of 65 posts

Re: Introducing Rec Room

#21

Post by fwenzel »

compedit wrote: post #17
wdmeldon wrote: post #15

I'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.

Yeah you're right. The grunt piece is definitely one that is not set in stone. Ember-CLI is exciting and we've started working closely with the Ember folks to monitor it and see if and when this should become another piece of the recroom puzzle.

Re: Introducing Rec Room

#22

Post by tofumatt »

compedit wrote: post #17
wdmeldon wrote: post #15

I'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.

This is certainly the biggest reason. In the future maybe we can use ember-cli and integrate more with them.

Ember does a LOT of what I want recroom to be able to do, but I'm okay using something that works better right now over using bleeding edge Ember stuff that may be more idiomatic.

Of course, as more people contribute to and use recroom we'll evaluate changing out components. If I picked the wrong thing I hope people will correct it and make this thing better ^_^

Re: Introducing Rec Room

#24

Post by fwenzel »

rdtsc wrote: post #16
snarkyturtle wrote: post #13

That'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.

Yes the whole space moves quickly. The current choice in tools in the recroom "tool belt" is not meant to be unchangeably set in stone. FWIW, Ember CLI is an interesting piece that would connect well to the core Ember framework as well.

Re: Introducing Rec Room

#25

Post by tofumatt »

snarkyturtle wrote: post #13

That'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?

I know Grunt a bit better, but as I explore Gulp I like it a lot. In the future we may switch, but I'd need the Gulpfile to do everything the Grunt one does.

Re: Introducing Rec Room

#26

Post by bilalhusain »

tofumatt wrote: post #23
Raphael wrote: post #6

I see no clock at this time: http://worldclock.tofumatt.com/

I have seen some invalidstateerrors on this for some folks. I'm looking into it, sorry! :-/

Isn't that because indexedDB isn't accessible in private browsing? Not sure what's wrong with Chrome though. It seems not to be complaining about invalid state or about anything.

edit: for Chromium the clock wasn't visible, fixing the height helps

    document.getElementsByTagName('section')[0].style.height = '100px';

Re: Introducing Rec Room

#27

Post by xfalcox »

It's kinda like Google's Web Starter Kit[1], isn't ?

For me, it's really helpful when we can use some guidance from great players in the industry when choosing which framework to use. We recently forked Web Starter Kit, added some bower instructions, integrated Twitter BootStraped and now we've got some internal guidelines for new SPA.

[1] https://github.com/google/web-starter-kit

Re: Introducing Rec Room

#28

Post by fwenzel »

Joeri wrote: post #11

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 sus…

That's actually where a large group of developers fall as well. You have the total beginners, who realistically won't build an app that has tests, or use a framework to sort out their models and views etc. They just need a HTML, CSS, JS file and some comments and can throw together something simple.

On the other end of the spectrum, you have the experts, who have evaluated a dozen frameworks of their own, know why they like gulp more than broccoli, and really just need an API reference to know what's possible, and off they go.

And in the middle of all this you have the huge group of developers who would really like to have some more help, even if only to help them make decisions of their own and eventually get them over the hump to expert-level. That's the group this is targeted at.

If you make a client-side app with it and figure out you don't like certain pieces of the toolbelt, you can replace them on the spot (they're loosely coupled). If at some point you're so advanced you want to replace it all, fantastic! You don't need our help anymore :)

Re: Introducing Rec Room

#29

Post by albertoleal »

rdtsc wrote: post #16
snarkyturtle wrote: post #13

That'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.

https://gist.github.com/substack/8313379

Re: Introducing Rec Room

#30

Post by tofumatt »

xfalcox wrote: post #27

It's kinda like Google's Web Starter Kit[1], isn't ? For me, it's really helpful when we can use some guidance from great players in the industry when choosing which framework to use. We recently forked Web Starter Kit, added some bower instructions, integrated Twitter BootStraped and now we've got some internal guidelines for new SPA. [1] https://github.com/google/web-starter-kit

That's really good to hear.

I think you're right about it being like Google's Web Starter Kit. The WSK feels a bit more sparse and less idiomatic than recroom, but it's definitely in the same vein. I haven't checked it out since it was announced a few months back though, so maybe it's grown since then.

I'd love to see people do that to recroom -- add what they think is missing. Pull requests are definitely welcome. My aim is to take the headache out of decisions like "Which framework/tool do I use?" so you can get to writing code if, like me, you don't really care which tool you use as long as it works well.

Post reply on HN