What you're describing requires implementing a layer to do the interpretation required. Existing wikis do not do this, and if you're going to write a management layer to interpret the diffs, you might as well be storing them in git for subsequent presentation through [insert any front end here]. The VCS solves a heck of a lot of the underlying issues, giving you the ability to just focus on the mechanics of interpreting the results.
For the most common use cases, 64-bit operating systems are nothing more than a waste of resources. You might want to reference my other post on this topic for an explanation of why your position is rather counterproductive.
Sorry EU has ruled the internet is a basic human right now.
That's a laughable proposition. You can call the Internet a "basic human right" all you want, right up to the point where corporations buy the ability to monitor all your communications to "enforce law and order." Don't worry, you'll still have an Internet connection, though... have fun with your half-baked "freedom."
You're sorely lacking in understanding of what revision control systems do. Code is text. As a matter of fact, the "source tree" for the entire site in my sig is stored in a git repository as RST files.
Unless they manage to outlaw one-to-one encrypted communications...
The vast majority of Internet users (a) wouldn't understand that concept if you spent an hour trying to explain it, or (b) wouldn't bother to implement it even if they did "get it."
I'm a huge fan of encryption, and I actively promote its use wherever possible. That said, the much larger issue is very simple: at what point will our government start allowing private corporations to instantly determine guilt or innocence? What's to stop them from outlawing "illegal" encryption using mechanisms like the DMCA, i.e. only allowing crypto they have keys for on their networks? We're getting uncomfortably close to that point (some would argue that we're teetering on the brink), and there's probably no going back once that bridge is crossed. It'd be easy to simply inflate prices for "unchecked" connections to the point where no ordinary person could afford them, making them only accessible to business interests.
All the good intentions and solidarity in the world won't get you anywhere if you're sitting in a jail cell on the whim of some company that decides you're a criminal worthy of confinement.
... don't expect to actually read the legislative language...
If United States Senators can't be bothered to read and comprehend the legislation they're voting on, then:
(1) why are they elected to posts that, as the most basic of job requirements, requires the ability to do so, and
(2) why haven't they been removed from office for complete and utter failure to serve the American people?
That's right, folks... your elected officials are attempting to pass legislation that will have massive consequences for our generation and several more to come, without having actually read the material they're about to vote on. Here's the best part: this is nonthing new. It's been the status quo for a huge chunk of Washington's electoral finest for longer than I've been alive. Outstanding work!
This depends entirely on your application's requirements. For many (most in the case of multi-core machines doing common tasks) users, the speed gain realized using a 64-bit platform is negligible. The loss is available memory, however, is very real.
In a hosting environment like ours, CPU is almost never the bottleneck (access to four Xeon cores per VPS, on hosts that are idle most of the time, tends to go a long way). Memory utilization is a different story.
Quite frankly, unless users are running applications (whether on the server or workstation) that absolutely need the most raw CPU optimization attainable, running a 64-bit operating system is a waste of resources.
The industry will be satisfied when they gain the ability to monitor everyone's net connection for signs of "illicit filesharing activity." If you think I'm joking, watch the kind of legislation the entertainment lobbies put their weight behind.
This is due to the fact that the vast majority of applications on the market do not need 64-bit features. This includes the most commonly used server applications. Using a 64-bit operating system merely for the sake of "it's 64-bit" is pretty stupid, especially when one considers the additional, needless RAM overhead this requires. This applies much more to smaller-scale VPS environments than workstations and servers that come with 4 GB of RAM at minimum, but it's still a very valid point.
While the OP didn't actually say that, the end result would indeed be the act of promoting ignorance. Of course, this is a case of one convention being followed by the general public and another being used by the scientific community. Given that this image is scientific in nature, I'd have to go with the coloration as it stands. If this were a photo of bathtub faucets, I'd reverse that view.
Unfortunately, many hosting companies make bold claims about their capabilities without actually being able to deliver on those promises. In this case, the host appears to be ovh.com (judging by whois info on the IP), providing a dedicated server. Of course, this does leave open the possibility that the server is badly configured for traffic on this scale.
Here's a direct link to the full-size version of the image contained in my earlier comment: panoramic night sky view. It is indeed absolutely gorgeous.
Slashdot Mirror
What you're describing requires implementing a layer to do the interpretation required. Existing wikis do not do this, and if you're going to write a management layer to interpret the diffs, you might as well be storing them in git for subsequent presentation through [insert any front end here]. The VCS solves a heck of a lot of the underlying issues, giving you the ability to just focus on the mechanics of interpreting the results.
It's October now. A lot of them might be nine.
For the most common use cases, 64-bit operating systems are nothing more than a waste of resources. You might want to reference my other post on this topic for an explanation of why your position is rather counterproductive.
Sorry EU has ruled the internet is a basic human right now.
That's a laughable proposition. You can call the Internet a "basic human right" all you want, right up to the point where corporations buy the ability to monitor all your communications to "enforce law and order." Don't worry, you'll still have an Internet connection, though... have fun with your half-baked "freedom."
Times change. The Berlin Wall fell, and the USSR collapsed shortly thereafter. I recall it vividly.
You're sorely lacking in understanding of what revision control systems do. Code is text. As a matter of fact, the "source tree" for the entire site in my sig is stored in a git repository as RST files.
Unless they manage to outlaw one-to-one encrypted communications ...
The vast majority of Internet users (a) wouldn't understand that concept if you spent an hour trying to explain it, or (b) wouldn't bother to implement it even if they did "get it."
I'm a huge fan of encryption, and I actively promote its use wherever possible. That said, the much larger issue is very simple: at what point will our government start allowing private corporations to instantly determine guilt or innocence? What's to stop them from outlawing "illegal" encryption using mechanisms like the DMCA, i.e. only allowing crypto they have keys for on their networks? We're getting uncomfortably close to that point (some would argue that we're teetering on the brink), and there's probably no going back once that bridge is crossed. It'd be easy to simply inflate prices for "unchecked" connections to the point where no ordinary person could afford them, making them only accessible to business interests.
All the good intentions and solidarity in the world won't get you anywhere if you're sitting in a jail cell on the whim of some company that decides you're a criminal worthy of confinement.
... don't expect to actually read the legislative language ...
If United States Senators can't be bothered to read and comprehend the legislation they're voting on, then:
(1) why are they elected to posts that, as the most basic of job requirements, requires the ability to do so, and
(2) why haven't they been removed from office for complete and utter failure to serve the American people?
That's right, folks... your elected officials are attempting to pass legislation that will have massive consequences for our generation and several more to come, without having actually read the material they're about to vote on. Here's the best part: this is nonthing new. It's been the status quo for a huge chunk of Washington's electoral finest for longer than I've been alive. Outstanding work!
This depends entirely on your application's requirements. For many (most in the case of multi-core machines doing common tasks) users, the speed gain realized using a 64-bit platform is negligible. The loss is available memory, however, is very real.
In a hosting environment like ours, CPU is almost never the bottleneck (access to four Xeon cores per VPS, on hosts that are idle most of the time, tends to go a long way). Memory utilization is a different story.
Quite frankly, unless users are running applications (whether on the server or workstation) that absolutely need the most raw CPU optimization attainable, running a 64-bit operating system is a waste of resources.
The industry will be satisfied when they gain the ability to monitor everyone's net connection for signs of "illicit filesharing activity." If you think I'm joking, watch the kind of legislation the entertainment lobbies put their weight behind.
My results concur with this.
Ukraine isn't Communist. Go back to school, starting with the fourth grade.
This purging was brought to by the Ministry of Truth and viewers like you.
Leave my goat alone. He's already depressed from having to wade through hundreds of spam messages a day in his FarmMail inbox.
32 bit OS and applications why???
This is due to the fact that the vast majority of applications on the market do not need 64-bit features. This includes the most commonly used server applications. Using a 64-bit operating system merely for the sake of "it's 64-bit" is pretty stupid, especially when one considers the additional, needless RAM overhead this requires. This applies much more to smaller-scale VPS environments than workstations and servers that come with 4 GB of RAM at minimum, but it's still a very valid point.
Somebody with mod points please mod the parent down as an obvious troll before any more replies get incited. Kthx.
While the OP didn't actually say that, the end result would indeed be the act of promoting ignorance. Of course, this is a case of one convention being followed by the general public and another being used by the scientific community. Given that this image is scientific in nature, I'd have to go with the coloration as it stands. If this were a photo of bathtub faucets, I'd reverse that view.
There's a cached version of one of the pictures here: color Milky Way image.
I'm sorry, but in my experience the things you apparently consider "optimization" are basic rules of the road.
The usefulness of Coral caches is rapidly approaching zero these days. Here's some Engadget coverage of the item in question.
Read the source.
I'll have to give this a spin. Thanks for the heads up!
Unless his name is Barack Obama, someone works above him.
Unfortunately, many hosting companies make bold claims about their capabilities without actually being able to deliver on those promises. In this case, the host appears to be ovh.com (judging by whois info on the IP), providing a dedicated server. Of course, this does leave open the possibility that the server is badly configured for traffic on this scale.
Here's a direct link to the full-size version of the image contained in my earlier comment: panoramic night sky view. It is indeed absolutely gorgeous.