6 ms·
Because it's a relatively large JavaScript library. Total line count is in the several hundreds of thousands. The file in question is for this class http://jgr
by davidjgraph 13y ago
Because it's a relatively large JavaScript library. Total line count is in the several hundreds of thousands.
The file in question is for this class http://jgraph.github.io/mxgraph/docs/js-api/files/view/mxGraph-js.html http://jgraph.github.io/mxgraph/docs/js-api/files/view/mxGra....
1) It's the main public API to the the library, there's no logical way to split it.
2) We'd have a couple of thousand, very-annoyed-cos-they-paid-quite-a-lot-for-it customers, frankly, go apeshit if we split the file and broke their app on the next update because we wanted to switch IDE...
- Touche 13y agoThis is a third party library or your own? Why can't you break it into multiple files and concat them with a build step?
- philliphaydon 13y agoHe could if he wanted to, but he doesn't want to have a maintainable library.
- nickdoesdesign 13y agoEven if it isnt a part of the normal build, a separate one that does that would help immensely. AMD makes this ridiculously easy, and grunt etc will help him even further.
- jmduke 13y agoTo clarify, you feel that using Eclipse is more work than breaking a file into multiple shards and setting up a build process to recombine them? (I'm not trying to be snarky and I apologize if the above comes off that way.)
- WalterSear 13y agoContemporary javascript development without a build step?
- Touche 13y agoWell yeah, if you have to use one specific editor because the file is larger than most can handle that should be a signal that the file is the problem. I for one think that developing a project in multiple files that can all be understood on their own is the only sane way to develop at all, regardless of editor choice.
- hawleyal 13y agoYou need modules