Re: [NNagain] Internet Education for Non-technorati?

[rjmcmahon <rjmcmahon@rjmcmahon.com>]

I agree that sw & firmware upgrades are better than big jumps.

I don't know the numbers but a guess is that a majority of SoCs with 
WiFi radios aren't based on openwrt. I think many on this list use 
openwrt but that may not be representative of the actuals. Also, the 
trend is less sw in a CPU forwarding plane and more hw, one day, linux 
at the CPEs may not be needed at all (if we get to remote radio heads - 
though this is highly speculative.)

 From my experience, sw is defined by the number & frequency of commits, 
and of timeliness to issues more than a version number or compile date. 
So the size and quality of the software staff can be informative.

I'm more interested in mfg node process then the mfg location & date as 
the node process gives an idea if the design is keeping up or not. Chips 
designed in 2012 are woefully behind and consume too much energy and 
generate too much heat. I think Intel provides this information on all 
its chips as an example.

Bob
> On Wed, 11 Oct 2023, David Bray, PhD via Nnagain wrote:
> 
>> There's also the concern about how do startups roll-out such a label 
>> for
>> their tech in the early iteration phase? How do they afford to do the 
>> extra
>> work for the label vs. a big company (does this become a regulatory 
>> moat?)
>> 
>> And let's say we have these labels. Will only consumers with the money 
>> to
>> purchase the more expensive equipment that has more privacy and 
>> security
>> features buy that one - leaving those who cannot afford privacy and
>> security bad alternatives?
> 
> As far as security goes, I would argue that the easy answer is to ship
> a current version of openwrt instead of a forked, ancient version, and
> get their changes submitted upstream (or at least maintained against
> upstream). It's a different paradigm than they are used to, and right
> now the suppliers tend to also work with ancient versions of openwrt,
> but in all the companies that I have worked at, it's proven to be less
> ongoing work (and far less risk) to keep up with current versions than
> it is to stick with old versions and then do periodic 'big jump'
> upgrades.
> 
> it's like car maintinance, it seems easier to ignore your tires,
> brakes, and oil changes, but the minimal cost of maintaining those
> systems pays off in a big way over time
> 
> David Lang
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
> 
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain