JavaScript Toolkit V1.1.0 Released 65
First time accepted submitter Mensa Babe writes "Oliver Morgan, the original author of the JavaScript Toolkit, or just 'The Toolkit' as it is known in the JavaScript community, has just announced the release of the long awaited version 1.1.0, with better documentation and added function support. Quoting the project documentation: '[JavaScript] Toolkit offers a large number of integrated methods and utilities to help enrich the javascript object library. Javascript was built originally for browsers and as such lacks a large number of data utility methods with are seen in languages such as Python and Ruby. However times have changed and JavaScript is being used more and more in backend platforms. JS Toolkit aims to bridge that gap and provide everyone a modern developer needs to produce fast, secure and tidy code quick and easily.' The Toolkit fully supports ECMAScript 5 and runs on the most important virtual machines that we have today, including Node.JS, V8, Rhino, RingoJS, and many others. It continues to be actively developed."
Re:feh, try phpjs (Score:5, Informative)
They have the vast majority of core PHP functions implemented in JavaScript.
I just threw up in my mouth.
A little clarity.... (Score:5, Informative)
I created the toolkit, I never spoke with this timothy and never asked for it to be published here? I'm not particularly happy with it being done either given that i've been working on it for several days and there is a load of issues which need fixing before I'd even want it considered let alone used in production.
So let me clarify.
- It's not based off any existing language or framework in particular. I'm taking what I find useful from the different ones available. The API is not set in stone yet there are still a number of large changes I still plan to make.
- I haven't and will never condone this as official in anyway. It's something I want to continue to use throughout MY projects and would find help/contribution helpful so i made it open-source. I have never come across Slashdot before - ever. And why on earth would I want to run a "PR campaign" for it anyway? I have much better things to do with my life.
- In short response to all your pointless negativity:
1) It's not long awaited - perhaps by me but I've never thought anyone else really cared.
2) It's never been known as "The Toolkit" I've never called it that so I don't know where the JS Community got the name from.
3) It has a handful of PHP functions, most of functions came from Ruby and Underscore.JS.
4) Every O-S project starts somewhere, U.JS had a humble beginning - so has mine. They are considerably different in their goals and current implementation. I strongly advise you know the difference before choosing or listening to the dismissive people in this thread.
And a final thanks to those of you who kindly took the time out of your day to come send me hate-mail.
Peace :) x
Re:A little clarity.... (Score:3, Informative)
Haha I can't believe how spiteful this place is. I don't understand why it's so impossible for you guys to just ignore something you think should be ignored. Or do you have to make sure that everyone who wants to make up their own mind should ignore it too.
Just incase you haven't got it already... I had a need for an ECMA5 targeted toolkit for my Node.JS development that provided all the useful goodness Ruby, Python and PHP had been given over the years which JS had never really had a need for (living mainly in the cave of the browser). A simple comparison:
Underscore.JS:
_.map([1,2,3], function(a, b) { return a * b });
JS Toolkit:
[1,2,3].map(function(a, b) { return a * b });
I didn't care about intruding the object namespace because ECMA5 introduced property descriptors which allowed me to make any extension methods non-enumerable and essentially no different to how other native methods were implemented. So with that in mind I created something that made more sense to me than underscore.js, as why should I have to use an underscore at all? Trust me if there were something that suited my needs I would have used and contributed to that instead.
I'm surprised it managed to find it's way here so quickly. It is still an immature project but perfectly useable with a few small bugs i'm working my hardest to iron out. It wasn't published by me so clearly there was someone who thought it worth showing to the world. I'm grateful to that person's support and I will do my best to see it through.