----------------------------------------------------------------------------------
@MSGID: <ai1hhi91fdglirhgljn9l2nob0dq9u54cf@4ax.com>
98002f5a
@REPLY: .dlg@v.nguard.lh> e91929a2
@REPLYADDR micky <NONONOmisc07@fmguy.com>
@REPLYTO 2:5075/128 micky
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<ai1hhi91fdglirhgljn9l2nob0dq9u54cf@4ax.com>
@RFC-References: 1@dont-email.me>
1@dont-email.me> 3@dont-email.me> .dlg@v.nguard.lh>
@TZUTC: -0400
@TID: FIDOGATE-5.12-ge4e8b94
In comp.mobile.android, on Tue, 26 Sep 2023 13:36:13 -0500, VanguardLH
<
V@nguard.LH> wrote:
>Moribundo <
lindev.null@protonmail.com> wrote:
>
>> candycanearter07:
>>
>>> Being technically better doesn`t mean it will succeed. Just look at
>>> webp or apng.
>>
>> Sure, I don`t think that it will spread and create standard
>
>For sure, especially if Huawei won`t license it to anyone else (well, to
>the US). Of course, it`ll only work when used with another device
>capable of doing Nearlink.
>
>While I use wi-fi at home, and rare times when travelling, I don`t need
>more speed for bandwidth that is already for more proficient than needed
>for calling. I don`t play videos on my phone. And Bluetooth is, well,
>now that I think of it, only used from my phone to my car for
>navigation, and it`s fast enough, so faster won`t give me anything.
Same for me.
Of the list, double the range would have meant I could play sounds from
my computer on my bedroom radio, but where was Huawei when I needed to
solve this. It`s solved now, but if I could switch to Nearlink, I`d
need to buy a new radio to go with it. So I`d stick with what I`ve got.
--- Forte Agent 4.2/32.1118
* Origin: Tweaknews (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441