Together by the window (by Iryna Viter)
Together by the window (by Iryna Viter) #arcane #leagueoflegends #vi #jinx #lolfanart #fanart #leagueart #leagueofart #leagueoflegendsart #leagueoflegendsfanart #LoLFanArt#vi
All these yougsters calling it “vim” LOL
kevin flynn canonically uses vi instead of emacs
Một lập trình viên vừa ra mắt ResumeAdapter, một công cụ AI giúp phân tích lý do CV của bạn bị từ chối và cách để khắc phục.
Chỉ cần tải lên CV và bản mô tả công việc (JD), công cụ sẽ ngay lập tức:
✅ Phân tích và chỉ ra các từ khóa, kỹ năng còn thiếu.
✅ Ước tính điểm ATS (hệ thống theo dõi ứng viên).
✅ Đề xuất các cải tiến để tăng cơ hội được phỏng vấn.
Đây là một công cụ hữu ích cho bất kỳ ai đang mệt mỏi vì gửi hàng trăm CV mà không nhận được phản hồi, đặc biệt là trong ngành công nghệ.
Tháng 10 này, Hồng Kông (Trung Quốc) là một điểm đến không thể bỏ lỡ cho những ai yêu thích du lịch.
🇭🇰 Khám phá những điều hấp dẫn tại đây:
🍜 Thưởng thức các lễ hội ẩm thực đặc sắc.
🙏 Viếng thăm những ngôi đền linh thiêng và cổ kính.
🌃 Chiêm ngưỡng cảnh sắc tuyệt đẹp của vịnh Victoria.
Đây là thời điểm lý tưởng để trải nghiệm và tạo nên những kỷ niệm khó quên tại "Hương Cảng".
#dulịch #HồngKông #dulịchHồngKông #tháng10 #vịnhVictoria #ẩmthực
#travel #HongKong #HongKongTravel #October #Vi
Korra and Vi's photoshoot: Another angle
Get the 🔞 pinup pack:
https://www.patreon.com/kowachi/shop/easter-2024-cross-over-pinups-pack-1064822?source=storefront
I'm repeatedly amazed by folks who reach for things like Microsoft Word or Google Docs first (or even OpenOffice, or the like), rather than "vi foo.txt"
Because reading, writing and modifying text has been a Solved Problem on computers for many decades now. and its hard to beat vi/vim (or the like) in terms of price, speed, efficiency, clarity, workflow composability and automation, rights preservation, privacy, security, offline-first/friendly, being immune from dark patterns like having your text being fed into LLM "training" (plagiarism and IP theft) ingest pipelines etc.
@jamie
So really it comes down to my view that #Vim is emulating #Vi, and so is #Emacs.
If you then look at the infrastructure around that,
Emacs is much more capable and less limiting in what you can do. That everything is a buffer means that it's buffer management is amazing.
The modes and key-bindings are awesome and it's all
pleasantly programmable in lisp.
Vi is a great editor, but there isn't much to it. It's a lightweight editor that works well. I think people confuse what is emulating Vi versus what is the application surrounding the emulator.
Emacs has, Evil, Viper, Meow, Boon and Meep modal editors. That says something too.
You’re right — pure #Unix minimalism couldn’t survive once systems became interactive and persistent. Early Unix assumed short-lived processes and text as shared state.
Once #editors became programmable and long-running, that boundary blurred. #Vi/#Neovim kept the file-centric DNA; #Emacs internalized it. Both descend from Unix, just different branches of its evolution.
@Zach 🇮🇱 🇺🇸
I did want to come back to my points that few actually follow the pure unix way any more, and that Vim isn't a small program by Unix standards.
As an indication(*), I've started terminal vim, neovim, and emacs -nw -Q processes, and KDE's system monitor reports the following:
nvim 3.0 MiB
vim 11.9 MiB
emacs 40.3 MiB
All of these are large or worse compared with original unix tools. I think McIlroy of 1978 would be horrified by all of them. Classic vi was 160kB or so later in its life. Bill Joy described ex as 'very large' in 1979.
They also all have scripting abilities and many packages of extensions available (neovim less so it seems, but it's also newer) None of them are really small, narrowly focused, or minimalistic by the standards of Unix in its first decade.
The classic Unix programming workflow as I understand it was to fire up an editor, edit, exit, recompile and retest.
I think the numbers of people who do that today are small. I think people using the vi family also fire up their editor and leave it running, and often controlling things from the editor.
(e.g. #^https://www.reddit.com/r/vim/comments/j33ow1/what_is_your_vim_workflow_like/ )
Also, once you've got a decent scripting language, you've already taken one step on the emacs path.
So compared with classic Unix ideas, they're all alike. They're all large, they're all scriptable, they all have libraries of plugins, and they all enable if not promote a form of use where you live in the editor, not the shell. The only real difference is that the vi-family communities haven't gone as far as writing extensions —but that's cultural, the software itself allows for this.
#unix #vim #vi #emacs
--
(*) what would be a fair comparison? There seem to be many possibilities. If one is trying to get the smallest possible memory footprint and is prepared to work for it, of course the size of emacs could be reduced, perhaps substantially.
But if we're less concerned with individual binaries and more 'how much do we need to get equivalent functionality' then we'd have to look at vim + mutt + tmux + fish + lynx + ...
I did want to come back to my points that few actually follow the pure unix way any more, and that Vim isn't a small program by Unix standards.
As an indication(*), I've started terminal vim, neovim, and emacs -nw -Q processes, and KDE's system monitor reports the following:
nvim 3.0 MiB
vim 11.9 MiB
emacs 40.3 MiB
All of these are large or worse compared with original unix tools. I think McIlroy of 1978 would be horrified by all of them. Classic vi was 160kB or so later in its life. Bill Joy described ex as 'very large' in 1979.
They also all have scripting abilities and many packages of extensions available (neovim less so it seems, but it's also newer) None of them are really small, narrowly focused, or minimalistic by the standards of Unix in its first decade.
The classic Unix programming workflow as I understand it was to fire up an editor, edit, exit, recompile and retest.
I think the numbers of people who do that today are small. I think people using the vi family also fire up their editor and leave it running, and often controlling things from the editor.
(e.g. #^https://www.reddit.com/r/vim/comments/j33ow1/what_is_your_vim_workflow_like/ )
Also, once you've got a decent scripting language, you've already taken one step on the emacs path.
So compared with classic Unix ideas, they're all alike. They're all large, they're all scriptable, they all have libraries of plugins, and they all enable if not promote a form of use where you live in the editor, not the shell. The only real difference is that the vi-family communities haven't gone as far as writing extensions —but that's cultural, the software itself allows for this.
#unix #vim #vi #emacs
--
(*) what would be a fair comparison? There seem to be many possibilities. If one is trying to get the smallest possible memory footprint and is prepared to work for it, of course the size of emacs could be reduced, perhaps substantially.
But if we're less concerned with individual binaries and more 'how much do we need to get equivalent functionality' then we'd have to look at vim + mutt + tmux + fish + lynx + ...
Korra and Vi's photoshoot
Full pic in my sh0ppe:
https://www.patreon.com/kowachi/shop/easter-2024-cross-over-pinups-pack-1064822?source=storefront
📰 NOS verkoopt uitzendrechten WK voetbal toch niet
Nanocomposite CNT với độ đàn hồi cao được sản xuất bằng công nghệ in 3D. CNT được phân tán đều trong chất lỏng photopolymer, tạo ra độ dẫn điện và độ đàn hồi cao. Các cảm biến TPMS có độ nhạy tuyến tính và hiệu suất đáng tin cậy, có thể tích hợp vào đế giày thông minh để theo dõi áp lực bàn chân. Công nghệ này mở ra nhiều cơ hội cho các ứng dụng điện tử linh hoạt. #CNT #Nanocomposite #3DPrinting #CôngNghệIn3D #CảmBiến #ĐiệnTửLinhHoạt #TinHọc #Technology #TechNews #VietnamTech #VietnameseTech #Vi
Das #Internet ist im Arsch ...
... wenn du auf den #Suchbegriff
drölfzigmillionen #Links zu einer KI-unterstützten #Tagebuch-App bekommst, aber nur einen zu
OK, ist natürlich total überzogen , aber wer, bitte, nennt eine Tagebuch-App Rosebud?
Und warum sollte diese KI-Unterstüzung benötigen?
Es gibt doch #Stift und #Papier und im #Notfall #vi
Ich bin definitiv zu alt für den Scheiß!
Das #Internet ist im Arsch ...
... wenn du auf den #Suchbegriff
#Rosebud
drölfzigmillionen #Links zu einer KI-unterstützten #Tagebuch-App bekommst, aber nur einen zu
#Citizen_Kane
OK, ist natürlich total überzogen , aber wer, bitte, nennt eine Tagebuch-App Rosebud?
Und warum sollte diese KI-Unterstüzung benötigen?
Es gibt doch #Stift und #Papier und im #Notfall #vi
Ich bin definitiv zu alt für den Scheiß!
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst