[FoRK] AngularJS — Superheroic JavaScript MVW Framework

Ken Meltsner meltsner at alum.mit.edu
Tue Oct 8 20:07:53 PDT 2013


The Firebase version sounds especially interesting:

http://firebase.github.io/angularFire/

Durable entity store, priced in a variety of sizes.

I guess, in the future, no one will buy infastructure or databases.

Ken


On Tue, Oct 8, 2013 at 8:26 PM, Stephen D. Williams <sdw at lig.net> wrote:

> Sounds nice!  A quick list of cool things (libraries, methods, etc.) to
> use/pay attention to on the web app side would be very helpful.  I was
> aware of AngularJS and a number of others, and I've been itching to use
> WebSockets. Hopefully I will dive into some web development shortly.  Best
> practices hints would be great.
>
> sdw
>
>
> On 10/8/13 1:25 PM, John Mitchell wrote:
>
>> We deal with both build time as well as runtime dependency & bundling.
>> Fwiw, for this we're also using the grunt toolchain for builds, etc.
>>
>> The main trick we're using is that each version of each file is uniquely
>> identified with a content hash of the file. We then shove all of this stuff
>> into our own origin servers as well as cdn's.  Then our bundling uses the
>> explicit name for all of these resources and only the high level end points
>> are generic/unversioned.
>>
>> Cheers,
>> John
>>
>> On Oct 8, 2013, at 4:30 AM, Gregory Alan Bolcer <greg at bolcer.org> wrote:
>>
>>  Ivy doesn't do javascript?
>>>
>>> On 10/7/2013 11:12 PM, John Mitchell wrote:
>>>
>>>> On Oct 7, 2013, at 10:47 PM, Bill Humphries <whump at mac.com> wrote:
>>>>
>>>>> On Oct 7, 2013, at 10:44 PM, John Mitchell <jdmitchell at gmail.com>
>>>>> wrote:
>>>>>
>>>> […]
>>>>
>>>>> FWIW, I do agree that for most people Ember's approach to things like
>>>>>> templating is more approachable. Angular takes a bit of work to internalize
>>>>>> it's approach.
>>>>>>
>>>>> How do you do dependency and module management with Angular?
>>>>>
>>>> Our case is a bit odd in that we're building our own "framework" on top
>>>> of Angular for use by various internal and external teams so we're doing
>>>> modularization, dependency management, and the whole bootstrapping thing
>>>> ourselves. We have a server-side packager that works in conjunction with
>>>> our own client-side bootstrapping "shell" in which the various modules are
>>>> pulled down on-demand.
>>>>
>>>> John
>>>>
>>>>
>>>> ______________________________**_________________
>>>> FoRK mailing list
>>>> http://xent.com/mailman/**listinfo/fork<http://xent.com/mailman/listinfo/fork>
>>>>
>>>>  --
>>> greg at bolcer.org, http://bolcer.org, c: +1.714.928.5476
>>> ______________________________**_________________
>>> FoRK mailing list
>>> http://xent.com/mailman/**listinfo/fork<http://xent.com/mailman/listinfo/fork>
>>>
>>
>> ______________________________**_________________
>> FoRK mailing list
>> http://xent.com/mailman/**listinfo/fork<http://xent.com/mailman/listinfo/fork>
>>
>
>
> --
> Stephen D. Williams sdw at lig.net stephendwilliams at gmail.com LinkedIn:
> http://sdw.st/in
> V:650-450-UNIX (8649) V:866.SDW.UNIX V:703.371.9362 F:703.995.0407
> AIM:sdw Skype:StephenDWilliams Yahoo:sdwlignet Resume: http://sdw.st/gres
> Personal: http://sdw.st facebook.com/sdwlig twitter.com/scienteer
>
>
> ______________________________**_________________
> FoRK mailing list
> http://xent.com/mailman/**listinfo/fork<http://xent.com/mailman/listinfo/fork>
>



-- 
After 30+ years of email, I have used up my supply of clever ,sig material.


More information about the FoRK mailing list