And it had to do no less than thoroughly rape C++ with a preprocessor only to accomplish what Smalltalk accomplished naturally.
Hold your horses there. I don't much like the MOC either, but it's a small blemish compared to the massive rape GTK perpetrates with C. And the deep rooted crappiness of GTK shows through to the end user. Compare a QT file dialog to GTK for example, just a tiny tip of the iceberg.
Meanwhile creating bindings to Gtk+, whatever its deficiencies in manual C programming are (admittedly that really sucks), is way easier, not least because of C++'s ABI's piss-poor interoperability compared to C's ABI, hence the much higher avalability of higher language bindings for Gtk+.
You're making that up, you obviously haven't done it yourself. I have, so I know you're full of crap. Anybody who has coded in both GTK and QT knows exactly why Lubuntu is switching to QT.
What is the value add of the Ubuntu part? Honest question. I appreciate that Ubuntu has popularized the Linux desktop, bringing it to millions of users who otherwise would otherwise be stuck on Windows or Apple, but since I went back to Debian, I've been happier. No more having update-manager doing dark and mystical things, then crapping out in the middle of upgrading to a new version for example. And what the heck is a "software channel"?
For now, running both Debian and Ubuntu on different workstations and laptops, but gradually phasing out all the Ubuntus for Debians, which is just easier to maintain. Other than update-manager vs just dist-upgrade I hardly notice any difference.
When LXQT lands in Debian I will certainly try it and see how it stacks up against KDE, it's just an apt install away.
GUI apps on Linux generally work well regardless of which desktop you run them under, and which desktop is "native" for them. This is largely because of freedesktop's work on standardizing the relatively few desktop APIs needed, like tray docking and notifications.
what they're saying is: lxqt is a fucking hog, even worse than gtk based lxde, and it won't run on lower-end hardware anymore.
You wish. But my experience with QT contradicts your claim, it is quite light on its feet. Better than GTK by every measure including performance, especially being actual OO instead of a hot mess of C abuse.
There was no business case for introducing Metal instead of going with Vulkan
Other than that when Apple released Metal, Vulkan wasn't publicly released yet.
But Apple was a prominent member of Kronos group and could easily have done a Vulkan alpha release, or glNext as it was called. Instead, Apple abused its Kronos membership to learn Vulkan design details and rushed out an incompatible API a few months ahead of Vulkan. How sleazy can you get! And how sweet Apple got smacked on the head by Autodesk.
Whatever they were already using, nobody was screaming for a change, especially not a proprietary lock-in change. Lets not make stupid mistakes because of being in a rush over a fictitious deadline. But you know perfectly well that Apple concocted the Metal scheme in hopes of creating lock in, and not because of any timing thing. Instead, they succeeded at creating a lock-out scheme as any fool could have predicted.
I note that IOS game revenue is now behind Android, just one more number that Apple cultists used to love trotting out and can't any more. What's the next fallback? Apple makes more profit on games than anybody? Until that isn't true either.
Trump has done more to protect your job from Indians than any president since Carter.
And from Canadians. British, Germans, French, Asians, Africans, Australians... But Russians and Nokos are welcome. Oh, about your job. Sorry the hats are made in China now.
There is a memory code waiting to be discovered, much like the genetic code. The idea that long term memory is recorded in synapses is already crumbling, it appears instead that the synapses are under the control of RNA within the cell, which invites the question: how does memory map to the four letter genetic code?
It is obvious that a few billion nucleotides in the human genome is far too little to encode the innate abilities we are born with. Think of it in terms of game model assets: how detailed a world can you model with 10 GB of data? Compress it, do whatever you like. The world we are born with is way more detailed than that. So there must be other channels of inheritance than DNA, with far more total volume than DNA. How does RNA encode a memory symbol, or a relationship between symbols? Somebody is going to get a Nobel for that.
Bullshit. Vulkan is now available on over 40% of Android devices, which by itself makes it the second most widely distributed graphics API in the universe
I don't know about *that*
You do know about that. Vulkan ships on Nougat and later, which is over 40% of active Android devices. So, more than all the Windows PCs in the world. Only OpenGL ES is more widely available than that, available on 100% of Android devices.
Could have used Vulkan, did not need to create a home rolled API to do the same thing less flexibly, leaving out important features, and not used by anybody outside of Apple.
They COULD have used Vulkan, IF it had Existed; but it wasn't even a Final SPECIFICATION
Could have used Vulkan, did not need to create a home rolled API to do the same thing less flexibly, leaving out important features, and not used by anybody outside of Apple.
Well governed open source projects don't get forked.
There are whole operating systems that have been forked. For example BSD, OpenBSD, NetBSD, etc.
You know nothing of FreeBSD. For example DragonflyBSD started after a food fight that ended up with revoking one of the core dev's commit access.
Apple wasn't sufficiently responsive to Google's needs so Google forked it, simple.
HAHAHAHAHA. [Citation Needed]
Sweet, your concept of intelligent discourse marks you as an Apple employee. Then you criticize other people's posts like an asshole. Again, how Apple of you. Chrome's multiprocess architecture was awkward to develop in Webkit. Apple could have moved Safari in the same direction but chose not to. So bam, fork.
You said " now used by Safari and nobody else." That is factually untrue.
You niggle. Close enough to describe the reality. Would you prefer I said "mass migration away from Webkit"? There, said it.
My assertion. Mark it down. I said the same about Metal, mark that down too. Do LLVM too while you're at it, though I think that of the three it has the best chance of avoiding a fork for now.
So you have no evidence for anything that you've said then. Then I can discount your posting as mere imagination.
How imaginative of you, feel free to paste a gold star on your nose.
Apple has no credible business case for Metal, which is a bespoke 3D API. I thought that was clear.
The same results or better (geometry shaders!) could have been accomplished with Vulkan. There was no business case for introducing Metal instead of going with Vulkan, which can do the same but with less flexibility and no standarization. You can tattoo that on your Apple ass.
Apple will never get back the community karma it lost by rolling its own Vulkan-like API and will eventually be forced to support Vulkan anyway to avoid more developer defections. Enjoy.
Bullshit. Vulkan is now available on over 40% of Android devices, which by itself makes it the second most widely distributed graphics API in the universe, second only to OpenGL ES, available on 100% of Android devices. Vulkan is supported by numerous PC titles. Most AAA game engines support Vulkan, the others have it on the way. Unity Engine supports Vulkan on Android, Linux and Windows. Likewise Unreal. ID tech 6 was the AAA engine to support Vulkan and is widely licensed. Steam's Source2 engine supports Vulkan. Nintendo Switch supports Vulkan (and OpenGL 4.5). Looks like not dead.
Here is an Android Vulkan demo of Unreal Engine from two years ago. That is 100% real time on a Galaxy S7. You can see why it got traction.
Apple can and should participate in the group that develops the standard. To do otherwise would make Apple seem like a bunch of assholes. Oh wait, I'm starting to understand. You are from Apple right? You certainly are an asshole, so that would fit.
Read your own link. Count the number of discontinueds. It's basically down to just Apple and Adobe. That happened really fast.
Apple will eventually give up backporting Blink improvements and repurpose their engineers officially as Blink contributors,
Do you have proof of that or that your assertion
My assertion. Mark it down. I said the same about Metal, mark that down too. Do LLVM too while you're at it, though I think that of the three it has the best chance of avoiding a fork for now.
Apple has no credible business case for a bespoke 3D library...
You mean beside Metal?
Apple has no credible business case for Metal, which is a bespoke 3D API. I thought that was clear.
users donâ(TM)t have to know about Metal, they can still get the benefits.
Huh? That is actually an argument for not using metal. Since users don't know about Metal they dion't give a flying fuck about it, and can get more benefit from Vulkan, which is lower level and more efficient, and which developers actually do care about.
The good thing about Vulkan is that it is cross-platform. The bad thing is that it's very finicky to use.
That's far from the only good thing about Vulkan. It also succeeds dramatically at killing off CPU load and removing the CPU as a render bottleneck. It was designed to suit highly skilled 3D developers for building engines and libraries. Anybody not capable of coding a 3D engine themselves should program to the engine or library API. That's the way everybody wants it except Apple, who wants a dumbed down API that doesn't excel at anything and instantly shoves Apple to the back of the crossport list. If you can see the point of that then you have more imagination than me.
Slashdot Mirror
And it had to do no less than thoroughly rape C++ with a preprocessor only to accomplish what Smalltalk accomplished naturally.
Hold your horses there. I don't much like the MOC either, but it's a small blemish compared to the massive rape GTK perpetrates with C. And the deep rooted crappiness of GTK shows through to the end user. Compare a QT file dialog to GTK for example, just a tiny tip of the iceberg.
Meanwhile creating bindings to Gtk+, whatever its deficiencies in manual C programming are (admittedly that really sucks), is way easier, not least because of C++'s ABI's piss-poor interoperability compared to C's ABI, hence the much higher avalability of higher language bindings for Gtk+.
You're making that up, you obviously haven't done it yourself. I have, so I know you're full of crap. Anybody who has coded in both GTK and QT knows exactly why Lubuntu is switching to QT.
What is the value add of the Ubuntu part? Honest question. I appreciate that Ubuntu has popularized the Linux desktop, bringing it to millions of users who otherwise would otherwise be stuck on Windows or Apple, but since I went back to Debian, I've been happier. No more having update-manager doing dark and mystical things, then crapping out in the middle of upgrading to a new version for example. And what the heck is a "software channel"?
For now, running both Debian and Ubuntu on different workstations and laptops, but gradually phasing out all the Ubuntus for Debians, which is just easier to maintain. Other than update-manager vs just dist-upgrade I hardly notice any difference.
When LXQT lands in Debian I will certainly try it and see how it stacks up against KDE, it's just an apt install away.
GUI apps on Linux generally work well regardless of which desktop you run them under, and which desktop is "native" for them. This is largely because of freedesktop's work on standardizing the relatively few desktop APIs needed, like tray docking and notifications.
what they're saying is: lxqt is a fucking hog, even worse than gtk based lxde, and it won't run on lower-end hardware anymore.
You wish. But my experience with QT contradicts your claim, it is quite light on its feet. Better than GTK by every measure including performance, especially being actual OO instead of a hot mess of C abuse.
There was no business case for introducing Metal instead of going with Vulkan
Other than that when Apple released Metal, Vulkan wasn't publicly released yet.
But Apple was a prominent member of Kronos group and could easily have done a Vulkan alpha release, or glNext as it was called. Instead, Apple abused its Kronos membership to learn Vulkan design details and rushed out an incompatible API a few months ahead of Vulkan. How sleazy can you get! And how sweet Apple got smacked on the head by Autodesk.
Whatever they were already using, nobody was screaming for a change, especially not a proprietary lock-in change. Lets not make stupid mistakes because of being in a rush over a fictitious deadline. But you know perfectly well that Apple concocted the Metal scheme in hopes of creating lock in, and not because of any timing thing. Instead, they succeeded at creating a lock-out scheme as any fool could have predicted.
I note that IOS game revenue is now behind Android, just one more number that Apple cultists used to love trotting out and can't any more. What's the next fallback? Apple makes more profit on games than anybody? Until that isn't true either.
Trump has done more to protect your job from Indians than any president since Carter.
And from Canadians. British, Germans, French, Asians, Africans, Australians... But Russians and Nokos are welcome. Oh, about your job. Sorry the hats are made in China now.
There is a memory code waiting to be discovered, much like the genetic code. The idea that long term memory is recorded in synapses is already crumbling, it appears instead that the synapses are under the control of RNA within the cell, which invites the question: how does memory map to the four letter genetic code?
It is obvious that a few billion nucleotides in the human genome is far too little to encode the innate abilities we are born with. Think of it in terms of game model assets: how detailed a world can you model with 10 GB of data? Compress it, do whatever you like. The world we are born with is way more detailed than that. So there must be other channels of inheritance than DNA, with far more total volume than DNA. How does RNA encode a memory symbol, or a relationship between symbols? Somebody is going to get a Nobel for that.
Bullshit. Vulkan is now available on over 40% of Android devices, which by itself makes it the second most widely distributed graphics API in the universe
I don't know about *that*
You do know about that. Vulkan ships on Nougat and later, which is over 40% of active Android devices. So, more than all the Windows PCs in the world. Only OpenGL ES is more widely available than that, available on 100% of Android devices.
"Vulkan is now available on over 40% of Android devices, which by itself makes it the second most widely distributed graphics API in the universe"
Available != widely distributed and supports != runs.
In all the cases I listed it does make that. Vulkan is here to stay whether a random slashdot weenie buries their head in the sand or not.
Could have used Vulkan, did not need to create a home rolled API to do the same thing less flexibly, leaving out important features, and not used by anybody outside of Apple.
They COULD have used Vulkan, IF it had Existed; but it wasn't even a Final SPECIFICATION
Neither was Metal. You speak with forked tongue.
Look in the mirror.
All Apple cultists should do that. Oh wait, it's a iMirror, that shows you only what you want to see!
Could have used Vulkan, did not need to create a home rolled API to do the same thing less flexibly, leaving out important features, and not used by anybody outside of Apple.
Well governed open source projects don't get forked.
There are whole operating systems that have been forked. For example BSD, OpenBSD, NetBSD, etc.
You know nothing of FreeBSD. For example DragonflyBSD started after a food fight that ended up with revoking one of the core dev's commit access.
Apple wasn't sufficiently responsive to Google's needs so Google forked it, simple.
HAHAHAHAHA. [Citation Needed]
Sweet, your concept of intelligent discourse marks you as an Apple employee. Then you criticize other people's posts like an asshole. Again, how Apple of you. Chrome's multiprocess architecture was awkward to develop in Webkit. Apple could have moved Safari in the same direction but chose not to. So bam, fork.
You said " now used by Safari and nobody else." That is factually untrue.
You niggle. Close enough to describe the reality. Would you prefer I said "mass migration away from Webkit"? There, said it.
My assertion. Mark it down. I said the same about Metal, mark that down too. Do LLVM too while you're at it, though I think that of the three it has the best chance of avoiding a fork for now.
So you have no evidence for anything that you've said then. Then I can discount your posting as mere imagination.
How imaginative of you, feel free to paste a gold star on your nose.
Apple has no credible business case for Metal, which is a bespoke 3D API. I thought that was clear.
No you are merely wrong.
The same results or better (geometry shaders!) could have been accomplished with Vulkan. There was no business case for introducing Metal instead of going with Vulkan, which can do the same but with less flexibility and no standarization. You can tattoo that on your Apple ass.
Apple will never get back the community karma it lost by rolling its own Vulkan-like API and will eventually be forced to support Vulkan anyway to avoid more developer defections. Enjoy.
Look in the mirror.
Vulcan is a dead standard. Nobody uses it.
Bullshit. Vulkan is now available on over 40% of Android devices, which by itself makes it the second most widely distributed graphics API in the universe, second only to OpenGL ES, available on 100% of Android devices. Vulkan is supported by numerous PC titles. Most AAA game engines support Vulkan, the others have it on the way. Unity Engine supports Vulkan on Android, Linux and Windows. Likewise Unreal. ID tech 6 was the AAA engine to support Vulkan and is widely licensed. Steam's Source2 engine supports Vulkan. Nintendo Switch supports Vulkan (and OpenGL 4.5). Looks like not dead.
Here is an Android Vulkan demo of Unreal Engine from two years ago. That is 100% real time on a Galaxy S7. You can see why it got traction.
Apple can and should participate in the group that develops the standard. To do otherwise would make Apple seem like a bunch of assholes. Oh wait, I'm starting to understand. You are from Apple right? You certainly are an asshole, so that would fit.
Your point is?
Which part of your fevered imagination makes you think that supporting standards amounts to being beholden?
As I alluded to before, Apple management seems to be smoking crap in the back room, how else could they keep coming up with such braindamaged ideas.
to be clear you don't think the graphics API is important enough for Apple to develop on it's[sic] own?
Apple should develop its own implementation of Vulkan. But I don't really give a crap whether they do or not, it's your funeral.
As open source, Google wanted to fork it and make Blink.
Well governed open source projects don't get forked. Apple wasn't sufficiently responsive to Google's needs so Google forked it, simple.
That is rather factually untrue...
Read your own link. Count the number of discontinueds. It's basically down to just Apple and Adobe. That happened really fast.
Apple will eventually give up backporting Blink improvements and repurpose their engineers officially as Blink contributors,
Do you have proof of that or that your assertion
My assertion. Mark it down. I said the same about Metal, mark that down too. Do LLVM too while you're at it, though I think that of the three it has the best chance of avoiding a fork for now.
Apple has no credible business case for a bespoke 3D library...
You mean beside Metal?
Apple has no credible business case for Metal, which is a bespoke 3D API. I thought that was clear.
users donâ(TM)t have to know about Metal, they can still get the benefits.
Huh? That is actually an argument for not using metal. Since users don't know about Metal they dion't give a flying fuck about it, and can get more benefit from Vulkan, which is lower level and more efficient, and which developers actually do care about.
(Thanks for the car analogy. Not.)
The good thing about Vulkan is that it is cross-platform. The bad thing is that it's very finicky to use.
That's far from the only good thing about Vulkan. It also succeeds dramatically at killing off CPU load and removing the CPU as a render bottleneck. It was designed to suit highly skilled 3D developers for building engines and libraries. Anybody not capable of coding a 3D engine themselves should program to the engine or library API. That's the way everybody wants it except Apple, who wants a dumbed down API that doesn't excel at anything and instantly shoves Apple to the back of the crossport list. If you can see the point of that then you have more imagination than me.
We have different definitions of "OS". What you call OS, I call platform. At least we don't disagree about Tim Cook's crack habit.