Good point. When they say this is faster and has better endurance than NAND, did they mean TLC, MLC, or SLC? You are right that SLC NAND has good endurance and speed, but maybe this is better? The ultimate memory would be memory that is fast enough to eliminate the separate concepts of "RAM" and "storage" entirely, and make it one thing. Then instead of having 8GB of RAM and 2TB of storage, you would have 2TB of "storage RAM." This might be fast enough and reliable enough for that. Or maybe it is close enough that DRAM is used merely as a cache. No more save buttons. No more need to read a file into memory before processing it. You would just use memory mapped I/O for everything.
the guy was using a socket clearly marked not for public use
What the heck does "clearly not marked for public use" mean? I've never seen a socket marked either way. In the US, people do this all the time in airports and convention centers. It is common to see a cluster of people hanging out in an otherwise unused area of a convention center or airport, huddled around some power outlets.
I like your zoology analogy. I would like to add that naming things is useful and important.
Years ago, I presented a 5-10 page design for a software component to my manager and the company architect. I had a nice document with diagrams and all that. After about 10 minutes in the meeting of presenting some stuff, the architect patiently said something like "So you plan on using a builder pattern, using chain of responsibility to dispatch the events. Sounds good, go for it!" He called for the meeting to be over and, slightly stunned, that ended the meeting.
This was a really good experience. Had I known the design patterns for what I was putting together, I could have simplified my document into a few paragraphs and saved a lot of time. Having a common vocabulary makes it easier and faster to communicate.
Anyone who has designed with multiple teams with different backgrounds will have similar experiences with vocabulary. One person says "queue" but they really meant "signal" and 45 minutes of arguing happens before the parties realize they meant the same thing but didn't know the word. (P.S. Microsoft loves to confuse terminology by naming their products after industry acronyms. Their development platform is "Dot Net" their SQL server is "SQL Server" and their web framework is "MVC")
I don't know about other OSs, but with Windows, the OS actually already knows some of this information. The appdata\roaming folder is important stuff that should go with you. The appdata\local can be lost, and just stays with the machine. appdata\locallow is even less important. The folders above appdata are user's files and are extremely important. Also, there are hints in the Windows CreateFile API where you can specify access patterns, including one which means "delete upon close."
Unfortunately, most apps don't use these features correctly. But if they did, they could be useful hints to the drive as to how to allocate things.
we are assured that her social security number is not being used and that they will clear her name and email address out of their system. Yet a few weeks later we get another email.
Then they are not clearing it out: they are either incompetent or lying. Consider having a lawyer draft a letter referencing this recent judgement. That might help.
I think weilawei really meant to say: "Provide a technical argument for why Node.js is gaining so much popularity." I am not sure if your post does that.
The features you listed are in pretty much every other major language. The book you referenced is a somewhat tongue-in-cheek look at how to use the good parts of a bad language. The conclusion I reach from those points is "yeah, it's bad, but see how people took the good parts and made it useful." Which doesn't really support the argument for why it is gaining popularity on the server-side.
The rebalancing is why a historical comparison is valid. If they didn't rebalance, it would have even fewer companies, and become even less representative of the economy.
If you are looking, the hubble space telescope is HST or 1990-37B. If you want to find more designations, follow the external links in https://en.wikipedia.org/wiki/International_Designator like the NSSDC Master Catalog.
If they don't sell your friend list to marketing companies, don't display ads offering hook-ups, and don't send invites to play Cow Clicker and Farmville, then I'll sign-up.
Take, for example, Global Cooling back in the 1970's. That was refuted with Global Warming in the 2000's
It was refuted in the 1970s, not the 200's. It was never a popular theory. No one should doubt Global Warming on the basis that the scientific community switched its stance. It never did: the majority of scientists were saying it was warming all along.
now it's simply Global Climate Change
It has been called "climate change" since before 1988, when the Intergovernmental Panel on Climate Change (IPCC) was formed. Today, people act like the name is some kind of knee-jerk defense against the switch between "global cooling" and "global warming" when in fact, there was no name change at all, nor was there ever a switch.
He never said he was happy with Windows Server's versioning.
From the submission.
That is, users have a highly available network location where they can "go back" to how their file was an hour ago. How do you do that with Linux? This is a highly desirable situation for users.
I took "is highly desirable" to indicate he was happy with it.
You can only use a file system snapshot to store a database file because databases are designed specifically to handle this. 3-phase commit logic, journals, transaction logs... The database builds transactional capabilities on top of the file system. And even those don't work if the drive "lies" and says it committed data when it didn't. That's why you should be careful running an enterprise file system on consumer-grade drive.
It's the Microsoft Volume Shadow Service. It's not the same thing as Sharepoint. FYI: A Sharepoint admin recently told me "If you are just using Sharepoint as a way to share files, then you are using it's weakest most awful feature."
Slashdot Mirror
Even if it's a thousand times more durable than NAND it's not much in a loop
That's why I said to use the DRAM as a cache. But maybe it just isn't good enough even with that.
Good point. When they say this is faster and has better endurance than NAND, did they mean TLC, MLC, or SLC? You are right that SLC NAND has good endurance and speed, but maybe this is better? The ultimate memory would be memory that is fast enough to eliminate the separate concepts of "RAM" and "storage" entirely, and make it one thing. Then instead of having 8GB of RAM and 2TB of storage, you would have 2TB of "storage RAM." This might be fast enough and reliable enough for that. Or maybe it is close enough that DRAM is used merely as a cache. No more save buttons. No more need to read a file into memory before processing it. You would just use memory mapped I/O for everything.
Does the US manufacture a significant amount of solar panels, or will much of this money go overseas?
Does XM Satellite radio count? It maxes out at 64kbps.
Okay, I withdraw my statement and shame myself because I didn't RTFA. The article says:
Electricity sockets on Overground trains are clearly marked with the words: “cleaners use only and not for public use”.
the guy was using a socket clearly marked not for public use
What the heck does "clearly not marked for public use" mean? I've never seen a socket marked either way. In the US, people do this all the time in airports and convention centers. It is common to see a cluster of people hanging out in an otherwise unused area of a convention center or airport, huddled around some power outlets.
I like your zoology analogy. I would like to add that naming things is useful and important.
Years ago, I presented a 5-10 page design for a software component to my manager and the company architect. I had a nice document with diagrams and all that. After about 10 minutes in the meeting of presenting some stuff, the architect patiently said something like "So you plan on using a builder pattern, using chain of responsibility to dispatch the events. Sounds good, go for it!" He called for the meeting to be over and, slightly stunned, that ended the meeting.
This was a really good experience. Had I known the design patterns for what I was putting together, I could have simplified my document into a few paragraphs and saved a lot of time. Having a common vocabulary makes it easier and faster to communicate.
Anyone who has designed with multiple teams with different backgrounds will have similar experiences with vocabulary. One person says "queue" but they really meant "signal" and 45 minutes of arguing happens before the parties realize they meant the same thing but didn't know the word. (P.S. Microsoft loves to confuse terminology by naming their products after industry acronyms. Their development platform is "Dot Net" their SQL server is "SQL Server" and their web framework is "MVC")
The submitter has asked for input on a solution, but not defined the problem yet. So we can't truly help.
I don't know about other OSs, but with Windows, the OS actually already knows some of this information. The appdata\roaming folder is important stuff that should go with you. The appdata\local can be lost, and just stays with the machine. appdata\locallow is even less important. The folders above appdata are user's files and are extremely important. Also, there are hints in the Windows CreateFile API where you can specify access patterns, including one which means "delete upon close."
Unfortunately, most apps don't use these features correctly. But if they did, they could be useful hints to the drive as to how to allocate things.
Are you familiar with the recent judgement against Time Warner Cable over a very similar matter?
we are assured that her social security number is not being used and that they will clear her name and email address out of their system. Yet a few weeks later we get another email.
Then they are not clearing it out: they are either incompetent or lying. Consider having a lawyer draft a letter referencing this recent judgement. That might help.
As a discussion grows longer, doesn't the probably of every topic increase?
Engine.dll
ExhaustManagement.dll
SteeringBrakes.dll
IRRangeFinder.dll
BackupCamera.dll
CupHolder.dll
I think weilawei really meant to say: "Provide a technical argument for why Node.js is gaining so much popularity." I am not sure if your post does that.
The features you listed are in pretty much every other major language. The book you referenced is a somewhat tongue-in-cheek look at how to use the good parts of a bad language. The conclusion I reach from those points is "yeah, it's bad, but see how people took the good parts and made it useful." Which doesn't really support the argument for why it is gaining popularity on the server-side.
The rebalancing is why a historical comparison is valid. If they didn't rebalance, it would have even fewer companies, and become even less representative of the economy.
If you are looking, the hubble space telescope is HST or 1990-37B. If you want to find more designations, follow the external links in https://en.wikipedia.org/wiki/International_Designator like the NSSDC Master Catalog.
I rarely post to Slashdot unless I have something to contribute, but this time I just have to say:
WOW.
1) I didn't know there was a .space domain.
2) Holy moly that is beautiful.
If they don't sell your friend list to marketing companies, don't display ads offering hook-ups, and don't send invites to play Cow Clicker and Farmville, then I'll sign-up.
Take, for example, Global Cooling back in the 1970's. That was refuted with Global Warming in the 2000's
It was refuted in the 1970s, not the 200's. It was never a popular theory. No one should doubt Global Warming on the basis that the scientific community switched its stance. It never did: the majority of scientists were saying it was warming all along.
now it's simply Global Climate Change
It has been called "climate change" since before 1988, when the Intergovernmental Panel on Climate Change (IPCC) was formed. Today, people act like the name is some kind of knee-jerk defense against the switch between "global cooling" and "global warming" when in fact, there was no name change at all, nor was there ever a switch.
t's like taking code licensed under BSD and putting it under the GPL
Is it? Or is it like reimplementing code licensed under BSD, and putting it under the GPL? Put another way: Is the API "code?"
agreed.
mod up. That statement, along with the following one, made no sense to me.
The leakage occurs because network operators are increasingly deploying a new version of the protocol used to run the Internet called IPv6.
I wasn't aware that IPv6 was fundamentally flawed. This sounds more like bad network design or something.
He never said he was happy with Windows Server's versioning.
From the submission.
That is, users have a highly available network location where they can "go back" to how their file was an hour ago. How do you do that with Linux? This is a highly desirable situation for users.
I took "is highly desirable" to indicate he was happy with it.
If that was the case he'd still be on windows.
If what was the case?
He wants something better, that's both distributed and has version control.
The submission does not ask for those things.
You can only use a file system snapshot to store a database file because databases are designed specifically to handle this. 3-phase commit logic, journals, transaction logs... The database builds transactional capabilities on top of the file system. And even those don't work if the drive "lies" and says it committed data when it didn't. That's why you should be careful running an enterprise file system on consumer-grade drive.
It's the Microsoft Volume Shadow Service. It's not the same thing as Sharepoint. FYI: A Sharepoint admin recently told me "If you are just using Sharepoint as a way to share files, then you are using it's weakest most awful feature."