3 ms·
Presumably they wanted the telemetry. It's not clear that this was a dev-initiated switch. Perhaps we can blame the 'statistical monetization' policies of adte
by mjburgess 1y ago
Presumably they wanted the telemetry. It's not clear that this was a dev-initiated switch.
Perhaps we can blame the 'statistical monetization' policies of adtech and then AI for all this -- i'm not entirely sold on developers.
What, after all, is the difference between an `/etc/hosts` set of loop'd records vs. an ISP's dns -- as far as the software goes?
- sgarland 1y agoYou’re right, and I shouldn’t necessarily blame devs for the idea, though I do blame their CTO for not standing up to it if nothing else. Though it’s also unclear to me in this particular case why they couldn’t collect commands being issued, and then batch-send them hourly, daily, etc. instead of having each one route through the cloud.
- skydhash 1y ago> Presumably they wanted the telemetry Why not log them to a file and cron a script to upload the data? Even if the feature request is nonsensical, you can architect a solution that respect the platform's constraints. It's kinda like when people drag in React and Next.js just to have a static website.
- arolihas 1y agosomeone out there now has a cool resume line item about doing real time cloud microservices on the edge