a brush of slashdot


I have slept about 2 hours in the last 36, but the pre-beta release of spaces is almost done. In the meantime, I've been so consumed by it that I mostly stopped checking news, stats, technorati and everything else. And lo and behold, what happened? Yesterday there was, predictably, a thread on the Chandler 0.1 release, and two people made comments pointing to spaces (here and here) with the (also predictable) jump in downloads. It took a while to find (I first knew about it because of an email) because the first comment, which appears close to the beginning and so would generate the most hits, has the URL for dynamicobjects but not a link, so it wasn't showing up on the referrers list. To the people who posted the comments, thanks! :-)

Btw, the first comment on Chandler on the slashdot thread is funny. It reads:

already emulating Outlook well

Since I just managed to crash it.

No virus propagation yet though, it is only 0.1 I suppose.

The perils of native code... not that Java will never ever crash, it just won't be a common occurrence and would normally result from a bug in the JVM.

Categories: clevercactus
Posted by diego on April 23 2003 at 4:32 PM
Comments (please see the comments & trackback policy).

I haven't tried it out myself, but I just thought I'd comment that Chandler is written in Python, not "native code".

Posted by: Avdi at April 23, 2003 5:38 PM

Hi Avdi,

Actually, it's not written in Python. Python is used only as higher level "glue" code on top of a WxWindows/WxPython framework, and the WxWindows framework is written in C/C++. Additionally, they are planning to use other components, such Mozilla, that are native code in all or part. More info here: http://www.osafoundation.org/technology.htm

d

Posted by: Diego at April 23, 2003 6:04 PM

I dunno, where I come from that's called "writing it in Python". WxWindows and WxPython are already written. If I write a Ruby application using the FXRuby toolkit (Ruby bindings to the C++ FOX toolkit) I don't say I've written it in C++. And if I then plugged in Mozilla components using the Ruby XPCOM bindings I still wouldn't say it's written in C/C++, even if that's what XPCOM is written in.

I always thought apps were considered to be "written in" whatever language the *application specific* functionality is written in, not the language their foundation libraries were written in. In the sense that you are using, every app is written in native code, since Python is written in C, Perl is written in C, all the library bindings are written in C or C++, etc.

Posted by: Avdi at July 9, 2003 1:59 PM

Copyright © Diego Doval 2002-2007.
Powered by
Movable Type 3.35