Ben Matthews

  • New here on lemmy, will add more info later …
  • Also on mdon: @benjhm@scicomm.xyz
  • Try my interactive climate / futures model: SWIM
  • 0 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: September 15th, 2023

help-circle


  • Isn’t it technically possible to split browser functions so we can recombine as we like? - i.e. separating the rendering / js engine from everything around the side - managing all the tabs, bookmarks, cookies and passwords, workspaces and sessions, mail, notes etc. In my case, I like the workspace structure provided by Vivaldi, but don’t see why it has to be built on chromium browser. Anyway as a developer I need to test against blink, webkit and gecko, so would be nice to swap them within the same user interface structure.
    By the way, I develop a “javascript-heavy” web-app (interactive climate model) and it seems to be working fine, and fast, in firefox, so I’m not convinced by complaints in the article.









  • I’d like to have no phone at all, I don’t like small screens, nor being interrupted. Problem is that phone apps are now almost obligatory for IDs, transport tickets, passes, banking, etc. So I’d just like a phone-receiver (modem) with a sim card on a USB stick that can enable phone-app-stuff via my laptop or tablet. (Yes some tablets have data sim cards, but we still need sms and occasional phone functions for ‘verification’ etc.). Any suggestions?








  • I built personal webpages in the 1990s, and still do it now, I included javascript then, and still do now - to make calculations, show interactive graphics, quantitative stuff about climate change - see for example this model.
    I get your concept, that more websites should be written and hosted by individuals not big tech - but javascript is not the essence of the problem - js is just calculating stuff client-side for efficiency. In theory big tech could still serve up personalised algorithm-driven feeds and targeted advertising, just with server-side page generation (like php) and a few cookies, would waste more bandwidth but no stress to them. Whereas disabling client side calculations would kill what i do, as I can’t as an individual afford to host big calculations on cloud servers (which is also technically harder).