Earlier quoted context omitted.
"not an official google product"
"Used by many teams across Google, running on billions of devices through multiple Google products"
still not appropriate to refer to it as "Google Ion" or even "Google's Ion"
Ion: Cross-platform OpenGL library from Google
11–20 of 46 posts
Re: Ion: Cross-platform OpenGL library from Google
#12Earlier quoted context omitted.
"Used by many teams across Google, running on billions of devices through multiple Google products"
still not appropriate to refer to it as "Google Ion" or even "Google's Ion"
"Copyright 2016 Google Inc. All Rights Reserved." Is in all of the files. It's hardly imprudent to call it Google's.
If it's not Google's, it's nobody's.
Could go for "Google publishes Ion, a cross-platform OpenGL abstraction."
Re: Ion: Cross-platform OpenGL library from Google
#13Earlier quoted context omitted.
still not appropriate to refer to it as "Google Ion" or even "Google's Ion"
"Copyright 2016 Google Inc. All Rights Reserved." Is in all of the files. It's hardly imprudent to call it Google's. If it's not Google's, it's nobody's. Could go for "Google publishes Ion, a cross-platform OpenGL abstraction."
There is a subtle and nuanced difference between simply owning the IP for something, and endorsing it as an officially supported product.
Re: Ion: Cross-platform OpenGL library from Google
#14Earlier quoted context omitted.
"Copyright 2016 Google Inc. All Rights Reserved." Is in all of the files. It's hardly imprudent to call it Google's. If it's not Google's, it's nobody's. Could go for "Google publishes Ion, a cross-platform OpenGL abstraction."
There is a subtle and nuanced difference between simply owning the IP for something, and endorsing it as an officially supported product.
That's right. But 'Google's' covers both cases. Evidence:
case a: Bernie Sanders' socks.
case b: Bernie Sanders' campaign promises.
You weren't confused by the nuanced difference in ownership and endorsement, but you learned more about the socks - and may be more interested in them - than if the name was omitted.
Re: Ion: Cross-platform OpenGL library from Google
#15This illustrates one of the serious issues with C++: numerous code files in a project authored relatively recently that are dedicated to basic application plumbing such as memory allocation/tracking and concurrency.
Its 2016. There are a number of performant cross-platform systems/languages that have good built-in facilities for these basic plumbing problems.
C++ is an outdated language, and the entire mindset and ecosystem is wasteful and constantly reinventing the wheel. C++ was still sort of relevant when I was playing with it in High School in 1994, but even then it was dated in most ways.
These are some very poor software engineering choices.
Educate yourselves about the Nim programming language.
Re: Ion: Cross-platform OpenGL library from Google
#16This illustrates one of the serious issues with C++: numerous code files in a project authored relatively recently that are dedicated to basic application plumbing such as memory allocation/tracking and concurrency. Its 2016. There are a number of performant cross-platform systems/languages that have good built-in facilities for these basic plumbing problems. C++ is an outdated language, and the entire mindset and ec…
Curious notion. C++ has perhaps the richest library set in the world.
Re: Ion: Cross-platform OpenGL library from Google
#17This illustrates one of the serious issues with C++: numerous code files in a project authored relatively recently that are dedicated to basic application plumbing such as memory allocation/tracking and concurrency. Its 2016. There are a number of performant cross-platform systems/languages that have good built-in facilities for these basic plumbing problems. C++ is an outdated language, and the entire mindset and ec…
I'm not exactly a fan of C++, but this isn't fair. What you're describing is more of a problem with this project's coding style than the language. Most of https://github.com/google/ion/tree/master/ion/base is covered either by the STL or Boost; most of what the C++ committee has been doing lately consists of trying to encourage people to not do what this project is doing (by improving the breadth of the standard library).
Re: Ion: Cross-platform OpenGL library from Google
#18This illustrates one of the serious issues with C++: numerous code files in a project authored relatively recently that are dedicated to basic application plumbing such as memory allocation/tracking and concurrency. Its 2016. There are a number of performant cross-platform systems/languages that have good built-in facilities for these basic plumbing problems. C++ is an outdated language, and the entire mindset and ec…
To provide performance improvements that you don't get using the built in facilities.
You don't have to write these things yourself, but if you're trying to eke out every last drop of performance (either at runtime or build time) then you have the option to do so.
Re: Ion: Cross-platform OpenGL library from Google
#19This illustrates one of the serious issues with C++: numerous code files in a project authored relatively recently that are dedicated to basic application plumbing such as memory allocation/tracking and concurrency. Its 2016. There are a number of performant cross-platform systems/languages that have good built-in facilities for these basic plumbing problems. C++ is an outdated language, and the entire mindset and ec…
"one of the serious issues with C++: numerous code files in a project authored relatively recently that are dedicated to basic application plumbing such as memory allocation/tracking and concurrency."
For some applications, manually tending to the basic plumbing is a necessity and not a burden. I.e high performance applications tend to be memory bouns.
I agree that C++ is not a right tool for every job and that as a language it has issues. But those issues are not about verbosity nor about manual memory management - the latter is rather a feature.
Re: Ion: Cross-platform OpenGL library from Google
#20I get "ERROR: gyp returned non-zero" while building. Missing dependencies? (Win10.)
I get the same error. Earlier in the error message it says generate_ninja_environment.gyp not found
It does not appear to be in the file system.