This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ripe-list] https://www.ripe.net/ inappropriate javascript
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Sun May 5 13:34:14 CEST 2019
> On 4 May 2019, at 16:39, Leslie <geekgirl at gmail.com> wrote: > > Jim, I'm not sure if you've worked doing web development, but I agree > with Nick that you can get a lot of performance data from these > services (not just tracking or marketing) which is incredibly useful. AFAICT nobody’s disputing that Leslie. I simply question that gathering and analysing such data is worthwhile or appropriate for RIPE. After all we aren’t in the marketing business or running a social networking site (same thing really). > People visit websites with all sorts of combinations of browsers, > OS'es, and extensions -- and no matter how good of a test system you > have, you'll never be able to accurately predict each combination and > weird side effects will happen. All the more reason to avoid needless cruft that gets in the way of interoperability. Too many web designers seem to ignore this. It shouldn’t/needn’t be necessary to crunch through a raft of web analytics to learn that either. As my gran used to say, you don’t need to jump into the Clyde to find out if you’re going to get wet.
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]