I have. It sucked. It doesn't expose very much functionality. To write a complex query you need to use the plaintext editor. For that you need to know SQL.
I've written queries longer than your comment. Yes, they needed to be that long because they were taking a large ammount of data from a large database and filtering on a variety of fields. There is absolutely no way I could have "designed" those queries in the visual editor.
Windows has drawing issues too. Classic MacOS had the same issue. Mac OS X is the only OS I know of that doesn't have the drawing issue. The RAM and Processor requirements for keeping the screen buffer are rather large, which is why the other, older systems don't have it. Even on a Mac, there are still problems. Moving a window might be smooth but resizing it isn't. I have a Dual 1.2Ghz G4 with a Radeon 8500 at home. There's no reason such a system should have drawing issues yet it does. My PC at work running Linux handles window resizing better than my Mac.
Windows will get a screen buffer in Longhorn.
X will get one when someone writes it. I'm pretty sure there is work going on to put something like this in X already.
You can get Qtopia Desktop from Trolltech but it is not compatible with Sharp's "new" and incompatible syncing stuff. It is possible to sync with an "older" zaurus (it's the ROM that matters, not the hardware). It should be possible to setup OpenZaurus/Opie and be able to sync with Trolltech's Qtopia Desktop if you've got a "new" zaurus and you can't put an older ROM on it.
There is a USB driver somewhere that you'll need to connect your Zaurus to a Mac.
I've synchronized an A300 (older model zaurus only sold in Japan) and a SL5000D (really old "developer only" zaurus) with a Mac.
My opinion of operator overloading is that it is absolutely bad. Let me be clear. It is always bad, under any circumstances, when used for any reason. It has exactly zero functional value, and, as opposed to other kinds of "syntactic sugar" it has a tendency to make code where it is used with any frequency into a confusing, unmaintainable minefield.
My favorite peeve about Java was it's "special" treatment of java.lang.String. Argue all you want about overloaded operators being bad but + meaning "contatenate these two immutable objects into a new String object" is clearly an example of an overloaded operator.
Actually, without the special treatment of String, lots of code would break badly. String bar = "bar"; System.out.println("foo = " + bar); wouldn't work.
I'd also point out that databases and other applications in those same environments perform case conversions quite easily on those same platforms.
I'd like to point out to you that "databases and other applications" are USER programs. USERs generally expect case insensitivity. However, it's not USERs that do the coding.
Seriously, they are everywhere. NetBSD wants to run on everything. Cockroaches do run on everything (literally).
If I could draw, I'd make a logo with a cockroach coming out of (or from behind) a computer, or maybe a front on shot showing a cockroach standing over a computer (with perspective making it seem large compared to the computer). The catchphrase could be something like "we'll look after your machine".
I disagree for one simple reason... Konqueror does not prompt for the name of a bookmark. All the browsers I use besides konq have a hotkey for this (or it's the default). I don't like saving bookmarks with names like "site name - the best site that talks about foo keyword keyword keyword - article name".
While I'm whinging about bookmarks, why can't you setup a hotkey for "managing bookmarks"? Again, every other browser I use has this.
It wasn't really an addiction though, I was just having enough coffee to cause the headaches when I stopped. I stopped, had headaches for a week and was fine from them.
Now I generally have 2 cups a day in the morning (unless I don't want to sleep at night). For me it's just under the "addictive" theshold so I can easily miss my coffee for the day and not get a headache. 3 cups does wonders for me when I'm tired but if I do that for a few days the headaches return. I have a supply of instant decaf in case my body decides it needs more coffee. Better than real coffee and my body doesn't seem to notice the difference.
FYI - I have a big insullated cup (holds about 3 standard mugs) that I put 2 espresso shots + water and milk into. I like this arrangement because I get "lots" of coffee without having to have lots of coffee.
its relly bad to get splling mistke's 'n bad gramer in resmes. Youd think someon wood teach this in skool. Adding apostrofe's everywhere is relly anoying tooo.
I don't remember where I read this but Apple is moving the iMac into a space between the ultra-cheap eMac and the expensive PowerMac. There's a clear difference between the iMac and the PowerMac. People are obviously willing to pay more for an iMac with a big screen. I remember when the LCD iMac first came out and I swore I'd never buy one since it still had that crappy 1024x768 resolution. The 17" or 20" models would be ok for me except for the ripoff price. I care more about my CPU than my screen. For some that's not the case.
Some people want the cheapest computer they can get. Of course, I'd like it if Apple would provide a cheap, upgradeable model without a builtin monitor but that would lose money for Apple.
I worked at a company that produced Telco products (switches, base stations, etc) and we had an estimate of $10,000 per bug found in the field. This was assuming it was a relatively straightforward problem that could be fixed within a few days. If it took longer for the developers to invetigate/fix the bug, the cost went up. The cost was so high because we had multiple levels of support who would investigate before passing the info onto a developer who would confirm the bug's presence and fix it. A new build would be made and tested (to ensure the bug was fixed and nothing else was broken) before being sent out to the customers.
We had a dedicated Verification (testing) team that tested the unreleased code (ie. the next release). They spent their entire time trying to figure out how customers would use the system and using it in that way. We even had a small mobile network setup to do the testing properly.
Bugs caught before release were much cheaper to fix since it didn't require a dedicated build/test run, just a developer to fix it and a verification person to test the fix. The Verification team got a new build each week containing all the bug fixes made in that time.
My suggestion is that we should focus on what is wrong in our platform, and focus on what is good in their platform, to find out what needs to be solved.
Well, for a start, how about not changing major interfaces (kernel and userland) every release? Solaris apps from long ago continue to work with little or no modifications on the current hardware/OS. Linux can't claim that. It's the distros that are at fault with userland of course, but there's no reason why version x+1 of a program/library/whatever needs to be incompatible with version x.
It's all about your focus. Sun is like IBM in that regard. They want customers to migrate their stuff from older systems to newer ones. You shouldn't need to rewrite everything to do that. Unforunately, the Linux world seems to have copied Microsoft's philosophy of "change the interface every release so we're a moving target". Serious companies don't bother with that.
I doubt they have expanded their FS support. Apple will stick with HFS+ until they develop something better, hopefully based on BeFS (since they've got some ex-BeOS people working there).
Of course, with the modular nature of xnu (the Darwin kernel) there's no reason why you couldn't port your favorite FS. You could probably pay the Rieser people to port their FS.
Also, if Apple's incorporated any of the recent changes FreeBSD's made to the UFS code they'll have Soft Update support which makes UFS fast without sacrificing the stability that it's famous for, basically removing the need for a journal. (FreeBSD 5 uses Soft Updates + background fsck to do what a journal would otherwise give you).
I've got a HP 712/80 (yes, 80 Mhz!) that runs my home network. It's curently running Debian but I do have a tape backup of the HP-UX 10.20 it was running when I got it.
I have a 21" Fixed Frequency (1280x1024@72hz) monitor (HP A2094B) that's currently plugged into the 712.
I have a Matrox Millenium 1 (useful for powering the monitor above from a PC since I only have a SyncOnGreen cable).
I *was* running an old Pentium 166 machine but it died so now I've got a 500Mhz Pentium 3 system.
The SystemStarter process that Mac OS X uses is based on the Next init/rc system which is similar in principle to how FreeBSD does it's init/rc system. Since it's part of Darwin it should be available under a BSD license. I'm sure it could be rewritten to use X rather than WindowServer for it's graphics.
I think that's a more worthwhile replacement for linux's init/rc system IMHO.
A SSH server written in Java will have zero buffer overflows.
/me thinks you misunderstand how Java works... You can indeed have a buffer overflow in Java, the only difference is that it causes the VM to crash (unless there's a RuntimeException catch somewhere up the calling chain). A DoS attack on a buggy Java server could be just as bad as a buggy C server.
I've seen firsthand what happens when a random RuntimeException isn't caught. I was involved in a telecommunications software that was programmed in Java. Due to the architecture of the program, an uncaught exception resulted in the program entering a zombie state. There were threads running so the app didn't die. The "watchdog" thread was still running so the app didn't get restarted. However, the processing thread was killed so the app did nothing. The system took around 12 hours before it managed to fall over and restart itself. Due to telco uptime standards, the app is only allowed to be down for an hour a year (or something like that... 99.999% uptime). That single flaw would have completely ruined our uptime claim if it had got into the field.
It's not a case of needing language x over language y, it's a case of using "safe" structures/functions. C++/Java/C# programmers will tend to use List/Collection classes rather than manually sizing and handling arrays. There's no reason why you couldn't use something like Glib to get the same behaviour in a C server.
Well the 'before' sample has an obviously flat note. However, the 'after' sample takes that note and makes it just a bit too sharp. There's a reason people tend to sing flat rather than sharp, it sounds better. If the 'before' sample had managed to get the pitch up just a bit it would have been fine.
I cringed more at the sharpness of the 'after' sample than I did at the flatness of the 'before' sample. So much for perfect pitch! The ideal pitch for that note was just a bit flat. Of course, you can't expect a computer to know that.
I'm sure an untrained ear wouldn't notice but having played in an Orchestra and sung in a choir, I know how important pitch is. Most instruments allow you to 'bend' the pitch half a tone or more. In an orchestral setting, it's the rule rather than the exception to do just that.
If you put autotuners on instruments in an orchestra, you'd create an abomination of sound. What makes singers any different?
I did a search... (search for "quicktime full screen") and found the applescript required to put QuickTime into fullscreen mode is "present movie 1 scale screen". This puts the frontmost window into fullscreen mode and starts playing it.
Ultrasonic is crap. It's noisy (I can hear it anyway) and pretty useless. I've had great success getting cockroaches out of my house with one of those magnetic resonance devices. They're probably called something different. They work by sending pulses down your power lines that create "bad" magnetic fields that insects (I don't know about rodents) don't like. I haven't noticed any problems with electronics devices either so it mustn't do bad things to the power source.
Slashdot Mirror
I have. It sucked. It doesn't expose very much functionality. To write a complex query you need to use the plaintext editor. For that you need to know SQL.
I've written queries longer than your comment. Yes, they needed to be that long because they were taking a large ammount of data from a large database and filtering on a variety of fields. There is absolutely no way I could have "designed" those queries in the visual editor.
There is an automatical fallback to perl5 mode.
Windows has drawing issues too. Classic MacOS had the same issue. Mac OS X is the only OS I know of that doesn't have the drawing issue. The RAM and Processor requirements for keeping the screen buffer are rather large, which is why the other, older systems don't have it. Even on a Mac, there are still problems. Moving a window might be smooth but resizing it isn't. I have a Dual 1.2Ghz G4 with a Radeon 8500 at home. There's no reason such a system should have drawing issues yet it does. My PC at work running Linux handles window resizing better than my Mac.
Windows will get a screen buffer in Longhorn.
X will get one when someone writes it. I'm pretty sure there is work going on to put something like this in X already.
Link
You can get Qtopia Desktop from Trolltech but it is not compatible with Sharp's "new" and incompatible syncing stuff. It is possible to sync with an "older" zaurus (it's the ROM that matters, not the hardware). It should be possible to setup OpenZaurus/Opie and be able to sync with Trolltech's Qtopia Desktop if you've got a "new" zaurus and you can't put an older ROM on it.
There is a USB driver somewhere that you'll need to connect your Zaurus to a Mac.
I've synchronized an A300 (older model zaurus only sold in Japan) and a SL5000D (really old "developer only" zaurus) with a Mac.
Link
I remember playing Warcraft 2 on a 25Mhz 386 with 4MB RAM. The box said it required a 486 with 16 MB RAM!
No problemo, I just ran it under Windows 3.1 with virtual memory to fill the gap between required and actual RAM.
Sure the game started up really slow but once it was going, it was fine. The biggest problem I had was that it took up around 80% of my hard disk.
Link
My favorite peeve about Java was it's "special" treatment of java.lang.String. Argue all you want about overloaded operators being bad but + meaning "contatenate these two immutable objects into a new String object" is clearly an example of an overloaded operator.
Actually, without the special treatment of String, lots of code would break badly. String bar = "bar"; System.out.println("foo = " + bar); wouldn't work.
Link
There is a way to add case-sensitivity to Mac OS X. http://homepage.mac.com/lgw4/iblog/C675550648/E871 090033/
e =2003111009264885
Note the warnings about this though... http://www.macfixit.com/staticpages/index.php?pag
Link
I'd like to point out to you that "databases and other applications" are USER programs. USERs generally expect case insensitivity. However, it's not USERs that do the coding.
If an admin on your box has no password. Nobody requires a password to log in.
Seriously, they are everywhere. NetBSD wants to run on everything. Cockroaches do run on everything (literally).
If I could draw, I'd make a logo with a cockroach coming out of (or from behind) a computer, or maybe a front on shot showing a cockroach standing over a computer (with perspective making it seem large compared to the computer). The catchphrase could be something like "we'll look after your machine".
I disagree for one simple reason... Konqueror does not prompt for the name of a bookmark. All the browsers I use besides konq have a hotkey for this (or it's the default). I don't like saving bookmarks with names like "site name - the best site that talks about foo keyword keyword keyword - article name".
While I'm whinging about bookmarks, why can't you setup a hotkey for "managing bookmarks"? Again, every other browser I use has this.
Link
It wasn't really an addiction though, I was just having enough coffee to cause the headaches when I stopped. I stopped, had headaches for a week and was fine from them.
Now I generally have 2 cups a day in the morning (unless I don't want to sleep at night). For me it's just under the "addictive" theshold so I can easily miss my coffee for the day and not get a headache. 3 cups does wonders for me when I'm tired but if I do that for a few days the headaches return. I have a supply of instant decaf in case my body decides it needs more coffee. Better than real coffee and my body doesn't seem to notice the difference.
FYI - I have a big insullated cup (holds about 3 standard mugs) that I put 2 espresso shots + water and milk into. I like this arrangement because I get "lots" of coffee without having to have lots of coffee.
its relly bad to get splling mistke's 'n bad gramer in resmes. Youd think someon wood teach this in skool. Adding apostrofe's everywhere is relly anoying tooo.
I don't remember where I read this but Apple is moving the iMac into a space between the ultra-cheap eMac and the expensive PowerMac. There's a clear difference between the iMac and the PowerMac. People are obviously willing to pay more for an iMac with a big screen. I remember when the LCD iMac first came out and I swore I'd never buy one since it still had that crappy 1024x768 resolution. The 17" or 20" models would be ok for me except for the ripoff price. I care more about my CPU than my screen. For some that's not the case.
Some people want the cheapest computer they can get. Of course, I'd like it if Apple would provide a cheap, upgradeable model without a builtin monitor but that would lose money for Apple.
Link
I worked at a company that produced Telco products (switches, base stations, etc) and we had an estimate of $10,000 per bug found in the field. This was assuming it was a relatively straightforward problem that could be fixed within a few days. If it took longer for the developers to invetigate/fix the bug, the cost went up. The cost was so high because we had multiple levels of support who would investigate before passing the info onto a developer who would confirm the bug's presence and fix it. A new build would be made and tested (to ensure the bug was fixed and nothing else was broken) before being sent out to the customers.
We had a dedicated Verification (testing) team that tested the unreleased code (ie. the next release). They spent their entire time trying to figure out how customers would use the system and using it in that way. We even had a small mobile network setup to do the testing properly.
Bugs caught before release were much cheaper to fix since it didn't require a dedicated build/test run, just a developer to fix it and a verification person to test the fix. The Verification team got a new build each week containing all the bug fixes made in that time.
Link
Well, for a start, how about not changing major interfaces (kernel and userland) every release? Solaris apps from long ago continue to work with little or no modifications on the current hardware/OS. Linux can't claim that. It's the distros that are at fault with userland of course, but there's no reason why version x+1 of a program/library/whatever needs to be incompatible with version x.
It's all about your focus. Sun is like IBM in that regard. They want customers to migrate their stuff from older systems to newer ones. You shouldn't need to rewrite everything to do that. Unforunately, the Linux world seems to have copied Microsoft's philosophy of "change the interface every release so we're a moving target". Serious companies don't bother with that.
Link
Disclaimer: I don't have Panther yet.
I doubt they have expanded their FS support. Apple will stick with HFS+ until they develop something better, hopefully based on BeFS (since they've got some ex-BeOS people working there).
Of course, with the modular nature of xnu (the Darwin kernel) there's no reason why you couldn't port your favorite FS. You could probably pay the Rieser people to port their FS.
Also, if Apple's incorporated any of the recent changes FreeBSD's made to the UFS code they'll have Soft Update support which makes UFS fast without sacrificing the stability that it's famous for, basically removing the need for a journal. (FreeBSD 5 uses Soft Updates + background fsck to do what a journal would otherwise give you).
I don't know why the Fire people haven't updated their MSN protocol stuff since every other IM client I've seen has.
I'm also getting crashes from MSN Messenger (3.5.1, not to be confused with 3.5 which no longer works since it speaks the old protocol).
I found a program called JSuperChat that is a Java-based IM that can talk MSN. It was really slow though (perhaps because my machine is a 400Mhz G3).
I'm in the middle of compiling Psi... hopefully I'll be able to get to MSN from Jabber.
Link
I've got a HP 712/80 (yes, 80 Mhz!) that runs my home network. It's curently running Debian but I do have a tape backup of the HP-UX 10.20 it was running when I got it.
I have a 21" Fixed Frequency (1280x1024@72hz) monitor (HP A2094B) that's currently plugged into the 712.
I have a Matrox Millenium 1 (useful for powering the monitor above from a PC since I only have a SyncOnGreen cable).
I *was* running an old Pentium 166 machine but it died so now I've got a 500Mhz Pentium 3 system.
The SystemStarter process that Mac OS X uses is based on the Next init/rc system which is similar in principle to how FreeBSD does it's init/rc system. Since it's part of Darwin it should be available under a BSD license. I'm sure it could be rewritten to use X rather than WindowServer for it's graphics.
I think that's a more worthwhile replacement for linux's init/rc system IMHO.
Link
/me thinks you misunderstand how Java works... You can indeed have a buffer overflow in Java, the only difference is that it causes the VM to crash (unless there's a RuntimeException catch somewhere up the calling chain). A DoS attack on a buggy Java server could be just as bad as a buggy C server.
I've seen firsthand what happens when a random RuntimeException isn't caught. I was involved in a telecommunications software that was programmed in Java. Due to the architecture of the program, an uncaught exception resulted in the program entering a zombie state. There were threads running so the app didn't die. The "watchdog" thread was still running so the app didn't get restarted. However, the processing thread was killed so the app did nothing. The system took around 12 hours before it managed to fall over and restart itself. Due to telco uptime standards, the app is only allowed to be down for an hour a year (or something like that... 99.999% uptime). That single flaw would have completely ruined our uptime claim if it had got into the field.
It's not a case of needing language x over language y, it's a case of using "safe" structures/functions. C++/Java/C# programmers will tend to use List/Collection classes rather than manually sizing and handling arrays. There's no reason why you couldn't use something like Glib to get the same behaviour in a C server.
Well the 'before' sample has an obviously flat note. However, the 'after' sample takes that note and makes it just a bit too sharp. There's a reason people tend to sing flat rather than sharp, it sounds better. If the 'before' sample had managed to get the pitch up just a bit it would have been fine.
I cringed more at the sharpness of the 'after' sample than I did at the flatness of the 'before' sample. So much for perfect pitch! The ideal pitch for that note was just a bit flat. Of course, you can't expect a computer to know that.
I'm sure an untrained ear wouldn't notice but having played in an Orchestra and sung in a choir, I know how important pitch is. Most instruments allow you to 'bend' the pitch half a tone or more. In an orchestral setting, it's the rule rather than the exception to do just that.
If you put autotuners on instruments in an orchestra, you'd create an abomination of sound. What makes singers any different?
Link
I did a search... (search for "quicktime full screen") and found the applescript required to put QuickTime into fullscreen mode is "present movie 1 scale screen". This puts the frontmost window into fullscreen mode and starts playing it.
Quicktime does support fullscreen without going pro. You just need to do some applescript.
I think there was a hint on this on macosxhints.com...
Ultrasonic is crap. It's noisy (I can hear it anyway) and pretty useless. I've had great success getting cockroaches out of my house with one of those magnetic resonance devices. They're probably called something different. They work by sending pulses down your power lines that create "bad" magnetic fields that insects (I don't know about rodents) don't like. I haven't noticed any problems with electronics devices either so it mustn't do bad things to the power source.