Re:Tiobe Index: Go language at all time high and in the top 10
by rbehrends on Sunday July 09, 2017 @09:27AM
(#14729629)
C++ templates are a very idiosyncratic way of doing parametric polymorphism, and the C/C++ compilation model is even more idiosyncratic. You cannot make general statements about parametric polymorphism based on that.
Re:Tiobe Index: Go language at all time high and in the top 10
by Arzh on Sunday July 09, 2017 @10:52AM
(#14729971)
Everything I said was based on my experience with C++, I was making pointed statements not general ones.
Re:Tiobe Index: Go language at all time high and in the top 10
by kerkeslager on Sunday July 09, 2017 @09:24AM
(#14729618)
It's 2017. C++ was invented in 1984.
Just because a 33-year old language has problems doesn't mean Go is the best solution.
Re:Tiobe Index: Go language at all time high and in the top 10
by Arzh on Sunday July 09, 2017 @10:57AM
(#14730004)
I find that go is the best solution for my problems
Re:Tiobe Index: Go language at all time high and in the top 10
by yazr on Sunday July 09, 2017 @11:52AM
(#14730298)
Can you please comment on this code base ?
Which tools / build chain r u using ?
Did the actual compile take 1hr or the full CI/test ?
Did u try use any parallelization ? I am curious because i am working on a "smart" parallelizer builder
Re:Tiobe Index: Go language at all time high and in the top 10
by Arzh on Sunday July 09, 2017 @01:56PM
(#14730862)
Yeah each build would take about an hour, 4-5 hours for the whole CI/test to get finished. It was crossed complied so there was an MSBuild and a gcc build. It was sone in serial since we didn't want to waste time building the release if the testing or QA builds failed.
I've also had a large (5M+ lines) C++ project that would need to be complied 3-4 times to do things like CI and automated testing. So each build taking 1-1.5 hours, which is not crazy, because of rebuilding code that is static 99% of the time mean that it is worth it to me.