The problems you describe (beating of innocents, opression of women) are not problems that are solved by military force, nor occupation. If those are your sufficient justifications for imperialism, occupation, and our own breed of opression, then you are an easy tool of evil.
It is absolutely NOT a superset of email. It says "you can only participate if you're connected, and connected most of the time, and using a web browser that is capable of running all the new fancy stuff on hardware that can run the new fancy web browser.
Email works on *everything*.
Email has a client, that client can work the way the user needs it to. Wave requires the user to adapt to it, rather than the other way around. Wave is moving backwards, to tightly coupled systems and interfaces. The reast of the world is currently still digesting the last wave of interoperability called "Service Oriented Architecture" which dictates esentially that you do the opposite of what Wave does.
Wave is already obsolete, even though the technology for it doesn't yet exist.
It is absolutely NOT a superset of email. It says "you can only participate if you're connected, and connected most of the time, and using a web browser that is capable of running all the new fancy stuff on hardware that can run the new fancy web browser.
Email works on *everything*.
Email has a client, that client can work the way the user needs it to. Wave requires the user to adapt to it, rather than the other way around. Wave is moving backwards, to tightly coupled systems and interfaces. The reast of the world is currently still digesting the last wave of interoperability called "Service Oriented Architecture" which dictates esentially that you do the opposite of what Wave does.
Wave is already obsolete, even though the technology for it doesn't yet exist.
Unicode is not a complete description. That's not a problem with software handling names, though. It's a problem with unicode. Any system which tried to do something else is going to be worse.
The correct response is to dissolve the corporation. Only by applying this totally legitimate and completely reasonasble and acceptable measure with extensive precedent will we return to an era of corporate responsibility.
You missed it. His people didn't play the games because they felt entitled. They played the games because they just didn't see a big moral issue in doing so.
No amount of castigation is going to change the general perception that casual piracy is no big thing.
No mac or Linux support, and no source code available.
Yeah, it could still be a project trying to "serve the community" but as we've learned by difficult example, the only way to really "be the community" is to be open.
The windows-only thing is possibly practical, but it means I'm not excited.
How do you safely download and run executable code without risk of an exploit vector? You can't.
Linux distributions deal with a slightly less difficult version of this, in terms of packaging and shipping public source code. Given that a lot of what they do (in order to package, resolve bugs etc) is inspect the source, there's some level of overview, and necessary precautions built into the blessing of packages before they are made availble, but still exploits are possible.
If I were designing a site like this, I would put the following pieces into place.
1 - categorize mods into no-executable content, sandboxed executable content, and unsandboxed executable content
2 - For sandboxed executable content, use an automated software tool to unpack the mod and sniff the files for object module headers. If any files are executable, reject.
3 - For no-executable content, sanitize as sandboxed, but also mark unploaded mods as unverified until some people manually review the package to identify that it doesn't contain lua, python, etc
At this point you can get a pretty informed level of risk on the mods you download.
Of course these people are probably more interested in features for gaming than features for safety. I hope they end up with both.
The second answer is that the Amiga had this video mode too, which was called 'dynamic hi-res'. It was how you got 4096 colors on an Amiga at a resolution higher than what HAM supported. Why didn't anyone use it at lower resolutions instead of HAM? Because it was just impractical to calculate a palette-per-line on a frequent basis.
There may have been some nice capabilities of the video hardware of the IIgs, but the thing was dog slow, so for pratical graphics hacking and making.. you know.. graphical programs, it was kind of a joke. The IIgs finder would take many seconds just to animate a window open, let alone trying to find the icons to display.
The sound is another area that's interesting to compare. It had 16 channels of stereo, but you had to cut open the case and do custom sautering to avoid being stuck with mono. It had a lot of channels which was interesting, but the synthesis it offered wasn't very good, so you got kind of a sea of tinny noises.
There were some interesting ideas going on in the IIgs, and with some different engineering choices it could have been a neat computer, but as shipped it was shackled, underperforming, and unable to provide any of its promise.
The original DRM was removed, since steam is a central DRM provider, and having two DRM systems would be extremely undesirable.
It is a kind of snapshot of the waste that is DRM, but that's not really any different from any sort of licensing being non-productive overhead. It's a cost of doing business.
- a menu bar
- a title bar (required in most environments)
- a url bar
- a bookmark link bar
- a tab bar
- some random other toolbar
Of these, the most useful is the url bar (you can't access anything without this), followed by the tabs, and then the menu bar third. Try deleting the bookmarks, and the random stupid buttons before taking away the menu.
Because it really makes sense to have a parallel health care system only for soldiers?
VA hospitals are a pretty good system, but they should really be for everyone, not just ex soldiers. Public health care is good for everyone, not just people who were in wars.
Redundantly, the law doesn't say that at all. The law is a restriction on what the school itself may provide for students as food, in order to force them to provide healthy meals for their students. There are no restrictions placed on what parents may provide for students for their own meals, on nutritional grounds. The school is just being ridiculous.
You're right about the scale and recovery, but you're wrong that it's not an ecological disaster. It is. It's a disaster which is still unfolding, and you don't see that yet, I can only hope you will keep your eyes open and pay attention as this plays out.
Now whether or not it's some mother-of-all-disasters catastrophe, I do not currently know. To my uneducated eye, it seems doubtful at this time.
Interesting, the MacBook Pro I'm typing on got around 2-3 hours when it was new (2 hours if i was doing work on it for those two hours -- web browsing & text editing). Playing WoW on it got about 15-20minutes, for comparison. A year and change in, I'm down to 1-2 hours on the battery.
Yeah, the lawyers bear the risk of failure, but in practice they don't engage in class action suits where there's a real risk of failure. They go for the sure thing, get a helping of cash, and then the vendor is off the hook forevermore.
This means that they short circuit liability issues that really should require much stronger measures, because these lawyers are not acting in the interest of the aggrieved parties. Why should they? No one hired them!
The way class actions are currently structured, the only significant winners are the law firms.
That said, they still seem to offer some kind of reasonable counterweight to big business, so no one's really racing to get rid of them, but neither is anyone really sure how to make them work better.
He's not talking about tokenring, but rather phonenet/appletalk which is an overgrown multidrop serial bus. In that system, of course, is just like a 10Base2 ethernet in that it's a broadcast medium and a crashed node will not affect the other nodes in the least.
You *can* have a problem if the server is configured as a router, since it is persistently establishing the 'zone' or roughly the network number for the network, since appletalk is ridiculous there is a whole sad state that occurs where reset or newly introduced computers will be in the 'automatic' network, and the ones that have seen the router lately will be in the routed network, but that would just entail weird effects where some nodes couldn't communicate with the rest.
Slashdot Mirror
Nice non-sequitor.
The problems you describe (beating of innocents, opression of women) are not problems that are solved by military force, nor occupation. If those are your sufficient justifications for imperialism, occupation, and our own breed of opression, then you are an easy tool of evil.
It is absolutely NOT a superset of email. It says "you can only participate if you're connected, and connected most of the time, and using a web browser that is capable of running all the new fancy stuff on hardware that can run the new fancy web browser.
Email works on *everything*.
Email has a client, that client can work the way the user needs it to. Wave requires the user to adapt to it, rather than the other way around. Wave is moving backwards, to tightly coupled systems and interfaces. The reast of the world is currently still digesting the last wave of interoperability called "Service Oriented Architecture" which dictates esentially that you do the opposite of what Wave does.
Wave is already obsolete, even though the technology for it doesn't yet exist.
It is absolutely NOT a superset of email. It says "you can only participate if you're connected, and connected most of the time, and using a web browser that is capable of running all the new fancy stuff on hardware that can run the new fancy web browser.
Email works on *everything*.
Email has a client, that client can work the way the user needs it to. Wave requires the user to adapt to it, rather than the other way around. Wave is moving backwards, to tightly coupled systems and interfaces. The reast of the world is currently still digesting the last wave of interoperability called "Service Oriented Architecture" which dictates esentially that you do the opposite of what Wave does.
Wave is already obsolete, even though the technology for it doesn't yet exist.
Unicode is not a complete description. That's not a problem with software handling names, though. It's a problem with unicode. Any system which tried to do something else is going to be worse.
Aging is not a disease. "Curing" it would be a much larger problem.
Journalism and rumor mills are not equivalent. Repeating news reports is not gossip.
The repeat may be inaccurate, but your insinuation is pathetic.
The correct response is to dissolve the corporation. Only by applying this totally legitimate and completely reasonasble and acceptable measure with extensive precedent will we return to an era of corporate responsibility.
Be a bit more careful in your definition. Languages like python and perl meet your stated requirements, as well as java and so on.
"Statically compiled to machine code with dynamic dispatch" might get you to a pretty small set.
Then, to answer your question I'm not sure if OCaml technically qualifies, but it solves the same problems just fine.
How about making the slashdot link handling code less ridiculous?
I dunno, i took a break from playing a game, encountered this article, and wondered "wtf is project natal?"
I guess I don't exist.
You missed it. His people didn't play the games because they felt entitled. They played the games because they just didn't see a big moral issue in doing so.
No amount of castigation is going to change the general perception that casual piracy is no big thing.
Interesting. My career goal is to do quality work maintaining and improving existing product lines. It's hard to find these jobs!
No mac or Linux support, and no source code available.
Yeah, it could still be a project trying to "serve the community" but as we've learned by difficult example, the only way to really "be the community" is to be open.
The windows-only thing is possibly practical, but it means I'm not excited.
Sounds like an unsolvable problem.
How do you safely download and run executable code without risk of an exploit vector? You can't.
Linux distributions deal with a slightly less difficult version of this, in terms of packaging and shipping public source code. Given that a lot of what they do (in order to package, resolve bugs etc) is inspect the source, there's some level of overview, and necessary precautions built into the blessing of packages before they are made availble, but still exploits are possible.
If I were designing a site like this, I would put the following pieces into place.
1 - categorize mods into no-executable content, sandboxed executable content, and unsandboxed executable content
2 - For sandboxed executable content, use an automated software tool to unpack the mod and sniff the files for object module headers. If any files are executable, reject.
3 - For no-executable content, sanitize as sandboxed, but also mark unploaded mods as unverified until some people manually review the package to identify that it doesn't contain lua, python, etc
At this point you can get a pretty informed level of risk on the mods you download.
Of course these people are probably more interested in features for gaming than features for safety. I hope they end up with both.
The second answer is that the Amiga had this video mode too, which was called 'dynamic hi-res'. It was how you got 4096 colors on an Amiga at a resolution higher than what HAM supported. Why didn't anyone use it at lower resolutions instead of HAM? Because it was just impractical to calculate a palette-per-line on a frequent basis.
There may have been some nice capabilities of the video hardware of the IIgs, but the thing was dog slow, so for pratical graphics hacking and making .. you know.. graphical programs, it was kind of a joke. The IIgs finder would take many seconds just to animate a window open, let alone trying to find the icons to display.
The sound is another area that's interesting to compare. It had 16 channels of stereo, but you had to cut open the case and do custom sautering to avoid being stuck with mono. It had a lot of channels which was interesting, but the synthesis it offered wasn't very good, so you got kind of a sea of tinny noises.
There were some interesting ideas going on in the IIgs, and with some different engineering choices it could have been a neat computer, but as shipped it was shackled, underperforming, and unable to provide any of its promise.
Not exactly.
The original DRM was removed, since steam is a central DRM provider, and having two DRM systems would be extremely undesirable.
It is a kind of snapshot of the waste that is DRM, but that's not really any different from any sort of licensing being non-productive overhead. It's a cost of doing business.
Let's see.
By default firefox comes with:
- a menu bar
- a title bar (required in most environments)
- a url bar
- a bookmark link bar
- a tab bar
- some random other toolbar
Of these, the most useful is the url bar (you can't access anything without this), followed by the tabs, and then the menu bar third.
Try deleting the bookmarks, and the random stupid buttons before taking away the menu.
Because it really makes sense to have a parallel health care system only for soldiers?
VA hospitals are a pretty good system, but they should really be for everyone, not just ex soldiers. Public health care is good for everyone, not just people who were in wars.
Redundantly, the law doesn't say that at all. The law is a restriction on what the school itself may provide for students as food, in order to force them to provide healthy meals for their students. There are no restrictions placed on what parents may provide for students for their own meals, on nutritional grounds. The school is just being ridiculous.
You're right about the scale and recovery, but you're wrong that it's not an ecological disaster. It is. It's a disaster which is still unfolding, and you don't see that yet, I can only hope you will keep your eyes open and pay attention as this plays out.
Now whether or not it's some mother-of-all-disasters catastrophe, I do not currently know. To my uneducated eye, it seems doubtful at this time.
Interesting, the MacBook Pro I'm typing on got around 2-3 hours when it was new (2 hours if i was doing work on it for those two hours -- web browsing & text editing). Playing WoW on it got about 15-20minutes, for comparison. A year and change in, I'm down to 1-2 hours on the battery.
I envy your well honed sense of tautology.
Yeah, the lawyers bear the risk of failure, but in practice they don't engage in class action suits where there's a real risk of failure. They go for the sure thing, get a helping of cash, and then the vendor is off the hook forevermore.
This means that they short circuit liability issues that really should require much stronger measures, because these lawyers are not acting in the interest of the aggrieved parties. Why should they? No one hired them!
The way class actions are currently structured, the only significant winners are the law firms.
That said, they still seem to offer some kind of reasonable counterweight to big business, so no one's really racing to get rid of them, but neither is anyone really sure how to make them work better.
He's not talking about tokenring, but rather phonenet/appletalk which is an overgrown multidrop serial bus. In that system, of course, is just like a 10Base2 ethernet in that it's a broadcast medium and a crashed node will not affect the other nodes in the least.
You *can* have a problem if the server is configured as a router, since it is persistently establishing the 'zone' or roughly the network number for the network, since appletalk is ridiculous there is a whole sad state that occurs where reset or newly introduced computers will be in the 'automatic' network, and the ones that have seen the router lately will be in the routed network, but that would just entail weird effects where some nodes couldn't communicate with the rest.