3 ms·

My personal evolution has gone from Sublime Text 3 to Atom to VS Code to Sublime Text 3. I've never been a heavy plugin user, mainly sticking to code highlight

My personal evolution has gone from Sublime Text 3 to Atom to VS Code to Sublime Text 3. I've never been a heavy plugin user, mainly sticking to code highlighting. The thing I really like is speed. Sublime Text rarely chokes on me. I love being able to type `cat some_one_gigabyte_file | subl` and getting it to open up with little difficulty. VS Code chokes on files of non-trivial size, and that was the thing I liked about it the least. For anyone wondering why I'd open up a 1 GB file in a text editor, I guess the answer is largely because it's convenient. Big log file? No problem. Huge CSV? No problem. Complete list of AWS pricing for every product in every region stored as JSON? No problem.

fartcannon 6y ago
Vim handles large csv files pretty good, as well. Not saying you should use it, just something that I found out years ago.
- PopeDotNinja 6y ago
  I've tried pure text editors, but they haven't really grabbed me, and my fingers are quite clumsy.
whowhatwhy 6y ago
i just use less for big files, convenience is a matter of taste
- xwdv 6y ago
  I don’t open big files at all. There’s no point. Files exist as data made to be transformed from one form to another. It is only worth looking at a file in its final form unless you are making some kind of edit. And even then, I make edits on large files through a series of commands, never opening the file. By thinking of files in this way, it becomes easy to create programmable tool chains for manipulation.
  - whowhatwhy 6y ago
    not everybody uses a computer for the same exact thing you use a computer for
    - xwdv 6y ago
      Of course, if they did there would be no point in making my comment, it would be redundant.
      - abbadadda 6y ago
        I think the issue with your original comment is with "there's no point," which is in effect invalidating the opinion of others.
  - TheColorYellow 6y ago
    What's your typical strategy for parsing something like a large text file for some relevant data? Suppose you could cat and grep, but what if you don't know what you're looking for?
tomxor 6y ago
I'm an atom user, and it chokes for the very same reason. However I also use vim for tweaking server side stuff, and use less by default whenever I want to read something (logs is an obvious one)... This is both for speed but also UX, i believe vim style navigation (which less basically gives you), is great for reading and searching - what I cannot stand though is doing more than small edits in vim, for development (and i mean code is flying around like crazy stage of development, not read for 1 hour and make tweaks), then I am fastest with the kind of flexibility atom provides. I know it can be tempting to have one tool for everything when it seems like the tools are supposed to be doing the same thing, but in my mind lean text editors tend not to compete with the big fat slow electron style editors - so just use them both, for their respective strengths.
- PopeDotNinja 6y ago
  I hear you on the value a text editor on the server side. I have picked up the basics of vi for this use case, but I ain't fast with it :)
stephc_int13 6y ago
Over time I've tried quite a few popular text editors, Notepad, Emacs, Vim, UltraEdit, Sublime Text, and of course VSCode. VSCode is surprisingly good for a Microsoft product and they had to do some crazy smart engineering work to make it not sucks while being built on top of Electron. That said, it still quite slow and memory hungry, I've gone back to Sublime 3 a few weeks ago and I am not coming back to VSCode.
cgrealy 6y ago
>> VS Code chokes on files of non-trivial size VS Code isn't really designed as a general purpose text editor. It's meant as a development environment. If MS choose to optimise the experience of 99% of the use cases (i.e. editing source code, which should never even approach 1GB), then that's the correct call IMO. >> For anyone wondering why I'd open up a 1 GB file in a text editor, I guess the answer is largely because it's convenient. I can completely appreciate the use of a text editor to open a massive log file, etc, I just don't think that's something VS Code is designed for. You can always use Sublime or Atom to open those files; while getting the nicer (IMO) dev experience with VS Code.
- fomine3 6y ago
  This. VSCode isn't Vim and vice versa.
0xkd 6y ago
> Complete list of AWS pricing for every product in every region stored as JSON Is this a hypothetical file that you mention or something you actually have? Asking since I have a use-case for this data and am interested in knowing how to get it. I have read AWS has APIs for pricing info - is that where you got the data from?
- PopeDotNinja 6y ago
  It's a thing. https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/using-ppslong.html https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2...

fartcannon 6y ago

Vim handles large csv files pretty good, as well. Not saying you should use it, just something that I found out years ago.

PopeDotNinja 6y ago
I've tried pure text editors, but they haven't really grabbed me, and my fingers are quite clumsy.

whowhatwhy 6y ago

i just use less for big files, convenience is a matter of taste

xwdv 6y ago
I don’t open big files at all. There’s no point. Files exist as data made to be transformed from one form to another. It is only worth looking at a file in its final form unless you are making some kind of edit. And even then, I make edits on large files through a series of commands, never opening the file. By thinking of files in this way, it becomes easy to create programmable tool chains for manipulation.
- whowhatwhy 6y ago
  not everybody uses a computer for the same exact thing you use a computer for
  - xwdv 6y ago
    Of course, if they did there would be no point in making my comment, it would be redundant.
    - abbadadda 6y ago
      I think the issue with your original comment is with "there's no point," which is in effect invalidating the opinion of others.
- TheColorYellow 6y ago
  What's your typical strategy for parsing something like a large text file for some relevant data? Suppose you could cat and grep, but what if you don't know what you're looking for?

tomxor 6y ago

I'm an atom user, and it chokes for the very same reason. However I also use vim for tweaking server side stuff, and use less by default whenever I want to read something (logs is an obvious one)... This is both for speed but also UX, i believe vim style navigation (which less basically gives you), is great for reading and searching - what I cannot stand though is doing more than small edits in vim, for development (and i mean code is flying around like crazy stage of development, not read for 1 hour and make tweaks), then I am fastest with the kind of flexibility atom provides. I know it can be tempting to have one tool for everything when it seems like the tools are supposed to be doing the same thing, but in my mind lean text editors tend not to compete with the big fat slow electron style editors - so just use them both, for their respective strengths.

PopeDotNinja 6y ago
I hear you on the value a text editor on the server side. I have picked up the basics of vi for this use case, but I ain't fast with it :)

stephc_int13 6y ago

Over time I've tried quite a few popular text editors, Notepad, Emacs, Vim, UltraEdit, Sublime Text, and of course VSCode. VSCode is surprisingly good for a Microsoft product and they had to do some crazy smart engineering work to make it not sucks while being built on top of Electron. That said, it still quite slow and memory hungry, I've gone back to Sublime 3 a few weeks ago and I am not coming back to VSCode.

cgrealy 6y ago

>> VS Code chokes on files of non-trivial size VS Code isn't really designed as a general purpose text editor. It's meant as a development environment. If MS choose to optimise the experience of 99% of the use cases (i.e. editing source code, which should never even approach 1GB), then that's the correct call IMO. >> For anyone wondering why I'd open up a 1 GB file in a text editor, I guess the answer is largely because it's convenient. I can completely appreciate the use of a text editor to open a massive log file, etc, I just don't think that's something VS Code is designed for. You can always use Sublime or Atom to open those files; while getting the nicer (IMO) dev experience with VS Code.

fomine3 6y ago
This. VSCode isn't Vim and vice versa.

0xkd 6y ago

> Complete list of AWS pricing for every product in every region stored as JSON Is this a hypothetical file that you mention or something you actually have? Asking since I have a use-case for this data and am interested in knowing how to get it. I have read AWS has APIs for pricing info - is that where you got the data from?

PopeDotNinja 6y ago
It's a thing. https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/using-ppslong.html https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2...