hmmm what would you get if you had a scripted physics engine?
You get your average shooter or adventure game, where a mini-nuke will absolutely refuse to do any kind of damage against a perfectly ordinary-looking door. Or, more correctly, the door cannot react except for things it's specifically scripted to react to. By contrast, to a physics engine that door is not a door but a "damageable" and thus the nuke can tell it to suffer damage (or apply force with more advanced engines), as can a stick of dynamite or the player's foot.
It only "suggests" that if you ignore the obvious like widespread disincentives to employ people in the developed world.
Which were put in place to keep the developed world from falling into a general revolution. Which will simply start again if you remove them.
Or in other words, society made the problem in the first place in part by shutting down said industry. If they didn't do that, then not only would they have those workers, they'd have others employed to provide goods and services for those workers.
Right, so did that actually happen before those regulations were put in place? Why do you Lazy-Fairy fanbois keep ignoring history?
Furthermore, if an industry becomes unprofitable simply because they have to actually pay their employees a decent wage, it seems to me that it wasn't producing any value to begin with. Why should I have to subsidize it, either through food stamps for its employees or through amed might necessary to keep them from revolting out of despair?
Sorry you can't land one with your BS in Literary History of Transgendered Elves of Valinor.
As it happens, "hard" subjects are easier to automate than "soft" ones. That's why our games have physics engines but stories are scripted. And on top of that, Tolkien's writings specifically - which are mostly just histories of Middle-Earth - have made around $5 billion from the LotR and Hobbit movie trilogies alone.
A side comment here: the "= 0" seems bizarre. Back when it was created the mantra was to avoid new keywords [at any cost]. Wouldn't "virtual void fnc() pure;" or "pure virtual void fnc();" be easier to grasp?
How about "unimplemented"? Why try to come up with witty synonyms when there's a perfectly accurate word in the English language already? Especially since "pure" already has a completely different meaning in relation to functions: it's a function that has no side effects and returns a value that depends only on the parameters.
By the same token, "virtual" is less clear than "overridable".
My notion is that any public class hierarchy that allows fncX4 from class X to show up in class Z without an explicit definition in Z violates encapsulation.
Suppose W is a private member of X. Suppose the author of W changes some public function W.f which X relies on so that another function X.g develops a bug. Has encapsulation been violated? Remember that any complete and unambigious definition of W.f is itself already an implementation.
If your code references any outside code in any way, it can be broken by unexpected changes in that outside code. That loss of control is the price you pay for not coding everything yourself. It's not avoidable by any means whatsoever.
However, it seems like your specific complaint could be solved with a simple addition of syntactic sugar: "private X someName (exports: public: fncX1, fncX2, fncX3)" which would make compiler generate the corresponding proxy functions for you (or better yet, just make Z.fncX1 be a synonym for Z.someName.fncX1 for all purposes except checking for access permission).
From the very previous sentence: "What gives us the right to extend its legal definition from what a religion - or a set of religions - says marriage should be?"
Notice the word "legal" there? The issue is not whether you recognize same-sex marriage as valid, the issue is whether the law does. And the law is subject to First Amendment, which specifically excludes religious law.
The state's power to do what? Tell people that they can't willy nilly change the meanings of words?
To have anything whatsoever to do with marriage. Specifically, to recognize it as affecting one's legal status in any way. The state can't do that without having a legal definition of marriage (because otherwise how can it tell if you're married or not?), and it can't simply leave that up to your church's word because that would be making a law "respecting an establishment of religion", which the First Amendment forbids.
This should create the head of steam required to get some legislation passed to make companies and specific executives SUFFER if they screw up their data security. Ultimately that means if an executive is advised that a system is insecure, fails to act and it gets hacked, the executive needs to personally liable, with a small taste of prison. It happening once is all that is required....
That will simply mean executives make darn sure no one will dare give them such advice.
No, what's required is understanding that handling identities is a specialized task with the consequences of failure being a matter of life and death. In other words, it needs mandatory insurance - anyone's name gets out, they get paid massive mandatory damages sufficient to start a new life if they so choose regardless of whether they actually come to any harm, and the insurance company then handles punishing the culprit by trying to recover their money either through the courts or through higher rates.
Ignoring the political aspect for a moment, isn't this a simple TOS violation? Twitter offer a feature (deleting tweets) and these guys are using their API access to subvert it. It's hardly surprising that they were blocked.
Twitter is claiming they have a feature - taking back something after it has been published on the Internet - which they have no way of delivering. Politwoops highlighted this fact. So no, it's not surprising they got blocked.
Going back to the politics, are you arguing that Twitter should remove the delete button from its service? That would be fine of course, I'm just asking if you think that is what they should do, or if you think it should be up to third party services to selectively archive everything certain people of interest say and then change their mind about.
Which is more important, Twitter's ability to deliver shareholder value or the public's ability to know what their elected representatives actually believe, rather than whatever PRotoshopped image they wish to project? Gee, I wonder.
Inheritance violates encapsulation. If you have three classes X, Y, and Z (X is the base class, Y inherits from X, and Z inherits from Y), and each has various fncX1/fncX2/..., fncY1/fncY2/..., and fncZ1/fncZ2/... Now, you instantiate class Z. Then, when you use Z.fncX1 you're violating encapsulation because you're having to have [incestuous] knowledge of how Z was implemented in order to know that is has [by virtue of a two level inheritance from X] that Z.fncX1 is valid.
But how does that violate encapsulation? You yourself talked about the difference between "is a" and "has a". "Is a" is not an implementation detail, it's a declaration about the API of the class.
JavaFX uses something that looks a little bit like CSS. In fact CSS is theoretically applicable to any kind of hierarchical scene graph, you just need to define what object types exist and what properties they have. You'd think that'd be more widespread nowadays, when every project requires programmers and multiple artists to work together and modding is all the rage.
What gives you the right to extend the definition of marriage?
What gives us the right to extend its legal definition from what a religion - or a set of religions - says marriage should be? Why the First Amendment, of course.
You don't get to call upon state's power without being subject to its checks and balances. Think very carefully what victory over that would cost you.
I assure you, it's not. Using Firefox is a constant hunt for the open tab that's slowing the whole browser down due to 100% CPU utilization. Did I say 100%? No, that would require a multi-threaded design - Firefox is effectively single-threaded, or at least a single thread getting overworked will jam the entire program.
Firefox is losing market share because it has numerous technical problems that show no sign of going anywhere. It's going the same way Netscape and old versions of IE did, and for the same reason: turd polishing only works until someone actually has to use the disgusting thing. And breaking existing extensions will probably be the last straw.
I think that in most cases, most people don't even care.
It really depends. In Simpons, there's no timewise continuity - the whole town's been nuked multiple times. Instead, the basic elements are the characters and the conceptual realm they inhabit. Those might be refined over time, but Mr. Burn's never going to clean up his act permanently, Bart's never going to grow up, etc. The show doesn't take place in spacetime, it takes place in the realm of myth. And the same is true for most ongoing series - for example, how old is Lois Lane?
On the other hand, a series with a defined endpoint - or a single episode of most series - does take place in a space-time continuum, so continuity matters. For example, if the God-Emperor of Mankind showed up to duel Emperor Palpatine in the climatic battle of the Return of the Jedi, it would be awesome but also effectively destroy the movie.
Of course, most continuity errors are subtle glitches that only come to light after careful analysis. These can actually end up enhancing the work by providing both a motivation and points of attachment for fan works. These fan works can then be further refined by other fans, with the best ideas eventually becoming attached to the work's image (fanon) in popular culture. This process is not only entertaining to the participants, but can easily turn a mediocre work to a hit; there simply isn't a turd so disgusting that enough cycles of de- and reconstruction wouldn't turn it into a delicious raisin, as long as there's enough people willing to touch it to get the process started. My Little Pony franchise is probably the most (in?)famous recent example, but it's also how you get from a genocidal tribal god to Jesus, and is what ultimately underlays current culture wars.
Humanity can be regarded as a kind of distributed supercomputer with individual humans as computing nodes, and stories we tell as intermediate results that keep getting evaluated, altered, and combined with other results to produce further ones. The process kicked into high gear with freedom of speech, and the Internet is a fancy new high-speed bus combined with storage space. Any even remotely popular series is going to have more fan works than a human can consume in their lifetime, and a fraction of those will be higher quality than the original work - and inspire new works in their turn. Copyrights currently hinder realizing the full potential of this self-organizing worldwide cultural factory somewhat, which is one of the many reasons they are mostly just disregarded.
So, people do care about continuity, just like they do about all ingredients, but the trick is putting the right amount there. A work with perfect continuity - no errors and nothing unexplained - has no room to grow and is thereby dead. Perhaps some authors wish to keep total control to themselves, and thus end up trying to fill every gap with midichlorians and Boba Fett clones, but ultimately they simply end up sabotaging their own legacy that way. If you wish to have one, you better hope your work catches on and serves as a seed for the tree and perhaps a whole forest to come. But it's not going to be just your tree, and that's something some people can't accept, ultimately to their own loss.
...then they'd presumably be advanced enough to understand special relativity and take account for it in all their calculations.
Would they? A photon's momentum is a function of its frequency, thus an object in motion relative to the CMB - one who sees one half of the sky blueshifted and the other redshifted - is going to effectively experience friction and come to an asymptotic halt eventually.
Of course, that is going to take a very long time. And that rises a question: do we have an effective velocity relative to CMB? That is, do we see it blueshifted in one direction and redshifted in the opposite? Because Earth orbits the Sun, Sun orbits the Milky Way, Milky Way orbits the local cluster... We should have an easily measurable nonzero velocity relative to the local Hubble flow.
You need something installed, put in a ticket with a justification. You don't need War and Peace, just a blurb on how the software relates to your job.
If you can't do that, you don't need it and most certainly do not need to be able software at will.
And after you've wasted enough time writing those tickets and waiting for answers, you just say "screw it" and use whatever tools are at hand, whether they're a good fit or not. Because if you don't get your job done, you'll get fired. And so we end up with Excel databases and other clever repurposings of existing technology.
Looks like the SJWs are modding you down. Fuck 'em if they can't take a joke.
Propaganda doesn't stop being propaganda just because it's dressed up as a joke. No one is under any obligation to pretend it does, either. Your very expression - the concept of "taking" a joke - implies you know full well it was meant as an attack.
So how much warmer is Mars now, compared to its theoretical black-body temperature? Well, the black-body temp is 210K. The measured average temp is also 210K. So CO2 is not doing any warming of the Martian atmosphere, even though it is a greenhouse gas.
"In astronomy, the radiation from stars and planets is sometimes characterized in terms of an effective temperature, the temperature of a black body that would emit the same total flux of electromagnetic energy."
A black body in thermal equilibrium will emit the same amount of energy it abosrbs. Mars, no matter its composition, must also emit all the energy it absorbs and reflect the rest. Thus, measuring Mars's average temperature from its energy flux is always going to equal a black body, and there haven't been nearly enough probes to average it any other way.
Even Microsoft Windows had preemptive multitasking half a decade before Apple.
Every system that has interrupts has pre-emptive multitasking. Even DOS had the "terminate and stay resident" system call. It's just that old systems didn't have the resources to multitask complex programs so the methods to do so were undeveloped. We're seeing the same thing now with multithreading, which is still all-manual and thus a constant source of trouble.
Meanwhile, the PC's 286 also lacked a virtual memory (that did only came later with the 386), but used (and abused) the protected mode's segmented memory as a "poor's man virtual memory".
Protected mode memory was accessed through a segment: a "handle" pointing where the chunk actually stays in memory. (A bit more complex than the real mode segment of 8088/8086 which where just spead 16bytes appart).
The soft doesn't know much, it only uses the handle it was assigned to use. If the OS needs to move memory around, it just maps the segment to a different address space. The soft doesn't know and keeps using the same handle as before.
But is this really any different from how 386 did things? A pointer to memory address can be thought of as consisting of two parts: a segment identifier and an offset within that segment. 386 and later simply uses lots of small, fixed-size segments called pages sized and arranged so that segment identifiers and offsets can be interpreted as contiguous numeric ranges, streamlining management and programming.
So 386 is basically a 286 with a better API. Which, as it turns out, is important. And that rises the question of what other, perhaps even more important, features are being held back by being just a little bit too hard to use for the wheel of progress to gain momentum?
You mean Welcome to 1990. Everything old is new again.
As well as it should be. We now have fast multicore CPUs that (should) have the spare capacity to handle such background tasks without degradation of performance.
You can go to nearly all sites and spend money that is recognised via major credit agencies, why take a chance on a do nothing vapour ware middle person, just why.
You can give your credit card number to people you've never even met and hope they're nice enough to not misuse it, yes. Why anyone would prefer this to a system where people aren't in a position to initiate more transactions from your account after you've done business with them is beyond me.
Any bitcoiner worth his salt will tell you that any problem will be taken care of by the market!
No, but this problem will. If BT-XT gets enough traction to switch over, every other client will add support too, since the alternative is being incompatible with 3/4 majority of the network. The same goes for any other solution or change anyone might come up with.
And that's pretty obvious, too. It's what happens with every network protocol change for every P2P network. What makes this one interesting is the emotional responses it draws out. Just what are those directed against? The usually quoted reason, "pyramid scheme", can't be the real one both because Bitcoin is not a pyramid scheme and because actual bona fida intentional scams - like Mars One - don't draw nearly this amount of outrage. Do people simply love PayPal so much they can't bear the thought of them losing business, or do they fear some economic meme - for example "deflation is bad" - being proven false?
Economics holds the place of religion in our society, but has gone unchallenged since the Soviet block fell, so it's fascinating to see what issues and conflicts get dragged into light as the dawning Information Age hatches a new round of revolutions.
Requiring taxis to have a "special" license to do something simple like driving others around is nothing more than an artificial barrier to competition.
Well, obviously. That's what a license is. The question is: is it a necessary barrier?
OH, I think that boat has long sailed already with the current president appearing with YouTube "stars" that bathe and eat in bathtubs full of cereal and milk.
If inconveniencing a few million people is worth saving a few hundred lives, then inconveniencing a few hundred million people is worth saving tens of thousands of lives, yes?
So let's ban driving.
That would make it impossible to move enough food into cities, resulting in hundreds of millions starving to death. In fact the entire society would collapse since people couldn't get to work.
Slashdot Mirror
You get your average shooter or adventure game, where a mini-nuke will absolutely refuse to do any kind of damage against a perfectly ordinary-looking door. Or, more correctly, the door cannot react except for things it's specifically scripted to react to. By contrast, to a physics engine that door is not a door but a "damageable" and thus the nuke can tell it to suffer damage (or apply force with more advanced engines), as can a stick of dynamite or the player's foot.
Which were put in place to keep the developed world from falling into a general revolution. Which will simply start again if you remove them.
Right, so did that actually happen before those regulations were put in place? Why do you Lazy-Fairy fanbois keep ignoring history?
Furthermore, if an industry becomes unprofitable simply because they have to actually pay their employees a decent wage, it seems to me that it wasn't producing any value to begin with. Why should I have to subsidize it, either through food stamps for its employees or through amed might necessary to keep them from revolting out of despair?
As it happens, "hard" subjects are easier to automate than "soft" ones. That's why our games have physics engines but stories are scripted. And on top of that, Tolkien's writings specifically - which are mostly just histories of Middle-Earth - have made around $5 billion from the LotR and Hobbit movie trilogies alone.
How about "unimplemented"? Why try to come up with witty synonyms when there's a perfectly accurate word in the English language already? Especially since "pure" already has a completely different meaning in relation to functions: it's a function that has no side effects and returns a value that depends only on the parameters.
By the same token, "virtual" is less clear than "overridable".
Suppose W is a private member of X. Suppose the author of W changes some public function W.f which X relies on so that another function X.g develops a bug. Has encapsulation been violated? Remember that any complete and unambigious definition of W.f is itself already an implementation.
If your code references any outside code in any way, it can be broken by unexpected changes in that outside code. That loss of control is the price you pay for not coding everything yourself. It's not avoidable by any means whatsoever.
However, it seems like your specific complaint could be solved with a simple addition of syntactic sugar: "private X someName (exports: public: fncX1, fncX2, fncX3)" which would make compiler generate the corresponding proxy functions for you (or better yet, just make Z.fncX1 be a synonym for Z.someName.fncX1 for all purposes except checking for access permission).
From the very previous sentence: "What gives us the right to extend its legal definition from what a religion - or a set of religions - says marriage should be?"
Notice the word "legal" there? The issue is not whether you recognize same-sex marriage as valid, the issue is whether the law does. And the law is subject to First Amendment, which specifically excludes religious law.
To have anything whatsoever to do with marriage. Specifically, to recognize it as affecting one's legal status in any way. The state can't do that without having a legal definition of marriage (because otherwise how can it tell if you're married or not?), and it can't simply leave that up to your church's word because that would be making a law "respecting an establishment of religion", which the First Amendment forbids.
That will simply mean executives make darn sure no one will dare give them such advice.
No, what's required is understanding that handling identities is a specialized task with the consequences of failure being a matter of life and death. In other words, it needs mandatory insurance - anyone's name gets out, they get paid massive mandatory damages sufficient to start a new life if they so choose regardless of whether they actually come to any harm, and the insurance company then handles punishing the culprit by trying to recover their money either through the courts or through higher rates.
Twitter is claiming they have a feature - taking back something after it has been published on the Internet - which they have no way of delivering. Politwoops highlighted this fact. So no, it's not surprising they got blocked.
Which is more important, Twitter's ability to deliver shareholder value or the public's ability to know what their elected representatives actually believe, rather than whatever PRotoshopped image they wish to project? Gee, I wonder.
But how does that violate encapsulation? You yourself talked about the difference between "is a" and "has a". "Is a" is not an implementation detail, it's a declaration about the API of the class.
JavaFX uses something that looks a little bit like CSS. In fact CSS is theoretically applicable to any kind of hierarchical scene graph, you just need to define what object types exist and what properties they have. You'd think that'd be more widespread nowadays, when every project requires programmers and multiple artists to work together and modding is all the rage.
What gives us the right to extend its legal definition from what a religion - or a set of religions - says marriage should be? Why the First Amendment, of course.
You don't get to call upon state's power without being subject to its checks and balances. Think very carefully what victory over that would cost you.
I assure you, it's not. Using Firefox is a constant hunt for the open tab that's slowing the whole browser down due to 100% CPU utilization. Did I say 100%? No, that would require a multi-threaded design - Firefox is effectively single-threaded, or at least a single thread getting overworked will jam the entire program.
Firefox is losing market share because it has numerous technical problems that show no sign of going anywhere. It's going the same way Netscape and old versions of IE did, and for the same reason: turd polishing only works until someone actually has to use the disgusting thing. And breaking existing extensions will probably be the last straw.
It really depends. In Simpons, there's no timewise continuity - the whole town's been nuked multiple times. Instead, the basic elements are the characters and the conceptual realm they inhabit. Those might be refined over time, but Mr. Burn's never going to clean up his act permanently, Bart's never going to grow up, etc. The show doesn't take place in spacetime, it takes place in the realm of myth. And the same is true for most ongoing series - for example, how old is Lois Lane?
On the other hand, a series with a defined endpoint - or a single episode of most series - does take place in a space-time continuum, so continuity matters. For example, if the God-Emperor of Mankind showed up to duel Emperor Palpatine in the climatic battle of the Return of the Jedi, it would be awesome but also effectively destroy the movie.
Of course, most continuity errors are subtle glitches that only come to light after careful analysis. These can actually end up enhancing the work by providing both a motivation and points of attachment for fan works. These fan works can then be further refined by other fans, with the best ideas eventually becoming attached to the work's image (fanon) in popular culture. This process is not only entertaining to the participants, but can easily turn a mediocre work to a hit; there simply isn't a turd so disgusting that enough cycles of de- and reconstruction wouldn't turn it into a delicious raisin, as long as there's enough people willing to touch it to get the process started. My Little Pony franchise is probably the most (in?)famous recent example, but it's also how you get from a genocidal tribal god to Jesus, and is what ultimately underlays current culture wars.
Humanity can be regarded as a kind of distributed supercomputer with individual humans as computing nodes, and stories we tell as intermediate results that keep getting evaluated, altered, and combined with other results to produce further ones. The process kicked into high gear with freedom of speech, and the Internet is a fancy new high-speed bus combined with storage space. Any even remotely popular series is going to have more fan works than a human can consume in their lifetime, and a fraction of those will be higher quality than the original work - and inspire new works in their turn. Copyrights currently hinder realizing the full potential of this self-organizing worldwide cultural factory somewhat, which is one of the many reasons they are mostly just disregarded.
So, people do care about continuity, just like they do about all ingredients, but the trick is putting the right amount there. A work with perfect continuity - no errors and nothing unexplained - has no room to grow and is thereby dead. Perhaps some authors wish to keep total control to themselves, and thus end up trying to fill every gap with midichlorians and Boba Fett clones, but ultimately they simply end up sabotaging their own legacy that way. If you wish to have one, you better hope your work catches on and serves as a seed for the tree and perhaps a whole forest to come. But it's not going to be just your tree, and that's something some people can't accept, ultimately to their own loss.
Would they? A photon's momentum is a function of its frequency, thus an object in motion relative to the CMB - one who sees one half of the sky blueshifted and the other redshifted - is going to effectively experience friction and come to an asymptotic halt eventually.
Of course, that is going to take a very long time. And that rises a question: do we have an effective velocity relative to CMB? That is, do we see it blueshifted in one direction and redshifted in the opposite? Because Earth orbits the Sun, Sun orbits the Milky Way, Milky Way orbits the local cluster... We should have an easily measurable nonzero velocity relative to the local Hubble flow.
And after you've wasted enough time writing those tickets and waiting for answers, you just say "screw it" and use whatever tools are at hand, whether they're a good fit or not. Because if you don't get your job done, you'll get fired. And so we end up with Excel databases and other clever repurposings of existing technology.
Propaganda doesn't stop being propaganda just because it's dressed up as a joke. No one is under any obligation to pretend it does, either. Your very expression - the concept of "taking" a joke - implies you know full well it was meant as an attack.
From the Wikipedia page for Black Body:
"In astronomy, the radiation from stars and planets is sometimes characterized in terms of an effective temperature, the temperature of a black body that would emit the same total flux of electromagnetic energy."
A black body in thermal equilibrium will emit the same amount of energy it abosrbs. Mars, no matter its composition, must also emit all the energy it absorbs and reflect the rest. Thus, measuring Mars's average temperature from its energy flux is always going to equal a black body, and there haven't been nearly enough probes to average it any other way.
Every system that has interrupts has pre-emptive multitasking. Even DOS had the "terminate and stay resident" system call. It's just that old systems didn't have the resources to multitask complex programs so the methods to do so were undeveloped. We're seeing the same thing now with multithreading, which is still all-manual and thus a constant source of trouble.
But is this really any different from how 386 did things? A pointer to memory address can be thought of as consisting of two parts: a segment identifier and an offset within that segment. 386 and later simply uses lots of small, fixed-size segments called pages sized and arranged so that segment identifiers and offsets can be interpreted as contiguous numeric ranges, streamlining management and programming.
So 386 is basically a 286 with a better API. Which, as it turns out, is important. And that rises the question of what other, perhaps even more important, features are being held back by being just a little bit too hard to use for the wheel of progress to gain momentum?
As well as it should be. We now have fast multicore CPUs that (should) have the spare capacity to handle such background tasks without degradation of performance.
You can give your credit card number to people you've never even met and hope they're nice enough to not misuse it, yes. Why anyone would prefer this to a system where people aren't in a position to initiate more transactions from your account after you've done business with them is beyond me.
No, but this problem will. If BT-XT gets enough traction to switch over, every other client will add support too, since the alternative is being incompatible with 3/4 majority of the network. The same goes for any other solution or change anyone might come up with.
And that's pretty obvious, too. It's what happens with every network protocol change for every P2P network. What makes this one interesting is the emotional responses it draws out. Just what are those directed against? The usually quoted reason, "pyramid scheme", can't be the real one both because Bitcoin is not a pyramid scheme and because actual bona fida intentional scams - like Mars One - don't draw nearly this amount of outrage. Do people simply love PayPal so much they can't bear the thought of them losing business, or do they fear some economic meme - for example "deflation is bad" - being proven false?
Economics holds the place of religion in our society, but has gone unchallenged since the Soviet block fell, so it's fascinating to see what issues and conflicts get dragged into light as the dawning Information Age hatches a new round of revolutions.
Well, obviously. That's what a license is. The question is: is it a necessary barrier?
The process starts with moss sucking nutrients from rock, and goes with other plants from there.
It's terrible getting old, isn't it?
That would make it impossible to move enough food into cities, resulting in hundreds of millions starving to death. In fact the entire society would collapse since people couldn't get to work.