101 reputation
1
bio website
location
age
visits member for 1 year, 10 months
seen Apr 15 at 19:24

Sep
22
comment Is the Java package name convention flawed?
1) I never said it's a problem that needs to be solved; I just said it's what they're trying to solve for. 2) The OP already answered your question as to who wants strong guarantees against namespace clashes: library developers. 3) Yes, obviously the convention only guarantees uniqueness for as long as you own the domain.
Sep
21
comment Is the Java package name convention flawed?
@Allon Guralnek: I never said the .NET style doesn't facilitate local uniqueness and constancy. I said it don't guarantee universal uniqueness, in contrast to the Java style. I moreover said this is because the latter is not trying to solve for constancy (let alone verbosity), but rather solely for global uniqueness. I'm not saying the .NET style is bad; I'm just saying it's solving for a different problem.
Sep
20
comment Is the Java package name convention flawed?
@dr Hannibal Lecter: Cf. docs.oracle.com/javase/tutorial/java/package/namingpkgs.html
Sep
20
comment Is the Java package name convention flawed?
As pointed out in @Thorbjørn's answer, the problem the Java naming convention solves for is not guaranteeing constancy but rather guaranteeing uniqueness. Note the Microsoft convention guarantees neither.
Sep
20
awarded  Supporter
Sep
20
comment Is the Java package name convention flawed?
+1 "You are looking at the solution to a different problem."