Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Zapotec Newsgroups: comp.lang.java.programmer Subject: Re: Death To Sub-Sub-Sub-Directories! Date: Fri, 06 May 2011 05:57:14 -0400 Organization: Azteca atlatl Lines: 22 Message-ID: References: <34va98-dgm.ln1@dagon.net> NNTP-Posting-Host: sq22xTww2sm6KI+ZPa+8iw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Forte Agent 2.0/32.652 X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3658 On 05/05/2011 8:35 PM, Daniele Futtorovic wrote: > Gosh, you're such a twat. Whereas I recognize the technical and engineering reasons for requiring the deeply nested long directory names, I also have to say I agree that they can be a pain in the butt, on two counts: 1. Typing long directory names or click-click-clicking to deeply-nested folders is a pain, and will be required if you aren't using an IDE like NetBeans or Eclipse -- and if you are, you just have the package/class hierarchy to click-click-click through to get to particular source files, instead, though at least you'll usually be working in one small area at a time, and when there are compiler errors or stack traces you can usually click in an IDE to jump directly from the message to a suspect line in a source file. Of course, the one-public-class-per-file thing (which has the same engineering reasons) then becomes annoying when it leads to a tab explosion in your editor. :) 2. On Windows, at least, it's not implausible to reach the path name length limit of the filesystem and run into even more headaches.