If the lessons of IE6 are anything to go by HTML5 won't really be relevant for about another 10 years, ie. when IE8 has faded into obscurity. I just started upgrading my CSS skills and the landscape is only now ready for phasing out IE6 support. With IE7 as the baseline most of CSS3 is irrelevant, never mind HTML5. Microsoft has a lot to answer for. Despite the insidious tentacles of their insipid monopoly they don't seem to have the ability to use it for good and impose browser upgrades, largely due to the way they encouraged companies to build IE(6)-only apps for so long.
Layer groups and related editing are scheduled for the next release - 2.8
Who the fsck pays silly money like this for spec featuring
... wait for it ... a 320GB 5400rpm disk?
An anonymous reader writes "Wondering where all that bloat comes from, causing even the classic 'Hello world' to weigh in at 11 KB? An MIT programmer decided to make a Linux C program so simple, she could explain every byte of the assembly. She found that gcc was including libc even when you don't ask for it. The blog shows how to compile a much simpler 'Hello world,' using no libraries at all. This takes me back to the days of programming bare-metal on DOS!"
plasmacutter writes "The Video Lan dev team has recently come forward with a notice that the number of active developers for the project's MacOS X releases has dropped to zero, prompting a halt in the release schedule. There is now a disturbing possibility that support for Mac will be dropped as of 1.1.0. As the most versatile and user-friendly solution for bridging the video compatibility gap between OS X and windows, this will be a terrible loss for the Mac community. There is still hope, however, if the right volunteers come forward."
No, but they teach you how to throw a chair.
I've watched SMB fail in so many different ways, first on Tiger then much worse on Leopard. Visit the Mac forums and you'll see hundreds of messages along the same lines - the SMB/Finder combo is broken and Apple doesn't seem to give a damn about fixing it. It's no good saying change your
/etc/smb.conf when Finder is gumming the works. Shares should auomtaically appear in Finder and thej don't. If you have 2 similar systems, say desktop and laptop, with similar accounts and files try moving files on one machine via symlink and watch OS X move the files on your desktop machine instead. OK, change your /etc/smb.conf again and it can (maybe) be fixed but ... you get my drift. I have had files appear in remote shares and I copy them to my desktop machine only to find they were never copied, and that's after waiting for the progress bar to complete. With Finder/SMB you solve one problem and it either reappears next time or another one takes its place. To me this is THE issue stopping me from recommending OS X in mixed network environments. With Snow Leopard Apple seems to have surpassed itself with new Finder/SMB problems. I didn't think there were any more to add to the long list of unresolved bugs.
I haven't upgraded to Snow Leopard yet but as far as I'm concerned unless Apple has fixed the dire state of its SMB networking all talk of Exchange support is whistling in the wind.
Much as I would love to tout Ubuntu, the nearest thing to "desktop Linux", as an alternative to Windows my recent experience with 9.04 left me in doubt that it would ever happen. Although it's getting better I'm a Linux/OS X geek and still found I had to spend a long time futzing with the OS to get it working properly. I came to the conclusion that it hadn't been fully tested considering the appalling state of video playback. When I put a DVD in the drive the default video player couldn't parse the dvd:// URL for some reason and I had to create a custom desktop launcher complete with command-line foo from a geek internet source before I could get it to work. Finding codecs was also a pain. I can't imagine how an inexperienced Linux user would cope with this so, no, Linux is not ready for the desktop/netbook and we shouldn't be surprised if Windows users find it too hard to get to grips with. Destop Linux is a viable option in organisations where you have experienced sysadmins but a Windows user left on his own with a new Linux installation is going to have problems.
With Perl6 taking almost a decade to complete it doesn't make sense to waste this small amount of money on anything other than getting Perl6 out the door?