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

Ember Fastboot

ember-fastboot.com

Post reply on HN
Print view View original

71–80 of 100 posts

Re: Ember Fastboot

#71

Post by hardwaresofton »

orf wrote: post #68
sotojuan wrote: post #67

Earlier quoted context omitted.

Good points, though I'll say I've rarely seen Ember be recommended to beginners. And to be fair, the same thing has been said about React, though both Ember and React allow you to use a CDN link like in the good old days.

> I've rarely seen Ember be recommended to beginners. I started a new job and went from 0 JS (other than some JQuery and knowing the syntax) to 100 with Ember. Ember is really really good for beginners, grandparent talks of having to know transpiling, broccoli/task runners and livereload but doesn't understand that you need to know none of that to get working with Ember. Write your app by editing the files ember-cli…

I stand corrected -- clearly what I thought was what beginners would feel is not what they did.

My point though, was that after you build on all this complexity that you don't understand (and don't have to deal with), when something goes wrong, you're in for a world of hurt. But maybe that's not an issue

Re: Ember Fastboot

#72

Post by hardwaresofton »

qaq wrote: post #63
hardwaresofton wrote: post #61

Earlier quoted context omitted.

I agree it helps -- but there is a hidden cost of people not understanding all the towers of abstraction that have been built up for them, despite sitting on top of it. Ember CLI does file generation and a whole lot more. I'm not saying it shouldn't -- but that shouldn't be the easiest most approachable way to start with Ember. Why should someone have to learn all the following things: - transpiling - nodejs - npm &…

For the 3 major frameworks it's about the same list (minus bower but Ember is phasing it out too.

How so? angular1 does not require you to download anything node-related, for example?

Angular doesn't recommend any tooling, pretty much (just include the framework code and you're off to the races, write some html write some js)...

Re: Ember Fastboot

#73

Post by qaq »

hardwaresofton wrote: post #72
qaq wrote: post #63

Earlier quoted context omitted.

For the 3 major frameworks it's about the same list (minus bower but Ember is phasing it out too.

How so? angular1 does not require you to download anything node-related, for example? Angular doesn't recommend any tooling, pretty much (just include the framework code and you're off to the races, write some html write some js)...

Angular 2 does :) about the same list as was outlined for Ember

Re: Ember Fastboot

#74

Post by iamstef »

hardwaresofton wrote: post #71
orf wrote: post #68

Earlier quoted context omitted.

> I've rarely seen Ember be recommended to beginners. I started a new job and went from 0 JS (other than some JQuery and knowing the syntax) to 100 with Ember. Ember is really really good for beginners, grandparent talks of having to know transpiling, broccoli/task runners and livereload but doesn't understand that you need to know none of that to get working with Ember. Write your app by editing the files ember-cli…

I stand corrected -- clearly what I thought was what beginners would feel is not what they did. My point though, was that after you build on all this complexity that you don't understand (and don't have to deal with), when something goes wrong, you're in for a world of hurt. But maybe that's not an issue

Abstractions aim to hide complexity until one requires them.

As a developer, one becomes productive when one realize when to put the blinders on, and when to take them off. As such I for one, love that I don't need knowledge of x86 assembler, chip design, or signal processing until the problem at hand actually requires them.

Ember-cli aspires to keep developers focused on features, not orthogonal tech. That is unless they need to peel back that layer of the onion, and dive in. Even then, the goal is for only a few community members to dive in, explore the problem space, and ultimately contribute the solution. Next release, all community members benefit, without also having to invest (until the point where they have a specific itch to scratch).

Abstractions hurt when they leak, as such we must aspire to provide the best abstractions we can (at each layer), and this is only possible in collaboration with an eager and enthusiastic community.

An symptom of a curated solution, is all aspects of the stack evolve to work together. Mitigate abstraction leaks at the various boundaries.

Re: Ember Fastboot

#75

Post by cubano »

