Tower chat shows calm before Java crash
685790
Transcripts of control tower  conversations with the pilots of a crashed Indonesian passenger  jet showed no adverse conditions as it prepared to land,  Australian newspapers reported on Wednesday.
420221
By Cinthia Ritchie, Anchorage Daily News, Alaska  Feb. 26--The cables were the problem.   Or wait! Maybe it was the RAM. Or the processors. Or ...
152107
Rather Dented Users of the popular Trillian instant messaging client need to update their software following the discovery of a serious security bug.â¦
200433
An enhanced multi-threaded syslogd, supporting reliable syslog over TCP and RFC 3195, writing to MySQL databases, fully configurable output formats (with great timestamps), ability to filter on anything, and on-the-wire message compression.   Hi all,  Rsyslog 3.11.2 has just been released. Now it has the ability to convert text files into syslog. This is done by the imfile plugin, which monitors text files. A new libdbi-based output plugin has been written. This adds six additional databases (including Firebird and Oracle) to the supported database set. Also contains small bug fixes. Version 3.11.2 is a recommended release for all version 3 users.  Doc for new Modules:    http://www.rsyslog.com/doc-omlibdbi.html    http://www.rsyslog.com/doc-imfile.html  Changelog:    http://www.rsyslog.com/Article175.phtml  Download:    http://www.rsyslog.com/Downloads-req-getit-lid-79.phtml  I hope this release is useful. As always, feedback is appreciated.  Best regards, Rainer Gerhards
768444
Great writeup from Tim Bray WRT Dynamic Java  ...  Here's the funny part.  Whats up with all the damn coffee in these pictures?  One can only come to the conclusion that caffeine makes you smart as hell!  caption: Coffee  caption: Coffee and Java  caption: Java and Coffee
658521
Your work computer just suffered a major meltdown. Maybe the operating system failed, or a virus crashed the hard drive.
731048
Asia's financial markets got off to a calm start to the week on Monday with investors waiting to hear from top central banks what to make of the turmoil that has kept markets on edge for weeks.
126013
On Dynamically Typed today, there's a new posting concerning the PHP Atom Server.
481653
I'm back, with a very interesting topic too!  Joel Spolsky, ex-Microsoft Manager and software engineering guru has a new essay, How Microsoft Lost the API War that is creating quite a big storm in the blogging communitiy.  Joel posits that the priests in the holy Temple of Microsoft have lost their way, because it has split into two factions, and the wrong faction is winning. One faction worships on the alter of backward compatibility, while the other is led by fervent priests who are proselytizing to raise up the new gods of .NET and Longhorn. Joel suggests that the new gods will cause the destruction of the holy Temple because Microsoft's great victories were built on the altar of keeping customers happy with backward compatibility. Furthermore the old gods of the Windows API continue to grow more grotesque and cruel with the passing of time, driving former worshipers into the arms of the friendlier gods of World Wide Web.  This story sounds extremely plausible. I must admit that i fit the profile of the developer who used to develop on the Window's API, is familiar with COM and Win32 who now develops mostly using PHP and Python. However I continue to develop and maintain Windows apps that keep our customers happy, and we still plan to develop new Windows apps. Some points:  Temple of the Blind? Firstly, Microsoft is still a compelling place to work for to people who feel that they can make a difference. The Temple continues to attract talented people with a Unix background. For example we have the recent hiring of Ward Cunningham, author of the Wiki.  Microsoft is still able to keep talented people like Raymond Chen, and others like him who continue to look after the Windows API, and Longhorn apparently will still give high priority to backward compatibility. Open sourcerers like Miguel Icaza are sufficiently attracted to the .NET vision to stake their careers on Mono. Longhorn and .NET are compelling technologies, so even if Win32 is not so cute anymore, M'soft is providing something that remains very attractive.  What i do see M'soft doing wrong is that they aren't disseminating the .NET runtime fast enough. It remains an optional install in XP Service Pack 2 for example. Also their IE dev team appears to be hog-tied due to political reasons; nevertheless IE remains good enough, particularly when I can embed IE as an activeX control, something I cannot do with Mozilla (AFAIK) - Update: I'm wrong.  Temple of the Spider?  Secondly, people don't merely use a web browser. They run the web browser in the OS.  So let me ask you, if you are using DreamWeaver or HomeSite or Photoshop or vi or emacs or Gimp, how many of you are willing to give it up for a java applet (or whatever your favorite technology is) running in your web-browser? Precisely.  Temple of the Abandoned?  Third, Joel makes the claim that developers are not developing to the Windows API. Well he could be right. But I bet a lot of them are still calling Win32.  If you are using a framework or IDE like Delphi or wxWindows (or .NET or VB) then you certainly are insulated from the Windows API, but that doesn't mean that you're not calling the Windows API all the time. I don't see Borland dropping their Windows version of Delphi at any point in time.   In fact, the fact that many developers are using some form of framework is a compelling argument for Microsoft to enhance the .NET framework to attract developers who are using other frameworks.  Today, not that many students learn x86 assembler, but that doesn't mean that Intel lost the CPU wars. Just because fewer people are learning Win32 doesn't mean Microsoft has lost the API wars, if the frameworks run predominantly on Win32.  Temple of the Lost  Joel even warns you in the beginning that "because I'm talking about big trends, I need to exaggerate and generalize". But you still get sucked in because Joel Spolsky is a first-class writer, in the same order as Philip Greenspun or Eric Raymond. That makes him so persuasive and plausible. But this is not Indiana Jones and doomed temples, but Steve Jobs and reality distortion fields.  Other opinions:  Harry Fuecks (PHP is ASP's upgrade path),  Dennis Hamilton (M'soft is just covering all bases), Robert McLaws (Joel is wrong in 7 points), Oliver Travers (the web is not good enough), One Run-time to Rule them all....
243498
There's a big yellow bar on the Twitter home page today saying it will be down for maintenence betw 10AM and 10PM today. I haven't heard any grumbling about this, but it's worth a bit of a grumble. What other basic form of communication goes down for 12 hours at a time? What if the web went offline for 12 hours at a time? It's unthinkable, because the web is built on the Internet and is decentralized and redundant. A single router or server can go down for a few hours, days or forever, and the web keeps on tickin.  Same with email. If Gmail started having twelve-hour planned outages, as much as I like Gmail, I'd switch. I can't be without email for any extended period of time.  Okay, let's give the guys at Twitter credit -- they stopped being flip about Twitter taking naps or showers. No one likes jokes when a line of communication is down. Now I'd like them to take another step. Assuming these long outages are really necessary, explain to us what they're for. I can take a guess -- something about their database needs changing, and all the data in all the files must be processed to implement the change. Any updates made while such a process is running would be lost, so the server must be shut off. But this is just a guess.  Another guess -- maybe they've hired a scaling expert who needs to make one final major adjustment before these outages are a thing of the past? No one would want to make such a promise, that's offering too much temptation to Dr Murphy, but that would be good news. Maybe Twitter is getting on to solid ground, finally.  It's fairly amazing that there isn't a viable Twitter clone out there yet. I'd also like to see something much more decentralized, based on static files, available to any Twitter-like system. It doesn't seem that far out of reach. With all the scaling troubles Twitter has had it's surprising that there haven't yet been any entrepreneurs willing to enter the space as competition to Twitter.  Users and developers are learning first-hand why centralized systems are so fragile. I'm sure they're doing a heroic job at Twitter, the best they can with what they have, but it's not good enough when the service takes a 12-hour break while many of the humans that depend on it are awake and working.
710470
Nice!  My patches to java-memcached  went in!    This provides significant savings for primitive datatypes.  Significant meaning the difference between a few gigs of memory vs a few hundred megs.  "11-01-2005 Released the client as 1.2 today. Added in socket timeout on initial connection option. Custom serialization added for primitive types by Kevin Burton. This gets a big space savings for primitives over default java serialization."
740094
In his travels as a PHP developer, Jamie Wong has gathered some helpful debugging tips that are shared in this latest post to his blog.   Here are some bugfixing rules and tips Iâve learned working all these years with PHP. I emphasize mostly on fixing bugs than preventing them, which is another subject worth of its own article. Iâve moved to Rails, but I wanted to finish this post as a farewell and thanks to every article and documentation that was useful to me. Hope this is useful to you too.   Topics covered include:  Assume nothing Turn Error Reporting to show all errors Read the error message Understand the bug "Scooby-Bug, where are you?" Get as much information as possible  Each has some explanation below it and, in some places, a bit of code to clarify the point.
507324
Do mobile application developers need to band together to tackle the tough issues facing them? Attendees at Sun's Java Mobile &amp; Embedded Developer Days Conference in Santa Clara, Calif. on Thursday afternoon will briefly discuss this issue.The idea is that developers must deal with issues such as fragmentation in features, behavior, security policies, and deployment policies and could form an alliance providing a single voice, said Terrence Barr, Sun technical evangelist for the mobile and embedded developer community."We call it the mobile developer alliance and it's essentially a developer activism group," Barr said on Wednesday evening. "It's just a grassroots thing. We haven't thought about it too much. The idea is to bring developers together to give them a common voice and try and work on some of the fragmentation and issues that the industry has."The mobile developer alliance is envisioned as an industrywide effort and not Java-specific. Developers, Barr said, have not had a consistent, uniform voice in facing issues.Among the problems developers face is having to slightly rework applications for each of the many phones, Barr said. Every phone, he said "has certain quirks that you have to deal with, and if you're trying to cover 80, 90 percent of the installed base out there it becomes very painful because you're literally producing hundreds of slightly different versions of the same application," he said.The alliance could serve as sort of a citizens' voice, but the exact mode of operation is still up for discussion, Barr said. Agreement on high-priority issues that developers want to make progress on would be a main focus, as well as trying to establish relationships with players such as carriers and original equipment manufacturers (OEMs)."It's not necessarily [about] battling your enemies but it's about getting everybody on the same page," said Barr. No single player can address them, he said."At the end of the day, [developers] are the ones who have to make all this stuff work," he said.OEMs care about the platform and carriers care about the networks, said Barr. "The developer has to bring all these pieces together and that's why it's so painful," he said.Sun officials Wednesday also talked about Java ME (Micro Edition) development tools, including plans for a Java ME development toolkit with a consolidated environment for both the CDC (Connected Device Configuration) framework and CLDC (Connected Limited Device Configuration) technology.Also highlighted were enhancements planned for the Sun Java Wireless Toolkit for CDLC. Planned features include an application testing framework and support for Java Specification Request (JSR) 256 - Mobile Sensor API Submission to the JCP (Java Community Process) and JSR 280 - XML API for Java ME.The application testing framework is intended to automate manual testing. It will support refined testing scenarios in an emulated environment as well as improvements for testing of applications for users with visual, motor, or dexterity impairments.JSR 256 offers a unified way of managing sensors connected to mobile devices and easy access to sensor data. JSR 280 is designed to provide a general-purpose XML API for next-generation mobile devices.
83975
Three different ActiveX vulnerabilities affect Yahoo Instant Messenger version 3.5,  and Yahoo Messenger versions 4.0, 5.0, and 5.5
405451
Bothered by the ugly way Xdebug stack traces were turing out, Derick Rethans has created a script to fix that.   I've always been annoyed by the way how Xdebug's stack traces looked liked. So I spend some time on making them look better. I will show the differences according to the following script.   The simple script takes the output and adds a bit of formatting, stripping down the information to make it a bit more clear. Check out the before and after shots to see the difference.
306188
In recent work, Ian Selby came across something odd - a setup where PHP was segfaulting without any real indication of where the error might be:   Starting to get a little frustrated, I took a peek at my error logs (/var/log/httpd/error_log for the unitiated), and discovered a wonderful message [about the segfault]. As any person scratching their head would do, I hit up google.. to no real avail. Just a bunch of php bug reports. So, what happened, and how did I fix it?   After searching through the code and narrowing down where it could be, the culprit looked like a custom session handler he was using. It uses MySQL to store the sesion information and, unfortunately, when Ian had compiled the server he didn't let PHP know about his unique setup.   His default installation was trying to use the default MySQL information (including the socket) to reach the database. Obviously failing, the server simply gave up and segfaulted. Thankfully, all it takes it a recompile with a few extra parameters and you're back in business.
466300
Desktops, servers affected, but no vulnerabilities deemed critical.