Basically, if I request the parts at the time I authorize their replacement, the mechanic must either provide them to me, or show them to me if the parts are required for coverage under waranty. All of the garages I've used have shown me the parts without a request to do so.
What, you expect someone on slashdot to read something that isn't explicitly linked to (only the test was linked in the article). I thought I was being a good denizen by actually reading one of the links in the article, even if there wasn't much on it.
So, I had to try this out and see it for myself. And, sure enough it rendered correctly. Then I started noticing the problems.
Here is a screenshot after "scrolling" using either the scroll wheel or up/down keys (despite the fact — as you point out — that there are no scroll bars).
And another one after a resize of the window. I restarted konq before doing the resize, so the issues aren't left over from the scrolling.
Also, note in the resized screenshot that the progress bar is stuck at 37%.
So, IMO, close, but not quite. However, close is better than most of the other browsers out there.
I not sure I agree with the statement that back SHOULD undo if possible. My concern is that this would essentially overload the back button to have two functions (navigation and application state). As a user, I would hate having to wonder if the site I'm browsing supports undo-on-back. However, as a user, I'd hate to have a new button to worry about.
As for improving the back/forward, refresh, and stop issues, I don't think they are broken enough to justify changing them. I don't think they could be made simpler (at least I haven't heard of any proposals for this). The current implementations are well known, and work well enough for the majority of users. The only thing I'd really like to see is a standard way for pages to disable the forward/back when appropriate, or to indicate that certain pages should not be added to the stack (such as pages that don't do anything but redirect you to the real page).
I think you are confusing back and unod. If you POST data to a website, hitting the back botton does not undo that post. In fact, browsers even warn you when you go back to a POSTed page, saying that you might redo (rather than undo) the operation, which may cause problems.
no, not fixed.....I finally DID get an OutOfMemoryError, with a fairly detailed message (compared to normal ones) and the VM exited. I tried it again with a counter on it, and it usually happens about 600,000 iterations into it....oh well. Not like its going to matter when I try to have a server app that runs for years on end:)
My favorite VM/class library shortcoming is the lack of a way to unmap mapped files. Relying on the GC works just fine, unless you are doing all of your processing using the mapped files, and don't ever put anything on the heap. Finally had to resort to using reflection, setAccessible(true), etc to manually unmap the files. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id =4724038
I have tried this on linux: Linux hostname 2.6.8-1-686-smp #1 SMP Mon Sep 13 23:02:39 EDT 2004 i686 GNU/Linux
using java: java version "1.4.2_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
I never receive OutOfMemoryError exceptions, and jvmstat (http://developers.sun.com/dev/coolstuff/jvmstat/) shows that the VM is collecting as it should (heap never grows, eden fills up, is collected, repeat).
How exactly are you determining that "It grows and grows!"?
actually...."fu" and "bar" are constants, there is no 'new String("fu")'. String's do not have an append() method, but StringBuffer does. String concatenation done with the "+" operator always uses an implicit StringBuffer object.
user@foo:~/tmp$ cat Foo.java public class Foo {
public static void main(String[] args) { String a = "fu"; String b = a + "bar"; } } user@foo:~/tmp$ javac Foo.java user@foo:~/tmp$ javap -c Foo.class // compiler version: 46.0
@source "Foo.java" public class Foo extends java.lang.Object {
The java.lang.reflect.AccessibleObject.setAccessible() method may allow you to invoke private methods you wouldn't otherwise have access to in Java. Of course, you still need the security managers permission to do this, so it is still more restricted than C++.
"Patient's would never be in danger of dying if someone used a cell phone in the units but they might interfere with the wireless monitoring causing faulty transmission of these signals.
If the cell phone signal can interfere with monitoring, that interference could cause real alerts to not go off. Also, a false alarm could result in improper care being given. Both of these could result in a preventable death.
I'm not saying either of these situations is likely, but avoiding cell phones altogether lowers the risk of either of these happening.
NIO != Non-blocking IO, it is New I/O -- http://java.sun.com/j2se/1.4.2/docs/guide/nio/
The non-blocking features of NIO are only a portion. NIO also includes (http://java.sun.com/j2se/1.4.2/docs/api/java/nio/ package-summary.html):
* Buffers, which are containers for data;
* Charsets and their associated decoders and encoders, which translate between bytes and Unicode characters;
* Channels of various types, which represent connections to entities capable of performing I/O operations; and
* Selectors and selection keys, which together with selectable channels define a multiplexed, non-blocking I/O facility.
"These are the men that do the real work in any engineering firm. They are the men that can do"
Do you supose they could be women as well?
Re:Does this work for non native speakers?
on
Can You Raed Tihs?
·
· Score: 1
I too live in the US, but I guess growing up in a British colony (Hong Kong) helped me figure it out:)
Re:Does this work for non native speakers?
on
Can You Raed Tihs?
·
· Score: 3, Informative
I think it is actually cheerio.
WordNet (r) 1.7 [wn]
cheerio
n : a farewell remark; "they said their good-byes" [syn: adieu,
adios, arrivederci, auf wiedersehen, au revoir,
bye, bye-bye, good-by, goodby, good-bye, goodbye,
good day, sayonara, so long]
I had the same experience with the 8.x series as you. 8.0, 8.1 and 8.2b2 worked great. I was very excited for 8.2 final to be released, installed it, and lots of things didn't work right.
I recently switched to RedHat 8.0 at work and was very impressed.....
I haven't tested this, but it looks as though the given cronjob will delete ~/trash, afterwhich the first rm command will move the file to the _file_ ~/trash, not the _directory_ trash. all subsequent ones will overwrite the previous file. modify like this if you want it to work:
I am not saying that it shouldn't be documented. I am trying to make the point that documenting it the code (presumably with comments) is not the proper place to do it. The code is for the compiler. Something as complicated as the linux implementation of the buddy system cannot be documented in the code and if you are looking there for it you are looking in the wrong place. You are better off understanding it prior to hacking the code.
As mentioned by someone earlier, explaining it to a compiler is very defined. Explaining it to a bunch of hackers from various backgrounds and native languages is nearly impossible.
If you aren't able to understand it from the code alone, should you really be hacking it? By having comments like that you raise the barrier to entry, thereby making it so that when you do understand it, you REALLY understand it.
I agree with everything you said. I was impressed with XP in the store, bought a copy for myself (full professional version -- ouch) and don't regret it one bit. However, I still boot into linux since that is what I am used to for personal use. For too long Microsoft released buggy/unstable/etc software and I found a solution that worked for me. Microsoft has finally produced a product that I am not afraid to use too much. That may change once the viruses get released, but for the time being, I am very impressed.
Slashdot Mirror
"The more fear you instill in spammers, the higher the chance they'll stop."
So, you are proposing we resort to a form of terrorism as a means of bettering our society?
Luckily, where I live (Washington state), we have laws to help with this:
/ RCW%20%2046%20.%2071%20%20CHAPTER/RCW%20%2046%20.% 2071%20.021.htm
http://www.mrsc.org/mc/rcw/RCW%20%2046%20%20TITLE
Basically, if I request the parts at the time I authorize their replacement, the mechanic must either provide them to me, or show them to me if the parts are required for coverage under waranty. All of the garages I've used have shown me the parts without a request to do so.
What, you expect someone on slashdot to read something that isn't explicitly linked to (only the test was linked in the article). I thought I was being a good denizen by actually reading one of the links in the article, even if there wasn't much on it.
Thanks for enlightening me on this.
So, I had to try this out and see it for myself. And, sure enough it rendered correctly. Then I started noticing the problems.
Here is a screenshot after "scrolling" using either the scroll wheel or up/down keys (despite the fact — as you point out — that there are no scroll bars).
And another one after a resize of the window. I restarted konq before doing the resize, so the issues aren't left over from the scrolling.
Also, note in the resized screenshot that the progress bar is stuck at 37%.
So, IMO, close, but not quite. However, close is better than most of the other browsers out there.
I not sure I agree with the statement that back SHOULD undo if possible. My concern is that this would essentially overload the back button to have two functions (navigation and application state). As a user, I would hate having to wonder if the site I'm browsing supports undo-on-back. However, as a user, I'd hate to have a new button to worry about.
As for improving the back/forward, refresh, and stop issues, I don't think they are broken enough to justify changing them. I don't think they could be made simpler (at least I haven't heard of any proposals for this). The current implementations are well known, and work well enough for the majority of users. The only thing I'd really like to see is a standard way for pages to disable the forward/back when appropriate, or to indicate that certain pages should not be added to the stack (such as pages that don't do anything but redirect you to the real page).
I think you are confusing back and unod. If you POST data to a website, hitting the back botton does not undo that post. In fact, browsers even warn you when you go back to a POSTed page, saying that you might redo (rather than undo) the operation, which may cause problems.
no, not fixed.....I finally DID get an OutOfMemoryError, with a fairly detailed message (compared to normal ones) and the VM exited. I tried it again with a counter on it, and it usually happens about 600,000 iterations into it....oh well. Not like its going to matter when I try to have a server app that runs for years on end :)
d =4724038
My favorite VM/class library shortcoming is the lack of a way to unmap mapped files. Relying on the GC works just fine, unless you are doing all of your processing using the mapped files, and don't ever put anything on the heap. Finally had to resort to using reflection, setAccessible(true), etc to manually unmap the files. http://bugs.sun.com/bugdatabase/view_bug.do?bug_i
I have tried this on linux:
) shows that the VM is collecting as it should (heap never grows, eden fills up, is collected, repeat).
Linux hostname 2.6.8-1-686-smp #1 SMP Mon Sep 13 23:02:39 EDT 2004 i686 GNU/Linux
using java:
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
I never receive OutOfMemoryError exceptions, and jvmstat (http://developers.sun.com/dev/coolstuff/jvmstat/
How exactly are you determining that "It grows and grows!"?
actually...."fu" and "bar" are constants, there is no 'new String("fu")'. String's do not have an append() method, but StringBuffer does. String concatenation done with the "+" operator always uses an implicit StringBuffer object.
/**
/**
user@foo:~/tmp$ cat Foo.java
public class Foo {
public static void main(String[] args) {
String a = "fu";
String b = a + "bar";
}
}
user@foo:~/tmp$ javac Foo.java
user@foo:~/tmp$ javap -c Foo.class
// compiler version: 46.0
@source "Foo.java"
public class Foo extends java.lang.Object {
* <init>
*
* stack 1
* locals 1
*/
@signature "()V"
public void <init>() {
@line 2
@aload 0
@invokespecial void java.lang.Object.<init>()
@return
}
* main
*
* stack 2
* locals 3
*/
@signature "([Ljava/lang/String;)V"
public static void main(java.lang.String[]) {
@line 5
@const "fu"
@astore 1
@line 6
@new java.lang.StringBuffer
@dup
@invokespecial void java.lang.StringBuffer.<init>()
@aload 1
@invokevirtual java.lang.StringBuffer java.lang.StringBuffer.append(java.lang.String)
@const "bar"
@invokevirtual java.lang.StringBuffer java.lang.StringBuffer.append(java.lang.String)
@invokevirtual java.lang.String java.lang.StringBuffer.toString()
@astore 2
@line 7
@return
}
}
The java.lang.reflect.AccessibleObject.setAccessible() method may allow you to invoke private methods you wouldn't otherwise have access to in Java. Of course, you still need the security managers permission to do this, so it is still more restricted than C++.
If the cell phone signal can interfere with monitoring, that interference could cause real alerts to not go off. Also, a false alarm could result in improper care being given. Both of these could result in a preventable death.
I'm not saying either of these situations is likely, but avoiding cell phones altogether lowers the risk of either of these happening.
NIO != Non-blocking IO, it is New I/O -- http://java.sun.com/j2se/1.4.2/docs/guide/nio/
/ package-summary.html):
The non-blocking features of NIO are only a portion. NIO also includes (http://java.sun.com/j2se/1.4.2/docs/api/java/nio
* Buffers, which are containers for data;
* Charsets and their associated decoders and encoders, which translate between bytes and Unicode characters;
* Channels of various types, which represent connections to entities capable of performing I/O operations; and
* Selectors and selection keys, which together with selectable channels define a multiplexed, non-blocking I/O facility.
"These are the men that do the real work in any engineering firm. They are the men that can do"
Do you supose they could be women as well?
I too live in the US, but I guess growing up in a British colony (Hong Kong) helped me figure it out :)
I think it is actually cheerio.
WordNet (r) 1.7 [wn]
cheerio
n : a farewell remark; "they said their good-byes" [syn: adieu,
adios, arrivederci, auf wiedersehen, au revoir,
bye, bye-bye, good-by, goodby, good-bye, goodbye,
good day, sayonara, so long]
I any language were to program itself, perl would be it.
no, this is a perfect example of a SINGLE bad software patent.
everyone is trying to keep their minds off war.
see http://etree.org for mailing lists about sites with free music to trade. Mirrors of the sites on this list are needed. Please consider it.
of course you are aware that NTFS write support is experimental and considered dangerous, right?
Of course I consider MS's ntfs implementation dangerous as well.
I had the same experience with the 8.x series as you. 8.0, 8.1 and 8.2b2 worked great. I was very excited for 8.2 final to be released, installed it, and lots of things didn't work right.
I recently switched to RedHat 8.0 at work and was very impressed.....
I haven't tested this, but it looks as though the given cronjob will delete ~/trash, afterwhich the first rm command will move the file to the _file_ ~/trash, not the _directory_ trash. all subsequent ones will overwrite the previous file. modify like this if you want it to work:
echo "* 4 * 1 *
I am not saying that it shouldn't be documented. I am trying to make the point that documenting it the code (presumably with comments) is not the proper place to do it. The code is for the compiler. Something as complicated as the linux implementation of the buddy system cannot be documented in the code and if you are looking there for it you are looking in the wrong place. You are better off understanding it prior to hacking the code.
As mentioned by someone earlier, explaining it to a compiler is very defined. Explaining it to a bunch of hackers from various backgrounds and native languages is nearly impossible.
If you aren't able to understand it from the code alone, should you really be hacking it? By having comments like that you raise the barrier to entry, thereby making it so that when you do understand it, you REALLY understand it.
I agree with everything you said. I was impressed with XP in the store, bought a copy for myself (full professional version -- ouch) and don't regret it one bit. However, I still boot into linux since that is what I am used to for personal use. For too long Microsoft released buggy/unstable/etc software and I found a solution that worked for me. Microsoft has finally produced a product that I am not afraid to use too much. That may change once the viruses get released, but for the time being, I am very impressed.