Slashdot Mirror
JavaScript Toolkit V1.1.0 Released
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."
Is only a temporary fix for the fact that you bought the wrong size.
This will nicely complement my soon-to-be-released JS-LAPACK and JS-FDLIB packages.
The more Javascript the better as far as I'm concerned!
But I think it'd be nice if we just saw more dev activity in Prototype JS.
Since when is this known as "The Toolkit"? The lack of github followers and general references across the internet makes this claim suspect. Its History file only goes back a few days, so I wonder how this could possibly be "long-awaited."
has just announced the release of the long awaited version 1.1.0
My first thought was... by whom? The prior version, 1.0.0, was released on Aug 27, a week ago.
It continues to be actively developed.
By which we mean, he got back into it last month.
First time accepted submitter Mensa Babe...
Is an idiot.
I admit I haven't heard of this before but a quick glance through the documentation reveals nothing that any CS student couldn't knock out with a couple days work. Compared to the excellent Underscore.js (http://documentcloud.github.com/underscore/) this comes out as a damp squib. Am I missing something?
Okay, I've done some moderate JavaScript programming in the course of programming many websites and I've used most of the popular libraries out there. But I've never even heard of this JavaScript toolkit. A quick trip to the home page shows that it's trying to be yet another attempt at a JavaScript standard library. And not a very good one, either. A few helper libraries. Pfft!
If you really want a JS library that does damn near everything under the sun, check out php.js. They have the vast majority of core PHP functions implemented in JavaScript.
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
I was sad to discover that some code I'd recently written was perfectly readable and maintainable. I thought to myself "If people can easily understand and maintain this code, they'll think I'm some kind of n00b."
Thanks to judicious use of libraries like jquery and prototype.js, I'm happy to report that my code is both impossible to understand, difficult to extend, and an absolute nightmare to maintain. That's right, I'm now officially a "rock star" level programmer.
"The Toolkit" as us rock stars call it, now offers me the perfect opportunity to do away with those nasty simple library functions I've collected over the years. Things like string manipulation, for example, that were handled quickly and efficiently by a few simple easy-to-understand functions are now garbled up in yet another over-sized and bug ridden JS library.
My pages take longer to load and run slower than ever before! This is enterprise level code I'm pushing out here folks.
Here's a few hints to help you achieve the same level of greatness:
1) RAM is cheap, use as much as you can.
2) Forget about performance, if your code is too slow, upgrade. Computers get faster every year.
3) Arrays are for idiots who can't code. Import a collections framework for even the simplest of tasks. Need 10 integers to be manipulated by one function and then discarded? You can't go wrong with a thread safe hash table!
4) Load the library that has the function you want, even if you've already loaded a library with similar functionality. Like jquery's trim() function better than underscore.js? Import them both! Never mind that you only needed to use one function from each library or that any first-year CS student could write them in 10 minutes, you're a rock star. You use what you want.
5) Don't be afraid to re-invent the wheel. Other people are idiots, so assume that whatever you can hack together is automatically better. This especially applies to date and time functions.
So fellow rock stars (and future rock stars) ignore all of the negative comments in this discussion about "The Toolkit". Just because these n00b's can't comprehend its awesomeness dos not mean that it's not the perfect hammer for driving screws.
Required reading for internet skeptics
No? Well, shit.
If it looks like a duck, let's call it a moose.
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.
You think an "odd number" means "divisible by 3", which means you have a less-than-middle-school education in math. That's not a "humble beginning". You're simply not qualified for the task you've undertaken. For fuck's sake, you didn't even look at the wikipedia page on parity, apparently.
Please help metamoderate.
... for the people writing it. A useful learning experience. They can easily compare actual (PHP) and their 77th iteration/bug fix and with any luck get better at creating accurate code in the process.
I sure hope none of my pet projects ever make it to slashdot!
Though IMHO http://sugarjs.com/ looks better + have way more github followers.
...it's a fundamental misunderstanding of mathematics.
Please help metamoderate.