• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • Most games, image processing libraries and other compute demanding libraries already use WASM in the browser. Have been for quite some time. It’s already widely used in every case where it provides a substantial benefit.

    But writing for GUI, which is what 99% of JS is used for, WASM provides little benefit. The speed bottleneck is mostly in DOM manipulation. And every web GUI framework uses 200 npm packages with something like webpack. Getting that to somehow work with your WASM code would be a nightmare if it’s even feasible.







  • There are AOSP based roms that are de-googled. You can use third party app stores to download foss software, or other 3rd party stores that let you download from Google play (aurora). iPhone is basically the only other choice, but it’s not any better in this context.

    Lots of alternative email providers. Protonmail is one.

    For maps, openstreetmap exists. You can also use Google maps without an account inside a secure browser. That will minimize data collection.

    You can use a downloader (yt-dlp or a gui that wraps it) for YouTube, or use a 3rd party app like NewPipe. Again, using YouTube without an account in a secure browser is an option.

    Chrome can obviously be replaced with Firefox/LibreWolf. If you must have a chromium based browser, you can use ungoogled chromium. chrlauncher is a small app that can be used to make it easy on windows and keep it updated.

    You cant really do anything about the apps that use chromium internally for rendering, besides finding replacements.



  • All the issues KOSA is aiming to address are also issues that affect the general population. I would say legal age teenagers and young adults are affected just as much.

    If the issues are deemed harmful enough to require legislation, then it should be addressing the issue themselves rather than adding harm by passing insanely privacy violating bills.

    And when it comes to children, parents should be responsible for what their children as exposed to on the internet. This debate is decades old and it’s pretty much been settled. Despite the society being strongly against exposing children to any sexual content, porn websites don’t have any age verification. Parents are responsible for what their child views on the internet.




  • Users often depend on websites trusting the client environment they run in. This trust may assume that the client environment is honest about certain aspects of itself, keeps user data and intellectual property secure, and is transparent about whether or not a human is using it. This trust is the backbone of the open internet, critical for the safety of user data and for the sustainability of the website’s business.

    Jesus christ just the introduction paragraph is a load of horseshit. Actually bold faced lies. Users depend on websites trusting the client? In what fucking world are websites trusting the client??? Literally the only case is the media DRM that should have never been part of the web in the first place.





  • Being easy to understand is one of the primary goals of any programming languages.

    The problem with Javascript is that it isn’t easy to understand. Javascript is easy to write.

    That’s why it’s easy for novices to pick up and why it ends up being spaghetti code. It’s very unrestrictive and allows writing very poor code that works based on assumptions and breaks when the assumptions aren’t met.

    It made sense at the time because it was just a scripting language for some minor website things, and you didn’t want your site to crash if your script ran into a problem.

    Now it’s being used to write full fledged applications and it’s past design choices are still haunting it.