Earlier quoted context omitted.
It's different than TCP/IP in that every transaction changes the topography of a payment channel network, by changing the maximum amount that can be sent across various channels. This is a fundamental difference. Moreover, even if LN worked as a full substitute for on-chain transactions (all indications point to only a very centralized hub and spoke LN model working efficiently), Bitcoin's three transactions per seco…
Yes this is something I'm following too. So although Bitcoin has a low transaction per second limitation, the database Transaction objects can contain hundreds of transactions between users. This is what batching does. Segwit further helps lower the size of Transaction objects. And further proposals also lower that further.
Can you elaborate or provide a link?
If you're referring to off-chain transactions through LN that are 'batched' on chain: these cannot set up payment channels. On-chain transactions for payment channel set up are the necessary minimum for the LN, and even to do just this, Bitcoin's block size limit doesn't come close to being adequate.
As for Segwit, it's a one time limit increase to something like 1.67 MB per 10 minutes (~2 KB/s). The limit needs a couple order of magnitude increase to make Bitcoin viable as a global currency.