Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AN
Posts
0
Comments
197
Joined
2 yr. ago

  • My wife used to never consider herself a feminist because of how white feminists simply do not care about the issues of black women. Back in the old site there were tons of discussions around r/blackladies about how subs like 2x were horrible because every single time a black woman would post about her issues she faced with racism all the white liberal women would come out and invalidate and question and deny their experiences. Feminism without anti racism is dead. Gloria Steinam realized this and I wish others paid attention.

  • If you use rust and structure your program correctly you can avoid debugging directly by building unit tests in language the verify behavior. Debugging tools are great and I look forward to better dx stories there (you can use chrome + DWARF to debug your native code) but strictly speaking it isn't necessary most of the time.

  • The language best suited for wasm is easily rust. And you can still interface with the Dom using frameworks like yew sycamore or leptos.

    Debugging is still a little tricky but you can debug wasm in chrome and DWARF allows you to have source maps that map to your rust code. This is s problem the community is working to improve. Until then you have the full power of console log which is how a large portion of developers already debug their applications.

  • JS has little to do with accessibility. Most web accessibility comes from the Dom and aria attributes as well as semantic tags. You can do all of that with wasm too.

    Are you asking about how it will work with wgpu based applications? This will work the same as it does on desktop applications. The program calls out to libraries that support talking to screen readers. I know rust the language with the best support for and ecosystem around wasm libraries like this already exist and ui frameworks like egui already have some support built in.

  • Ok but no one is talking about hand writing wasm. You write wasm with a language, such as rust, which already has great web frameworks such as yew (which replaces react) as well as leptos (which replaces solid.js). Leptos is already faster than react vue and svelte

  • Hate to break it to you bud. The world isn't ending. It's going to still be here. Humanity is going to still be here. We're going to survive the worst of it and continue going. It'll get real hard but at no point are we looking at the end of the world or of humanity. The stuff that'll be really bad won't be any time soon. Probably not in your lifetime. You can go ahead and live your life and have fun.

  • Ugh word does this. I didn't realize until I wrote some documentation for a cli tool I made for a client and I wrote the documentation in word because they are fairly non technical so I wrote in the documentation sample arguments they can copy and paste and shipped it feeling good that it would work flawlessly because I tested the crap out of it. Or so I thought because they immediately hit back with it doesn't work. I spent hours recreating their environment and watching it work no matter what I tried to get it to not work. Then I hopped on a call and had the client step by step show me what they did and they opened the word doc and copied the example commands, changed the arguments to be correct and run it. I followed along on my own machine and then I fucking saw what had happened. Fucking Microsoft Word replaced my " " with “ ” (straight quotes for smart quotes for those who cant see the difference). A quick patch of the cli to properly parse those and things were working again.