Well isn't that presumptuous.
Well, yes, I mean having to defend the use of an IDE is sort of unusual and I can only presume that someone who needed justification for standardised and IDE enforced code organisation hadn't dealt with a large project.
The project I'm working on right now is massive, and doing a quick check it shows that it has 15,737 code files, not including front-end resources like images or video.
And you edit that only in Sublime Text know what ever file does, and where every class is, etc?
From what you were saying I was right, and you were talking about something totally different, code navigation.
That's part of it, yes. But the organisation is important because it helps with refactoring, naming, maintenance, etc. Your perspective seems to be based on much smaller projects, even if you seem to be dealing with an obscenely large one. Our ERP is up to about 2 million lines and it's only 4,500 files, including HTML templates.
But in reality I probably navigate my code as quickly or more quickly than you do
I doubt that, I can ctrl + click any class or anything and find it's origin, or right click and find all usages of it anywhere, and the context, or do the same with alt + b if I don't want to leave my keyboard, and since all the code is indexed, it barely takes a second despite 2 million lines of code in this ERP.
It sounds like you're making these giant assumptions about Sublime Text based on your perception of its class of application, throwing it into a lump with "text editors" in your mind, when in reality it can be extended to do endless things in the same way that any "formal IDE" ( like Eclipse ) can.
I never said it wasn't a great editor, I said it was better than Notepad++ earlier. Eclipse is a piece of garbage, it's like a busted version of ... I don't even know, it's just bad.
I personally see having to rely on your IDE to help you figure out where other code lives as the digital equivalent of a training wheel.
This is from the perspective of someone who hasn't worked on a team with probably more than two people and really doesn't know what a large project is, at least that's my perception. This is sort of silly, honestly, the idea you could know hundreds or thousands of classes, especially if you work on multiple large projects. Not only that, why spend the extra effort to do that in the first place if you don't have to?
It's better to deeply understand your code, strategize its organization in a way that that problem is automatically solved and that you know the exact location of every piece of code by convention, and could see it being useful when you take over a large project from someone else and have to learn it quickly by exploration using that method, although in all honesty that'd be just as easy to do using Sublime's keystroke navigation features.
IRL enterprise doesn't work this way, sorry, it just doesn't, and it can't, otherwise large projects would never get done if everyone on the team had to create a special bond with all of the code. Personal projects that does happen though.
Right, which is why your IDE has nothing to do with your code organization, which was my point.
Yes, it does, because it keeps you on track and also the organisation of the code can tell your IDE about it as well, such as testing, class autoloading/including (for use in code), etc. You seem to believe that structure and names are meaningless beyond what you feel like, but that's not the case; certainly you can approach it that way, but then it becomes unmaintainable if the directory file structure and naming does not match name spaces and classes in some meaningful way.
It's just sort of weird to defend using an IDE and have it called training wheels, that's certainly not a professional perspective on development, and is basically out of line with probably much of the professional programming world; especially in team environments.
Is WebStorm written in Java? The choppy and awkward interface kind of feels like it was. If so that's very unfortunate.
Yes, I also consider that a problem, and it being a memory hog is a pretty big give away that it's Java. However, it's not that a problem if you've got enough system resources; I'd certainly rather see it written in C++.
Also missing the granular font-rendering and aliasing controls off the bat, and it's sad that you can't shrink and magnify the font size w/ Ctrl +/- like in a browser.
You can probably create a short cut for that, you can for damn near everything else. I suggest using it longer than a day, the problem is it takes time to really understand how to use it properly to get everything out of it, because you can approach it like a regular text editor and get no benefits at all; I've seen this happen.
Wow, there's a tangible delay between when you open a file and when the colorization and text-modification renders. That feels gross! And I'm on a 2015 3.9 Ghz quad w/ a PCIe SSD and 16GB. I'm not sure I could live with performance like this, it's slowing me down within a few minutes of firing it up.
That's really weird, my specs are almost the same and I don't experience that sort of latency. Sometimes on larger files, first view, there's a lag as it renders in the background, but that's substantially large files, and that's why the single responsibility principle is your friend.