Slashdot Mirror
The Year in Scripting Languages
Mitchell writes "People from several language communities came together to create a
joint year-in-review
for Lua, Perl, Python, Ruby, and Tcl."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
It does have a large market share, ya know.
From the website: "PerlQt-3 is Ashley Winters' full featured object oriented interface to Trolltech's C++ Qt toolkit v3.0. It is based on the SMOKE library, a language independent low-level wrapper generated from Qt headers by Richard Dale's kalyptus thanks to David Faure's module".
Another thing that's nice is that "All Qt classes are accessed through the prefix Qt::, which replaces the initial Q of Qt classes. When browsing the Qt documentation, you simply need to change the name of classes so that QFoo reads Qt::Foo". So, essentialy the API is similar to QT with reduces the learning curve quite a bit.
Mecworks BLOG
Not really ports to the platform itself, but great productivity boosters regardless. I've used VisualPython with VS.NET 1.0 and it rocks.
... PHP?
This report shows how it is growing.
I hope Python integrates wxPython. With Python + wxPython, it can take on things like Java, Mono, and .Net.
I originally learned Tcl/Tk about 4 years ago, but stopped using it once my job no longer required it. I took a joke course on scripting languages last fall, and the professor was in love with Tcl/Tk, but seeing as how no one cared, we learned Perl/Tk instead. The Tk widgets are the more useful part of it...Tcl was OK, but it frankly shocked me that it was still being developed actively. Anyone used the new version and can vouch for the speed boost? It was so gawd awful slow before that I couldn't bear it.
http://thechubbyferret.net - Ferret pictures and informative links.
I do! a very large project, btw.
and please do not put your own opionion as the opinion of the masses.
People who think in commands and strings choose TCL!
As a wxPython user I can say that, for a good reason, wxPython should not be part of Python.
It's a complete bitch to debug your programs when the wxWindows library goes berserk, and it does, way too often.
Btw, I think there should be no GUI toolkit at all in Python as default.
Python is an amazing scripting language--I'm just wondering when gcc will be able to compile it! :) (Yes, I know about psyco.) For the next year, one thing I would like to see is either Python switching to wxPython for GUI stuff, or improving tkinter so that it isn't so...1996ish. (On the other hand, wxPython isn't quite as intuitive as pyQT, but isn't hampered by the licensing issue on the Windows side of things.) Also, what are the plans for Python 3+? Is there any site listing future plans, apart from the 2.3 release?
:Peter
Incidentally, for those 5 years, NBC has been using Tcl in mission critical, real time applications to stream video to affiliates across the country.
I've been using tDOM lately, a Tcl interface to the DOM. It is, quite simply, the fastest XML parser I have found.
-- Don't Tase me, bro!
Less is more !
awk essential for pipe work.
you'll see it here used like
wget -O - http://domain/info.html | awk -f proc.awk | mysql -u news newsdb
rc shell and it's unix implmentation
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
Earlier this year I had to use LUA in a project that I was working on, and I must admit that it was a pretty interesting language. I had to use it primarly for scipting: writing generic function calls and tailoring formatted "pages" of code to be submitted into a database (one might think of this as being similar to web pages, though it a little bit different than that). To me the language seemed to be very versatile, and it had some nifty features as well as very simplistic syntax. To someone familiar with other languages like Perl or Python, I guess it might not seem so nifty, but I appreciated its simplicity because it took me less than an hour to learn as much of the language as I needed for the project.
DOS scripting is no longer Microsoft's preferred scripting feature.
Windows batch files are a holdover from DOS. DOS as we know it originally ran on IBM PCs and early descendants, which were cheap, slow, 16-bit, underfeatured toy computers. At that same time, Unix was running on expensive, fast, 32-bit, featurful computers. Before that, Unix did run on 16-bit computers (various submodels of PDP-11), but PDP-11s were certainly more expensive and more featureful than 8086- and 80286-based PCs, and PDPs were most definitely not toys.
The point? Unix scripting was better than DOS scripting. Windows evolved from DOS, and as a result it got DOS's scripting capabilities. That evolution is only now reaching the stage where it can be said with any regularity that Windows is evolving from itself rather than from DOS. Win2K and (maybe) WinNT4 were the first incarnations of Windows with this property. It is a very slow process.
What we see now is Windows evolving its own scripting engines. I'm not savvy about some of these things, but I do know that there are VBScript or Windows Scripting Host for automating things in the OS, and VBA for scripting inside individual apps like Excel or Access. Granted, these are all based on VB, which is lacking when compared to Java or C++, but these are quite well-suited for scripting in a Windows environment.
Just yesterday, for example, I wrote a simple Windows script that renames files in a directory tree by doing regular expression search and replace. This clearly represents an improvement over the legacy DOS scripting capabilities.
Washington, DC: It's like Hollywood for ugly people.