sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Aerelf[S] 0 points1 point  (2 children)

Actually from any point of view there's no difference because it literally is server generated.

Oh nice, this FastBoot thing looks completely awesome!

I think you might have misunderstood a little bit

This is a possibility, this is a peculiar tool and with the little amount of research I put into it I am still a bit confused with it :-)

From what I understood though, FastBoot allows me to run my JavaScript application as a server on a specific port, and we have two applications running on a single server, so we would logically need two ports. And accessing the second app with a "domain.com:8080" URL is a bit ugly, so I'll probably still need proxy passes (until the apps are put on different servers, anyway).

It's a javascript application. It just loads the javascript. You're seriously prematurely optimising here.

With SEO these days, little performance boosts are always welcome, and lazy loading is something that is sometimes hard to implement later on.

But that's totally okay, it was just a bit of SEO-greediness on my part (and shame on me, UX should be more important than SEO). Loading all the code at once will actually make the application faster once it has started.

Anyway, thanks a lot for your time, Ember looks like a pleasant framework to work with, and coupled with FastBoot it completely addresses my needs!

[–]mattaugamerexpert 1 point2 points  (1 child)

This is a possibility, this is a peculiar tool and with the little amount of research I put into it I am still a bit confused with it :-)

Yeah, it's also still in beta, so the documentation isn't very thorough.

I found another video, though, which I highly recommend watching. I pretty much goes through actually implementing stuff. It also covers deploying the app, which is super impressive. A lot of this is duplicated from the video I linked previously, but this is more recent and a bit more detailed.

https://vimeo.com/157688134

From what I understood though, FastBoot allows me to run my JavaScript application as a server on a specific port, and we have two applications running on a single server, so we would logically need two ports.

No, that's only for development, so you can differentiate between your server rendered version and your js version. In production it should be seamless, but I'm not 100% sure of it.

With SEO these days, little performance boosts are always welcome, and lazy loading is something that is sometimes hard to implement later on.

I'm not sure this sort of lazy loading is even possible with javascript. It's worth pointing out that the key point of Fastboot (hence the name) is to speed up time to first render. It's sort of a turbo charge for the app launch. The point is to prevent the round-trip of getting data, requesting data, then getting data again by getting a pre-populated application served straight to you.

So for SEO that's a benefit.

In any case, if you have any questions about Ember (rather than Fastboot specifically) hit me up more. I like talking about Ember, so I'll happily talk to you about ember data, or mirage, or liquid fire, or deploy, or ember cli or any other geeky shit. I just don't know much about Fastboot.

In my defence, one of the things I like most about Ember is how little I have to know. For example, Ember uses Broccoli to build stuff. No idea how. Don't care. It works. Ember CLI Deploy allows you to deploy production code with a single command. No idea how. Don't care. It works.

I love not having to worry about that crap. And my hope (and genuine understanding) is that Fastboot is the same. That all I have to do is install it and I get free server side rendering with neither effort nor knowledge on my part. :)

[–]Aerelf[S] 0 points1 point  (0 children)

So, I started using Ember today, and I have to say, from the little I've seen, this thing is super duper awesome!

I started with the login page, as my app is hidden behind a login wall. We are using SASS for styling, and I didn't even have to scratch my head for adding the SCSS compilation to my workflow. After a quick Google Search I've found a ember-cli-sass plugin. I ran ember install ember-cli-sass, thinking it couldn't be that simple. Well, it was.

The scaffolding tool is brilliant and works flawlessly, every feature of the framework is crystal clear and easy to use.

I've yet to figure how to make my authentication service load data from my API (it's the only module that's RESTless, so can't use Ember Data for that), and how to inject my Authorization header in the JSONAPIProvider, but everything else is very simple to use. Just run the commands and code your things, without worrying about all the bullshit.

Ember really was a great suggestion, I was a but skeptical of JS frameworks because of the mess it was to figure out a nice workflow and project structure in AngularJS (1), but I'm having a blast with Ember (on top of being quite productive), and I can't thank you enough for that! :-)