• 0 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • At some point you have to let them fail. Remind them of it again, so that when they cause a major issue in prod you can point out that you communicated it to them multiple times. If this team keeps causing outages (and aren’t covered for by other teams) then, hopefully, management high enough will become aware of it and start to crackdown on them. I know you said elsewhere you don’t want them to lose their jobs but if they can’t do it, they shouldn’t have it. It’s not like you’re sabotaging them - you’re still helping them with advice and warnings. If despite that help they still can’t get by, then them getting terminated is the remaining best outcome.




  • festus@lemmy.catoProgramming@programming.devnew Date("wtf")
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    17 days ago

    Yes and no. Wasm has no “standard library” so if you wanted to use Dates, your wasm would need to have its own implemation bundled for when the user visits the page. Ditto for everything else including string support! As you can imagine having to ship all this basic functionality can bloat the wasm and slow page loads.

    You also can’t fully escape JS, as the only way wasm can interact with the page & browser are through the JS functions you write and make available to your wasm. I suppose you could take advantage of this to not have to ship your own standard library & use the JS Date implementation, but at that point why not just use JS?

    Wasm has strengths but it’s not suitable for replacing JS for everyday websites.