Actually, what is really surprising is that Google considered the project worth doing to get only 15-30% advantage vs GPU, if those numbers are accurate. In the best case, this buys roughly an 18 month advantage before GPUs get faster and the engineering has to be done all over again, or the project will just go the way of other Google abandonware. And in that brief window, do saved operating costs justify the sunk engineering and fabrication cost? I doubt it.
Now, on second look, this smells like a vanity project more than anything.
It takes considerable organizational effort to push an ASIC all the way through through the pipe from design to production. Even budgeting and staffing are nontrivial. The technology might not be earth shattering, but the engineering process is respectable. And who knows, the technology might be earth shattering. But probably not. It uses numerical methods, analog would be faster and more interesting.
Sorry to break it you, but "lit" is already cringy to actual teens, as opposed to teen wannabees lurking around Goog's cafeterias. And pretty much anything a Goog thinks is cool to teens, is actually cringy. Hangouts, for example.
How they got there makes perfect sense. That K&R chose to double down on such a messed up plan is demented. There are better alternatives grammatically, that are equivalently powerful and work just as well or better with LALR parsers.
C++ meets or beats C in all but a very few respects. Designated initializers is a really painful and stupidly short sighted omission. C++ has a wealth, even a surplus (see "most vexing parse") of initialization mechanisms, but none of them can do what design initializers do. Unfortunately, when converting C code to C++, this frequently results in maintainability regresses as code has to be converted to rely more on positional parameters... which you hope you have correct, but you don't always, and you hope the order of members never change, but it does.
Just because AMD can work with game developers to optimize code for the CPU does not necessarily mean that the game developers want to, or can even afford to, optimize their code for two different platforms.
That won't be necessary. For every game house now, Vulkan is a top priority. Invented by AMD, it works best on everything but especially, AMD.
The half-life of a game library is three months, if that, before the games go on the shelf to gather dust forever, or a faster machine comes out that makes performance quibbles silly. I've done my research, I'm sold on Ryzen. I'll be picking up a box as soon as they start moving through the channel, with a modest lag in case of motherboard kinks. This is not primarily for gaming, by the way, this is supposed to be a cost effective work horse. Being a great game machine is just a bonus. Oh, and Vulkan.
Amazon is a great idea, and a great contributor to the global economy. But Amazon is headed in the wrong direction: now taking it upon itself to censor the things you buy. This project needs a fork.
You know what I *would* pay for, though? A phone that didn't need a case, and that could be dropped from chest height with no visible damage.
I dropped my Nexus 4 from higher than that, onto cement, and I'm still using it. Landed solidly on one corner, now slightly chewed, damage barely visible. No massive shatter.
Already did. Another lame view, what is it trying to be, pretty on a 4 inch handset? Why does it waste so much screen space, just to show a title, short description and icon? Continues the theme of form over function. Where is a simple list of all projects, one per line? That should be the base functionality, then shovel on the shiny, if you must. Or not. The kind of person who matters to this site doesn't want shiny, they want deep and functional. Take a look at Github if that isn't clear.
Wow, what an annoying front end. I don't want to see bouncy balls and random projects, I want some kind of rational, useful view, perhaps by popularity, contribution rate, dependent projects? Something that does not scream PR. Something that does not scream style over substance. As PR, this just reminds of Google's sad record of trying to force its anti-copyleft views on the community. So far, every random project that popped up is Apache-licensed. Hey Google, Apache may be your favourite license, it is not necessarily ours. Looks like the same arrogant people running this PR effort as Google's previous abandonware project hosting. At least they seem to have stopped beating the dead Subversion horse, that is at least something. All the random projects that popped up for me point at Github.
If this page is indicative of how Google "does" open source, then Google has serious issues "doing" open source. Maybe Google should be less concerned about "doing" open source and more about participating in it.
As long as software is made with the same broken techniques, the same broken tools, by the same broken people, it will continue to be just as broken as proprietary software.
Slashdot Mirror
Actually, what is really surprising is that Google considered the project worth doing to get only 15-30% advantage vs GPU, if those numbers are accurate. In the best case, this buys roughly an 18 month advantage before GPUs get faster and the engineering has to be done all over again, or the project will just go the way of other Google abandonware. And in that brief window, do saved operating costs justify the sunk engineering and fabrication cost? I doubt it.
Now, on second look, this smells like a vanity project more than anything.
It takes considerable organizational effort to push an ASIC all the way through through the pipe from design to production. Even budgeting and staffing are nontrivial. The technology might not be earth shattering, but the engineering process is respectable. And who knows, the technology might be earth shattering. But probably not. It uses numerical methods, analog would be faster and more interesting.
Now? Not so much.
I wouldn't be so sure about that.
3D.
Sorry to break it you, but "lit" is already cringy to actual teens, as opposed to teen wannabees lurking around Goog's cafeterias. And pretty much anything a Goog thinks is cool to teens, is actually cringy. Hangouts, for example.
And please don't flatter yourself that you are the only one to have read the C grammar. I hope you also read your dragon book.
How they got there makes perfect sense. That K&R chose to double down on such a messed up plan is demented. There are better alternatives grammatically, that are equivalently powerful and work just as well or better with LALR parsers.
i think sociopath is more common.
synonym.
Left out a kind of terrible manager: The Complete Psycho. Unfortunately, too common.
If you don't get the concept of function pointers then sad for you and hopefully this isn't your day job.
What particularly don't you like about C syntax?
Function declaration syntax is demented, just to pull one thing off the top of a huge stack. Ever tried declaring an array of functions?
C++ meets or beats C in all but a very few respects. Designated initializers is a really painful and stupidly short sighted omission. C++ has a wealth, even a surplus (see "most vexing parse") of initialization mechanisms, but none of them can do what design initializers do. Unfortunately, when converting C code to C++, this frequently results in maintainability regresses as code has to be converted to rely more on positional parameters... which you hope you have correct, but you don't always, and you hope the order of members never change, but it does.
Just because AMD can work with game developers to optimize code for the CPU does not necessarily mean that the game developers want to, or can even afford to, optimize their code for two different platforms.
That won't be necessary. For every game house now, Vulkan is a top priority. Invented by AMD, it works best on everything but especially, AMD.
The half-life of a game library is three months, if that, before the games go on the shelf to gather dust forever, or a faster machine comes out that makes performance quibbles silly. I've done my research, I'm sold on Ryzen. I'll be picking up a box as soon as they start moving through the channel, with a modest lag in case of motherboard kinks. This is not primarily for gaming, by the way, this is supposed to be a cost effective work horse. Being a great game machine is just a bonus. Oh, and Vulkan.
Fair is only fair., even worthless trolls crave legitimacy. Propose: new "Verified Trailer Trash" tag
Amazon is a great idea, and a great contributor to the global economy. But Amazon is headed in the wrong direction: now taking it upon itself to censor the things you buy. This project needs a fork.
Message not received.
Last nail in the coffin for Apple... now Donald Trump owns one.
You know what I *would* pay for, though? A phone that didn't need a case, and that could be dropped from chest height with no visible damage.
I dropped my Nexus 4 from higher than that, onto cement, and I'm still using it. Landed solidly on one corner, now slightly chewed, damage barely visible. No massive shatter.
it's like how they used to stack Mac sales against every PC maker combined...
So unfair to Apple! sniff.
Click the grid View button on the upper right
Already did. Another lame view, what is it trying to be, pretty on a 4 inch handset? Why does it waste so much screen space, just to show a title, short description and icon? Continues the theme of form over function. Where is a simple list of all projects, one per line? That should be the base functionality, then shovel on the shiny, if you must. Or not. The kind of person who matters to this site doesn't want shiny, they want deep and functional. Take a look at Github if that isn't clear.
Self-masterbatory
Isn't that kind of redundant?
As opposed to mutual-masterbatory.
Wow, what an annoying front end. I don't want to see bouncy balls and random projects, I want some kind of rational, useful view, perhaps by popularity, contribution rate, dependent projects? Something that does not scream PR. Something that does not scream style over substance. As PR, this just reminds of Google's sad record of trying to force its anti-copyleft views on the community. So far, every random project that popped up is Apache-licensed. Hey Google, Apache may be your favourite license, it is not necessarily ours. Looks like the same arrogant people running this PR effort as Google's previous abandonware project hosting. At least they seem to have stopped beating the dead Subversion horse, that is at least something. All the random projects that popped up for me point at Github.
If this page is indicative of how Google "does" open source, then Google has serious issues "doing" open source. Maybe Google should be less concerned about "doing" open source and more about participating in it.
As long as software is made with the same broken techniques, the same broken tools, by the same broken people, it will continue to be just as broken as proprietary software.
Bitter, are we?
Anxious Albatross?