Originally posted by johnc
View Post
Announcement
Collapse
No announcement yet.
Apple Announces A New 3D API, OpenGL Competitor: Metal
Collapse
X
-
-
You do realize Metal is for Apples A7's at this point and very likely the coming A8. AMD has nothing to do with this, Metal is simply a software solution to performance on A7 based hardware.
Originally posted by DMJC View PostI see a LOT of AMD Users being very butthurt over AMD's poor quality engineering team. Open source drivers are getting there and the performance is coming with the engineering. But NVIDIA has always had good OpenGL support and it's fast. Maybe people should stop blaming OpenGL and start blaming their crap GPU vendor. Intel has never been into making hard-core GPU chips. But they are actually making pretty reasonable progress making decent entry level cards. AMD has had years to get this stuff right, and doesn't hire anywhere near enough people to get this job done. It's time to stop launching 50 different API's and start pressuring AMD to put real resources into getting the job done right. I know this will come off as trolling to a lot of people. But come on, they've had more than a decade to get GL support correct. Intel gets it done first try. They just aren't making super fast GPUs. AMD obviously has a software engineering resourcing problem. I think Apple's metal is their latest attempt to make up for AMD's engineering shortcomings, else it's just Apple's way to avoid porting any legacy API code to iOS/Mac OSX.
Comment
-
Originally posted by jimbohale View PostThe reason they're doing Swift is likely just because they're not content with Objective-C anymore (realistically, who else besides Apple used it on a large scale).
It's not similar at all to Go structurally, it's more of a functional language where functions are first-class, much like Scala. It uses one file instead of two (header & object are the same thing). It might *look* similar to Go to a non-Go or a non-Swift programmer, but it's not even remotely close. Again, far more similar to Scala than to Go. Either way, I suspect their primary reason for Swift is that they wanted to make it easier than Objective C. It's very well documented, and interoperability is good between the two.
NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO. NO.
WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG.
Right now, OpenGL ES from iOS to Android is not very similar. Yes, it technically has some of the same method names but realistically they're DIFFERENT PROGRAMMING LANGUAGES. Think about that for a moment. Yes, that means entirely different because Objective C and Java are not very similar. At the moment it's *already* very difficult to port from one to the other, it's not as easy as you make it sound.
You are everything that is wrong with the tech world, and please just take a break until you realize what is true and what is false. You're hurting everyone by making these stupid comments and assumptions.
Comment
-
Originally posted by berolinux View PostExcept Android is in no way tied to Java. Use the NDK and you can write C and C++ code, and you're already a lot closer (and yes, Android has a C OpenGL ES library).
Hack the NDK a little and you can write Objective-C code (Edit the rebuilt scripts that come with the NDK to use --enable-languages=objc when building gcc, then rebuild. Bundle the libobjc runtime library with your app. And yes, I've actually done this, so I know what I'm talking about) - and suddenly porting iOS code that uses standard APIs like OpenGL ES becomes an easy and quick thing (iOS code that heavily relies on Cocoa Touch is a different matter).
That's why Apple is scared of standard APIs.
Comment
-
Originally posted by wizard69 View PostAll this crap about lock in is just silly to me. A 3D API is the least likely thing to cause significant porting issues.
...ohh, wait...
But it's good to have the Lt. Official Apple Fanboy on hand to straighten us all out.
Comment
-
Originally posted by johnc View PostYeah, that's why there are just as many OpenGL games as Direct3D games on the PC.
...ohh, wait...
But it's good to have the Lt. Official Apple Fanboy on hand to straighten us all out.
What you've said is a fallacy. Direct3D generally works better on Windows which is the dominant platform on computers and is much easier to program for. I don't believe real programmers care very much about which 3D api they use, I think most real programmers learn them all (or the relevant ones such as OpenGL* or Direct3D, at the moment) and will use whichever is most suited. I think that this is a non-issue that non-3d programmers need to fuck off. You should focus on the real issues, such as whether or not Swift is going to be open sourced (which we don't know yet, that's a WAY bigger deal than Metal). If it is, then good, otherwise that's a much bigger example of vendor lock-in than Metal. An entire programming language and base APIs vs a single 3D api that's written specifically for a minority of devices.
Comment
-
Originally posted by jimbohale View PostSomeone says you're wrong and that instantly makes them a fanboy.
Comment
-
Originally posted by johnc View PostHe's not a fanboy because he said I'm wrong, he's a fanboy because he posted 20 straight messages extolling the amazing impeccable flawlessness of Apple. And this isn't the first time he's done that.
All I'm saying is that you guys need to stop focusing on what Apple is doing in their little corner of their minor market share on their phones and focus on what actually COULD have an effect, which is Swift. You guys should focus on it being open source. It has a FAR larger impact, and it runs on OS X as well as iOS. It's much harder to port a Swift application to C or C++ than it is to port an Objective-C application although admittedly it's still harder, a C++ application is going to be structured similarly to an Objective-C application so it's doable in steps while Swift entirely changes quite a few things and things like functions as a first class citizen don't have replacements, same with random things like it's mapping functions. Personally I hope Swift is open sourced and it winds up overtaking C++, but that's just me. It has nothing to do with me being an Apple fanboy because I'm not, it has everything to do with me using Swift and using C++, and much preferring Swift because I respect when something is good regardless of who it is from.
Comment
Comment