I had just ported php.js (http://phpjs.org) for Node.js.
My motivation was to available new functions that could help programmers
to accomplish simple tasks and yup, I came from PHP and I was really
missing some basic functions :)
the only idea I have is to get some torches and burn your repository down because PHPJS has the most horrible un optimized piece of javascript ever created.
you are only limiting your ability to learn the language this way. If you want PHP, write PHP.. if want learn js, write JS not phpJS.
Just out of curiosity, what kind of "basic" functions where you missing?
On Friday, June 1, 2012 at 3:17 PM, Alan Hoffmeister wrote:
> Hello there!
> I had just ported php.js (http://phpjs.org) for Node.js.
> My motivation was to available new functions that could help programmers to accomplish simple tasks and yup, I came from PHP and I was really missing some basic functions :)
> --
> Att,
> Alan Hoffmeister
> -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com (mailto:nodejs@googlegroups.com)
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@googlegroups.com (mailto:nodejs+unsubscribe@googlegroups.com)
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
That's ok, I had already separated some sticks and gasoline to help
people to burn me down because of this package...
Why everyone get scared when they read PHP in the name of the package?
I should have name it node-bunch-of-functions :)
There's no PHP inside this package, just similarly named functions.
Unoptimized? Of course it is.. Did you read somewhere in my e-mail
"production ready"?
Come on Arnout, you know that I'm not trying to make people write
javascript in the PHP way, for example, if you want to captalize the
first letter of a sentence you can write a function:
function ucfirst(str) {
return str.charAt(0).toUpperCase() + str.substr(1);
}
Or you can require some package that already have this function and
use it, but not you, of course, because that damn function is named
exactly as a well known PHP function, so let's burn that repo down!
Mind note: *do not* use PHP inside the name of the packages.
> the only idea I have is to get some torches and burn your repository down because PHPJS has the most horrible un optimized piece of javascript ever created.
> you are only limiting your ability to learn the language this way. If you want PHP, write PHP.. if want learn js, write JS not phpJS.
> Just out of curiosity, what kind of "basic" functions where you missing?
> On Friday, June 1, 2012 at 3:17 PM, Alan Hoffmeister wrote:
> Hello there!
> I had just ported php.js (http://phpjs.org) for Node.js.
> My motivation was to available new functions that could help programmers to accomplish simple tasks and yup, I came from PHP and I was really missing some basic functions :)
> I should have name it node-bunch-of-functions :)
You exactly right! And really, in this case you can skip some phpjs fucntions from there,
especially aliases like explode/implode and, IMO, unefective bcmath port.
There is node-bigint for node.js that, i think, will better fit in node.js project.
Other functions, that are usefull, like ucfirst, is a good thing to combine in some node.js module :)
пятница, 1 июня 2012 г., 18:02:41 UTC+4 пользователь Alan Hoffmeister написал:
> That's ok, I had already separated some sticks and gasoline to help > people to burn me down because of this package... > Why everyone get scared when they read PHP in the name of the package? > I should have name it node-bunch-of-functions :) > There's no PHP inside this package, just similarly named functions.
> Unoptimized? Of course it is.. Did you read somewhere in my e-mail > "production ready"?
> Come on Arnout, you know that I'm not trying to make people write > javascript in the PHP way, for example, if you want to captalize the > first letter of a sentence you can write a function:
> Or you can require some package that already have this function and > use it, but not you, of course, because that damn function is named > exactly as a well known PHP function, so let's burn that repo down!
> Mind note: *do not* use PHP inside the name of the packages.
> > the only idea I have is to get some torches and burn your repository > down because PHPJS has the most horrible un optimized piece of javascript > ever created.
> > you are only limiting your ability to learn the language this way. If > you want PHP, write PHP.. if want learn js, write JS not phpJS.
> > Just out of curiosity, what kind of "basic" functions where you missing?
> > On Friday, June 1, 2012 at 3:17 PM, Alan Hoffmeister wrote:
> > Hello there!
> > I had just ported php.js (http://phpjs.org) for Node.js. > > My motivation was to available new functions that could help programmers > to accomplish simple tasks and yup, I came from PHP and I was really > missing some basic functions :)
Due the great expectation around node.js, libs and functions grow up without control.
Nowadays we have a lot of "requires" and we need to memorize a lot of names (fs, path, vm, ...); with time, we'll spend more and more time reading documentation :-(
My proposal is incorporate the mechanism of "register" the module, for example, phpjs library could register the function "isset" into "utils", and "abs" function into "math"
> I had just ported php.js (http://phpjs.org) for Node.js.
> My motivation was to available new functions that could help > programmers to accomplish simple tasks and yup, I came from PHP and I > was really missing some basic functions :)
> Due the great expectation around node.js, libs and functions grow up
> without control.
> Nowadays we have a lot of "requires" and we need to memorize a lot of
> names (fs, path, vm, ...); with time, we'll spend more and more time
> reading documentation :-(
> My proposal is incorporate the mechanism of "register" the module, for
> example, phpjs library could register the function "isset" into "utils",
> and "abs" function into "math"
> So we could have libraries well sorted !!
> El 01/06/12 15:17, Alan Hoffmeister escribió:
>> Hello there!
>> I had just ported php.js (http://phpjs.org) for Node.js.
>> My motivation was to available new functions that could help programmers
>> to accomplish simple tasks and yup, I came from PHP and I was really
>> missing some basic functions :)
> On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee <seijisam...@gmail.com> wrote:
>> Due the great expectation around node.js, libs and functions grow up
>> without control.
>> Nowadays we have a lot of "requires" and we need to memorize a lot of
>> names (fs, path, vm, ...); with time, we'll spend more and more time reading
>> documentation :-(
>> My proposal is incorporate the mechanism of "register" the module, for
>> example, phpjs library could register the function "isset" into "utils", and
>> "abs" function into "math"
>> So we could have libraries well sorted !!
>> El 01/06/12 15:17, Alan Hoffmeister escribió:
>>> Hello there!
>>> I had just ported php.js (http://phpjs.org) for Node.js.
>>> My motivation was to available new functions that could help programmers
>>> to accomplish simple tasks and yup, I came from PHP and I was really missing
>>> some basic functions :)
> > On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee <seijisam...@gmail.com>
> wrote:
> >> Due the great expectation around node.js, libs and functions grow up
> >> without control.
> >> Nowadays we have a lot of "requires" and we need to memorize a lot of
> >> names (fs, path, vm, ...); with time, we'll spend more and more time
> reading
> >> documentation :-(
> >> My proposal is incorporate the mechanism of "register" the module, for
> >> example, phpjs library could register the function "isset" into
> "utils", and
> >> "abs" function into "math"
> >> So we could have libraries well sorted !!
> >> El 01/06/12 15:17, Alan Hoffmeister escribió:
> >>> Hello there!
> >>> I had just ported php.js (http://phpjs.org) for Node.js.
> >>> My motivation was to available new functions that could help
> programmers
> >>> to accomplish simple tasks and yup, I came from PHP and I was really
> missing
> >>> some basic functions :)
>> > On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee <seijisam...@gmail.com>
>> > wrote:
>> >> Due the great expectation around node.js, libs and functions grow up
>> >> without control.
>> >> Nowadays we have a lot of "requires" and we need to memorize a lot of
>> >> names (fs, path, vm, ...); with time, we'll spend more and more time
>> >> reading
>> >> documentation :-(
>> >> My proposal is incorporate the mechanism of "register" the module, for
>> >> example, phpjs library could register the function "isset" into
>> >> "utils", and
>> >> "abs" function into "math"
>> >> So we could have libraries well sorted !!
>> >> El 01/06/12 15:17, Alan Hoffmeister escribió:
>> >>> Hello there!
>> >>> I had just ported php.js (http://phpjs.org) for Node.js.
>> >>> My motivation was to available new functions that could help
>> >>> programmers
>> >>> to accomplish simple tasks and yup, I came from PHP and I was really
>> >>> missing
>> >>> some basic functions :)
>> >>> --
>> >>> Att,
>> >>> Alan Hoffmeister
>> >>> --
>> >>> Job Board: http://jobs.nodejs.org/ >> >>> Posting guidelines:
>> >>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> >>> You received this message because you are subscribed to the Google
>> >>> Groups "nodejs" group.
>> >>> To post to this group, send email to nodejs@googlegroups.com
>> >>> To unsubscribe from this group, send email to
>> >>> nodejs+unsubscribe@googlegroups.com
>> >>> For more options, visit this group at
>> >>> http://groups.google.com/group/nodejs?hl=en?hl=en
> >> > On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee <seijisam...@gmail.com>
> >> > wrote:
> >> >> Due the great expectation around node.js, libs and functions grow up
> >> >> without control.
> >> >> Nowadays we have a lot of "requires" and we need to memorize a lot of
> >> >> names (fs, path, vm, ...); with time, we'll spend more and more time
> >> >> reading
> >> >> documentation :-(
> >> >> My proposal is incorporate the mechanism of "register" the module,
> for
> >> >> example, phpjs library could register the function "isset" into
> >> >> "utils", and
> >> >> "abs" function into "math"
> >> >> So we could have libraries well sorted !!
> >> >> El 01/06/12 15:17, Alan Hoffmeister escribió:
> >> >>> Hello there!
> >> >>> I had just ported php.js (http://phpjs.org) for Node.js.
> >> >>> My motivation was to available new functions that could help
> >> >>> programmers
> >> >>> to accomplish simple tasks and yup, I came from PHP and I was really
> >> >>> missing
> >> >>> some basic functions :)
> >> >>> --
> >> >>> Att,
> >> >>> Alan Hoffmeister
> >> >>> --
> >> >>> Job Board: http://jobs.nodejs.org/ > >> >>> Posting guidelines:
> >> >>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > >> >>> You received this message because you are subscribed to the Google
> >> >>> Groups "nodejs" group.
> >> >>> To post to this group, send email to nodejs@googlegroups.com
> >> >>> To unsubscribe from this group, send email to
> >> >>> nodejs+unsubscribe@googlegroups.com
> >> >>> For more options, visit this group at
> >> >>> http://groups.google.com/group/nodejs?hl=en?hl=en
On Fri, Jun 01, 2012 at 12:42:42PM -0700, Martin Wawrusch wrote:
> > >> > On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee <seijisam...@gmail.com>
> > >> > wrote:
> > >> >> Due the great expectation around node.js, libs and functions grow up
> > >> >> without control.
> > >> >> Nowadays we have a lot of "requires" and we need to memorize a lot of
> > >> >> names (fs, path, vm, ...); with time, we'll spend more and more time
> > >> >> reading
> > >> >> documentation :-(
> > >> >> My proposal is incorporate the mechanism of "register" the module,
> > for
> > >> >> example, phpjs library could register the function "isset" into
> > >> >> "utils", and
> > >> >> "abs" function into "math"
> On Fri, Jun 1, 2012 at 12:39 PM, Joshua Holbrook <josh.holbr...@gmail.com>wrote:
> > -1 as I like my modules exactly as they are.
> > --Josh
> -1 as well. Thank you Josh.
-1
Perl has this, a default export. You'll need a switch to say that you don't want
the default exports. Then you're going to need a way to remap the default
exports. Pretty soon you're going to have Perl.
Actually, I am you're more likely to devolve into PHP, a global namespace full
of suprises.
On Fri, Jun 1, 2012 at 12:57 PM, Alan Gutierrez <a...@prettyrobots.com> wrote:
> On Fri, Jun 01, 2012 at 12:42:42PM -0700, Martin Wawrusch wrote:
>> > >> > On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee <seijisam...@gmail.com>
>> > >> > wrote:
>> > >> >> Due the great expectation around node.js, libs and functions grow up
>> > >> >> without control.
>> > >> >> Nowadays we have a lot of "requires" and we need to memorize a lot of
>> > >> >> names (fs, path, vm, ...); with time, we'll spend more and more time
>> > >> >> reading
>> > >> >> documentation :-(
>> > >> >> My proposal is incorporate the mechanism of "register" the module,
>> > for
>> > >> >> example, phpjs library could register the function "isset" into
>> > >> >> "utils", and
>> > >> >> "abs" function into "math"
>> On Fri, Jun 1, 2012 at 12:39 PM, Joshua Holbrook <josh.holbr...@gmail.com>wrote:
>> > -1 as I like my modules exactly as they are.
>> > --Josh
>> -1 as well. Thank you Josh.
> -1
> Perl has this, a default export. You'll need a switch to say that you don't want
> the default exports. Then you're going to need a way to remap the default
> exports. Pretty soon you're going to have Perl.
> Actually, I am you're more likely to devolve into PHP, a global namespace full
> of suprises.
> No, we're not going to do this. The module system is finished. It
> won't be changing except for critical bugs.
> On Fri, Jun 1, 2012 at 12:57 PM, Alan Gutierrez <a...@prettyrobots.com> wrote:
> > On Fri, Jun 01, 2012 at 12:42:42PM -0700, Martin Wawrusch wrote:
> >> > >> > On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee <seijisam...@gmail.com>
> >> > >> > wrote:
> >> > >> >> Due the great expectation around node.js, libs and functions grow up
> >> > >> >> without control.
> >> > >> >> Nowadays we have a lot of "requires" and we need to memorize a lot of
> >> > >> >> names (fs, path, vm, ...); with time, we'll spend more and more time
> >> > >> >> reading
> >> > >> >> documentation :-(
> >> > >> >> My proposal is incorporate the mechanism of "register" the module,
> >> > for
> >> > >> >> example, phpjs library could register the function "isset" into
> >> > >> >> "utils", and
> >> > >> >> "abs" function into "math"
> >> On Fri, Jun 1, 2012 at 12:39 PM, Joshua Holbrook <josh.holbr...@gmail.com>wrote:
> >> > -1 as I like my modules exactly as they are.
> >> > --Josh
> >> -1 as well. Thank you Josh.
> > -1
> > Perl has this, a default export. You'll need a switch to say that you don't want
> > the default exports. Then you're going to need a way to remap the default
> > exports. Pretty soon you're going to have Perl.
> > Actually, I am you're more likely to devolve into PHP, a global namespace full
> > of suprises.
Even though some of the functions are surely useful, it would be better if they weren't all in the same module. Having date, math, and string functions all piled in together is a bad pattern, it would be better to package them up in separate modules (and remove functions that duplicate node standard lib). Also, fyi my single brush with php.js was to grab strtotime, only to discover it was a poor/buggy implementation, so you may not want to trust the source material.
On Jun 1, 2012, at 7:11 AM, Oleg Efimov (Sannis) wrote:
> > I should have name it node-bunch-of-functions :)
> You exactly right! And really, in this case you can skip some phpjs fucntions from there,
> especially aliases like explode/implode and, IMO, unefective bcmath port.
> There is node-bigint for node.js that, i think, will better fit in node.js project.
> Other functions, that are usefull, like ucfirst, is a good thing to combine in some node.js module :)
> пятница, 1 июня 2012 г., 18:02:41 UTC+4 пользователь Alan Hoffmeister написал:
> That's ok, I had already separated some sticks and gasoline to help > people to burn me down because of this package... > Why everyone get scared when they read PHP in the name of the package? > I should have name it node-bunch-of-functions :) > There's no PHP inside this package, just similarly named functions.
> Unoptimized? Of course it is.. Did you read somewhere in my e-mail > "production ready"?
> Come on Arnout, you know that I'm not trying to make people write > javascript in the PHP way, for example, if you want to captalize the > first letter of a sentence you can write a function:
> Or you can require some package that already have this function and > use it, but not you, of course, because that damn function is named > exactly as a well known PHP function, so let's burn that repo down!
> Mind note: *do not* use PHP inside the name of the packages.
> > the only idea I have is to get some torches and burn your repository down because PHPJS has the most horrible un optimized piece of javascript ever created.
> > you are only limiting your ability to learn the language this way. If you want PHP, write PHP.. if want learn js, write JS not phpJS.
> > Just out of curiosity, what kind of "basic" functions where you missing?
> > On Friday, June 1, 2012 at 3:17 PM, Alan Hoffmeister wrote:
> > Hello there!
> > I had just ported php.js (http://phpjs.org) for Node.js. > > My motivation was to available new functions that could help programmers to accomplish simple tasks and yup, I came from PHP and I was really missing some basic functions :)
>> On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee<seijisam...@gmail.com> wrote:
>>> Due the great expectation around node.js, libs and functions grow up
>>> without control.
>>> Nowadays we have a lot of "requires" and we need to memorize a lot of
>>> names (fs, path, vm, ...); with time, we'll spend more and more time reading
>>> documentation :-(
>>> My proposal is incorporate the mechanism of "register" the module, for
>>> example, phpjs library could register the function "isset" into "utils", and
>>> "abs" function into "math"
>>> So we could have libraries well sorted !!
>>> El 01/06/12 15:17, Alan Hoffmeister escribi :
>>>> Hello there!
>>>> I had just ported php.js (http://phpjs.org) for Node.js.
>>>> My motivation was to available new functions that could help programmers
>>>> to accomplish simple tasks and yup, I came from PHP and I was really missing
>>>> some basic functions :)
> On Fri, Jun 01, 2012 at 12:42:42PM -0700, Martin Wawrusch wrote:
>>>>>> On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee<seijisam...@gmail.com>
>>>>>> wrote:
>>>>>>> Due the great expectation around node.js, libs and functions grow up
>>>>>>> without control.
>>>>>>> Nowadays we have a lot of "requires" and we need to memorize a lot of
>>>>>>> names (fs, path, vm, ...); with time, we'll spend more and more time
>>>>>>> reading
>>>>>>> documentation :-(
>>>>>>> My proposal is incorporate the mechanism of "register" the module,
>>> for
>>>>>>> example, phpjs library could register the function "isset" into
>>>>>>> "utils", and
>>>>>>> "abs" function into "math"
>> On Fri, Jun 1, 2012 at 12:39 PM, Joshua Holbrook<josh.holbr...@gmail.com>wrote:
>>> -1 as I like my modules exactly as they are.
>>> --Josh
>> -1 as well. Thank you Josh.
> -1
> Perl has this, a default export. You'll need a switch to say that you don't want
> the default exports. Then you're going to need a way to remap the default
> exports. Pretty soon you're going to have Perl.
> Actually, I am you're more likely to devolve into PHP, a global namespace full
> of suprises.
> --
> Alan Gutierrez - @bigeasy
A good idea is a good idea ;-) If it works in perl .....
> No, we're not going to do this. The module system is finished. It
> won't be changing except for critical bugs.
> On Fri, Jun 1, 2012 at 12:57 PM, Alan Gutierrez<a...@prettyrobots.com> wrote:
>> On Fri, Jun 01, 2012 at 12:42:42PM -0700, Martin Wawrusch wrote:
>>>>>>> On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee<seijisam...@gmail.com>
>>>>>>> wrote:
>>>>>>>> Due the great expectation around node.js, libs and functions grow up
>>>>>>>> without control.
>>>>>>>> Nowadays we have a lot of "requires" and we need to memorize a lot of
>>>>>>>> names (fs, path, vm, ...); with time, we'll spend more and more time
>>>>>>>> reading
>>>>>>>> documentation :-(
>>>>>>>> My proposal is incorporate the mechanism of "register" the module,
>>>> for
>>>>>>>> example, phpjs library could register the function "isset" into
>>>>>>>> "utils", and
>>>>>>>> "abs" function into "math"
>>> On Fri, Jun 1, 2012 at 12:39 PM, Joshua Holbrook<josh.holbr...@gmail.com>wrote:
>>>> -1 as I like my modules exactly as they are.
>>>> --Josh
>>> -1 as well. Thank you Josh.
>> -1
>> Perl has this, a default export. You'll need a switch to say that you don't want
>> the default exports. Then you're going to need a way to remap the default
>> exports. Pretty soon you're going to have Perl.
>> Actually, I am you're more likely to devolve into PHP, a global namespace full
>> of suprises.
A similar idea was considered by Ryan a few years ago. I think it looked like this
import('modulename')
All the exports are dumped by name in to the scope. There was also some copy-on-write isolate stuff in there if i remember correctly.
It was scrapped as a bad idea for a lot of the reasons people have already mentioned. Also, the `module.exports = function () {}` pattern has become pervasive and would be really hacky to get right with this kind of feature.
Modules are done. node.js is at a stage now where certain new ideas aren't welcome like they were a few years ago. That's just how projects evolve, some things solidify and in order to make progress elsewhere we have to reject a lot of alternative ideas.
-Mikeal
On Jun 8, 2012, at June 8, 20128:38 AM, Seiji Sam Lee wrote:
> El 01/06/12 21:59, Isaac Schlueter escribió:
>> No, we're not going to do this. The module system is finished. It
>> won't be changing except for critical bugs.
>> On Fri, Jun 1, 2012 at 12:57 PM, Alan Gutierrez<a...@prettyrobots.com> wrote:
>>> On Fri, Jun 01, 2012 at 12:42:42PM -0700, Martin Wawrusch wrote:
>>>>>>>> On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee<seijisam...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> Due the great expectation around node.js, libs and functions grow up
>>>>>>>>> without control.
>>>>>>>>> Nowadays we have a lot of "requires" and we need to memorize a lot of
>>>>>>>>> names (fs, path, vm, ...); with time, we'll spend more and more time
>>>>>>>>> reading
>>>>>>>>> documentation :-(
>>>>>>>>> My proposal is incorporate the mechanism of "register" the module,
>>>>> for
>>>>>>>>> example, phpjs library could register the function "isset" into
>>>>>>>>> "utils", and
>>>>>>>>> "abs" function into "math"
>>>> On Fri, Jun 1, 2012 at 12:39 PM, Joshua Holbrook<josh.holbr...@gmail.com>wrote:
>>>>> -1 as I like my modules exactly as they are.
>>>>> --Josh
>>>> -1 as well. Thank you Josh.
>>> -1
>>> Perl has this, a default export. You'll need a switch to say that you don't want
>>> the default exports. Then you're going to need a way to remap the default
>>> exports. Pretty soon you're going to have Perl.
>>> Actually, I am you're more likely to devolve into PHP, a global namespace full
>>> of suprises.
>>> --
>>> Alan Gutierrez - @bigeasy
>>> --
>>> Job Board: http://jobs.nodejs.org/ >>> Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscribe@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en > But is possible to develop a module called "namespace" to allow namespaces and a hierarchy of them. It could be a parallel developing.
