tion.
>
> --
> Martin Cooper
>
>
> On Fri, Oct 5, 2012 at 10:24 AM, Saleem Abdul Hamid
> >
> wrote:
> > More updates :)
> >
> > I added a plugin api, and wrote two example plugins. Now you can use
> those
> > plugins to include coffee-scri
There are situations where that is simply not enough. For example, let's
say you have a working module but you want to add an optimization like
caching to it. With or without caching the exposed interface will work
exactly the same (as it should). So there's really not another way to test
excep
Hi everyone,
This is now available as Connect middleware.
On Saturday, March 24, 2012 5:04:52 PM UTC-7, Saleem Abdul Hamid wrote:
>
> tl;dr - Client-side require with a server-side component that caches
> dependencies, bundles them, and caches the bundles. Need feedback on
>
tages). The crude, but sufficient ;), benchmarks
are available in the readme.
https://github.com/meelash/Mundlejs
On Saturday, March 24, 2012 5:04:52 PM UTC-7, Saleem Abdul Hamid wrote:
>
> tl;dr - Client-side require with a server-side component that caches
> dependencies, bundles th
Is there a license that says most people can do whatever you want with my
stuff but if Microsoft (example) uses it to make 100 million dollars, I
want to negotiate for a piece of it? That's really the question everyone is
asking, although they're too shy to say it, because wanting to make money
an issue when loading mundle
> modules from an HTTPS server. I found that all modules were loaded via HTTP
> only, even if the current page is HTTPS. Here's the fix:
> https://github.com/meelash/Mundlejs/pull/17
>
> I hope this helps!
>
> Tauren
>
>
>
&g
Mind that it is not a free software license.
>>
>> Jérémy.
>>
>> On 07/05/2013 14:51, Saleem Abdul Hamid wrote:
>> > Is there a license that says most people can do whatever you want with
>> my
>> > stuff but if Microsoft (example) uses it to make 100 mil
BTW, I also rereleased this under the MIT license. Thanks Martin and Oliver
for that advice.
On Saturday, March 24, 2012 8:04:52 PM UTC-4, Saleem Abdul Hamid wrote:
>
> tl;dr - Client-side require with a server-side component that caches
> dependencies, bundles them, and caches th
est to fix an issue when loading mundle
> modules from an HTTPS server. I found that all modules were loaded via HTTP
> only, even if the current page is HTTPS. Here's the fix:
> https://github.com/meelash/Mundlejs/pull/17
>
> I hope this helps!
>
> Tauren
>
>
&g
On Tuesday, May 7, 2013 3:02:51 PM UTC-4, Isaac Schlueter wrote:
>
> I've often thought it would be worthwhile to have some kind of "free
> once I make some money" license. Like, if you're a not-for-profit
> entity, you can use this code under BSD today. If you are a
> for-profit enterprise,
If you convert it back to javascript for V8, then anyone else could do the
same so you won't have really gained anything- no performance, because
you're giving V8 js anyway and no code protection, because anyone can take
your code and use it to convert the binary to javascript themselves.
It se
BTW, with respect to coffeescript vs javascript, let me just make it clear
that the package is compiled to js before publishing to npm. Also, for the
sake of one or two very good contributors with a strong anti-coffeescript
preference, I'd even be willing to switch from coffeescript for the sour
@deitch-
I see the problem differently. I would say that the fundamental problem of
a client-side module loader is exactly the same as that of a server-side
one:
1) Allow me to write really modular reusable code, without artificial
restrictions.
The client-side module loader has a lot of doma
As I understand it, webmake is the same thing as requirejs+optimizer: the
only difference is webmake uses sync require syntax and requirejs+optimizer
uses async syntax. In the end you have all 100+ files loading as a single
file.
Opposed to this, consider just using requirejs without its optimi
seDir/testFolder1/testFile1.js,
require('./testFolder2/testFile2.js')
Will load baseDir/testFolder1/testFolder2/testFile2.js.
This works for both asynchronous and synchronous requires.
Next up is probably cacheing.
On Saturday, March 24, 2012 5:04:52 PM UTC-7, Saleem Abdul Hamid w
loading one or two minified/compressed packages.
> I've tried many AMD loaders and in the end our projects are simpler without
> them. Stitch was trivial to patch to support multiple packages something
> like `require(package/some/path)`
>
>
> On Saturday, March 24, 2012 5:04:5
16 matches
Mail list logo