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

help-circle



  • Some Fillipino’s I’ve talked to have commented that drug problems in their area disappeared but used to be pretty horrible.

    I’m not one to defend crimes against human’s, but one cannot discount the level of criminality and the impact it was already having on people’s lives. Whether the tactics were fair or decent is one thing, but another is, did it work? Did it solve a serious problem the country was grappling with? You only have to look at Mexico to realise that if you don’t deal with these things, the level of murder and suffering often skyrockets.









  • 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.


  • CrypticCoffee@lemmy.mlMtoDeGoogle Yourself@lemmy.mlDegoogle Chromium help
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    8 months ago

    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).