zlacker

[parent] [thread] 6 comments
1. eastbo+(OP)[view] [source] 2025-01-29 07:04:16
I never get asked. It’s obvious. Just open a 4Gb log file as a developer.

All my developers have it.

replies(3): >>sparta+g1 >>noname+B5 >>james2+xR1
2. sparta+g1[view] [source] 2025-01-29 07:13:58
>>eastbo+(OP)
I only keep sublime text around for opening +500mb dumps, everything else was moved to vscode years ago.

Anything more than 500mb and I switch to less for instant reading/searching and sed for instant find/replace.

3. noname+B5[view] [source] 2025-01-29 08:06:38
>>eastbo+(OP)
VSCode is just as fast for opening 4 GB log files
replies(2): >>tasuki+ia >>tbriud+8s
◧◩
4. tasuki+ia[view] [source] [discussion] 2025-01-29 09:00:21
>>noname+B5
Vim is not slower!
replies(1): >>noname+4j
◧◩◪
5. noname+4j[view] [source] [discussion] 2025-01-29 10:39:02
>>tasuki+ia
I agree and I do use Vim for all quick edits I need. Just wanted to challenge the idea that Sublime Text was better than alternatives in the space of GUI text editors
◧◩
6. tbriud+8s[view] [source] [discussion] 2025-01-29 12:22:52
>>noname+B5
It is not just about the opening, it is about the searching. Vim is fantastique, although VSCode got faster over time too. Grep is fantastic too (I am not trying to out-hardcore here ... I mean specifically for log file searching not actual coding!). Splunk is better though, but sometimes you are local, and sometimes you don't have a few mill to burn.
7. james2+xR1[view] [source] 2025-01-29 19:00:17
>>eastbo+(OP)
Absolutely. I actually just made my own syntax for highlighting the log files in Laravel (Monolog): https://github.com/james2doyle/sublime-log-syntax
[go to top]