I guess I’ve activated to post random stories about #vim lately ;-) There’s so much hate for it, especially from some members #neovim community, so I just want to show that there is also other side of the story. In other words, there are people who pick “just” Vim purely based on technical advantages.

It is a bit over year since Bram Moolenaar died so I guess this is also good timing in that sense (RIP) ;-) Remembering that by migrating my vim files to vim9script 🍾

Just learned that #Servo is independent project these days because #Mozilla laid off all of its staff in 2020. #Rust was originally developed specifically for this project. So I guess we have now three competitive web engines instead of two: #Gecko, Servo and #WebKit. servo.org #rustlang

On #macOS, I’ve found that best way for me to manage #vim installation specifically is to just download the dmg and install pkg given that it auto-updates and contains all the command-line versions (instead of using homebrew or macports):

$ ls -1 /Applications/MacVim.app/Contents/bin
gview
gvim
gvimdiff
gvimtutor
mview
mvim
mvimdiff
mvimtutor
view
vim
vimdiff
vimtutor
xxd

https://youtube.com/watch?v=bcs_orvo9j4

One major advantage of x86: we already know its worse in detail. This article proves that at least and it is an asset. Unknown unknowns are a bitch.

When comparing micro-architectures in general so that it makes any possible sense, at minimum comparative analysis of advantages of disadvantages would be appropriate.

Not sure if I dare to say this but what a load of nonsense.

Just to name an example, the standard for RISC-V with MMU is unfinished and ambiguous to the point that how a SiFive CPU's do stuff is more of a guideline than the specs. The commercial weight if AFAIK more in the compute core area where you just "fork" the hardware description and make it your own.

Not slandering RISC-V per se, I actually like many thing in that ISA, just saying that it is not *even* comparative to x86 and ARM at this point of time. E.g. OpenMIPS would have been (if there had been any analysis of other ISA's than x86).

https://hackaday.com/2024/03/21/why-x86-needs-to-die/

@cuchaz I've moved on macOS to Safari and probably move to GNOME Web on Linux. The key element is that I've engineered myself out of browser sync feature and extensions by migrating all my passwords to https://www.passwordstore.org/. I still use browsers password manager for convenience and cache but not as an archive. I.e. they are not synced and I can delete all the passwords any time, as pass has the archive.

Other than I don't really care what the browser is as long as it is fairly modern (e.g. WebKit based). Safari and GNOME Web are reasonable, and I'd think that as they are not the selling product, they also minimize the harm, as it is not intended to make profit in any significant figures.

That said, not sure if I would trust Edge on Windows ;-)

@seve_py I bought Sublime Text exactly because I wanted a GUI editor for meetings instead of trying to make vim look like such (instead of vscode because I prefer paying with money over paying with soul) :-) Does the job for that purpose.

@seve_py modern open source = sdks and forks. Great, that is what I call moving forward.

@seve_py It's really a wider disease in modern software. Everything tries to be a platform that does nothing :-) I'd like to see more software where developers pick and make choices, and less like a generic software development platform.

@seve_py If I had to care about performance of plugins in vim in the first place, it would lead me to a conclusion that I'm using wrong editor in the first place :-) I only care functionality and performance of the stuff that is built in.

I mean why be the king of lua dependency hell, when you could have just as well installed vscode and zed, and call it a day. It being TUI interface does not help that much anymore of the editor being ubiquitous at that point.

For me people who pick vscode feel more like common sense people than 90% of neovim users. I get the pragmatic reasoning for that even tho I use an archaic editor.

@mallory @thcrt never gets out of date and applies to kubernetes: https://www.joelonsoftware.com/2001/04/21/dont-let-architecture-astronauts-scare-you/

Interactive external commands is also one reason that made me return back to regular #vim, in addition to working remotes out of the box and the fact that I use only a few plugins, which carry out somewhat trivial tasks where e.g. performance is not a factor.

Interactive external commands is a useful feature from time to time because it allows to leverage privileges for an external command.

For example, this will result an error in #neovim instead of a password prompt: :r !sudo ls.

The next time you're worried that you're not doing great at your job, just remember that someone probably made six figures to change HBO to HBO Max to Max.

Just published the #ASG2024 schedule! Lots of good stuff, and at least one terrible talk that nobody should attend.

Early bird tickets are also still available - but not for long - go grab them while they last!

https://all-systems-go.io/

Another step forward towards making the compiler omniscient:
https://discourse.llvm.org/t/rfc-overflow-idiom-exclusion/80093
(Excluding "test for overflow" code patterns when using the unexpected overflow checker in Clang.)

Built a site with a PDF resume (see /about) using Jekyll and Typst:

https://jarkko.codeberg.page/

Woodpecker CI puts everything together for every push building both site and the resume:

https://codeberg.org/jarkko/pages/src/branch/main/.woodpecker.yml

And resume made with Typst is a separate project, which can be updated independently while publication is taken care by the site project: https://codeberg.org/jarkko/resume

This is convenient…

#codeberg #woodpecker

I just realized that #vim has these in the distribution:

❯ ls -1 /usr/share/vim/vim91/pack/dist/opt/
cfilter
comment
dvorak
editexisting
editorconfig
justify
matchit
shellmenu
swapmouse
termdebug

Thus, I can shrink my plugin list a bit:

diff --git a/.vimrc b/.vimrc
index a66c03b..383ea80 100644
--- a/.vimrc
+++ b/.vimrc
@@ -35,13 +35,14 @@ nnoremap <silent> <C-l> :nohl<C-R>=has('diff')?'<Bar>diffupdate':''<CR><CR><C-L>
 nnoremap <silent> <leader>lcd :lcd %:p:h<CR>:pwd<CR>
 nnoremap <silent> <leader>n :set number!<CR>
 
+packadd! comment
+packadd! editorconfig
+
 if !empty(globpath(&rtp, 'autoload/plug.vim'))
   call plug#begin()
   Plug 'ap/vim-buftabline', { 'as': 'buftabline' }
   Plug 'catppuccin/vim', { 'as': 'catppuccin' }
-  Plug 'editorconfig/editorconfig-vim', { 'as': 'editorconfig' }
   Plug 'kaarmu/typst.vim', { 'as': 'typst' }
-  Plug 'tpope/vim-commentary', { 'as': 'commentary' }
   Plug 'vim-scripts/git_patch_tags.vim', { 'as': 'git_patch_tags' }
   call plug#end()
 endif

Leaving only:

if !empty(globpath(&rtp, 'autoload/plug.vim'))
  call plug#begin()
  Plug 'ap/vim-buftabline', { 'as': 'buftabline' }
  Plug 'catppuccin/vim', { 'as': 'catppuccin' }
  Plug 'kaarmu/typst.vim', { 'as': 'typst' }
  Plug 'vim-scripts/git_patch_tags.vim', { 'as': 'git_patch_tags' }
  call plug#end()
endif

#holiday activities

I think #hmac #encryption series for #TPM went well, and also think that enabling it by default only for x86-64 at first was the right call. The recent issue on power architecture proved it. It is better increase scope per request by architectures instead. #linux #kernel

@ljs sorry, umh ? :D Not opposing, just deciphering...