Readit NewsDeleted Comment
tiu commented on The Manuscripts of Edsger W. Dijkstra cs.utexas.edu/~EWD/... · Posted by u/nathan-barry
For the mathematically inclined, EWD717 and EWD765 have two really cool problems.
A while back someone posed EWD765 for an alternate solution, I don't recall if any other solution was found. That was my introduction to these.
I assume they mean those firms hire compiler engineers to work on the specific languages they use. Jane Street famously uses OCaml for pretty much everything. Not sure about Bloomberg, though a quick search shows that they have Bloomberg Query Language and Bloomberg Scripting Language, both proprietary.
Thanks!
Bloomberg also does use OCaml by the way, although probably not to the extent of Jane Street.
The comments are wildly fragmented in this thread. I agree with @torginus, the article has less and less of anything useful to people that want to get into compilers.
Anyways, the "Who .. hires compiler engineer?" section is fairly vague in my opinion, so: AMD, Nvidia, Intel, Apple, Google definitely hire for compiler positions. These hire fairly 'in-open' so probably the best bets all around. Aside from this, Jane Street and Bloomberg also do hire at the peak tier but for that certain language. The off beat options are: Qualcomm, Modular, Amazon (AWS) and ARM. Also see, https://mgaudet.github.io/CompilerJobs/
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
Helix boast itself as a no config tool, but you have to find a lsp, installl it, edit a toml to activate it. I dont think we can call that "config less".
Success would be something like LazyVim but without the nagging of updates each time you open it.
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.
Are you referring to the eldoc help text in the echo area at the bottom? Hard to know without more specifics, but maybe one thing to check might be the value of eldoc-echo-area-use-multiline-p. I have mine explicitly set to `nil` because I find the default eldoc behavior of constantly resizing the echo area to fit more information to be very distracting. I instead have a keybinding to call `eldoc` (an alias for `eldoc-print-current-symbol-info`) on demand, which opens a side split that shows the full symbol information.
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.
I think that is an accurate assessment! It's actually the reason I prefer it. I only wanted the ability to expand to treesitter text objects and then contract that selection if desired. I almost wrote it myself but then found that plug-in.
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.
tiu commented on (Cubyz)Voxel Sandbox Game written in Zig released. github.com/PixelGuys/Cuby... · Posted by u/tiu
No affiliations, just found it cool.
Release video: https://www.youtube.com/watch?v=jm_0nRQEn_o
[0]: https://www.youtube.com/watch?v=_qZliI1BKzI