• 13 Posts
  • 117 Comments
Joined 2 years ago
cake
Cake day: July 10th, 2023

help-circle




  • Astroturfing is designed not to look like an ad. It’s supposed to look like grassroots support for a product. Legitimising it for the audience. Strategically, it’s effective. “Privacy market leader is bad for x, y and z, what do you think of competitor?”. It’s classic marketing of “here is problem, here is solution”. Just subtle.

    Most people here are probably off gmail or close to it. Best way to make inroads is work your way into a niche which Proton, Tuta, Mailbox did to great effect. As I say, I don’t trash the tried and tested options including rival products of Proton. This is email though, usually you want to put data in hands of companies you trust. Its the reason folk running from google, yahoo, outlook. Being careful and skeptical is good.













  • Not perfectly optimised is fine, but non-functional isn’t acceptable. I’ve never seen a quirk personally, and quirks aren’t a good reason to help maintain Google’s monopoly on web standards.

    You may say less than 5% is fine, but it could be the margins in a low margin industry. 2% could be 40% of the profit.

    I haven’t seen a team operate where a senior isn’t checking it.

    Usually the bleeding edge stuff is used by small companies trying to establish themselves because they have nothing to lose and no reputation to protect.

    Plus, when you got Browser Stack, you catch a lot of problems like this.


  • Because in web development there are compatibility tables of what features work with which browser. If a developer has used a feature poorly supported, they either haven’t done their homework, or intentionally made that call.

    In web development, most reputable Front End Devs would not choose bleeding edge, barely supported features even if the temptation was there because the user comes first. Generally, you wait until it has been adopted by the main browsers (chrome, safari, ff).