Now that Google has strong-armed Firefox into supporting MSE (whether it's barely functional or not) it seems likely that Apple will fall into line as well, so it's becoming more of a realistic proposition.
It's hard to see why Mozilla had to be strong-armed. It looks like a perfectly reasonable W3C recommendation to me. Is there some gotcha that escapes a quick perusal?
BTW, is Silverlight still a thing? I thought it zombified a couple years back.
The Mother of Clippy says that somebody mashed up some code to solve all the world's education problems. I say: something of a wild exaggeration. Not the part about mothering Clippy.
Mesa has been about 5 years behind OpenGL, seems this follows the trend, not sure if that's a good or a bad thing.
How about: good and bad, mostly good. I find that Mesa is really nice to work with. I have one project that has tracked it all the way from OGL 1.1 to 10.5 as of today, with nary a bump on the road. From time to time I have needed to mess with extensions in order to "tunnel" through to OpenGL versions still not fully supported by Mesa, but this has been a relatively painless process. Never once did I old code break, even with a bunch of ARBs bolted on. I wish all libraries were as nice to work with as Mesa. Heck, I wish any other library was as nice.
You can view ES as a "purified" form of OpenGL. Though it came into being as a superset of a subset, these days it tracks a pragmatic subset of OGL very well. It's not an exaggeration to call ES a triumph of cooperation between developers, industry and the standards organization.
...a shim is available to provide ES with OpenGL compatibility, apparently all the way through to OGL 4.5. Not sure what ES versions are currently supported, it looks like ES 2. No data on how well this works. The primary purpose would appear to be, to help you be lazy with OpenGL ports. Better to write to the natively supported OGL subset, which will serve your project well for the future. Not to denigrate the value of Regal - no doubt it is a godsend for someone.
ES 3.1 is current, you don't go higher than that for the time being. OpenGL 4.1 has "full compatibility with OpenGL ES 3.0 APIs", which I interpret as "strict superset", and 4.3 has the same relationship with ES 3.1. Additionally, a shim is available to provide.
Wikipedia covers this here and here. Keep abreast of how Mesa is coming along here.
4.1 is nothing to be ashamed of. ES 2.0 compatibility is the elephant in that room. Program binaries, per-stage programs and multiple viewports are all worth the price of admission (free)
I will need to dismiss your nonsensical nonsense as nonsense. Henceforth, could you please consider writing words that may withstand an iota of logical scrutiny? Specifically: "works" means "functions". Please keep your own private definition of "works" to yourself.
If you want to improve the poor performance, start with a faster net connection. Then get busy fixing the code, which is broken but not unfixably broken.
OK, over to you. Expecting yet another downclue from you.
O brave and omniscient anonymous coward, brave indeed behind that keyboard, unlike you I actually tried, using my own OpenGL app and it worked, though slow over the crappy wifi. Even the shaders worked. Knock me over with a feather.
I don't suppose you have what it takes to admit that you were wrong. Obviously, anybody can repeat this experiment.
Downsides: 1. you lose remote access (save for second-class stuff like VNC), 2. you need to port most software or use X emulation. Upsides:... [crickets]...
I'm having trouble seeing why your post was marked troll. Funny, maybe. Insightful, more like it. Clearly not a troll. what on earth is going on with mods in this thread?
..the analogy was a polite way to point out that your "get some servers" was missing the point of the question entirely, which was about what type of "servers"...
You don't need to tell anybody what the question was, it was plainly stated, e.g., "Is it even reasonable to order $50k worth of components and put together our own high-performance, reasonably-priced blade cluster?"
Maybe try answering that instead of twisting more. Not sure why you're putting in so much energy trying to find reasons to be irrelevant. For example: "there's no such thing as a commodity blade."
People care if an Opendocument Foundation document is part of an ISO standard, not so much about ISO itself, subsequent to well documented acts of prostitution.
Is this a software question looking for hardware, or a systems question looking for efficiency, budget constraint, or just sexy buzzwords?
The first two and not the third, quite obviously. OS is easy: Linux. I vote -1 for containers. One fat app sounds like a bad idea, except certain hot spots, but that's not what the OP asked, is it?
You're getting warm with the speed and cache management. Now add a cost axis and you're addressing the original question. I hope.
A good analogy of what is going on here is if the question was "why is the sky blue" and you have answered "dust" while the other has mentioned rayleigh scattering and a variety of other factors.
Your analogy fell down and can't get up. The OP asked about cost effective hardware for fluid dynamics. You wrote some poetry that doesn't even rhyme.
I wish you hadn't posted AC, and I wish I had mod points!
This is the right answer.
No it isn't. You conveniently forgot that OP clearly stated "FEA/CFD", narrowing down the appliction area and available solutions more than sufficiently. Perhaps you focused on jumping on the loudmouth wagon instead of actually considering the question that was asked?
Could have been a great thread if not for you guys.
...If you can get by with a 2-node system, then 10GE interconnect is good enough (AND MUCH CHEAPER); for more nodes, you will need Infiniband (since 10GE does not scale well)...
Useful commentary for the most part, but this bit is just wrong. Nobody needs Infiniband. If you think you need Infiniband then get some RDMAoE instead. Save yourself some money and some grief.
And what OP wants most probably would be as commodity as possible. What about cheapo meta shelving with minitowers carrying dual socket server boards with mid range 8 core machines? Density low enough to cool with built in fans and ambient air.
Slashdot Mirror
Now that Google has strong-armed Firefox into supporting MSE (whether it's barely functional or not) it seems likely that Apple will fall into line as well, so it's becoming more of a realistic proposition.
It's hard to see why Mozilla had to be strong-armed. It looks like a perfectly reasonable W3C recommendation to me. Is there some gotcha that escapes a quick perusal?
BTW, is Silverlight still a thing? I thought it zombified a couple years back.
The Mother of Clippy says that somebody mashed up some code to solve all the world's education problems. I say: something of a wild exaggeration. Not the part about mothering Clippy.
"HTML5 session storage"
Give Anon a medal...
Mesa has been about 5 years behind OpenGL, seems this follows the trend, not sure if that's a good or a bad thing.
How about: good and bad, mostly good. I find that Mesa is really nice to work with. I have one project that has tracked it all the way from OGL 1.1 to 10.5 as of today, with nary a bump on the road. From time to time I have needed to mess with extensions in order to "tunnel" through to OpenGL versions still not fully supported by Mesa, but this has been a relatively painless process. Never once did I old code break, even with a bunch of ARBs bolted on. I wish all libraries were as nice to work with as Mesa. Heck, I wish any other library was as nice.
OpenGL and OpenGL ES are different.
You can view ES as a "purified" form of OpenGL. Though it came into being as a superset of a subset, these days it tracks a pragmatic subset of OGL very well. It's not an exaggeration to call ES a triumph of cooperation between developers, industry and the standards organization.
...a shim is available to provide ES with OpenGL compatibility, apparently all the way through to OGL 4.5. Not sure what ES versions are currently supported, it looks like ES 2. No data on how well this works. The primary purpose would appear to be, to help you be lazy with OpenGL ports. Better to write to the natively supported OGL subset, which will serve your project well for the future. Not to denigrate the value of Regal - no doubt it is a godsend for someone.
ES 3.1 is current, you don't go higher than that for the time being. OpenGL 4.1 has "full compatibility with OpenGL ES 3.0 APIs", which I interpret as "strict superset", and 4.3 has the same relationship with ES 3.1. Additionally, a shim is available to provide.
Wikipedia covers this here and here. Keep abreast of how Mesa is coming along here.
Or just keep reading those Phoronix articles.
4.1 is nothing to be ashamed of. ES 2.0 compatibility is the elephant in that room. Program binaries, per-stage programs and multiple viewports are all worth the price of admission (free)
Basically, after this thread I have no further interest in Wayland unless it gets network transparency.
I will need to dismiss your nonsensical nonsense as nonsense. Henceforth, could you please consider writing words that may withstand an iota of logical scrutiny? Specifically: "works" means "functions". Please keep your own private definition of "works" to yourself.
If you want to improve the poor performance, start with a faster net connection. Then get busy fixing the code, which is broken but not unfixably broken.
OK, over to you. Expecting yet another downclue from you.
Worked fine for me, 10 minutes ago. I suspect that there is FUD afoot. Possibly even *self serving* FUD. From the "my shiny is teh better" crowd.
Nobody was talking about SGI.
O brave and omniscient anonymous coward, brave indeed behind that keyboard, unlike you I actually tried, using my own OpenGL app and it worked, though slow over the crappy wifi. Even the shaders worked. Knock me over with a feather.
I don't suppose you have what it takes to admit that you were wrong. Obviously, anybody can repeat this experiment.
1. you lose remote access
The X.org guys have said themselves this isnt true of X.org anymore...
Then the correct response would be to fix that lameness instead of making it more lame. Somebody lacking the requisite design skills?
Downsides: 1. you lose remote access (save for second-class stuff like VNC), 2. you need to port most software or use X emulation. Upsides: ... [crickets] ...
I'm having trouble seeing why your post was marked troll. Funny, maybe. Insightful, more like it. Clearly not a troll. what on earth is going on with mods in this thread?
..the analogy was a polite way to point out that your "get some servers" was missing the point of the question entirely, which was about what type of "servers"...
You don't need to tell anybody what the question was, it was plainly stated, e.g., "Is it even reasonable to order $50k worth of components and put together our own high-performance, reasonably-priced blade cluster?"
Maybe try answering that instead of twisting more. Not sure why you're putting in so much energy trying to find reasons to be irrelevant. For example: "there's no such thing as a commodity blade."
People care if an Opendocument Foundation document is part of an ISO standard, not so much about ISO itself, subsequent to well documented acts of prostitution.
Wrong. The OP stated fluid dynamics. Read again please.
Is this a software question looking for hardware, or a systems question looking for efficiency, budget constraint, or just sexy buzzwords?
The first two and not the third, quite obviously. OS is easy: Linux. I vote -1 for containers. One fat app sounds like a bad idea, except certain hot spots, but that's not what the OP asked, is it?
You're getting warm with the speed and cache management. Now add a cost axis and you're addressing the original question. I hope.
A good analogy of what is going on here is if the question was "why is the sky blue" and you have answered "dust" while the other has mentioned rayleigh scattering and a variety of other factors.
Your analogy fell down and can't get up. The OP asked about cost effective hardware for fluid dynamics. You wrote some poetry that doesn't even rhyme.
I wish you hadn't posted AC, and I wish I had mod points!
This is the right answer.
No it isn't. You conveniently forgot that OP clearly stated "FEA/CFD", narrowing down the appliction area and available solutions more than sufficiently. Perhaps you focused on jumping on the loudmouth wagon instead of actually considering the question that was asked?
Could have been a great thread if not for you guys.
PC server stuff = OS that runs on a PC. Apps that run on a PC. Middleware that runs on a PC. Sad that I had to spell it out.
...If you can get by with a 2-node system, then 10GE interconnect is good enough (AND MUCH CHEAPER); for more nodes, you will need Infiniband (since 10GE does not scale well)...
Useful commentary for the most part, but this bit is just wrong. Nobody needs Infiniband. If you think you need Infiniband then get some RDMAoE instead. Save yourself some money and some grief.
And what OP wants most probably would be as commodity as possible. What about cheapo meta shelving with minitowers carrying dual socket server boards with mid range 8 core machines? Density low enough to cool with built in fans and ambient air.