fetchSize (around 1000), as the default fetch size caused up to 60× slowdown from network overhead.
PhysicalConnection.removeFromTemporaryLobs.
fetchSize (around 1000), as the default fetch size caused up to 60× slowdown from network overhead.
PhysicalConnection.removeFromTemporaryLobs.
Date / SimpleDateFormat are mutable and not thread-safe.List.of(...).contains(null) throws NPE.Collections.unmodifiableList is only a view - changes to the original list still show through.Integer.parseInt(null) throws NumberFormatException instead of NullPointerException.Arrays.sort(a, null) silently falls back to natural order. Objects.requireNonNull(some);
final A a = some.getA();
Objects.requireNonNull(a, "explanation");
validate(a);
final B b = a.getB();
Objects.requireNonNull(b, "explanation");
b.process(param1);
some..ensureNotNull()//
.getA()..ensureNotNull("explanation")..ensureValid()//
.getB()..ensureNotNull("explanation")//
..process(param1..ensureNotNull());
Can you be friend with this kind of dead code? In this particular subject my opinion is slightly different from the general. I can agree that in the ideal programming world there is no need to use dead code, but in reality there are situations when it's good to consider this solution as appropriate.
Wikipedia: 0.999... |
Searching a solution we often forget about the problem behind it. I'm familiar with the wrong focusing on 'how' instead on 'why', and what's more I've seen people doing the same mistakes as well. For example, let's just look at law regulations as synonym of complication paired with uncleanness. However, I'll drop that subject and introduce the similar problem occurring in maths. Do not expect any great proof, because I'll do that to explain it as simple as possible.
Czyż Internet Explorer nie służy do przeglądania internetu z twojego komputera i vice versa?
Mogliśmy jakiś czas temu zaobserwować miły gest ze strony Mozilli wspierający osoby które chcą zwiększyć bezpieczeństwo ich produktu (patrz: Refresh of the Mozilla Security Bug Bounty Program). Zaciekawiony tymże faktem poszperałem więcej w poszukiwaniu informacji o bezpieczeństwie naszych przeglądarek...
Ciekawostką jest raport firmy CERT z 2005r (ich pierwszy nawiasem mówiąc) - jednakże jego jakość jest wątpliwa i bardziej tu pasuje nazwa 'zestawienie'. Taki współczynnik jak ( Liczba luk / Popularność ) jest nie tyle nietrafiony co wręcz błędny. Otóż im większa szansa zysku z odkrytej luki tym częściej i szybciej zostanie ona wykorzystana, a w internecie ilość przekłada się przecież w bezpośredni sposób na zysk. Tak więc, moim zdaniem, powinno być raczej ( Liczba luk * Popularność ). Ten sam mechanizm działa też w drugą stronę: firmy mające małą liczbę użytkowników są znacznie mniej podatne na ataki.
Kolejny post dotyczący naszego Polskiego "zaścianka". A mianowicie chciałbym napomknąć jak wygląda egzystencja nas informatyków w kontekście przepisów prawnych oraz strachu przed naszymi umiejętnościami.
Basically, I do not like GridBagLayaout, but from my point of view it's the most effective way to build and maintain GUI. So before explaining my point of view, let's eliminate other path.
Each of Java programmer knows how exhausting a handing exception can be. So sooner on later he/she founds the situation when he/she exactly knows that he/she is handling the exception that will never occur. Some thoughts about this can be found here.
It's high time to clear doubts about: The '!' logical-complement operator. With little help of someone who can express himself more clearly, subject should be easier to follow.
Some time ago I used to know all operators priorities in C++, using a minimal number of braces resulted with a quite compact code in logical cases. It was really easy to read that again, but only for me, what I did not see as a problem. When I started to work on the same code with others there were no turn back and I had to make conditions more readable...
Maybe I'm weird but I really do not like syntax for this operator.
I like enum-s more than most people do.
They are really nice to use and synchronization-safe. But as I found, they have their limits as well.
After generating 1,8Mb Java code for one enum Eclipse dying after most try of refactorization ;), Java was not happy at all about it as well with error:
The code for the static initializer is exceeding the 65535 bytes limit