Because feature sets are often useless. I've had numerous routers in the past that "have" QoS, but when enable it, the entire network goes to crap because the QoS is being offloaded to the CPU (even though it has hardware QoS support). How something is implemented is often just as important as what is implemented.
Please read your own darn links. They refer to it as memory. If you aren't going to call it memory, which it is, what exactly would YOU call it? "thing that stores stuff for a computer, but isn't memory"?
Good work finding a detailed description of NAND and ignoring the information that is most front and center to consumers.
I don't have to when you send them to me.
You tried to discredit a promise Intel made on it's marketing material (which didn't make sense and failed to deliver) with... a promise made on Intel marketing material.
Well, it's not really just marketing material when you can buy it and do it yourself. Granted with the P4800X, it's a software hypervisor (by a 3rd party) running with your OS as a client balancing requests between DRAM and Optane, but to the OS and the applications running under it, it has nearly the same effect. It's just adding one more tier of memory caching to the memory subsystem. Not really all that hard to grasp for anyone in the field.
---
I'm done with this thread. You can go on thinking that the one and only true memory is DRAM, while the rest of the world will go on realizing that you are just plain wrong. I'm sure you can do it. Just put your fingers in your ears, shouting LALALALA! or bury your head in the sand.
Now why do you think that NAND isn't sold as "memory" to consumers?
Let's stop right there, because NAND *IS* sold as memory to consumers. For example, let's take one of the largest suppliers of NAND flash products that are consumer facing today... Kingston. And here is an article by them: https://www.kingston.com/us/co.... "Here's a quick primer on what you need to know about NAND Flash memory."
Cameras use "Memory Sticks" -- all based on flash memory.
I could sit here all day a google marketing press releases, articles, and spec sheets that showing how wrong you are, but you can easily do the same. Here you go: http://lmgtfy.com/?q=computer+...
The term memory has been well defined for over 50 years now. Not going to start redefining precise, well established terms because you don't understand them, or think they mean something they don't and never did.
-----
As for learning what marketing is, well... Considering that I understood the marketing and you did not, I would say that of the two of us, one of us doesn't understand what marketing is at all.
It really could replace DRAM
Maybe some day just not now, and not at launch, which is effectively the broken promise.
Or maybe it really could... at launch:
Intel® Optane SSD DC P4800X with Intel Memory Drive Technology enables data centers to deliver more affordable memory pools by displacing a portion of DRAM or significantly increasing the size of memory pools. This solution transparently integrates the drive into the memory subsystem and presents the SSD as DRAM to the OS and applications.
Available March of last year. Is it better than DRAM in every way? No. Is it better than DRAM in some ways? Yes.
Can't believe I have to explain this on slashdot, but... Optane IS memory. So is NAND, your old spinning rust drive, digital tapes, CDs, and blurays. In fact, not only is it memory, but it's also RAM (random access memory). But so is everything listed above with the exception of digital tapes. If you believe the only thing that qualifies something to be memory is DRAM, then your definition is simply wrong.
It really could replace DRAM -- if they can get the endurance back up -- it's not bad endurance, just not really good enough to replace DRAM for most applications currently. But it'd take a lot of architecture work, and likely won't ever happen because there are very few markets in which loading an application is such a terrible pain point that people would actually pay to fix it. Some markets sure, just not enough for a tipping point.
What promises did Optane break? It seems to be exactly where everyone believed it would be. Much lower latency than SSD, at a price point somewhere between SSD and DRAM prices. Every benchmark I've seen shows that is exactly where it is.
I have to agree that this is the only answer I've seen so far that is actually right.
Agile is often at odds with Lean. Agile wastes a lot of time and effort in rewrites that you wouldn't have with waterfall. DevOps (CI/Unit Tests/automated security scans/CD) becomes vastly more important with Agile because you are making so many more builds than you would with waterfall. In order to change from say monthly or quarterly builds to weekly/daily (or multiple per day) builds, you simply can't have a QA team that keeps up if they are doing it all manually.
What area do you live in? Here in the Chicago suburbs I have both Comcast and Netflix and have no issues with multiple 4k streams from them at the same time.
Netflix is far from the market leader today if you go by the amount of content they actually have. Amazon Prime has a MUCH larger movie selection, and Hulu has a much larger TV series selection. Netflix falls somewhere inbetween, but they do have the best (IMHO) interface. If you are just looking to watch something interesting netflix is pretty good at finding stuff you may not have heard about that you will enjoy. If you are looking for a service where you already know what you want to watch, then Amazon Prime is much better (if it isn't a Netflix Original that is).
They think autonomous cars will be a widespread thing as soon as 2025? HAHAHAHAHA... cough, sniff... Ummm, no they won't. I have confidence they will become a thing eventually but it just isn't going to happen that fast. The legal framework and insurance alone is going to take longer than that even if the technology was ready today. And the technology is no where near ready for the General Public today. Best case I'd imagine you'll see rollout start at the earliest sometime in the 2030s with lots of testing and pilot programs over then next 10-15 years. Then it will take a few decades to really start gaining large amounts of market share presuming everything goes well up to that point and there are no showstopper technology or political problems.
You'd be wrong. Roll out started back in 2017 (http://www.latimes.com/travel/deals/la-tr-las-vegas-first-driverless-shuttle-to-loop-the-city-20171228-story.html). Yes, limited roll out, but there are driverless buses in a few places already. Cars aren't far behind (if they aren't already) -- in limited number, in limited zones, but starting to roll out none the less.
Actually emergency SMS don't require a SIM card, or a cellular plan in the USA (pretty sure on that, I've never personally tried it). You can also make emergency calls even with no SIM. That I've personally seen on an iPhone I ripped the SIM card out of because I wanted to use it as a WIFI only device. You can even make an emergency call on an iPhone without having the unlock code as well. I'd assume the Canadian system works the same, but I'm not positive on that.
** Emergency call in this context means to 911, 999, 180 or similar number.
And disabling the GPS really isn't much of a solution. Just knowing which cell tower you connect to will likely pinpoint your location fairly accurately, and the only way to disable that is to turn your phone off and leave it off.
Yes, here in Illinois at 75, you have to take a full driver's test (written, driving, and vision) test, and your license must be renewed every 2 years. At 89, it becomes every year.
That actually explains a lot. Every once in a long while someone comes along and makes a truly insightful post and I remember why I still come here. Thank you for that.
I could be wrong, as much of this was before my time, but I don't recall a single printer that interpretted LF as moving to the start of the next line, and a cursory examination of terminfo (the most complete database of terminal capabilities that I am aware of), and having written a couple dozen terminal emulators myself shows that the vast majority does exactly what I said.. "cr" is defined as the ASCII CR character, cud1 is defined as the ASCII LF character, and nel (new line) is defined as the combination of ASCII CR and ASCII LF: dumb|80-column dumb tty,
am,
cols#80,
bel=^G, cr=\r, cud1=\n, ind=\n, unknown|unknown terminal type,
gn, use=dumb, lpr|printer|line printer,
OTbs, hc, os,
cols#132, lines#66,
bel=^G, cr=\r, cub1=^H, cud1=\n, ff=^L, ind=\n, glasstty|classic glass tty interpreting ASCII control characters,
OTbs, am,
cols#80,
bel=^G, clear=^L, cr=\r, cub1=^H, cud1=\n, ht=^I, kcub1=^H,
kcud1=\n, nel=\r\n,.kbs=^H,
Well except that baudot didn't have a line feed character. It had a "line" character which both returned to the beginning of the line (like carriage return) and advanced the paper (like a line feed). Line feed by itself didn't go back to the beginning of a line. For all the terminals and printers I know of, if you sent it "abcdef", it would turn out like this: abc
def
As it was defined to do. And that's why line feed by itself is just wrong. That's also why character code 10 in every ASCII chart including the first one defined in 1963 is called "line feed", not "line". Line feed has a very specific definition, and multics/unix/linux misused it if you actually want to be able to call your text files "ASCII". It either conforms to the ASCII standard or it does not, and having a line feed character act line a CRLF simply does not.
But I agree with the ^Z (EOF) character. I can't count the number of times that copy {src} {dst} landed up truncating a binary file on me because I was too lazy to specify the/b option to tell it that it was a binary file and not stop at the first EOF character.
Let's be fair here. The correct implementation of a new line in a text file *IS* CRLF. It is the format you need to send a printer to print the text. A single CR would just print all the text on a single line overwriting itself over and over, and a LF would make the text look like a staircase (until it ran off the side of the page). CRLF is therefore the correct way to end lines in a text file (or LF+CR which actually makes more sense, but I wasn't consulted when the standards started). Seriously, just go read any manual that describes the ASCII control characters and there will be no doubt left in your head about what SHOULD be the correct way.
Linux got it wrong because it copied it from Unix. Unix got it wrong because it got copied from Multics (some of the original devs working on Unix were also devs on Multics). Multics (most likely) got it wrong because it was a bad performance hack (using a single byte to end lines is easier).
It is stupidly easy so long as you are actually holding your phone. One of the problems I have is when doing something in my car using hands-free stuff (usually voice), the iPhone comes back and says you must unlock your phone first. Great. So then I fumble to get my phone out and put my thumb on the home button so it can unlock so then I can ask siri to do something. Not having a passcode means I never have to fumble for my phone while driving just so it will do what I asked it to via voice.
Just an example of course. I actually do have a pin on my phone, but I wish I had finer control over what would require my phone to be unlocked to do, and possibly "trust" voice commands coming from my car (with good authentication). AKA, The car is running, so I have my car keys on me, please trust the voice commands from the car implicitly.
A Tesla will happily drive you into a stopped fire truck, or a turning semi trailer, or a freeway divider while you're driving at full speed. So yes, it's actively instigating accidents that humans are pretty good at avoiding. See google.
Teslas are also pretty good at avoiding those things, but not perfect. Neither are humans. That's why they have those crumple zones on the freeway dividers because human were crashing into them already. Humans also hit fire trucks, police cars, and ambulances with their lights on or off.
Slashdot Mirror
Because feature sets are often useless. I've had numerous routers in the past that "have" QoS, but when enable it, the entire network goes to crap because the QoS is being offloaded to the CPU (even though it has hardware QoS support). How something is implemented is often just as important as what is implemented.
*sigh*
Please read your own darn links. They refer to it as memory. If you aren't going to call it memory, which it is, what exactly would YOU call it? "thing that stores stuff for a computer, but isn't memory"?
Good work finding a detailed description of NAND and ignoring the information that is most front and center to consumers.
I don't have to when you send them to me.
You tried to discredit a promise Intel made on it's marketing material (which didn't make sense and failed to deliver) with ... a promise made on Intel marketing material.
Well, it's not really just marketing material when you can buy it and do it yourself. Granted with the P4800X, it's a software hypervisor (by a 3rd party) running with your OS as a client balancing requests between DRAM and Optane, but to the OS and the applications running under it, it has nearly the same effect. It's just adding one more tier of memory caching to the memory subsystem. Not really all that hard to grasp for anyone in the field.
---
I'm done with this thread. You can go on thinking that the one and only true memory is DRAM, while the rest of the world will go on realizing that you are just plain wrong. I'm sure you can do it. Just put your fingers in your ears, shouting LALALALA! or bury your head in the sand.
Now why do you think that NAND isn't sold as "memory" to consumers?
Let's stop right there, because NAND *IS* sold as memory to consumers. For example, let's take one of the largest suppliers of NAND flash products that are consumer facing today... Kingston. And here is an article by them: https://www.kingston.com/us/co.... "Here's a quick primer on what you need to know about NAND Flash memory."
Here is the wikipedia article on NAND: https://en.wikipedia.org/wiki/....
Cameras use "Memory Sticks" -- all based on flash memory.
I could sit here all day a google marketing press releases, articles, and spec sheets that showing how wrong you are, but you can easily do the same. Here you go: http://lmgtfy.com/?q=computer+...
The term memory has been well defined for over 50 years now. Not going to start redefining precise, well established terms because you don't understand them, or think they mean something they don't and never did.
-----
As for learning what marketing is, well... Considering that I understood the marketing and you did not, I would say that of the two of us, one of us doesn't understand what marketing is at all.
It really could replace DRAM
Maybe some day just not now, and not at launch, which is effectively the broken promise.
Or maybe it really could... at launch:
Intel® Optane SSD DC P4800X with Intel Memory Drive Technology enables data centers to deliver more affordable memory pools by displacing a portion of DRAM or significantly increasing the size of memory pools. This solution transparently integrates the drive into the memory subsystem and presents the SSD as DRAM to the OS and applications.
Available March of last year. Is it better than DRAM in every way? No. Is it better than DRAM in some ways? Yes.
Can't believe I have to explain this on slashdot, but... Optane IS memory. So is NAND, your old spinning rust drive, digital tapes, CDs, and blurays. In fact, not only is it memory, but it's also RAM (random access memory). But so is everything listed above with the exception of digital tapes. If you believe the only thing that qualifies something to be memory is DRAM, then your definition is simply wrong.
It really could replace DRAM -- if they can get the endurance back up -- it's not bad endurance, just not really good enough to replace DRAM for most applications currently. But it'd take a lot of architecture work, and likely won't ever happen because there are very few markets in which loading an application is such a terrible pain point that people would actually pay to fix it. Some markets sure, just not enough for a tipping point.
What promises did Optane break? It seems to be exactly where everyone believed it would be. Much lower latency than SSD, at a price point somewhere between SSD and DRAM prices. Every benchmark I've seen shows that is exactly where it is.
Pretty sure that "BS" is well within the definition of profane. Could even be listed as an example if the dictionary had one.
Unless your significant other is a doctor, your fucking location shouldn't be in the doctors office.
I have to agree that this is the only answer I've seen so far that is actually right.
Agile is often at odds with Lean. Agile wastes a lot of time and effort in rewrites that you wouldn't have with waterfall. DevOps (CI/Unit Tests/automated security scans/CD) becomes vastly more important with Agile because you are making so many more builds than you would with waterfall. In order to change from say monthly or quarterly builds to weekly/daily (or multiple per day) builds, you simply can't have a QA team that keeps up if they are doing it all manually.
What area do you live in? Here in the Chicago suburbs I have both Comcast and Netflix and have no issues with multiple 4k streams from them at the same time.
Netflix is far from the market leader today if you go by the amount of content they actually have. Amazon Prime has a MUCH larger movie selection, and Hulu has a much larger TV series selection. Netflix falls somewhere inbetween, but they do have the best (IMHO) interface. If you are just looking to watch something interesting netflix is pretty good at finding stuff you may not have heard about that you will enjoy. If you are looking for a service where you already know what you want to watch, then Amazon Prime is much better (if it isn't a Netflix Original that is).
They think autonomous cars will be a widespread thing as soon as 2025? HAHAHAHAHA... cough, sniff... Ummm, no they won't. I have confidence they will become a thing eventually but it just isn't going to happen that fast. The legal framework and insurance alone is going to take longer than that even if the technology was ready today. And the technology is no where near ready for the General Public today. Best case I'd imagine you'll see rollout start at the earliest sometime in the 2030s with lots of testing and pilot programs over then next 10-15 years. Then it will take a few decades to really start gaining large amounts of market share presuming everything goes well up to that point and there are no showstopper technology or political problems.
You'd be wrong. Roll out started back in 2017 (http://www.latimes.com/travel/deals/la-tr-las-vegas-first-driverless-shuttle-to-loop-the-city-20171228-story.html). Yes, limited roll out, but there are driverless buses in a few places already. Cars aren't far behind (if they aren't already) -- in limited number, in limited zones, but starting to roll out none the less.
Half of those were actually the CIA. The FBI would have little/no interest in most of them.
Actually emergency SMS don't require a SIM card, or a cellular plan in the USA (pretty sure on that, I've never personally tried it). You can also make emergency calls even with no SIM. That I've personally seen on an iPhone I ripped the SIM card out of because I wanted to use it as a WIFI only device. You can even make an emergency call on an iPhone without having the unlock code as well. I'd assume the Canadian system works the same, but I'm not positive on that.
** Emergency call in this context means to 911, 999, 180 or similar number.
The TV emergency broadcast system has the problem that it can only reach those who have the TV turned on.
And disabling the GPS really isn't much of a solution. Just knowing which cell tower you connect to will likely pinpoint your location fairly accurately, and the only way to disable that is to turn your phone off and leave it off.
Yes, here in Illinois at 75, you have to take a full driver's test (written, driving, and vision) test, and your license must be renewed every 2 years. At 89, it becomes every year.
That actually explains a lot. Every once in a long while someone comes along and makes a truly insightful post and I remember why I still come here. Thank you for that.
I could be wrong, as much of this was before my time, but I don't recall a single printer that interpretted LF as moving to the start of the next line, and a cursory examination of terminfo (the most complete database of terminal capabilities that I am aware of), and having written a couple dozen terminal emulators myself shows that the vast majority does exactly what I said.. "cr" is defined as the ASCII CR character, cud1 is defined as the ASCII LF character, and nel (new line) is defined as the combination of ASCII CR and ASCII LF: .kbs=^H,
dumb|80-column dumb tty,
am,
cols#80,
bel=^G, cr=\r, cud1=\n, ind=\n,
unknown|unknown terminal type,
gn, use=dumb,
lpr|printer|line printer,
OTbs, hc, os,
cols#132, lines#66,
bel=^G, cr=\r, cub1=^H, cud1=\n, ff=^L, ind=\n,
glasstty|classic glass tty interpreting ASCII control characters,
OTbs, am,
cols#80,
bel=^G, clear=^L, cr=\r, cub1=^H, cud1=\n, ht=^I, kcub1=^H,
kcud1=\n, nel=\r\n,
vanilla|dumb tty,
OTbs,
bel=^G, cr=\r, cud1=\n, ind=\n,
Erm.. Yay slashdot for eating thing that look like HTML. That was supposed to be "abc^Adef" would turn out like:
abc
def
Well except that baudot didn't have a line feed character. It had a "line" character which both returned to the beginning of the line (like carriage return) and advanced the paper (like a line feed). Line feed by itself didn't go back to the beginning of a line. For all the terminals and printers I know of, if you sent it "abcdef", it would turn out like this:
abc
def
As it was defined to do. And that's why line feed by itself is just wrong. That's also why character code 10 in every ASCII chart including the first one defined in 1963 is called "line feed", not "line". Line feed has a very specific definition, and multics/unix/linux misused it if you actually want to be able to call your text files "ASCII". It either conforms to the ASCII standard or it does not, and having a line feed character act line a CRLF simply does not.
But I agree with the ^Z (EOF) character. I can't count the number of times that copy {src} {dst} landed up truncating a binary file on me because I was too lazy to specify the /b option to tell it that it was a binary file and not stop at the first EOF character.
Let's be fair here. The correct implementation of a new line in a text file *IS* CRLF. It is the format you need to send a printer to print the text. A single CR would just print all the text on a single line overwriting itself over and over, and a LF would make the text look like a staircase (until it ran off the side of the page). CRLF is therefore the correct way to end lines in a text file (or LF+CR which actually makes more sense, but I wasn't consulted when the standards started). Seriously, just go read any manual that describes the ASCII control characters and there will be no doubt left in your head about what SHOULD be the correct way.
Linux got it wrong because it copied it from Unix. Unix got it wrong because it got copied from Multics (some of the original devs working on Unix were also devs on Multics). Multics (most likely) got it wrong because it was a bad performance hack (using a single byte to end lines is easier).
It is stupidly easy so long as you are actually holding your phone. One of the problems I have is when doing something in my car using hands-free stuff (usually voice), the iPhone comes back and says you must unlock your phone first. Great. So then I fumble to get my phone out and put my thumb on the home button so it can unlock so then I can ask siri to do something. Not having a passcode means I never have to fumble for my phone while driving just so it will do what I asked it to via voice.
Just an example of course. I actually do have a pin on my phone, but I wish I had finer control over what would require my phone to be unlocked to do, and possibly "trust" voice commands coming from my car (with good authentication). AKA, The car is running, so I have my car keys on me, please trust the voice commands from the car implicitly.
Unfortunately, storing that shipping data for the most recent order could violate the GDPR.... (sigh)
A Tesla will happily drive you into a stopped fire truck, or a turning semi trailer, or a freeway divider while you're driving at full speed. So yes, it's actively instigating accidents that humans are pretty good at avoiding. See google.
Teslas are also pretty good at avoiding those things, but not perfect. Neither are humans. That's why they have those crumple zones on the freeway dividers because human were crashing into them already. Humans also hit fire trucks, police cars, and ambulances with their lights on or off.
Well, that's 250Mbps anywhere in my ~4100sq ft house, on any floor. Not standing next to the AP.
Perhaps you shouldn't assume everyone buys the $10 Kmart special wifi devices and hook them up to a $20 WiFi router like you apparently do.