Of course there is requirements for networks with different features compared to the current Internet, Cisco just have to realize that it can't call them 'Internet'.
'Internet' precisely define a relatively cheap to operate neutral network that don't grant performance. Anyone can use it like it want to as long at it contribute to it and don't cause problem to the others participants. This fact have a lot of implication on how the network is managed and how it is sustainable financially.
It's right that the internet is not the best network for a categories of uses cases that need granted performances. This is a justification to build a other better network that fit the expected requirement. Call it 'Servicenet' of you wants. But this not a justification the fight against the net neutrality of the Internet.
This is old news: this system is already used on some cars since many years. Toyota for example have it at least since the 10 years old Prius II. And now think about the driverless Google car...
Take the question in a other way: if the car is autonomous there is no driver anymore, so in case of inevitable fatality (maybe no involving an other car at all), who will likely die in the car, depending of the last car action ?
Now imagine that the family of the killed peoples sue you for having rooted your car and modified his safety rules that make you survive instead of many others.
Ok, but the problem is that you will maybe not known in advance that you are in a car that is programmed with this feature. You might be in a car owned by an other, in a taxi, in a bus, etc...
I remember having build and used perfectly working small RF transmission devices with 27 MHz frequency. There never required a 3.5 or 14 meter long antenna !
"The PD communication channel is an RF system: - 23.2 MHz DFSK with a nominal deviation of 500kHz"
So the VBUS/GND pair alone can be enough to transmit data than USB LS (1 Mbps) and USB FS (12 Mbps). I see this a a very interesting solution: a standard to deliver negotiated power and mid range data rate using only 2 wires. If only the USB PD will allow a broadcast topology, I see a lot of possible applications...
The frequency of the power delivery is so high that an antenna could maybe be enough to transmit wireless data, without power. LOL
I don't pretend that Nodejs is comparable to Tomcat or similar options. I just noted that restarting on an uncaught exception, while not included in the Nodejs environment, is technically nothing special in Javascript virtual machine compared to others language. I have do that with a manager application or script in many projects. I will probably try to use systemd to do that in the future.
Agree on that. Replace it by Javascript virtual machine in my previous text. This is the same relation than with Java and his virtual machines implementations: http://en.wikipedia.org/wiki/L...
I suppose that it's possible to find the same opinion for any language. Actually it seem that Node.js raise in popularity.
Personally, I use it with Qooxdoo, and I found it a more effective solution that PHP for example. Having the same language in the server side and in the client side make the whole thing more coherent and simpler to maintain. I now experiment it for it portability across platforms to control a testing device from a browser.
While I agree that node.js don't have a UI, it still have to balance the time passed to compile and the time passed to execute. AFAIK, node.js use a single thread loop for the execution and probably for the compilation too. I think that dispatching the compilation to a second thread could reduce the latency of the execution thread.
While forking is a necessary fact to develop a new idea (even into the original community), merging (at lead idea) is even more necessary long term consequence to avoid fragmentation. The most dangerous thing for open source communities is to start to see others projects and communities as futile and without interesting for learning something.
Desktop related projects should really start to go into that direction now.
An this one is a perfect example: Can anyone get a clear picture of a >1500 comments story ? Probably not, or at least for the vast majority. The actual system is limited by the fact that is very hard to attach a personal contribution into the flow of comments. So, similar idea are expressed many times with little difference. I am not saying that the little difference should go away, but there can be attached the the common idea. The simplest way I can imagine to start implementing something is that direction, is to let move the comments into a graph, instead of a hierarchical historical flow. Typically a comment tend to develop the parent idea in either "it's true" or "it's false" relation: the graph should show that. There is certainly a lot of useful relations to the parent to add in practice. Sometime the relation is related only a a part of the parent comment.
Fully agree. Every single time there asked my view of the beta I tell them that is a hug vast of time for them and a hug vast of screen space for me. Uniform white pixels yield no information to me and force to scroll a lot more than with the classic interface. There wast the horizontal space by cutting them. There vast the vertical space with a top menu and insane high interline and bigger fonts. Finally there lost the "personality" of the Slashdot look by replacing it by a fade look that is like a newbie site.
There would be a lot or more creative ways to improve Slashdot, like finding a way to sort and assemble a graph of the expressed view across all comments of a story. This is hard, yes. But something like this can be a way to compile the comments of a story into something that look like a draft of a article on the story, making the whole thing simpler to read and to contribute. Uhmm... Ok, I will stop dreaming and weak up.
Virtual desktop work fine for my in Gnome 2. I use a 8x8 grid with 1 to 4 windows each, so the task bar is never full. I use the windows menu applet to find the exact window I want across all the desktops. I use the same setting with XFCE and with MATE. This config is efficient, coherent and really fast.
Under Gnome 3 or Unity, managing a static grid is a problem. Because the desktop management is too dynamic, every desktop can change it position relative to the other. This is a nightmare ! Imagine a 64 apartments basement where every apartments change his position relative to the others. You lose any ability to navigate quickly with a map in your brain. I found the right stack of desktop view helpless compared to a static grid. Using multiple windows application with Gnome 3 is hard because it tend to center every special windows in the middle of the screen. Unity is even more crappy because the common top menu bar change his context every time you pass over a window with sloppy focus enabled (click to focus is terrible). For both the desktop and window switching is far to slow, the right desktop and the right window is hard to find. Really a step back in term of productivity.
Slashdot Mirror
Of course there is requirements for networks with different features compared to the current Internet, Cisco just have to realize that it can't call them 'Internet'.
'Internet' precisely define a relatively cheap to operate neutral network that don't grant performance. Anyone can use it like it want to as long at it contribute to it and don't cause problem to the others participants. This fact have a lot of implication on how the network is managed and how it is sustainable financially.
It's right that the internet is not the best network for a categories of uses cases that need granted performances. This is a justification to build a other better network that fit the expected requirement. Call it 'Servicenet' of you wants. But this not a justification the fight against the net neutrality of the Internet.
The Toyota Prius have it at least since the Prius II from 2003. Now that depend how much you think this is a common car model...
This is old news: this system is already used on some cars since many years. Toyota for example have it at least since the 10 years old Prius II.
And now think about the driverless Google car...
Take the question in a other way: if the car is autonomous there is no driver anymore, so in case of inevitable fatality (maybe no involving an other car at all), who will likely die in the car, depending of the last car action ?
Now imagine that the family of the killed peoples sue you for having rooted your car and modified his safety rules that make you survive instead of many others.
Ok, but the problem is that you will maybe not known in advance that you are in a car that is programmed with this feature.
You might be in a car owned by an other, in a taxi, in a bus, etc...
I remember having build and used perfectly working small RF transmission devices with 27 MHz frequency. There never required a 3.5 or 14 meter long antenna !
From page 18 of this document: https://intel.activeevents.com...
"The PD communication channel is an RF system:
- 23.2 MHz DFSK with a nominal deviation of 500kHz"
So the VBUS/GND pair alone can be enough to transmit data than USB LS (1 Mbps) and USB FS (12 Mbps). I see this a a very interesting solution: a standard to deliver negotiated power and mid range data rate using only 2 wires. If only the USB PD will allow a broadcast topology, I see a lot of possible applications...
The frequency of the power delivery is so high that an antenna could maybe be enough to transmit wireless data, without power. LOL
The same document in page 14 limits the 60W and 100W profiles to the A and B type. So the C type is probably limited to 36W.
All others have to be quiet naive idiots ?
Look like xkcd is as reliable as the LHC on this subject: no Supersymmetry...
Sorry, you don't use the right command to see the reverse dependencies.
Try this:
apt-cache rdepends libgnutls26
I will not post the result here, because it's 494 lines long on my system:
apt-cache rdepends libgnutls26 | wc -l
494
Actually the brakes alone are enough to stop the car even in case of a full throttle bug.
I don't pretend that Nodejs is comparable to Tomcat or similar options. I just noted that restarting on an uncaught exception, while not included in the Nodejs environment, is technically nothing special in Javascript virtual machine compared to others language. I have do that with a manager application or script in many projects. I will probably try to use systemd to do that in the future.
Agree on that. Replace it by Javascript virtual machine in my previous text.
This is the same relation than with Java and his virtual machines implementations:
http://en.wikipedia.org/wiki/L...
... restart the service.
Yes, there is many ways to restart an application that died on a fatal uncaught exception. Again this is nothing specific to a language.
I suppose that it's possible to find the same opinion for any language. Actually it seem that Node.js raise in popularity.
Personally, I use it with Qooxdoo, and I found it a more effective solution that PHP for example. Having the same language in the server side and in the client side make the whole thing more coherent and simpler to maintain. I now experiment it for it portability across platforms to control a testing device from a browser.
AFAIK, uncaught exception is fatal in any language.
While I agree that node.js don't have a UI, it still have to balance the time passed to compile and the time passed to execute. AFAIK, node.js use a single thread loop for the execution and probably for the compilation too. I think that dispatching the compilation to a second thread could reduce the latency of the execution thread.
Maybe in a future revision. This would bee great !
Good move.
While forking is a necessary fact to develop a new idea (even into the original community), merging (at lead idea) is even more necessary long term consequence to avoid fragmentation. The most dangerous thing for open source communities is to start to see others projects and communities as futile and without interesting for learning something.
Desktop related projects should really start to go into that direction now.
...
An this one is a perfect example: Can anyone get a clear picture of a >1500 comments story ? Probably not, or at least for the vast majority.
The actual system is limited by the fact that is very hard to attach a personal contribution into the flow of comments. So, similar idea are expressed many times with little difference. I am not saying that the little difference should go away, but there can be attached the the common idea.
The simplest way I can imagine to start implementing something is that direction, is to let move the comments into a graph, instead of a hierarchical historical flow. Typically a comment tend to develop the parent idea in either "it's true" or "it's false" relation: the graph should show that. There is certainly a lot of useful relations to the parent to add in practice. Sometime the relation is related only a a part of the parent comment.
Fully agree. Every single time there asked my view of the beta I tell them that is a hug vast of time for them and a hug vast of screen space for me. Uniform white pixels yield no information to me and force to scroll a lot more than with the classic interface. There wast the horizontal space by cutting them. There vast the vertical space with a top menu and insane high interline and bigger fonts. Finally there lost the "personality" of the Slashdot look by replacing it by a fade look that is like a newbie site.
There would be a lot or more creative ways to improve Slashdot, like finding a way to sort and assemble a graph of the expressed view across all comments of a story. This is hard, yes. But something like this can be a way to compile the comments of a story into something that look like a draft of a article on the story, making the whole thing simpler to read and to contribute. Uhmm... Ok, I will stop dreaming and weak up.
Virtual desktop work fine for my in Gnome 2. I use a 8x8 grid with 1 to 4 windows each, so the task bar is never full. I use the windows menu applet to find the exact window I want across all the desktops. I use the same setting with XFCE and with MATE. This config is efficient, coherent and really fast.
Under Gnome 3 or Unity, managing a static grid is a problem. Because the desktop management is too dynamic, every desktop can change it position relative to the other. This is a nightmare ! Imagine a 64 apartments basement where every apartments change his position relative to the others. You lose any ability to navigate quickly with a map in your brain. I found the right stack of desktop view helpless compared to a static grid. Using multiple windows application with Gnome 3 is hard because it tend to center every special windows in the middle of the screen. Unity is even more crappy because the common top menu bar change his context every time you pass over a window with sloppy focus enabled (click to focus is terrible). For both the desktop and window switching is far to slow, the right desktop and the right window is hard to find. Really a step back in term of productivity.