Search Results: "marv"

12 March 2006

Benjamin Mako Hill: Remembering Push Singh

I haven't blogged recently and have been somewhat quiet and out of touch over the last few weeks more generally. I've certainly been busy but have also been trying to find words to describe the recent death of my friend and colleague, Push Singh. Push was a next-door neighbor at the Media Lab, an academic neighbor in the Electronic Publishing research group, and a neighbor in my building at home. If you've come to parties at the Acetarium, chances are you met him. Push was an up-and-coming AI researcher and something of a protege of Marvin Minsky. He had recently accepted an appointment to the MIT Faculty starting next year. His loss has come as quite a shock to everyone, to say the very least. Last Thursday was the last of several organized memorial services for Push and it now seems that its time for those of us effected by his death to get back to our lives. Rather than poorly summarizing Push and his impact on me here, I can point you some of the things that I and others said about him on a wiki page we have created to collect remembrances and in the obituary published in MIT Tech Talk. Push will be missed and I will continue to mourn his loss.

22 January 2006

Miguel Gea: My firt time.

Uau!!!
It was marvelous, fant stic... I was up and down touching here and there... ufff... I was really nervous, impatient. I ask all I must do. Yes, I know I must no to ask and try myself. But, you can understand me. It's my first time I have a bug on a package! XD

15 January 2006

Matthew Palmer: Evolution vs Revolution

To rewrite, or not to rewrite, that is the question. If there's one thing programmers seem to love doing, it's rewriting a piece of software from scratch. Which is funny, because "the industry" spends a lot of time bemoaning duplication of effort and generally touting "reusability" and "component-based software development". Joel on Software has a fairly good treatise on why rewriting software, in general, is a Bad Thing. I may not agree with him all the time, Joel is always worth a read, and I certainly can't fault his reasoning on this issue. My primary experience with rewriting software, as with most things software-related, is in the Free Software world. Although I've been involved in (or led) rewrites of proprietary software in the past, I've seen a lot more "let's rewrite it all" death-marches in FOSS. While I wouldn't characterise them universally as "failures", they don't seem to have the beneficial effect the authors were probably hoping for. What does seem to happen, in these FOSS projects, is that the developers squirrel themselves away in their backyard labs, using the latest and greatest in software engineering processes and tools, to produce... the same end result. (If you produce something totally different, it's not a rewrite, it's a new piece of software that does much the same things as the old one). When I say "the same end result", I mean exactly that -- it does the same thing, the code is still subject to coderot over time, and so on. It doesn't seem like much useful output has been produced. So why do we do it? Joel gives some good reasons (and why they're not such good reasons). Rewrites always take a very, very long time to do. It's in their nature. They're also very demoralising -- you're not really creating anything new, you're just recreating existing functionality. In the beginning, though, it's amazingly exciting -- a whole new world of bugfree code, an engineering marvel, something for the annals of software history. But several months later, as your new code is becoming cruftier by the day, and you're just duplicating functionality that already exists, you get bored. And boredom is the death knell of FOSS projects. I presume that this excitement-fading-to-boredom progression is why everyone starts rewrites, but they're often abandoned (or, at least, take a lot longer to complete than estimated). I'd make a comparison to that favourite target of unfair comparisons, marriage, but I know my wife reads my blog, so I won't. <grin>. This boredom factor is what has affected the python-appserver backed rewrite of IRM (from php3-style PHP). I took on maintenance of the existing PHP codebase over a year ago, and the rewrite had been in progress for a while at that point. IRM now has a bunch of useful new features, and there still isn't any indication of a useable tarball emerging from the rewrite. A rewrite in progress is a terrible thing. It tends to make people wary of working on the existing codebase, if it's going to be a deadend. Without something to work on, they'll tend to wander off to other projects. However, sometimes (due to existing deployments), users will work on the deadend. If the developers have been more-or-less neglecting the existing codebase while they take on their glorious rewrite, then the rest of the world is going to have been playing with and tweaking the existing code, adding their own improvements and modifications. The result of this, when the new rewrite finally releases, is that there's great wodges of third-party code that's incompatible with the rewrite, and a large chunk of your userbase says "stuff it" and sticks with what they know. This is what looks like happening in the world of SysCP. A few days ago, I found out that they're planning on doing a rewrite from the functional-spaghetti-PHP of the current version to the cult-of-MVC-PHP. This is nice, but their current estimate is of a first RC release in February. I take this estimate with a boulder of salt -- for the full collection of usual reasons (boredom, real life, overoptimism, etc). The fact that there's not a huge amount of movement on the commit log doesn't inspire confidence, either, and despite early claims of a massive development team, only one person has been committing recently. In the meantime, I'm tasked with adding a number of small features to the current SysCP codebase, which we need for work. When the rewrite comes out, it's highly unlikely that there will be a business case for rewriting my features for the new code, and it's not likely that the features we need will make it into core. So, SysCP will probably fork -- the old, featureful, crufty codebase, vs the new, shiny codebase. If there's sufficient new features to warrant an upgrade, we'll take the plunge, but what SysCP does now is very close to what we want, so it'll take a fair amount of shiny! to get us to move. This is a general issue of software development in FOSS -- if you take your eye off the ball, for any reason, someone else will probably pick it up and run with it. Your rewrite will be a completely new project, and you'll get some of the users and the fork of your old codebase will continue to live on in another guise. Let's face it, though -- your code is going to accumulate cruft. Over time, it morphs into this bletcherous pile of huge functions, multi-purpose classes, and reams and reams of bug reports. How do you deal with this cruft? Surely at some point it's easier just to throw it out and start again? Reality says no. Joel gave the key advice in the article linked above (go read it if you haven't already -- seriously), and it's strongly hinted in my article title. Don't revolt; instead, evolve your codebase. Tweak it, evolve it, move it slowly (and compatibly) towards your utopian ideal of perfect code. You won't get there, but you'll almost certainly get closer by gradual and continuous improvement than you would be going back to the start line and walking in a different direction. There's one big question that's nagging at me, though -- what happens when you want to switch languages? I'm loving Ruby on Rails at the moment, and so are several other people at work, but we've got (both personally and professionally) huge swathes of code in PHP (and other second-rate languages) that needs to be dealt with. It's a lot harder to evolve code into a different language than apply a gradual degunking. I have a number of ideas on this point, but I'd love to hear your ideas too. In a few months, I'll have a lot better idea of what works and what doesn't in massive PHP to Rails conversions, and I'm sure everyone out there in the blogosphere will hear about them in due time.

