Check out the issues that Titanfall has with audio comparing the Xbone SPU with PCs that don't have a fancy SPU. It's probably the best example I can think of right now, but there are plenty of others regarding 3D audio and onboard sound. Onboard sound quality reached par with CD quality audio with multiple channels, but there's a lot more available. The truth is that the base quality of hardware reached a point where things are 'good enough', but the tradeoffs are still very noticeable when running applications that were designed to use the advanced functionality.
“Traditional single-processor pathnding strategies, such as A* and its derivatives, have been long praised for their exibility. We implemented several parallel versions of such algorithms to analyze their intrinsic behavior, concluding that they have a large overhead, yield far from optimal paths, do not scale up to many cores or are cache unfriendly. In this article, we propose Parallel Ripple Search, a novel parallel pathnding algorithm that largely solves these limitations.”
http://graphics.tudelft.nl/~ra...
I disagree with your basic assumptions.
I expect that the logic required to reasonably split up the pathfinding is going to easily reverse any potential savings. There is a completely disregard for the fact that in order to split the processing up, one must take the time to organize the processes such that they can be split up.
It's a little bit like rocket science. How each additional pound of fuel provides so much thrust, but the additional weight but also be accounted for. 'parallel the pathfinding' is adding fuel without accounting for the weight of the fuel.
All of these posts about how simple it should be to refactor the pathfinding are from people who have never developed anything of remote complexity in their lives.
I remember it as well...and found IBM's to be surprisingly high quality. The models that found their way onto Dell laptops, on the other hand, made me carry a mouse.
When you're resorting to sleeping on benches, there's not a lot of people willing to hire you.
Or let you take a shower.
Or clean your clothes.
And people talk about you like you have a choice in the matter.
They put spikes and dividers on the benches so you can't sleep.
Have you ever tried to find a job when you haven't slept comfortably for god knows how long, haven't had a solid meal, haven't been able to clean yourself up?
Have you ever once, for a moment, stepped outside of your privilege and thought about what it actually means to be in that position, and what it honestly takes to get out it?
Take a nap.
A cache option at the end-user would do absolutely nothing to solve the problem. It's the same situation: You're sending all that data to the end user.
Civilization gaps. Any first-world waste that makes it to the third-world stands the chance of empowering the third-world to shed the label. The people with the money and power know that modern civilization is unsustainable, but the best they can do is try to maintain pools of cheap labor by restricting advancement. Look at things like a modern chinese factory, the highest technical assembly lines in the world are people putting things together by hand, being paid minimally for it. But what changes if the people on the bottom of the ladder are empowered with the technology? They stop being at the bottom of the ladder, and the entire power structure as it currently exists collapses.
Actually, NSL is a TLA for National Security Letter.
Or as that other gentleman pointed out, an initialization. Where TLA is an initialization of "Three Letter Acronym" where I seem to actually mean initialization, so..
NSA is just as TLI as the rest of them.
This isn't so much 'giving up a privacy tool' as having the latest version of the privacy tool be stripped of the ability to encrypt and then released with the wording that it is not secure. The actions that will prevent a user from using this software were not made by the users. The choice was made by... who, exactly?
As far as we know so far, Truecrypt hasn't been compromised.
No, you're wrong.
From the TrueCrypt website: WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues WARNING: Using TrueCrypt is not secure
It may not use the explicit word 'compromised', but that says it clearly right there. TrueCrypt is compromised, whether a TLA did it or not.
It doesn't always show the paywall, they've put in a few workarounds here and there so that people following links get the content. It's just more dishonesty in their attempts to monetize a website.
They also seem to send daily ads out pressuring you to get a subscription to their website, if you've given them your e-mail.
I wish content providers trying to sell their content would focus on their content instead of the money. Else what the heck are you selling?
But notice how they were framed.
Can we stop the bullshit and quit pretending like releasing this information isdangerous?
The delay is what's dangerous. The longer the information is kept under wraps and the less willing they are to take the hard shots, the more FUCKED UP BULLSHIT will be perpetrated by these government organizations.
Except that there's no reason you would expect your computer to send you to the moon. I'm not about to ride my bike across the sea. It's not an argument against Wayland, it's an argument against pushing for things that Aren't Ready and pretending like they're suitable replacements for what they're intended to replace.
If the product is not up for the task, it's not up for the task. There are a lot of potentially good reasons for Wayland but every single one of them falls short until it matures to the point that these arguments are unnecessary.
It's an ugly problem, but it's one that isn't half as ugly as they want to make it.
In fact, I would go so far as to say they're actively trying to make it uglier.
At the end of the day, we're just drawing colored rectangles on the screen.
Is it too much to ask that they not fuck that up?
It started back in Alpha because it had to.
It's still not ready to go, at version 1.5.
I still need remote display functionality.
It's still not ready to go, at version 1.5.
It doesn't have to be feature complete in alpha.
It's still not ready to go, at version 1.5.
Cool RDP patches, bro. How do I use them?
Have they made it as easy as ssh -X?
Don't argue the merits of half-baked software that is incapable of providing equivalent functionality to the pre-existing solutions as if that's acceptable, that's FUCKED UP. I need a solution that works, not something I get to sit around and wait for them to develop the functionality for.
I'm getting really tired of watching these systems be slowly dismantled in favor of doing it a different way that isn't necessary better, and doesn't provide the functionality that I've come to expect from my computer systems. This isn't some groundbreaking new territory that the Wayland guys are treading, computer history has covered this ground. I'm all about new ways of thinking about things, I'm not okay with sacrificing my workflow for the new hotness when I've been using roughly the same stable stack for damn near 20 years now and the new shit doesn't provide equivalent functionality.
It's not progress.
Because the webpage data will likely have a higher footprint. Once you pack on the full distribution of a web application that does everything you need it to onto the embedded device, does it have any space left? There are certainly ways to save space with web applications, but for the most part we're talking distributing and executing raw source code which is often orders of magnitude larger than compiled binaries. This matters in the embedded space.
I agree that the developer should be programming against their own machines where possible. The target environment is always a limited system, and the developer must work within those limits. The developer must have the necessary local access to deal with the problems they personally encounter in their workflow, though that does not mean they must have unlimited access. I'm personally very fond of virtual machines and prefer to keep any limited environment ready to go using them, common CPUs have accelerated those for almost a decade now. If the developer is being limited at their end, it's because people are doing it wrong on the other.
Slashdot Mirror
Check out the issues that Titanfall has with audio comparing the Xbone SPU with PCs that don't have a fancy SPU. It's probably the best example I can think of right now, but there are plenty of others regarding 3D audio and onboard sound. Onboard sound quality reached par with CD quality audio with multiple channels, but there's a lot more available. The truth is that the base quality of hardware reached a point where things are 'good enough', but the tradeoffs are still very noticeable when running applications that were designed to use the advanced functionality.
“Traditional single-processor pathnding strategies, such as A* and its derivatives, have been long praised for their exibility. We implemented several parallel versions of such algorithms to analyze their intrinsic behavior, concluding that they have a large overhead, yield far from optimal paths, do not scale up to many cores or are cache unfriendly. In this article, we propose Parallel Ripple Search, a novel parallel pathnding algorithm that largely solves these limitations.”
http://graphics.tudelft.nl/~ra...
I disagree with your basic assumptions.
I expect that the logic required to reasonably split up the pathfinding is going to easily reverse any potential savings. There is a completely disregard for the fact that in order to split the processing up, one must take the time to organize the processes such that they can be split up.
It's a little bit like rocket science. How each additional pound of fuel provides so much thrust, but the additional weight but also be accounted for. 'parallel the pathfinding' is adding fuel without accounting for the weight of the fuel.
All of these posts about how simple it should be to refactor the pathfinding are from people who have never developed anything of remote complexity in their lives.
It's strange how so much of the world chooses pain over pleasure.
I remember it as well...and found IBM's to be surprisingly high quality. The models that found their way onto Dell laptops, on the other hand, made me carry a mouse.
When you're resorting to sleeping on benches, there's not a lot of people willing to hire you.
Or let you take a shower.
Or clean your clothes.
And people talk about you like you have a choice in the matter.
They put spikes and dividers on the benches so you can't sleep.
Have you ever tried to find a job when you haven't slept comfortably for god knows how long, haven't had a solid meal, haven't been able to clean yourself up?
Have you ever once, for a moment, stepped outside of your privilege and thought about what it actually means to be in that position, and what it honestly takes to get out it?
Take a nap.
Stay safe.
Think of it a little like any other form of studying. The frustration, patience, and mystical interpretation part? That's called living.
The police ought to shut these rogue units down.
A cache option at the end-user would do absolutely nothing to solve the problem. It's the same situation: You're sending all that data to the end user.
Bah!
Civilization gaps. Any first-world waste that makes it to the third-world stands the chance of empowering the third-world to shed the label. The people with the money and power know that modern civilization is unsustainable, but the best they can do is try to maintain pools of cheap labor by restricting advancement. Look at things like a modern chinese factory, the highest technical assembly lines in the world are people putting things together by hand, being paid minimally for it. But what changes if the people on the bottom of the ladder are empowered with the technology? They stop being at the bottom of the ladder, and the entire power structure as it currently exists collapses.
That's a reading comprehension issue on the user end.
Actually, NSL is a TLA for National Security Letter.
Or as that other gentleman pointed out, an initialization. Where TLA is an initialization of "Three Letter Acronym" where I seem to actually mean initialization, so..
NSA is just as TLI as the rest of them.
This isn't so much 'giving up a privacy tool' as having the latest version of the privacy tool be stripped of the ability to encrypt and then released with the wording that it is not secure. The actions that will prevent a user from using this software were not made by the users. The choice was made by ... who, exactly?
NSL is just as TLA as the rest of the them. As a spook, you gotta understand that you're in with all the other spooks whether you like it or not.
As far as we know so far, Truecrypt hasn't been compromised.
No, you're wrong.
From the TrueCrypt website:
WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues
WARNING: Using TrueCrypt is not secure
It may not use the explicit word 'compromised', but that says it clearly right there. TrueCrypt is compromised, whether a TLA did it or not.
It's a sad state of affairs that our engineers are so disconnected from reality that they forget it.
It doesn't always show the paywall, they've put in a few workarounds here and there so that people following links get the content. It's just more dishonesty in their attempts to monetize a website.
They also seem to send daily ads out pressuring you to get a subscription to their website, if you've given them your e-mail.
I wish content providers trying to sell their content would focus on their content instead of the money. Else what the heck are you selling?
But notice how they were framed.
Can we stop the bullshit and quit pretending like releasing this information isdangerous?
The delay is what's dangerous. The longer the information is kept under wraps and the less willing they are to take the hard shots, the more FUCKED UP BULLSHIT will be perpetrated by these government organizations.
Except that there's no reason you would expect your computer to send you to the moon. I'm not about to ride my bike across the sea. It's not an argument against Wayland, it's an argument against pushing for things that Aren't Ready and pretending like they're suitable replacements for what they're intended to replace.
If the product is not up for the task, it's not up for the task. There are a lot of potentially good reasons for Wayland but every single one of them falls short until it matures to the point that these arguments are unnecessary.
It's an ugly problem, but it's one that isn't half as ugly as they want to make it.
In fact, I would go so far as to say they're actively trying to make it uglier.
At the end of the day, we're just drawing colored rectangles on the screen.
Is it too much to ask that they not fuck that up?
It started back in Alpha because it had to.
It's still not ready to go, at version 1.5.
I still need remote display functionality.
It's still not ready to go, at version 1.5.
It doesn't have to be feature complete in alpha.
It's still not ready to go, at version 1.5.
Cool RDP patches, bro. How do I use them?
Have they made it as easy as ssh -X?
Don't argue the merits of half-baked software that is incapable of providing equivalent functionality to the pre-existing solutions as if that's acceptable, that's FUCKED UP. I need a solution that works, not something I get to sit around and wait for them to develop the functionality for.
I'm getting really tired of watching these systems be slowly dismantled in favor of doing it a different way that isn't necessary better, and doesn't provide the functionality that I've come to expect from my computer systems. This isn't some groundbreaking new territory that the Wayland guys are treading, computer history has covered this ground. I'm all about new ways of thinking about things, I'm not okay with sacrificing my workflow for the new hotness when I've been using roughly the same stable stack for damn near 20 years now and the new shit doesn't provide equivalent functionality.
It's not progress.
Because the webpage data will likely have a higher footprint. Once you pack on the full distribution of a web application that does everything you need it to onto the embedded device, does it have any space left? There are certainly ways to save space with web applications, but for the most part we're talking distributing and executing raw source code which is often orders of magnitude larger than compiled binaries. This matters in the embedded space.
I agree that the developer should be programming against their own machines where possible. The target environment is always a limited system, and the developer must work within those limits. The developer must have the necessary local access to deal with the problems they personally encounter in their workflow, though that does not mean they must have unlimited access. I'm personally very fond of virtual machines and prefer to keep any limited environment ready to go using them, common CPUs have accelerated those for almost a decade now. If the developer is being limited at their end, it's because people are doing it wrong on the other.