Most modern techniques for ensuring anonymization make assumptions that won't constrain sophisticated blackhats. They are good policy in a legal ass-covering sense and increase the cost required to de-anonymize but that is about it.
Most modern techniques for ensuring anonymization make assumptions that won't constrain sophisticated blackhats. They are good policy in a legal ass-covering sense and increase the cost required to de-anonymize but that is about it.
There were some rough edges, but it only took me a few days of hacking to get it working. Thankfully, the ecosystem is much better today
I’m glad you had an easier time than we did!
If we built the app with the stable branch the bundle size was orders of magnitude smaller: less than 200kb. Still a bit of a chonker, but more reasonable than the ridiculousness the experimental SSR branch spat out.
It didn't read like that to me, I thought the point was they went for a rewrite on the new breaking changes major version, expecting specific features to eventually land, were waiting for them, and React had them already.
So it's more (to me) like 1) don't do that; 2) if you're going to do that maybe take a step back and there's something else out there already or that's a better fit.
It could have been any technology. The silver bullet is choosing the right tool for the job.
I don’t have an attachment to any particular tech. At the time React was what I knew, and I was coming off the back of building a server side rendered React site when I joined this company. I had a team of JavaScript-focused engineers to work with.
The statement is wrong-headed in so many ways it invalided anything the author could possibly say after.
Everything about this particular situation was exceptional. I focused on the decision to do a rewrite in the post because I thought it was the more interesting part of the story. In hindsight I might have gotten that wrong.
I think when most people say "don't do big bang re-writes", the reason behind it is the current development team unlikely has a complete understanding of the codebase. Once you have a million+ lines, no single person has a complete understanding of how everything works. People leave and new hires come up to speed, people forget how things work, etc., so the understanding of the system from an organizational perspective is rather fuzzy. Starting over in this situation is risky because the organization will inevitably have to re-learn forgotten things, re-implement and re-forget them to get to the same state that it was originally in. Much better to do one piece at a time in this situation.
We wouldn’t have been able to hit such an aggressive deadline under different circumstances.
This presents a small annoyance when I need to use another computer and start TYPING IN CAPS when I don’t intend to
This home row mod idea makes a lot of sense to me but I don’t think I would want to train my muscle memory to use such a drastic difference in behavior lest I find myself embarrassingly useless when presenting on a random work computer that doesn’t support this
The kbd community has all kinds of small form factor / isometric layouts like this that are totally custom and efficient but just make me think how you just train your hands to be shockingly unproductive on 99.99% of other systems
I’m proficient enough that I can work on anyone else’s machine well, and I have the comfort and speed benefits on my main workstation.