Trying to run the demo in win10....

  Build error

  The Broccoli Plugin: [object Object] failed      with:
   RangeError: Maximum call stack size exceeded
    at new Error (native)
    at Error (native)
    at Object.fs.mkdirSync (fs.js:794:18)
    at sync (C:\Users\marke\ember\github-fastboot-    example\node_modules\ember-   network\node_modules\broccoli-  templater\node_modules\broccoli-stew\node_modules\broccoli-  funnel\node_modules\mkdirp\index.js:71:13)
    at sync (C:\Users\marke\ember\github-fastboot-  example\node_modules\ember-   network\node_modules\broccoli-templater\node_modules\broccoli-stew\node_modules\broccoli-funnel\node_modules\mkdirp\index.js:77:24)
    at sync (C:\Users\marke\ember\github-fastboot-example\node_modules\ember-network\node_modules\broccoli-templater\node_modules\broccoli-stew\node_modules\broccoli-funnel\node_modules\mkdirp\index.js:78:17)
    at sync (C:\Users\marke\ember\github-fastboot-example\node_modules\ember-network\node_modules\broccoli-templater\node_modules\broccoli-stew\node_modules\broccoli-funnel\node_modules\mkdirp\index.js:78:17)
    at sync (C:\Users\marke\ember\github-fastboot-example\node_modules\ember-network\node_modules\broccoli-templater\node_modules\broccoli-stew\node_modules\broccoli-funnel\node_modules\mkdirp\index.js:78:17)
    at sync (C:\Users\marke\ember\github-fastboot-example\node_modules\ember-network\node_modules\broccoli-templater\node_modules\broccoli-stew\node_modules\broccoli-funnel\node_modules\mkdirp\index.js:78:17)
    at sync (C:\Users\marke\ember\github-fastboot-example\node_modules\ember-network\node_modules\broccoli-templater\node_modules\broccoli-stew\node_modules\broccoli-funnel\node_modules\mkdirp\index.js:78:17)

  The broccoli plugin was instantiated at: 
  undefined
Any ideas?

Re: Ember Fastboot

#76

Post by mixonic »

cubano wrote: post #75

Trying to run the demo in win10.... Build error The Broccoli Plugin: [object Object] failed with: RangeError: Maximum call stack size exceeded at new Error (native) at Error (native) at Object.fs.mkdirSync (fs.js:794:18) at sync (C:\Users\marke\ember\github-fastboot- example\node_modules\ember- network\node_modules\broccoli- templater\node_modules\broccoli-stew\node_modules\broccoli- funnel\node_modules\mkdirp\index.…

Opening an issue on https://github.com/tildeio/ember-cli-fastboot is probably the best way to get help tracking down a bug.

Re: Ember Fastboot

#77

Post by cubano »

mixonic wrote: post #76
cubano wrote: post #75

Trying to run the demo in win10.... Build error The Broccoli Plugin: [object Object] failed with: RangeError: Maximum call stack size exceeded at new Error (native) at Error (native) at Object.fs.mkdirSync (fs.js:794:18) at sync (C:\Users\marke\ember\github-fastboot- example\node_modules\ember- network\node_modules\broccoli- templater\node_modules\broccoli-stew\node_modules\broccoli- funnel\node_modules\mkdirp\index.…

Opening an issue on https://github.com/tildeio/ember-cli-fastboot is probably the best way to get help tracking down a bug.

Yes of course. Thanks.

Looking around on the site I didn't see a link to report something like this, and I didn't immediately think to goto github with it.

Please excuse my ignorance.

Re: Ember Fastboot

#78

Post by mixonic »

cubano wrote: post #77
mixonic wrote: post #76

Earlier quoted context omitted.

Opening an issue on https://github.com/tildeio/ember-cli-fastboot is probably the best way to get help tracking down a bug.

Yes of course. Thanks. Looking around on the site I didn't see a link to report something like this, and I didn't immediately think to goto github with it. Please excuse my ignorance.

Np! There is also a #-fastboot room on the Ember Community Slack, directions for jumping in there can be found on emberjs.com: http://emberjs.com/community/

Re: Ember Fastboot

#79

Post by ef4 »

qaq wrote: post #73
hardwaresofton wrote: post #72

Earlier quoted context omitted.

How so? angular1 does not require you to download anything node-related, for example? Angular doesn't recommend any tooling, pretty much (just include the framework code and you're off to the races, write some html write some js)...

Angular 2 does :) about the same list as was outlined for Ember

Indeed, and AFAIK angular is even basing their build tooling code on ember-cli.

Re: Ember Fastboot

#80

Post by takno »

orf wrote: post #69
mtberatwork wrote: post #66

Earlier quoted context omitted.

> When an HTTP request comes in, we direct it to Ember's router, where it figures out what models to load and components to render. When it finishes, it sends the document back to the browser. Aren't we now just back to square one again in terms of MVC frameworks? What are the advantages here over simply implementing Django, RoR, Spring, Laravel, etc and cutting back on the JS (at least in terms of content-driven sit…

> What are the advantages here over simply implementing... You get all of the advantages of single page apps, without the unresponsive initial load time. There are also whole classes of apps you can't build with Django, RoR etc, so the question is a bit ridiculous IMO.

It really isn't. Jumping into using a huge performance sink like ember to add a little interactivity to a content page is a horrible decision to start with. This just seems to drag the poor performance back to kill your server
Post reply on HN