A lot of it will probably go to umbrella consultancy fees: spend $100m to learn how to spend $450m wisely among 'carefully chosen suppliers'. Yes, I know that adds up to $550m.
Dell screens have 'desktop', 'media', and 'gaming' modes, which (I guess) affect colour curves and pixel response. If you're really interested in these artifacts, I suggest you research the available modes that the screen supports. I also call upon reviewers to test these modes before commenting on problems.
Abstract concepts generally have the best game rules because they offer the widest set of possible options; game designers are not restricted by the constraints of 'the familiar', but players then face the initial bump in the learning curve in order to absorb the initial concept. The problem here is that algorithms cannot draw upon the vast life experience and everyday cultural references that ordinary people possess. Further, abstract games, no matter how well-designed, are difficult to market and sell (take The Sentinel as an example); they need someone else (reviewer) to say, "This is good, go buy it".
In my experience, paperless billing only cuts paper by about 20%. Companies and institutions that are savvy enough allow the switchover to paperless billing, are also savvy enough to have a continuous mailshot campaign. The result is that you are still mailbombed and sent changes to T&Cs, for example. The cynical view is that 'paperless billing' is Greenwash (go look that word up if you haven't seen it before) - it's really about saving the company money by not paying the third-party billing service.
This looks like a way in for agent software to charge for modules of software, e.g. episodic games.
Alternatively, it looks like a good technology to speed up app launch on any system, using caching.
Are we looking at a non-problem? Although it involves business to get funding and build infrastructure, could the NPO official site take a.org or.info name?
We need a four-rail power connector standard, which automatically negotiates the power needed: +1.25V? to handle negotiation signals, the DC power required, plus two ground lines. You then have one transformer box with 10+ leads off a signal bus. There is then the small matter of persuading the whole electronics industry to support the standard... *cough*
If systems declare themselves to be 'unreliable participants' by whatever measure, then perhaps that system will be less likely to be recruited? e.g. clients on radio networks, roaming, or part-time members of a network.
In the UK, we have the Computer Misuse Act, which (if I have this correct), protects against dependable functionality being withdrawn without adequate notice of the terms of service. It mainly protects against aggressive Shareware, critical business failure, and anti-consumer practices.
Undoubtedly, the new feature described in the article is the first step of a soft conditioning process, that teaches us to accept the temporary functionality of software, leading to subscription-based activation as the norm.
Future direction is a question of whether or not the public will have their way, of being allowed to purchase use of software without expiry.
This is our May Fool joke. Who would permit stinkies to come from their own phone, let alone re-order the package that makes the smell?
I smell a marketing exercise, designed to bring attention to the technology for other purposes. I suspect the real applications would not capture the public imagination, but instead be used in the retail and advertiing sector: sponsored phones, perhaps?
Malware would be subject to counter-claims that the purpose of the software was not clear. How do you make hidden details reasonably accessible? Surely, on testing a license breach in legal proceedings, there has to be a demonstration that the user knowingly breached the agreement, and reasonable steps were taken by the licensors to communicate their requirements?
The accpetability of this type of solution relies on trust, and on how much system and infrastructure resource people want to dedicate to 'social model maintenance'. Can many disparate organisations operate in this way, with their own agents squirreling in our systems on our behalf?
Is it better to have a central service that updates when mutually appropriate, rather than have services speculatively take up resources? Central resources benefit from economy of scale, but can be equally speculative in that they offer potentially glabal coverage.
Similar 'sacrifice' questions arise from P2P media solutions (e.g. Kontiki-based distribution), where users sacrifice some of their bandwidth and processing power for others, in order to obtain the media.
Most security problems are a result of misunderstanding the purpose of an object in the infrastructure, and telling other components lies about its nature (permissions boosting). Bad admin does this with a human face. Poor products do this when out-of-the-box configurations don't match the user's requirements, allowing too much be begin with, or having options that bad admins change inappropriately.
So, how do we do this in a product-based environment? Do we need new module API, covering anything that communicates, which authenticates its purpose and reconciles this with the policies of the larger infrastructure? Will good admins resent such technology?
Finally, a contentious summary: good admins are needed because of poor products.
We can't afford to render every pixel to infinite depth, so we must be smart. I predict that over the next five years or so, the techniques around ray tracing will develop. That's subtly different from saying, "We'll be using chips powerful enough to ray-trace."
Video encoding took the same path, but now the stream contains enough information to make us believe that the information is there.
While I don't believe that games will have every pixel in every frame rendered by ray tracing in the immediate future, I believe there will be a transition, where the likes of Intel and AMD (etc) are able to do more, but before this happens, we can be smart.
Would "Patent + docs + zero-charge licensing" work, and offer a more industry-aware solution, especially where innovation is concerned? My own answer: Yes, but only in a few major patent zones (US and EU, UK territories).
If the objective is to help the developing world, then there are two problems: international patenting can be expensive, but failure to patent could result in a big player patenting and then suing the originators of the design. Does every approach involve too much red tape to be worthwhile?
All that extra stuff, I hope is being written to the slower parts of a disk. Otherwise, even relatively well defragged drives will suffer slowness because of the extra piecemeal data.
Theft of a machine could pose a security problem, if the data is not fragmented enough. What if only some computers are switched on when the data is needed? It would need to be massivel redundant to work properly.
Try something else: sharing the network's RAM; that would make a significant performance difference.
Because I'm lacking downtime, I came to this/. thread late, which means this comment will never be seen or moderated. This leaves you (the moderator) with a decision: do you increase the score to prove me wrong?
>...after calculating all the rays
Not necessary:o) Assumedly, a game will have knowledge of its moving objects, and a quick calculation would create a region in the 2D viewing plane.
Slashdot Mirror
Should segments come adrift, they could do huge damage to property. Who would insure such a venture?
A lot of it will probably go to umbrella consultancy fees: spend $100m to learn how to spend $450m wisely among 'carefully chosen suppliers'. Yes, I know that adds up to $550m.
Dell screens have 'desktop', 'media', and 'gaming' modes, which (I guess) affect colour curves and pixel response. If you're really interested in these artifacts, I suggest you research the available modes that the screen supports. I also call upon reviewers to test these modes before commenting on problems.
...because there won't then be a wireless access that you can change their passwords with!
That's because your real-time clock is broken!
Abstract concepts generally have the best game rules because they offer the widest set of possible options; game designers are not restricted by the constraints of 'the familiar', but players then face the initial bump in the learning curve in order to absorb the initial concept. The problem here is that algorithms cannot draw upon the vast life experience and everyday cultural references that ordinary people possess. Further, abstract games, no matter how well-designed, are difficult to market and sell (take The Sentinel as an example); they need someone else (reviewer) to say, "This is good, go buy it".
In my experience, paperless billing only cuts paper by about 20%. Companies and institutions that are savvy enough allow the switchover to paperless billing, are also savvy enough to have a continuous mailshot campaign. The result is that you are still mailbombed and sent changes to T&Cs, for example. The cynical view is that 'paperless billing' is Greenwash (go look that word up if you haven't seen it before) - it's really about saving the company money by not paying the third-party billing service.
This looks like a way in for agent software to charge for modules of software, e.g. episodic games. Alternatively, it looks like a good technology to speed up app launch on any system, using caching.
I think I have Cyberchondria...
Are we looking at a non-problem? Although it involves business to get funding and build infrastructure, could the NPO official site take a .org or .info name?
We need a four-rail power connector standard, which automatically negotiates the power needed: +1.25V? to handle negotiation signals, the DC power required, plus two ground lines. You then have one transformer box with 10+ leads off a signal bus. There is then the small matter of persuading the whole electronics industry to support the standard... *cough*
Having a dead snake cluttering up a critical pipe would be no fun! Send in another snake! :o)
Now, where dd I put that RFID scanner?
If systems declare themselves to be 'unreliable participants' by whatever measure, then perhaps that system will be less likely to be recruited? e.g. clients on radio networks, roaming, or part-time members of a network.
In the UK, we have the Computer Misuse Act, which (if I have this correct), protects against dependable functionality being withdrawn without adequate notice of the terms of service. It mainly protects against aggressive Shareware, critical business failure, and anti-consumer practices.
Undoubtedly, the new feature described in the article is the first step of a soft conditioning process, that teaches us to accept the temporary functionality of software, leading to subscription-based activation as the norm.
Future direction is a question of whether or not the public will have their way, of being allowed to purchase use of software without expiry.
This is our May Fool joke. Who would permit stinkies to come from their own phone, let alone re-order the package that makes the smell?
I smell a marketing exercise, designed to bring attention to the technology for other purposes. I suspect the real applications would not capture the public imagination, but instead be used in the retail and advertiing sector: sponsored phones, perhaps?
Malware would be subject to counter-claims that the purpose of the software was not clear. How do you make hidden details reasonably accessible? Surely, on testing a license breach in legal proceedings, there has to be a demonstration that the user knowingly breached the agreement, and reasonable steps were taken by the licensors to communicate their requirements?
The accpetability of this type of solution relies on trust, and on how much system and infrastructure resource people want to dedicate to 'social model maintenance'. Can many disparate organisations operate in this way, with their own agents squirreling in our systems on our behalf?
Is it better to have a central service that updates when mutually appropriate, rather than have services speculatively take up resources? Central resources benefit from economy of scale, but can be equally speculative in that they offer potentially glabal coverage.
Similar 'sacrifice' questions arise from P2P media solutions (e.g. Kontiki-based distribution), where users sacrifice some of their bandwidth and processing power for others, in order to obtain the media.
Most security problems are a result of misunderstanding the purpose of an object in the infrastructure, and telling other components lies about its nature (permissions boosting). Bad admin does this with a human face. Poor products do this when out-of-the-box configurations don't match the user's requirements, allowing too much be begin with, or having options that bad admins change inappropriately.
So, how do we do this in a product-based environment? Do we need new module API, covering anything that communicates, which authenticates its purpose and reconciles this with the policies of the larger infrastructure? Will good admins resent such technology?
Finally, a contentious summary: good admins are needed because of poor products.
We can't afford to render every pixel to infinite depth, so we must be smart. I predict that over the next five years or so, the techniques around ray tracing will develop. That's subtly different from saying, "We'll be using chips powerful enough to ray-trace." Video encoding took the same path, but now the stream contains enough information to make us believe that the information is there. While I don't believe that games will have every pixel in every frame rendered by ray tracing in the immediate future, I believe there will be a transition, where the likes of Intel and AMD (etc) are able to do more, but before this happens, we can be smart.
Error: symbol JAYL not recognised.
If the objective is to help the developing world, then there are two problems: international patenting can be expensive, but failure to patent could result in a big player patenting and then suing the originators of the design. Does every approach involve too much red tape to be worthwhile?
Theft of a machine could pose a security problem, if the data is not fragmented enough. What if only some computers are switched on when the data is needed? It would need to be massivel redundant to work properly.
Try something else: sharing the network's RAM; that would make a significant performance difference.
Because I'm lacking downtime, I came to this /. thread late, which means this comment will never be seen or moderated. This leaves you (the moderator) with a decision: do you increase the score to prove me wrong?
> ...after calculating all the rays
Not necessary :o) Assumedly, a game will have knowledge of its moving objects, and a quick calculation would create a region in the 2D viewing plane.