...Fortunately, there are ways to interface with the outside world, and we're free to choose the best tool for the job, but often times that doesn't happen. ...
... but once you get comfortable using some advanced features, figuring out protocols and things like that, everything starts to get easier because you can always just choose the right tool for the job...
Language barriere prevents me to understand exactly what you mean with this, but I can share some personal "outside world communication"
Serial (RS232 RS485 Usb Bluetooth) just works fine.
Modbus RTU, anafase: works fine
Communication with their cheap Usb-ni-6008: Limit the datarate yourself.
Ethernet UDP: just works fine.
Ethernet TCP: a few reconnect problems, works fine with an extra test/workaround
Modbus TCP, their library: Slow and Reconnect problems
I/O server PLC OPC open protocols: Works at the end of the day, works for decades, till you need it.
I know. It's all under normal Windows XP/7, witch can be the root of all problems.
But there is a difference between how NI markets the "solutions" and how Labview performs.
In every program, I include a multi-state FSM where every connection has its own separate states loop, all auto re-entrant without restart/program-re-init. On top of the existing included fault detections, with some homebrew heartbeat or other test.