It’s just that there are lots of stuff that don’t really work (out of the box) with Wayland systems, an example being getting an IME with ibus/fcitx5 to work in browsers.
It’s just that there are lots of stuff that don’t really work (out of the box) with Wayland systems, an example being getting an IME with ibus/fcitx5 to work in browsers.
I agree with you. It’s a neat design idea to make things a bit more maintainable perhaps, but it’s just annoying to program with.
The something else is called kanji, and are very complicated characters stolen from China with many meanings and pronunciation. Learning Japanese is very 楽しい (it is really)
I’m also German, and our beautiful language being compared to java feels like an insult to me.
Strength in diversity, I guess
Nah it’s been invented, but working for many decades without all the crypto shit
Wait, you can’t use your phone in a bus? Ot do you mean talk on the phone in a bus, because that would be understandable?
But it gets the job done, chaotic good
Ig you sigkill a process, that process will no longer get CPU time, as far as I know. So if it didn’t work, you shot the wrong thing.
Peak editing with vim/neovim
Are you talking licenses or certificates? Because if certificates are not automated that’s not a problem with certificates but with administration.
Good to know, thanks
I found open-ssl to be much harder to use. Do you just manually make new certificates with the CA in CLI?
At some point it’s good to let things die
In that case, i recommend step-ca, which is a certificate authority server with acme support anyone can self host. The setup took a while but it’s been running for months now without problems for me.
No proper CA should give out a certificate for an IP, that’s a no go by the common rules.
You are making prejudiced, generalized, assumptions and presenting them as facts.
You are at best naive if you think people use vim and a terminal instead of “better graphical alternatives” (which there are none of if you’ve really gotten into vim/emacs/whatever). And we don’t do it to seem hardcore (maybe we are, but that’s a side effect). Software in the terminal is often more simple to use, because it allows chaining together outputs and has often simpler user interfaces.
The second paragraph is word salad. Developers should name their shit properly regardless of editor and it’s quite simple to have a professional dev setup with ‘intellisense’ and auto complete in neovim. In fact, vim/neovim and I assume emacs too have much more features and flexibility of which users of IDEs or vscode wouldn’t so much as think of.
I assume your prejudice comes from the fact that vim is not a “one size fits all no configuration needed” integrated development environment (IDE) but rather enables the user to personalize it completely to their own wishes, a Personalized Development Environment. In that regard, using one of the “better graphical tools” is like a mass produced suit while vim is like a tailor made one.
Just let people use what they like. Diversity is a strength.