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.
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
Actually the brakes alone are enough to stop the car even in case of a full throttle bug.
This is the same relation than with Java and his virtual machines implementations:
... 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 !
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.