One Of AMD's Leading LLVM Compiler Experts Jumped Ship To Unity

[pal666]

somebody has to tell them that it would be hard to make c# faster than c++ by using llvm, because faster llvm will make c++ faster. same old song again: base your startup off php and then employ c++ programmers to write c++ tools to compile your shit a little faster. wouldn't it be smarter to hire c++ programmers to just write your shit in c++ ?

[pal666]

I may be mistaken, but I think Apple heavily pushes for C# for iOS.

you are. apple has no place for competitor's languages

[pal666]

C# is a Java Derivative..created by the Same guy who created or envisioned Java, James Gosling..

not sure where did you get that from, c# was created by the same guy who created turbo pascal and delphi, https://en.wikipedia.org/wiki/Anders_Hejlsberg

[pal666]

If your SCM sucks ass for storing binary files then yes that is true. But if it doesn't then storing the binary files in the same repo makes for a really streamlined process.

git doesn't suck ass for storing large binary files. they are just large and not diff-friendly, so they suck without any git help. with perforce it's masked because small text files suck with perforce too, so large binary files are not much worse

[pal666]

are you saying that documentation for the source code should also be kept outside the tree and not be coordinated with the evolving source code ?

documentation doesn't have to be binary. it can even be inside source files (in comments)

[bridgman]

Agree that the documentation doesn't *have* to be binary...

... but also saying that if the documentation *did* happen to be binary then it would still make sense to store it alongside the source files. Documentation in MS Word is pretty common for the closed source teams, as an example.

[Marc Driftmeyer]

you are. apple has no place for competitor's languages

Right. C/C++ have no place at Apple. Oh except that they do. Apple's ObjC/ObjC++/C/C++ and now Swift 5.x are all part of OS X/iOS/tvOS/iPadOS, etc.

[Marc Driftmeyer]

You are thinking about Objective-C that was the Apple choice #1 before Swift.

That was Apple's language first licensed from Brian Cox back in 1986 for the future NeXTSTEP and later purchased and evolved to ObjC 2.0., etc.

The creator of LLVM's pet project at Apple after a few clever enhancements to ObjC [which was never released for LLVM proper] was Swift. It's now gone well beyond his original ideas.

[smitty3268]

somebody has to tell them that it would be hard to make c# faster than c++ by using llvm, because faster llvm will make c++ faster. same old song again: base your startup off php and then employ c++ programmers to write c++ tools to compile your shit a little faster. wouldn't it be smarter to hire c++ programmers to just write your shit in c++ ?

You're misunderstanding what they're attempting to do with it.

Obviously c is turing complete and can do anything they bake into the burst compiler, but the idea is to make simple c#-like code which automatically does a bunch of different advanced compilation techniques. Some of which would be difficult to do in unrestricted C as well, for example they can mandate strict pointer aliasing and provide built-in support for an optimized math library, vector types, etc. - all things entirely possible in c/c++, but not out of the box unless someone goes through the effort of making it happen. The other thing they're doing is vastly restricting the C# language to take out all the slow bits - for example, they outright get rid of the entire garbage collector.

[pal666]

Right. C/C++ have no place at Apple. Oh except that they do. Apple's ObjC/ObjC++/C/C++ and now Swift 5.x are all part of OS X/iOS/tvOS/iPadOS, etc.

moron, c and c++ are not owned by microsoft, they are languages in which all world is built, including compilers for apple and microsoft languages. objc and swift are apple languages, that's why they are part of apple platforms. you've just proved my point.