… and I have no idea what this means for MySQL, so I guess this is a short one.
Full press release on Oracle.com.
April 20, 2009
April 14, 2009
Book Review: Here Comes Everybody
I recently read Clay Shirky’s book Here Comes Everybody: The Power of Organizing Without Organizations. It gives us a few more examples about how the internet is changing the world:
We are used to a world where little things happen for love and big things happen for money. Love motivates people to bake a cake and money motivates people to make an encyclopedia. Now, though, we can do big things for love.
as well as explains why visitor interaction only sometimes succeeds:
Every webpage is a latent community. Each page collects the attention of people interested in its contents, and those people might well be interested in conversing with one another, too. In almost all cases the community will remain latent, either because the potential ties are too weak (any two users of Google are not likely to have much else in common) or because the people looking at the page are separated by too wide a gulf of time, and so on. But things like the comments section on Flickr allow those people who do want to activate otherwise-latent groups to at least try it. The basic question “How did you do that?” seems like a simple request for a transfer of information, but when it takes place out in public, it is also a spur to such communities of practice, bridging the former gap between publishing and conversation.
Whether you plan to have a small community or a large one, the focus is on making it easy and on trying to understand where your visitors will want interaction. If you’re interested in a web community or just want a little bit of occasional interaction with visitors, Here Comes Everybody will probably help you figure out how to do just that.
Just one last tidbit that I found interesting:
In 1991 Richard Gabriel, a software engineer at Sun Microsystems, wrote an essay that included a section called “Worse Is Better,” describing this effect. He contrasted two programming languages, one elegant but complex versus another that was awkward but simple. The belief at the time was that the elegant solution would eventually triumph; Gabriel instead predicted, correctly, that the language that was simpler would spread faster, and as a result, more people would come to care about improving the simple language than improving the complex one. The early successes of a simple model created exactly the incentives (attention, the desire to see your work spread) needed to create serious improvements.
April 13, 2009
goto in PHP
I had a class in middle school where we did a little bit of programming. I don’t remember much about it, and the programs we wrote probably weren’t more than 25 lines. The one thing I do remember is that we used gotos. No object-oriented programming, not even functional programming.
The reason I mention this now is that I was talking one of my colleagues today, arguing PHP’s case, as he supported Python, and I mentioned that as of PHP 5.3, PHP now has a goto operator. He was really hoping that was a joke, and now probably takes the language significantly less seriously.
There are plenty of criticisms of goto, not the least important of which is Edsger Dijkstra’s Go To Statement Considered Harmful. The crux of most arguments, though, seems to be that goto statements are not inherently semantic and as such aren’t appropriate for modern structured languages.
I’m not using PHP 5.3 yet, so I can’t say that I’ve used goto already, but I don’t see why having a goto operator can make a language intrinsicly bad. There’s some code that looks gacky however you try to write it, and in some cases a simple goto may actually make it easier to read and understand, even if it also has its share of bad uses.
Looking over some comments on goto use, one of the concerns I find most interesting is that of the kitchen sink mentality. Personally, I enjoy PHP because I can have one language and use it for procedural, functional, or object-oriented code–whatever I feel is most appropriate at the time. But, yes, this can also lead to poor coding standards and huge misunderstandings between, say two developers who are both writing code in PHP but with two completely different programming paradigms.
How well a language like this works for you depends on how you use it, and I think I can use it effectively, but if others prefer to work with just one subset at a time–that’s totally fine too. Anyhow, I plan to take a look this summer at this awe-inspiring Python that everyone around me keeps evangelizing (except for Jared, who loves Rails), so who knows? Maybe I’ll be enlightened then.
Faculty Lunch: Dr. J Strother Moore
On Friday, WICS hosted a faculty lunch with our department chair, Dr. J Strother Moore. I was a little late coming from class, but fortunately the part I missed out on was about backpacking, rock-climbing, and fishing, none of which interest me too much.
Afterwards, he talked quite a bit about his main project as chair–which is to get a new building for our Computer Science department. Right now our faculty is spread across 6 different buildings, not all close to each other, and having everyone together would be great for sharing ideas, working on research, and just building a community. I frequently hang out in the basement where the ACM and WICS offices are, but it’s not convenient for most other people to just come by, and yes, it does smell a little funny. Unfortunately, the date for starting the new building still isn’t set, and it would take four years or so to complete, so it definitely won’t be up while I’m still here. I’m still not completely sure it’s necessary to take on that cost of not having a central hub for that amount of time, but the ideas Moore presented of our new building sure did sound lovely.
Another interesting idea he had was to have senior faculty teach the lower-level classes, while the newer faculty who are doing more research would be teaching the upper level classes. Personally, I think that’s a great idea since there’s nothing that turns more students off of certain classes than not having a teacher who really has teaching experience. I agree with this completely, as well as his idea to have larger class sizes using tools such as iClicker for extra interaction. My one concern with his ideas here was that of reducing reliance on lecturers. It really makes sense financially since the funds for lecturers fluctuate every year, but Mike Scott has been doing a great job of teaching CS 307 for about a decade now, and I don’t know if anyone else could fill that role so well.
Anyhow, Moore is teaching CS 313k occassionally and I don’t have him next semester, so I may never get to see how he is as a professor, but it certainly was enjoyable to have our group sit down to lunch with him and learn a bit more about what’s going on with the department.
Damn Spammers
In the past few days, I’ve received about 25 emails from my blog to moderate spam comments–all obviously from the same idiot spambot. So I can understand now why the default option is set to send email notifications to the blog administrator. Even if the comments aren’t posted without moderation (by default), that administrator still needs to know what is going on to find some other method to keep these spam comments from getting in their way.
Since Akismet (I can never spell that right) is built into WordPress, the first thing I did was to activate it and see how that worked. Fortunately, on the Akismet configuration page is an option to “Automatically discard spam comments on posts older than a month.” That’s wonderful! The post that that bot keeps trying to comment on is over two months old. Why didn’t they make this option more obvious so I could’ve signed up sooner? Well, I can’t really complain. I just have to sit back now and make sure this works….
Update: it works! So many spam comments caught. Akismet, I love you!