It's interesting how STREAMS pervaded everything for a short while (Apple's Open Transport networking stack for System 7.5 and up was also based on STREAMS) but everyone almost immediately wanted to get rid of it and just use Berkley sockets interfaces.
I still don't quite get how you should had communicate with the other systems over the network with STREAMS.
With IP you have an address and the means to route the data to that address and back, with TCP/UDP sockets you have the address:port endpoint so the recipient doesn't need to pass a received packet to the all processes on the system, asking "is that yours".
So if there is already some network stack providing both the addressing and the messaging...
STREAMS isn’t a networking protocol, it’s an internal data routing thing some UNIXes use locally, and amongst other things to implement the network stack in it.
You’d still be talking of stuff like IP addresses and the like with it. Probably with the XTI API instead of BSD sockets, which is a bit more complex but you need the flexibility to handle different network stacks than just TCP/IP, like erm…
ZTE is also under scrutiny. The reason it's only Huawei and ZTE is that other Chinese providers are so insignificant that the telecoms will likely be able to replace the infrastructure themselves with spares or consolidation. However, in an emergency, the government would have to foot the bill for replacing Huawei/ZTE systems quickly, as the telecoms couldn't finance this and lack of capacity would mean very high prices.
"Chat Control" is mass surveillance, not targeted Action.
Targeted action mayhaps needs some readjustment, but by and large is already easy to obtain for law enforcement.
Normalizing mass surveillance would set a precedent for authoritarian regimes worldwide to demand similar access, further eroding privacy and human rights on a global scale.
I also oppose it on technical grounds, since it would be some kind of local or hybrid ai that does the scanning. A high number of false positives harming innocents would certainly be the result.
There is something to the existence of fads and fundamentals. When I started, it was Object-Oriented-Programming (with multiple-inheritance and operator overloading, of course), Round-Trip Engineering (RTE), XML, and UML.
IMHO, not the ideas were bad, but the execution of them was. Ideas were too difficult/unfinished/not battle-tested at the time. A desire for premature optimisation without a full understanding of the problem space. The problem is that most programmers are beginners, and many teachers are intermediate programmers at best, and managers don't understand what programmers actually do. Skill issues abound. "Drive a nail with a screwdriver" indeed.
Nowadays, Round-Trip Engineering might be ready for a new try.
MS Sidewinder Force Feedback Pro (1997) and Sidewinder Force Feedback 2 (USB).
You can buy similar today, but nowhere near the pricepoint. Also the out of the box support by Windows has vanished, and therefore the incentive of game developers to include force feedback.
I still have my MS Force Feedback 2, and it still works great!
I heard that some patent troll got a hold of the patent for force feedback joysticks, and all manufacturers just gave up on them because of the troll. The patent expired recently IIRC, so hopefully people will start making them again soon.
A bit of both. Also, the modern Codecs have slightly different tradeoffs (image quality (PSNR, SSIM), computational complexity (CPU vs DSP vs Memory), storage requirements, bit rate) and therefore there isn't one that is best for every use case.
reply