12 January 2006

Matthew Palmer: Xinerama is the r0x0r

I was motivated, this morning, to look into whether my laptop chipset (Intel 915GM, for anyone interested) could do this funky multihead thing. Much to my surprise, it was (a) possible, (b) quite simple, and (c) incredibly useful. I now have a 15" Dell LCD screen on a cardboard box behind my laptop docking station. What is it useful for, you ask? Let me count the ways (with the help of the <ol> tag, of course):
  1. I've gotten a couple of PDF versions of my current "must always have with me" technical books (Programming Ruby and Agile Web Development With Rails, since you didn't ask), and now I can stick them on the other monitor to refer to while I'm coding.
  2. I can stick my xchat window up on the external monitor, so I can quickly glance at what's going on without having to touch anything. With the ability to stick a window on all desktops, I can have xchat no matter where I go!
  3. If I want to show somebody else something, it's handy to be able to push it up onto the top screen so they can more easily see it without having to crane down at my laptop screen (plus, if they go "what about <smudge>that?</smudge>", it's work's monitor that's getting grotted on, not my laptop screen that I have to stare at for 10+ hours a day).
Since I rarely (read: never unless I'm forced to) reboot my machine, instead relying on the magical marvels of sleep/hibernate, I did have one major concern with this multihead thing -- when I'm out-and-about, obviously I'm not going to have my external monitor with me, so how do I view things that are up on the other screen (either because I left them there when I was in the office, or because the window autoplacer stuck them there)? It turns out to be a fairly trivial and rarely noticed problem (except when I shove the mouse at the top of the screen to hit a button and my mouse disappears off into the wilderness). The answer to the invisible window problem is trivial -- I wave my mouse around where I can't see it until the window I want is highlighted in the miniview, then hit Alt-M to lasso it, and drag the little beastie into the light. Much easier than trying to guess where the title bar is to bring it down. In the interests of sharing the love (and having a record of what I did for next time), here is the sum total of what I had to add to my xorg.conf to make it all work on Ubuntu Breezy (along with some comments to make it easier to understand what's happening):
Section "ServerFlags"
        Option  "DefaultServerLayout" "double"
        #Option "DefaultServerLayout" "Default Layout"
EndSection
# This Device section is effectively identical to the one for the
# primary screen, with the addition of the Screen 1 parameter to
# select the alternate display device.
Section "Device"
        Identifier      "vgaout"
        Driver          "i810"
        BusID           "PCI:0:2:0"
        Option          "MonitorLayout" "CRT"
        Screen          1
        Option          "DDC" "false"
EndSection
# external display
Section "Monitor"
        Identifier      "generic"
        # I kept all these loose because most monitors support
        # autodetection.
        HorizSync       27 - 96
        VertRefresh     50 - 110
        Option "DPMS"
EndSection
Section "Screen"
        Identifier      "external"
        Device          "vgaout"
        Monitor         "generic"
        DefaultDepth    24
        SubSection "Display"
                Depth           24
                # I'd have added many more modes here, but
                # the amazingly crufty external LCD I'm using
                # only supports 1024x768.
                Modes           "1024x768"
        EndSubSection
EndSection
# xinerama layout
Section "ServerLayout"
        Identifier      "double"
        # The 0 0 (I think) identifies this as the "root" monitor
        Screen          "Default Screen" 0 0
        # You can also use Below, LeftOf, or RightOf to position
        # your shiny subscreen
        Screen          "external" Above "Default Screen"
        InputDevice     "Generic Keyboard"
        InputDevice     "Configured Mouse"
        # Never, ever forget this option.  You'll get laughed at
        Option          "Xinerama" "true"
EndSection

8 January 2006

Jonathan McDowell: On previous posts.

I suppose I should really update the status of various things I've mentioned in the past. xsm: I gave up and just added the appropriate magic to my xinitrc to start my common apps. I tried fluxbox again for a while, but although it could cope with one of each app it didn't seem to do too well with half a dozen xterms. Maybe with a little effort it could, but xinitrc does the trick well enough. RSS reader: I've settled on Liferea for the moment, with my evil lj-openid-fetch script fetching LJ posts for me. Netgear DG834G: I wrote up a page of info about this, just to have something static. Unfortunately it seems that the Marvell 88E6060 switch chip used only supports port based vlans, which I think means you can split the switch up so that you can have completely separate ports, but doesn't allow the creation of a wan port on the device. This is a shame, as it means I can't use it to handle my setup unaided (I need wan, lan, wireless + adsl ports). X11 programming: I ended up using SDL, which gave me a framebuffer to play with. I suspect I could easily convert the code to run on /dev/fb0 directly, which is nice, though I should look at how to do the same with X again at some point.

21 December 2005

David Moreno Garza: Love storm

I couldn't be more happy. This was a great, marvelous weekend:
 
    
 
Ana arrived last Thrusday night. On Friday we went to the downtown area at midday and afternoon. By night, we went to my end of the year workdudes dinner. On Saturday, we went with Tacvbo to Celaya and returned quite late, by midnight, to a friend's party. On Sunday we enjoyed the whole day by doing nothing :) and in the afternoon, we went with Polo and Eunice to get some Christmas presents to a mall. At night, we went to Cuernavaca where her parents are on a nice resort. Yesterday, Monday, we (her parents, sister and me) went to Acapulco and at night, return to Cuernavaca. Today, at morning, I came back to Mexico City to work.
 
I just can't wait to move to Venezuela.
 

20 December 2005

Wichert Akkerman: Implementing a testing status for trac

As many other people, I have become addicted to the trac system. After having used it for a few personal projects and deciding that it really is cool technology and talking about it with a few other people I switched Plone from its old issue tracker to trac and the result has been marvelous: it runs smoothly with over 5000 tickets and produces great overviews such as this 2.1.x release issue status overview. However for our projects at Amaze we are missing an essential feature: the ability to have a testing status for issues. This is a seperate step between active and resolved where an issue should be resolved, but has not been certified to be resolved by full testing, which is (should) be done by other people. To support this I created a patch which added a new ticket status called 'testing', modified the milestone and roadmap to show that tickets in a testing status seperately and updated the unittests to reflect the new possible actions. screenshot of trac roadmap view with testing status In order to make this easier to use I also modified the trac-post-commit subversion hook: I added a --testing parameter which tells the hook to mark an issue as testing instead of fixed. The default is set to fixed in order to preserve backwards compability, and since I suspect that most trac installs are for small projects which do not have a need for a seperate testing status. If you are curious: you can download trac testing patch from here or look at trac ticket 2511. The patch is based on the current svn trunk for trac. Update: seems the trac folks already closed the issue since there is a larged project in progress which provides the same functionality (and more). However since there is no assigned milestone or estimate when it might be merged, so until then I still consider this patch to be a very useful addition to trac.

29 November 2005

Aigars Mahinovs: Fotography is dangrerouse


Fotography is dangrerouse
Originally uploaded by aigarius.
After a bit of sleep, a bit of rest and several hours of workign trough all the 293 photographs taken during the 3 days of AnimeFest, I must finally write something about the last day.
The last day of the fest (sunday) was easily the best. The morning was a bit disapointing as the planned special showing of Steamboy did not happen and the korean Hammerboy was quite boring for anyone over the age of 7. Many had a good nap.
Everything went wild when the second part of Hellsing series was supposed to start. Previouse day the showing stopped on 6th episode, so when after the intro we saw that the 10th episodes starts, all started shouting so loud that even mechanics understood that something was wrong. For about 5 minutes they seemed to wander aimlessly around the menu of the DVD. The mechanics were in a sealed room, so they couldn't hear us and we couldn't quite go to them either. I had a fun moment running up to the screen and showing with my hand which button should the mechanic press on the screen. I mimiced both pushing the button like it was a touchscreen and a also runned around trying to "drag" the cursor across the screen. It looked very fun to the audience. In the end it turned out that the DVD was doublesided and had to be turned around, but it took almost ten times of starting the 10th episode and around a half an hour of time. Thankfully the rest of days schedule could be pressed a bit to compensate.
Hellsing itself was just wonderfull, I hope they will decide to make a sequel soon and that they'll make it well.
Next up was Millenium Actress. I did not expect much realism from the creators of Prefect Blue, but I was so wrong. The movie is simply great - it is fun, has great story and ingeniose way to tell that story. Simply a marvel.
The final ceremony of the festival started with a concert of a local group of two Latvian girls singing Japaniese pop songs - "Tokio Dolls". Nice voices, very good choreography and reasonable lights - all in all a good show. In the conclusion there was Ghost in the Shell 2: Innocence. This is my second time trying to get it. I loved the first film. I liked the first season of series. But this film and the second season of series is just ... too smart? The first movie was a good combination of action, elegance, politics and wisdom. In the second part only distilled wisdom remains - typical scene is three people standing in a room for 20 minutes speaking loosely related citations of philosofers to each other. After a sleepless night of debugging gphoto, I slept well there.

All in all this festival was a fonderful event - lots of good friends came, lots of cosplays were seen, lots of anime was watched, a bit of go was played, a bit of buffed weapon fighting was done, a lot of good photos taken. I look forward to next animefest sometime next year. In the meanwhile I will try to sort out the few best pictures and post them to my flickr album during the week.

Aigars Mahinovs: Photography is dangerousAfter a bit of sleep,...


Photography is dangerous
After a bit of sleep, a bit of rest and several hours of working trough all the 293 photographs taken during the 3 days of AnimeFest, I must finally write something about the last day.
The last day of the fest (Sunday) was easily the best. The morning was a bit disapointing as the planned special showing of Steamboy did not happen and the Korean Hammerboy was quite boring for anyone over the age of 7. Many had a good nap.
Everything went wild when the second part of Hellsing series was supposed to start. Previous day the showing stopped on 6th episode, so when after the intro we saw that the 10th episodes starts, all started shouting so loud that even mechanics understood that something was wrong. For about 5 minutes they seemed to wander aimlessly around the menu of the DVD. The mechanics were in a sealed room, so they couldn't hear us and we couldn't quite go to them either. I had a fun moment running up to the screen and showing with my hand which button should the mechanic press on the screen. I mimicked both pushing the button like it was a touchscreen and a also ran around trying to "drag" the cursor across the screen. It looked very fun to the audience. In the end it turned out that the DVD was doublesided and had to be turned around, but it took almost ten times of starting the 10th episode and around a half an hour of time. Thankfully the rest of days schedule could be pressed a bit to compensate.
Hellsing itself was just wonderfull, I hope they will decide to make a sequel soon and that they'll make it well.
Next up was Millennium Actress. I did not expect much realism from the creators of Prefect Blue, but I was so wrong. The movie is simply great - it is fun, has great story and ingenious way to tell that story. Simply a marvel.
The final ceremony of the festival started with a concert of a local group of two Latvian girls singing Japanese pop songs - "Tokio Dolls". Nice voices, very good choreography and reasonable lights - all in all a good show. In the conclusion there was Ghost in the Shell 2: Innocence. This is my second time trying to get it. I loved the first film. I liked the first season of series. But this film and the second season of series is just ... too smart? The first movie was a good combination of action, elegance, politics and wisdom. In the second part only distilled wisdom remains - typical scene is three people standing in a room for 20 minutes speaking loosely related citations of philosophers to each other. After a sleepless night of debugging gphoto, I slept well there.

All in all this festival was a wonderful event - lots of good friends came, lots of cosplays were seen, lots of anime was watched, a bit of go was played, a bit of buffed weapon fighting was done, a lot of good photos taken. I look forward to next animefest sometime next year. In the meanwhile I will try to sort out the few best pictures and post them to my flickr album during the week.

17 November 2005

Ross Burton: Express Tosh

If I had known that the Daily Express front page yesterday was just so damn good I'd have bought a copy myself. With a paper bag on my head, obviously. Instead I have to make do with a small image. Diana Fund Pays Out To Gypsies And Asylum Seekers I'm still not sure that this isn't some great spoof or prank. Maybe someone broke in and changed the front page just as it went to press? What do we have here: Marvellous stuff. I can only imagine the Express has taken to being a parody of itself... NP: Individuality, Rachelle Ferrell

Next.

Previous.