Run away from Jonathan Blow, as of today he was full rant mode on language server and similar stuff including on people that think this is a acceptable stuff, notably Hacker News audience. FYI, I 150% disagree with his useless rants.
Cquery: highly-scalable, low-latency language server for C++
41–50 of 74 posts
Re: Cquery: highly-scalable, low-latency language server for C++
#42Wow! I consider myself lucky that I practically do not have to deal with C++, but if I were a C++ kind of person, right now I would deeply appreciate how much hard work goes into a tool like this. [1] In order to be any good, it has to be even more clever than the compiler, at least in a few ways. And I have a hunch that in the field of programming languages that are used these days, C++ is probably not the easiest o…
standard C 4 lyfe
Re: Cquery: highly-scalable, low-latency language server for C++
#43Wow! I consider myself lucky that I practically do not have to deal with C++, but if I were a C++ kind of person, right now I would deeply appreciate how much hard work goes into a tool like this. [1] In order to be any good, it has to be even more clever than the compiler, at least in a few ways. And I have a hunch that in the field of programming languages that are used these days, C++ is probably not the easiest o…
It is really odd that most of the people who complain c++ are the people who never or seldom use it.
Re: Cquery: highly-scalable, low-latency language server for C++
#44Author here! Wasn't quite ready to post to HN yet since cquery is still in development, and I plan to eventually publish on the vscode marketplace so using cquery should be as simple as using the existing C/C++ extension. Let me know if you have any questions.
Does this support Objective-C++? If not, do you have any plans to implement support for it?
Re: Cquery: highly-scalable, low-latency language server for C++
#45This project seems to be very similar to clangd. It is also similar to YouCompleteMe, though YCM does not support LSP yet. How does Cquery compare to those projects in terms of features?
In particular, should it be considered as an alternative to clangd? Could it make sense to combine efforts between clangd and Cquery?
Re: Cquery: highly-scalable, low-latency language server for C++
#46Earlier quoted context omitted.
Some advice if you do decide to learn C++: there has been a steady stream of improvements in standard C++ the past 8 years (C++11-17), and some (Bjarne Stroustroup, Herb Sutter, others) promote it as a better starting point for beginners under the name 'Modern C++'. From: https://msdn.microsoft.com/en-us/library/hh279654.aspx "[...] Over the years, features have been added to the language, together with highly-tested…
C++ as a language has certainly modernized, but its tools are still stuck in the 90's. Contrary to the increasingly bizarre rationalizations offered up by its proponents, CMake and friends are not acceptable package managers or build tools, at least to those of us who have used newer languages. I don't need a build tool assumes all projects are unique snowflakes in need of their own hand-crafted build system; I just…
Depends on which tools we are talking about.
QtCreator and Visual C++ (with UWP), are only now allowing what was already quite comfortable with C++ Builder in the 90's.
As I posted in another thread, Lucid and IBM had quite advanced environments based on Lisp and Smalltalk environments, that failed on the market due to hardware requirements and heavy price tags.
Other than that, I feel your pain.
C++ is no longer my daily tool, but I still enjoy using it, and would also like to have better tooling available for when I do.
The anti-modules discussion post-CppCon is a good example of what you are stating.
Re: Cquery: highly-scalable, low-latency language server for C++
#47Author here! Wasn't quite ready to post to HN yet since cquery is still in development, and I plan to eventually publish on the vscode marketplace so using cquery should be as simple as using the existing C/C++ extension. Let me know if you have any questions.
Does this support Objective-C++? If not, do you have any plans to implement support for it?
I have not tested it, but it should be a relatively straightforward to get working. Feel free to file an issue on github.
Re: Cquery: highly-scalable, low-latency language server for C++
#48This project seems to be very similar to clangd. It is also similar to YouCompleteMe, though YCM does not support LSP yet. How does Cquery compare to those projects in terms of features? In particular, should it be considered as an alternative to clangd? Could it make sense to combine efforts between clangd and Cquery?
At the moment, clangd and ycm are very similar projects; they are very limited compared to cquery. clangd and ycm support code completion, diagnostics, fixits, and goto declaration (but not definition), whereas cquery supports references, derived types, callers, etc. Basically, if the feature requires knowledge across multiple translation units, clangd/ycm do not support it.
cquery is designed to support very large projects, so it makes very specific design decisions w.r.t. the data model, indexing pipeline, and multithreading model. I hope clangd can match the performance - but so far every project I've seen simply does not run nearly fast enough on a code-base the size of Chrome/ChromeOS.
Re: Cquery: highly-scalable, low-latency language server for C++
#49Use c++ on a daily basis. I think the direction the language is going is really really troublesome. It was a mistake to follow the boost’s lead. At this point language is more or less a clusterfuck. While python peeps are saving the world here on this dark side of the world we wrestle with move semantics. Simplicity and beauty of C is long gone.
Re: Cquery: highly-scalable, low-latency language server for C++
#50Use c++ on a daily basis. I think the direction the language is going is really really troublesome. It was a mistake to follow the boost’s lead. At this point language is more or less a clusterfuck. While python peeps are saving the world here on this dark side of the world we wrestle with move semantics. Simplicity and beauty of C is long gone.
I used to use C++ a lot for a mixture of reasons. I avoid it like the plague now, because I'm not confident that anyone completely understands the semantics of a non-trivial C++ program.
Even if I did, the cognitive overhead of this stuff detracts from real programming.