Live data from Hacker News

Apple's investment into Clangd and refactoring tooling

lists.llvm.org

81–83 of 83 posts

Re: Apple's investment into Clangd and refactoring tooling

#81
post #29

Earlier quoted context omitted.

It's a parsable format. Not some arbitrary stream of text, like what UNIX streams deal with...

"arbitrary streams of text" are also parsed. Line breaks matter, whitespace matters as well, and in some cases tabs and spacea matter.

There's a difference if I tell you: I will send you any kind of text at any time, it's your responsibility to deal with it and parse it accordingly to whatever it might be, than if I tell you, I'll send you JSON with this schema.

Re: Apple's investment into Clangd and refactoring tooling

#82

I'm glad to see that Apple is putting work into making their tooling better and easier to work with, but I'm still not clear on the benefits of this change. Would someone care to enlighten me? Currently, the benefits of libclang that I see are that I can easily drop it into a project without requiring a lot of dependencies, and I don't need to figure out how to get permission to run different processes and manage int…

The main problem with libclang is actually that it puts another abstraction on top of the AST that nobody really had time to maintain. That's not made better by the amount of work changing libclang requires just due to its backwards compatibility promises.

Re: Apple's investment into Clangd and refactoring tooling

#83
post #77
post #72

Earlier quoted context omitted.

It proves nothing, it's just about my original comment about Microsoft: > bringing the idea of language servers to the programming mainstream Lucid failed to do this, Microsoft succeeded.

The simplicity of you statement ignores what it meant to get a computer running Energize C++ properly in 1993 and an Electron (VSCode) app in 2017. Specially the money part.

The Microsoft Tablet PCs and the Apple Newton failed because the hardware wasn't there yet. C'est la vie...
Post reply on HN