CCPA/CPRA provide opt out of data sharing for (ad) sales to third-party companies, but those were passed before the gAI boom. I imagine an analogue is already in motion for AI training opt-out in CA, but those two don't address model training.
But ~782 million ChatGPT users vs a few million pairs of glasses.
They are essentially choosing the philosophy of optimizing for speed in every dimension.
The tools selected are faster than their more mainstream counterparts — but since it's a static site anyway, the pre-build side of the toolchain is more about "nice dev ux" and the post-build is more about "really fast to load and read".
Location: Cincinnati, OH (Remote U.S.)
Remote: Yes
Willing to relocate: No
Technologies: Generalist SWE but lately Backend, Data Engineering & DevOps. Python, web apps & APIs (FastAPI / Starlette, Flask, Django / DRF, etc), workflows (Airflow) & automation, Platform Engineering & Cloud Engineering, AWS, GCP, Docker, Bash, Terraform, containers, infrastructure, CI/CD (especially GitHub Actions), architecture (software architecture, cloud architecture, data architecture).
Résumé/CV: https://www.linkedin.com/in/tedmiston/
Email: tedmiston+hn@gmail.com
Summary:
- I'm a principal software engineer (generalist recently focused on backend + DevOps) with 10+ YoE in software engineering roles professionally and experience from frontend to backend to shells, sysadmin, cloud, platform engineering, DevOps, CI/CD, security, etc etc
- I'm reentering the tech world after a sabbatical gap year and excited to find something that's a great fit
- I'm in the top 3% all-time on Stack Overflow having helped over 8 million software developers [1]
Please mention HN in the note if adding me on LinkedIn.
Location: Cincinnati, OH (Remote U.S.)
Remote: Yes
Willing to relocate: No
Technologies: Generalist SWE but lately Backend, Data Engineering & DevOps. Python, web apps & APIs (FastAPI / Starlette, Flask, Django / DRF, etc), workflows (Airflow) & automation, Platform Engineering & Cloud Engineering, AWS, GCP, Docker, Bash, Terraform, containers, infrastructure, CI/CD (especially GitHub Actions), architecture (software architecture, cloud architecture, data architecture).
Résumé/CV: https://www.linkedin.com/in/tedmiston/
Email: tedmiston+hn@gmail.com
Summary:
- I'm a principal software engineer (generalist recently focused on backend + DevOps) with 10+ YoE in software engineering roles professionally and experience from frontend to backend to shells, sysadmin, cloud, platform engineering, DevOps, CI/CD, security, etc etc
- I'm reentering the tech world after a gap year and excited to find something that's a great fit
- I'm in the top 3% all-time on Stack Overflow having helped over 8 million software developers [1]
If adding me on LinkedIn, please mention "HN" in the note or message, so I see it!
Mostly that FF has ~36k extensions (January 2024) [1] and Chrome has ~112k (June 2024) [2].
[No doubt, total count of extensions isn't the most important number and there's a long tail in both counts of very small user bases, but this paints the ~3x picture in a broad stroke.]
Of course, since FF migrated to WebExtensions in 2017, theoretically most Chrome extensions can be ported to FF with minimal changes [3] — practically speaking though, not all of the big ones actually have, or the FF equivalents to some of the most useful Chrome extensions are far less polished.
And also, if you're developing front end web apps for normal end users, most are still on Chrome... over the years, I've experienced an unfortunate number of sites that should work across Chrome/FF/Safari actually break because of things like the developers not even testing in browsers besides Chrome given its dominance. I'm not encouraging that by any means, but the reality is that it still happens.
reply