Comments on: Package Naming: To use “com.” or not http://almaer.com/blog/package-naming-to-use-com-or-not blogging about life, the universe, and everything tech Thu, 29 Jul 2010 17:37:13 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: barkas52 http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23490 barkas52 Wed, 05 Sep 2007 13:50:34 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23490 Barkas52147 Beliy Us Barkas52147 Beliy Us

]]> By: barkas52 http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23489 barkas52 Wed, 05 Sep 2007 13:47:13 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23489 Barkas52147 Beliy Us Barkas52147 Beliy Us

]]> By: SAMUEL http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23488 SAMUEL Sun, 08 Apr 2007 09:07:48 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23488 http://health86.narod.ru/index.html health insurance health insurance [url=http://health86.narod.ru]health insurance [/url] http://health86.narod.ru/index.html health insurance
health insurance
[url=http://health86.narod.ru]health insurance [/url]

]]> By: SAMUEL http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23487 SAMUEL Sun, 08 Apr 2007 09:06:28 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23487 louisiana home equity loan louisiana home equity loan

]]> By: Todd Huss http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23486 Todd Huss Tue, 31 May 2005 17:54:59 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23486 I stopped preceding package names a few years ago and have yet to run into a problem. Having the package name relate to a domain is silly and serves no practical purpose. If your company is called "Some Java Shop" then I would simply have somejavashop.com but use the namespace sjs.*. Preceding with com/net/org also unnecessarily lengthens the namespace forcing you to scroll sooner in your IDE's package navigator. I stopped preceding package names a few years ago and have yet to run into a problem. Having the package name relate to a domain is silly and serves no practical purpose. If your company is called “Some Java Shop” then I would simply have somejavashop.com but use the namespace sjs.*. Preceding with com/net/org also unnecessarily lengthens the namespace forcing you to scroll sooner in your IDE’s package navigator.

]]> By: Eelco http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23485 Eelco Fri, 27 May 2005 10:50:55 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23485 There is a difference though between accepted standards that leave nothing left for interpretation (like using camel case and starting your methods with javadoc comments) and those that do, like using a domain name. It could be the case that no domain is available. Or you're not sure whether you will be on the same domain the next year for a starting project. And whether a domain is cheap or not naturally is a relative statement. It might be for you, but not for someone this lives in India or China for example. There is a difference though between accepted standards that leave nothing left for interpretation (like using camel case and starting your methods with javadoc comments) and those that do, like using a domain name. It could be the case that no domain is available. Or you’re not sure whether you will be on the same domain the next year for a starting project. And whether a domain is cheap or not naturally is a relative statement. It might be for you, but not for someone this lives in India or China for example.

]]> By: Anonymous http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23484 Anonymous Thu, 26 May 2005 17:16:59 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23484 The conventions will only work if we uphold them. When you get into a name confilct with a vendor of yours then you'll end up renaming packages anyway so there is no gain there. That is, if not having your IDE refactor package names for you is a gain in the first place. For that matter, i think separating words in class names with _ is nicer, lets try that. Plus no indentation for me. And I also like my comments all at the end of each method. The conventions will only work if we uphold them.

When you get into a name confilct with a vendor of yours then you’ll end up renaming packages anyway so there is no gain there.

That is, if not having your IDE refactor package names for you is a gain in the first place.

For that matter, i think separating words in class names with _ is nicer, lets try that. Plus no indentation for me. And I also like my comments all at the end of each method.

]]> By: Charles Miller http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23483 Charles Miller Thu, 26 May 2005 13:09:41 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23483 Interestingly enough, Hibernate v1 was in the "cirrus.hibernate" package, I suspect because au.com.cirrustech.hibernate was just way too long already. There are also a bunch of Confluence classes in bucket.*, after the paved-with-good-intentions idea that if we put all our common code in there, it'd force us to come up with a good name for the package before we released it. :) Interestingly enough, Hibernate v1 was in the “cirrus.hibernate” package, I suspect because au.com.cirrustech.hibernate was just way too long already.

There are also a bunch of Confluence classes in bucket.*, after the paved-with-good-intentions idea that if we put all our common code in there, it’d force us to come up with a good name for the package before we released it. :)

]]> By: Eelco http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23482 Eelco Thu, 26 May 2005 08:25:57 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23482 That sounds pretty drastic. Do you refactor because you expect actual conflicts, or because you want to make this world a better place? And did you really refactor/delete JUnit, Ognl, Concurrent and Antlr to name of few? That sounds pretty drastic. Do you refactor because you expect actual conflicts, or because you want to make this world a better place?

And did you really refactor/delete JUnit, Ognl, Concurrent and Antlr to name of few?

]]> By: No one http://almaer.com/blog/package-naming-to-use-com-or-not/comment-page-1#comment-23481 No one Thu, 26 May 2005 03:59:44 +0000 http://almaer.com/blog2/package-naming-to-use-com-or-not#comment-23481 If people write code for com.mything and they don't own the domain mything.com, they are violating the spec. Domains are cheap. Why should we change the rule because some people violate the spec? If we get rid of the first level and I own mything.com and someone else owns mything.net, do I have to coordinate my classes with them to make sure we don't duplicate? If I download code and it violates the spec of reverse domain names, it either gets deleted or I refactor it. The bigger the package, the more time it takes to refactor, so it better provide a lot of bang for the buck, or it gets deleted. By the way, your comment box is the most annoying comment box anywhere. The cursor doesn't appear where the text is being typed. If people write code for com.mything and they don’t own the domain mything.com, they are violating the spec. Domains are cheap. Why should we change the rule because some people violate the spec? If we get rid of the first level and I own mything.com and someone else owns mything.net, do I have to coordinate my classes with them to make sure we don’t duplicate?

If I download code and it violates the spec of reverse domain names, it either gets deleted or I refactor it. The bigger the package, the more time it takes to refactor, so it better provide a lot of bang for the buck, or it gets deleted.

By the way, your comment box is the most annoying comment box anywhere. The cursor doesn’t appear where the text is being typed.

]]>