That is absolutely 100% what I am saying and is 100% the truth. You may think it’s “retarded” (nice ableism) but that’s probably because you are white and don’t talk to or listen to black people. Talk to any black woman or black trans person and ask them if they feel white people care about racism. News flash: the vast majority of white people and white progressives do not fucking care about racism unless it’s convenient for them to do so.
I like how everyone is concerned about the trans slurs but completely ignores them dropping the n word. Sounds about white for the crowd here I guess
deleted by creator
The caching is the result of service workers which Firefox definitely supports.
edit: oh just scrolled down and saw you already commented that later.
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
I’ll give a +1 for this course. Prime is a great teacher. I’ve been a dev for a decade at this point and it really helped fill in the gaps for me that I’ve been missing all these years.
That would be pretty neat if something like that existed.
https://youtubetranscript.com/?v=PJSTFzhs1O4
Here is the transcription gathered from the subtitles on the video.
Ok but local first p2p software doesn’t rely on centralized servers. So it’s not a huge deal if you don’t have always on servers. Hell you can probably avoid servers all together.
From their repo (https://github.com/rui314/mold#how-to-use)
Create .cargo/config.toml in your project directory with the following:
[target.x86_64-unknown-linux-gnu] linker = “clang” rustflags = [“-C”, “link-arg=-fuse-ld=/path/to/mold”] where /path/to/mold is an absolute path to the mold executable. In the example above, we use clang as a linker driver since it always accepts the -fuse-ld option. If your GCC is recent enough to recognize the option, you may be able to remove the linker = “clang” line.
[target.x86_64-unknown-linux-gnu] rustflags = [“-C”, “link-arg=-fuse-ld=/path/to/mold”] If you want to use mold for all projects, add the above snippet to ~/.cargo/config.toml
Holy fuck I know you did not just say you can say the fucking n word because of GTA. It doesn’t matter how many of your favorite rap songs say it. It doesn’t matter if your favorite video game says it. You cannot fucking say it. Jesus fuck are we letting the racists just be on these communities now? Get the fuck out of here you racist piece of shit.