Earlier quoted context omitted.
Especially with the Community Edition of VS making it really easy for pretty much anyone to get access to VS. I like GCC and everything but I will be happy to leave it behind if I am honest. The politics are just too damn much for me these days. GCC should be about building a great compiler collection for the world but politics plays too big a part in it as seen with the whole AST debate going on again because of RMS…
for you and people like you of course . people whos care about software freedom of course choosing GCC.
LLDB debugger is coming to Windows
31–37 of 37 posts
Re: LLDB debugger is coming to Windows
#32Earlier quoted context omitted.
for you and people like you of course . people whos care about software freedom of course choosing GCC.
Except the ones who want to do things that are 'forbidden' by RMS. Those people have no choice but to use LLVM. For example, a lot of academic work on compilers and languages can't easily use GCC, neither can people wanting to make more sophisticated tooling.
See also Linux kernels in most Android phones. That's exactly what GCC authors do not want.
Re: LLDB debugger is coming to Windows
#33Earlier quoted context omitted.
for you and people like you of course . people whos care about software freedom of course choosing GCC.
Except the ones who want to do things that are 'forbidden' by RMS. Those people have no choice but to use LLVM. For example, a lot of academic work on compilers and languages can't easily use GCC, neither can people wanting to make more sophisticated tooling.
Could you explain why not? GPL-incompatible release requirements on the code produced? Admittedly it's not a very accessible codebase either.
Re: LLDB debugger is coming to Windows
#34Earlier quoted context omitted.
Except the ones who want to do things that are 'forbidden' by RMS. Those people have no choice but to use LLVM. For example, a lot of academic work on compilers and languages can't easily use GCC, neither can people wanting to make more sophisticated tooling.
a lot of academic work on compilers and languages can't easily use GCC Could you explain why not? GPL-incompatible release requirements on the code produced? Admittedly it's not a very accessible codebase either.
Re: LLDB debugger is coming to Windows
#35Earlier quoted context omitted.
Probably not, actually. But it also depends on what you count. Google definitely has more people working directly on LLVM itself than Apple (At Google, they almost all work for me, and I know the numbers for Apple). If you start to include related open source projects (like clang, etc), the numbers get closer, but then you have things like all of the Android related open source stuff that gets worked on (Renderscript…
Google and Apple used to be friendly and working on the same open source project named WebKit. Looking at the precedent, it is not unreasonable to consider such things, even if everything is okay in LLVM at the moment.
In any case, i'm still not sure what we are "considering" here.
Re: LLDB debugger is coming to Windows
#36Earlier quoted context omitted.
Especially with the Community Edition of VS making it really easy for pretty much anyone to get access to VS. I like GCC and everything but I will be happy to leave it behind if I am honest. The politics are just too damn much for me these days. GCC should be about building a great compiler collection for the world but politics plays too big a part in it as seen with the whole AST debate going on again because of RMS…
for you and people like you of course . people whos care about software freedom of course choosing GCC.
Re: LLDB debugger is coming to Windows
#37Earlier quoted context omitted.
Isn't Linux support in libc++ still not 100%? I'm using libc++/c++14 on a new project and I love it! Much better than my last experience with c++ (c++98). I was worried about using libc++, but I recently found a great VPS provider which lets you install from an ISO so I can run FreeBSD in production. I no longer have any need for Linux. Develop on OSX, deploy on FreeBSD.
It's not quite 100%. There are still a few outstanding faults, mostly due to different localization assumptions made by the underlying libc. http://libcxx.llvm.org/results.Linux.html