You are either not logged in or not registered with our community. Click here to register.
 
December 10, 2016, 04:43:36 AM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

Click here if you are having problems.
Default Wide Screen Beige Lilac Rainbow Black & Blue October Send us your theme!

Hark!  The Herald!
Holiday Issue 2016

Wiki Blogs Dicebot

Author Topic: Silly question for any AngularJS devs lurking here  (Read 595 times)

0 Members and 1 Guest are viewing this topic.

Offline RivedaTopic starter

Silly question for any AngularJS devs lurking here
« on: December 22, 2015, 09:47:54 AM »
Is it wise to use Angular and other frills in your 404.html or should it be static?

(I don't dare ask dumb questions on StackOverflow, only smart ones)

Offline Vekseid

Re: Silly question for any AngularJS devs lurking here
« Reply #1 on: December 22, 2015, 05:00:48 PM »
If it's a part of your site, why not?

I haven't messed with 2.0 to see if it has the same issues 1.x did, but if it does, trying to implement it on a community site is not a great idea, FYI >_>

Offline RivedaTopic starter

Re: Silly question for any AngularJS devs lurking here
« Reply #2 on: December 23, 2015, 04:11:24 AM »
Why not? Because I don't know enough about Angular's JIT compilation to know whether it breaks when the server does an error redirectů

What are the issues? I'm using it for a small project that needs a ton of data binding but will only have like ten users.

Offline Vekseid

Re: Silly question for any AngularJS devs lurking here
« Reply #3 on: December 23, 2015, 01:07:37 PM »
4xx pages are html pages like any other. You should have them either mimic your CMS or be an actual part of it.

More difficult with 5xx, but that's a different topic. >_>

Angular 1.x starts to have issues once you get a lot of binds - more than a few hundred. Each one gets iterated over.

I remember thinking of a clever way to get around that problem but i ended up starting to switch over to React for the new CMS code, since it was basically designed to do what I needed.