"And if you want to print from gmail, it shouldn't be a print of the screen, but a specially built printable html page."
Funny you should say that, because the W3G specifically designed HTML so that it could be read from screen as well as printed on a printer (and other media like screen readers etc.). Same with CSS really. The whole idea that you should generate a special HTML page goes straight against this policy. I blame the current browsers for not doing a well enough job on printing HTML pages. If they had strictly sticked to HTML standards and recommendations for this, this should not have happened.
As for AJAX: the page *should* be printable as well. Just use the latest DOM and follow CSS guidelines and you should be OK. *IF* both sides implement HTML standards the way they are meant to be. Currently this only works well if you are an inhabitant of Utopia.
Although there are many (many many) similarities between C# and Java, to say C# is a reskinned Java makes no sense. Different syntax, different strategies (exceptions, static methods, properties, aliases, assemblies etc etc), different virtual machines...you get the idea.
Since J++ is no more, we now have J#, which (Microsoft claims) is 1.4.2 compatible. I don't know how much of that is true (my tests compiled without a hitch though). Of course, you *could* go and use.NET from it, but it makes little sense for new products, since it misses some specific.NET functionalities (and next to none MSDN examples are written for Java, so you would need to learn C# anyway).
"Those of us that are older will rmember that before the 1950's we actually DID spread soot EVERYWHERE. This was done by burning coal in open hearths."
You don't say. Currently, at least in the Netherlands, it's getting pretty common again to get hearths in the house. Nice and cosy. Except when you have a window open or if you're outside.
Smoking is prohibited at most public places, but suffocating an entire village apparently is not.
Yeah, why do anything like follow standards anyway? Problem is that most web-servers do not seem to have very extensive lists of extensions mime types, and as user you cannot easily change the HTTP header to indicate what kind of file you are serving. If you do have control over your server, please try to keep to the HTTP standards as good as possible. I mailed Tom's hardware once over this issue (for streaming video) and they fixed it straight away. Actually, IE does not look only to the extension, but to content as well afaik. This is one of the main reasons this problem still exists nowadays.
Swing has the wrong idea on how to integrate with the desktop. People do *not* want an application that looks the same on every OS. They only tend to work on *one* OS at a time anyway. They do not want an application to crappily emulate Windows, they want Window widgets (that look new when they go from one version of windows to another). Same goes for most Linux zealots, even though they are more used to see crappy windows on their X Windows enabled screen. SWT got that right, even though Swing might be more esthetically pleasing design wise (garbage collection). As long as Swing does not get this, it won't make a big dent in the desktop market.
Besides that, Java needs better application and library management, such as assemblies in.NET. (Even though I would not copy that implementation directly. I already installed a wrongly signed assembly in the assembly cache which only a command prompt delete could remove. Ouch.)
If Microsoft is such a monopoly, why does my (NL) government only provide for a Windows application to fill in my tax forms? 2 years down the lane and they are finally building an Apple version as well. Why have I (and the company I work for) received many documents that can only be viewed by Microsoft software. Thank god most information folders are formatted using Adobe. To get back to the Media Player issue; you would have to install it anyway, since almost all the broadcasts of the (public) TV network are either Real or MS formatted, and Real is not a real option.
Because they are written by lawyers. These are generally the kind of people that send all mail on high priority. Besides that, they answer to managers, who otherwise would make statements like: "that's not really clear, maybe you can make it more clear somehow?". When it is in capitals, it is the truth and it won't be debated. God spoke in capitals as well, I've heard.
My GUESS is that they are being rewritten in Vista/Longhorn. On Windows 2k and XP.NET uses a lot of wrappers. And since you cannot guess how big an image is supposed to be, you will still suffer buffer overruns. Java has a very small interface to native libraries, and with good reason (also for portability of course).
Don't worry. Normally you would use something like this:
String s = new String(new byte[] { 0x41, 0x42, 0x43 }, "UTF-8");
To get "ABC". I haven't got a clue why you would want to do convert characters to or from *any* integer, unless you would like to write a ROT-13 codec. I laugh at languages that use *that* as a way to show their strength (and many do).
The book Java Puzzlers doesn't assume you would like to do something like that. The whole book is about getting a more complete understanding of the language, and not about getting better hacks for your money. That said, byte's should really have been unsigned, like this they are a pain in the back (who would use a byte to show any other value than a hexadecimal value in a program?)
As any platform + language, Java tries to do a lot of things. And like everything in this world, it is not perfect. Some of the problems could have been avoided (the rather unnecessary overloading of the operator &, meaning both && with both expressions evaluated and the bitoperand AND). Others could not. Don't forget that Java is pretty old (1985 if I am not mistaken), and when it was invented people tended to scream at you when you did anything like wasting a byte or a CPU cycle. And some things (like unsigned support) were explicitly left out due to simplicity.
Yes, Java could have been better (there *IS* a new language specification, so even Sun thought so) but there will always be corner cases enough to make puzzlers about. I thouroughly enjoyed reading it, though effective Java was even better.
Ok, so I started reading (well, I tried to between the various popup windows) and immediately found the one about a new Raptor drive. So I read into the article and it seems that they are talking about the RE2.
Differences: RE (raid edition) & RE2 specialize in "limiting the drive's error recovery time", and are specialized for raid configurations and reliability. Raptor on the other hand is speciallized in latency and reliability.
And that's when I stopped reading (and clicking away the - cannot find add server popups). Maybe it is a fast drive, but it has nothing to do with Raptor.
What if you claim to have forgotten it? What if you actually forgot it? I've got lot's of archives that have been encrypted, and I do not know the passwords anymore (mostly since the archives where only used for transportation). Sorry, but this might be very difficult to enforce. Actually, I don't want it to be enforced, but that's another matter.
You would still have to wait for a response of the system. Maybe not of a complete web page, but the application server still has to answer. Most if not all of a page can be cached, so what you are really waiting for is the business logic. And that will be as slow as it always has been. And AJAX obviously would also be routed through HTTPS. So speed is not that much of a difference. The user experience may be better nonetheless, of course - no flickering, or page setup, and no bs like the back button, which does not work anyway.
This is funny? I've got 4 official DVD's that won't run on my player, and 3 or 4 CD's that don't play in my computer. If *they* are not going to play fair with me, I sure as hell will return the favour. I bought an offical DVD, and all I got was a cheap skate menu and 10 minutes worth of adverts and warnings. Bleh.
java.io.Console? That's an API change, not a language change. Language changes would be concerned with the syntax or semantics of Java constructs, not with something inside a package.
Don't they still have degradation problems? I believe the color blue was still degrading rather rapidly. They are used, but mostly for smaller displays that are supposed not to last that long or where color reproduction does not have to be perfect (such as phones / mp3 players). At least they are being produced, which means they are not solely a "could be" technology. And then there are patents apparently...
Downloads of service packs, IE6.xxxx and MSDN have spiked. Terrible cries are heard all over town, where developers tried to get the development environment installed on their 256MB 4200 RPM company laptops.
Seriously, it took me some *hours*, way into midnight to get the environment installed for a 4 day.NET course. Thank god there will be a stripped down version.
Well, at least they have a stab at real time parsing. I guess you can get enough information from the beta versions to guess what's coming. It's sure to have some refactoring support (renaming classes and updating references and stuff). If you've worked with Eclipse or NetBeans (most popular Java IDE's) you'll know what's possible (real time links between tools and classes for instance). Unfortunately, at least in Beta-1, the functions were still pretty much in their infancy, and there were not many of them. Does someone have access to the latest versions, and tell us what has happened in this respect? The parse tree (abstract syntax tree) should be there, so putting some refactoring functions in there should not prove to be too difficult.
"Sure you need to be able to take a loss on it for a while, but the original poster is correct that you need to have customers driving your requirements from day one."
That's like saying that marketing push does not work. For generic products like this it is very unlikely that you get any customers buying it up front - it does not directly solve any problem. The problem here is that there is probably only a niche market. So you will have few people interested in it as well. That makes it hard to do a market push.
Slashdot Mirror
"And if you want to print from gmail, it shouldn't be a print of the screen, but a specially built printable html page."
Funny you should say that, because the W3G specifically designed HTML so that it could be read from screen as well as printed on a printer (and other media like screen readers etc.). Same with CSS really. The whole idea that you should generate a special HTML page goes straight against this policy. I blame the current browsers for not doing a well enough job on printing HTML pages. If they had strictly sticked to HTML standards and recommendations for this, this should not have happened.
As for AJAX: the page *should* be printable as well. Just use the latest DOM and follow CSS guidelines and you should be OK. *IF* both sides implement HTML standards the way they are meant to be. Currently this only works well if you are an inhabitant of Utopia.
NO. That should be:
The nice thing about standards is that there are so many of them to choose from.
Andrew S. Tanenbaum
Unfortunately it has serious side effects. It decreases my humour dramatically, which is also bad for your health. I absolutely *despise* it's taste.
Although there are many (many many) similarities between C# and Java, to say C# is a reskinned Java makes no sense. Different syntax, different strategies (exceptions, static methods, properties, aliases, assemblies etc etc), different virtual machines...you get the idea.
.NET from it, but it makes little sense for new products, since it misses some specific .NET functionalities (and next to none MSDN examples are written for Java, so you would need to learn C# anyway).
Since J++ is no more, we now have J#, which (Microsoft claims) is 1.4.2 compatible. I don't know how much of that is true (my tests compiled without a hitch though). Of course, you *could* go and use
"Those of us that are older will rmember that before the 1950's we actually DID spread soot EVERYWHERE. This was done by burning coal in open hearths."
You don't say. Currently, at least in the Netherlands, it's getting pretty common again to get hearths in the house. Nice and cosy. Except when you have a window open or if you're outside.
Smoking is prohibited at most public places, but suffocating an entire village apparently is not.
Yeah, why do anything like follow standards anyway? Problem is that most web-servers do not seem to have very extensive lists of extensions mime types, and as user you cannot easily change the HTTP header to indicate what kind of file you are serving. If you do have control over your server, please try to keep to the HTTP standards as good as possible. I mailed Tom's hardware once over this issue (for streaming video) and they fixed it straight away. Actually, IE does not look only to the extension, but to content as well afaik. This is one of the main reasons this problem still exists nowadays.
Swing has the wrong idea on how to integrate with the desktop. People do *not* want an application that looks the same on every OS. They only tend to work on *one* OS at a time anyway. They do not want an application to crappily emulate Windows, they want Window widgets (that look new when they go from one version of windows to another). Same goes for most Linux zealots, even though they are more used to see crappy windows on their X Windows enabled screen. SWT got that right, even though Swing might be more esthetically pleasing design wise (garbage collection). As long as Swing does not get this, it won't make a big dent in the desktop market.
.NET. (Even though I would not copy that implementation directly. I already installed a wrongly signed assembly in the assembly cache which only a command prompt delete could remove. Ouch.)
Besides that, Java needs better application and library management, such as assemblies in
If Microsoft is such a monopoly, why does my (NL) government only provide for a Windows application to fill in my tax forms? 2 years down the lane and they are finally building an Apple version as well. Why have I (and the company I work for) received many documents that can only be viewed by Microsoft software. Thank god most information folders are formatted using Adobe. To get back to the Media Player issue; you would have to install it anyway, since almost all the broadcasts of the (public) TV network are either Real or MS formatted, and Real is not a real option.
Because they are written by lawyers. These are generally the kind of people that send all mail on high priority. Besides that, they answer to managers, who otherwise would make statements like: "that's not really clear, maybe you can make it more clear somehow?". When it is in capitals, it is the truth and it won't be debated. God spoke in capitals as well, I've heard.
Yup. One of the reasons being that you only have to factor in primes. Bwahaha, factor in, I crack myself.
My GUESS is that they are being rewritten in Vista/Longhorn. On Windows 2k and XP .NET uses a lot of wrappers. And since you cannot guess how big an image is supposed to be, you will still suffer buffer overruns. Java has a very small interface to native libraries, and with good reason (also for portability of course).
Don't worry. Normally you would use something like this:
String s = new String(new byte[] { 0x41, 0x42, 0x43 }, "UTF-8");
To get "ABC". I haven't got a clue why you would want to do convert characters to or from *any* integer, unless you would like to write a ROT-13 codec. I laugh at languages that use *that* as a way to show their strength (and many do).
The book Java Puzzlers doesn't assume you would like to do something like that. The whole book is about getting a more complete understanding of the language, and not about getting better hacks for your money. That said, byte's should really have been unsigned, like this they are a pain in the back (who would use a byte to show any other value than a hexadecimal value in a program?)
As any platform + language, Java tries to do a lot of things. And like everything in this world, it is not perfect. Some of the problems could have been avoided (the rather unnecessary overloading of the operator &, meaning both && with both expressions evaluated and the bitoperand AND). Others could not. Don't forget that Java is pretty old (1985 if I am not mistaken), and when it was invented people tended to scream at you when you did anything like wasting a byte or a CPU cycle. And some things (like unsigned support) were explicitly left out due to simplicity.
Yes, Java could have been better (there *IS* a new language specification, so even Sun thought so) but there will always be corner cases enough to make puzzlers about. I thouroughly enjoyed reading it, though effective Java was even better.
Ok, so I started reading (well, I tried to between the various popup windows) and immediately found the one about a new Raptor drive. So I read into the article and it seems that they are talking about the RE2.
Differences: RE (raid edition) & RE2 specialize in "limiting the drive's error recovery time", and are specialized for raid configurations and reliability. Raptor on the other hand is speciallized in latency and reliability.
And that's when I stopped reading (and clicking away the - cannot find add server popups). Maybe it is a fast drive, but it has nothing to do with Raptor.
What if you claim to have forgotten it? What if you actually forgot it? I've got lot's of archives that have been encrypted, and I do not know the passwords anymore (mostly since the archives where only used for transportation). Sorry, but this might be very difficult to enforce. Actually, I don't want it to be enforced, but that's another matter.
You would still have to wait for a response of the system. Maybe not of a complete web page, but the application server still has to answer. Most if not all of a page can be cached, so what you are really waiting for is the business logic. And that will be as slow as it always has been. And AJAX obviously would also be routed through HTTPS. So speed is not that much of a difference. The user experience may be better nonetheless, of course - no flickering, or page setup, and no bs like the back button, which does not work anyway.
This is funny? I've got 4 official DVD's that won't run on my player, and 3 or 4 CD's that don't play in my computer. If *they* are not going to play fair with me, I sure as hell will return the favour. I bought an offical DVD, and all I got was a cheap skate menu and 10 minutes worth of adverts and warnings. Bleh.
Neh, he's a 40-something. Should be ok :)
java.io.Console? That's an API change, not a language change. Language changes would be concerned with the syntax or semantics of Java constructs, not with something inside a package.
Don't they still have degradation problems? I believe the color blue was still degrading rather rapidly. They are used, but mostly for smaller displays that are supposed not to last that long or where color reproduction does not have to be perfect (such as phones / mp3 players). At least they are being produced, which means they are not solely a "could be" technology. And then there are patents apparently...
http://en.wikipedia.org/wiki/OLED
For free:
http://en.wikipedia.org/wiki/Waveguided
Downloads of service packs, IE6.xxxx and MSDN have spiked. Terrible cries are heard all over town, where developers tried to get the development environment installed on their 256MB 4200 RPM company laptops.
.NET course. Thank god there will be a stripped down version.
Seriously, it took me some *hours*, way into midnight to get the environment installed for a 4 day
Pffft, only about .3 oo/o of warp 1. I'm not impressed.
And how many metres a second is this "slowly" exactly? Pfft, I bet it's gone before I see it.
Well, at least they have a stab at real time parsing. I guess you can get enough information from the beta versions to guess what's coming. It's sure to have some refactoring support (renaming classes and updating references and stuff). If you've worked with Eclipse or NetBeans (most popular Java IDE's) you'll know what's possible (real time links between tools and classes for instance). Unfortunately, at least in Beta-1, the functions were still pretty much in their infancy, and there were not many of them. Does someone have access to the latest versions, and tell us what has happened in this respect? The parse tree (abstract syntax tree) should be there, so putting some refactoring functions in there should not prove to be too difficult.
"Sure you need to be able to take a loss on it for a while, but the original poster is correct that you need to have customers driving your requirements from day one."
That's like saying that marketing push does not work. For generic products like this it is very unlikely that you get any customers buying it up front - it does not directly solve any problem. The problem here is that there is probably only a niche market. So you will have few people interested in it as well. That makes it hard to do a market push.