tiu

I seriously attempted getting into compilers last year before realising it is not for me but during those times it felt like people who want to be compiler devs are much much more in number compared to jobs that exist (yes exist, not vacant).

The common way to get going is to do LLVM. Making a compiler is great and all but too many people exist with a lox interpreter-compiler or something taken from the two Go books. Contributing to LLVM (or friends like Carbon, Swift, Rust) or atleast some usage experience is the way. The other side of this is doing GNU GCC and friends but I have seen like only one opening that mentions this way as being relevant. University level courses are rarely of any use.

Lastly, LLVM meetups/conferences are fairly common at most tech hubs and usually have a jobs section listing all requirements.

A few resources since I already made this comment too long (sorry!):

[0]: https://bernsteinbear.com/pl-resources/ [1]: https://lowlevelbits.org/how-to-learn-compilers-llvm-edition... [2]: https://www.youtube.com/@compilers/videos

Comment · 1 year ago

I am whole off the vim (&friends) trend but my 2c-

The helix situation is still miles better for up and running asap compared to dancing with files/lua on lazyvim. Just having to refer to docs to install a plugin, writing sane remaps etc eats up time. If you really just speedrun everything under an hour good for you. But for the rest, a lsp is a one package manager install away (even on windows scoop seems to have become the de facto), editing a toml is much easier than fiddling with the lua api/vimscript "just" to set some variables.

(Not a helix user though I have tried both vim/nvim/helix)

The only problem for me was the keybindings work good unless my vim instincts kick in where I become slow. The other one was lack of plugins.

Comment · 1 year ago

Yes I am talking about the help text in echo area. In newer versions apparently they only show a single line by truncating the eldoc-doc-buffer content(not super sure on this but they do truncate to 1 line). eldoc-echo-area-use-multiline-p does not work for that sadly.

Apparently this was changed only recently. I am surprised not many people know/talk about this change. Still looking for a fix.

Edit: I do agree it is annoying but for unknown codebases it helped me a lot.

Comment · 1 year ago

Slightly off topic here but do you (or anyone) happen to know how to get old Eglot behaviour back of showing entire types and parameter information instead of only the first line? It has been bugging me whole week and I cannot seem to find any fix for this.

Comment · 1 year ago