-
Good read. But isn’t the Multi-language point exactly what WebAsm is trying to address? In WebAsm we are able to target different languages to one lower level language browsers understand, but seems like author wants the browser to understand how to work with them natively (meaning supporting other languages and have their VMs, runtimes etc). Won’t that make browser bigger OS-like monsters, memory hogs etc? I think this is a bit of an overwhelming idea for a browser. Web Assembly is a good solution for what it does
-
-
Even if they use the ones on my machine that’ll mean browser will require me to have them installed, as prerequisites, or try to install them itself, and use them on runtime. This is way too much for what a browser needs to do, IMHO. Just go for Wasm to accomplish the same without having to support tens of languages on the browser, and also, you need to react to render “on your own native language”. They’ll have to convert render calls to canvas, WebGL, DOM, whatever. You can’t achieve that by just using the VMs installed
-
-
-
-
deankevorkian
7 months ago
|
link
| on:
nEXT Browser: an extensible, keyboard driven Lisp Browser based on WebKit
Nice. So it’s mostly for web developers or really as mentioned power users. A matter of time until we see “how do I quit nEXT” posts :) The navigation experience reminds me of Chrome’s Vimium ext. https://chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb?hl=en
-
-
Good start… now what about templating alternatives like Telegram’s Instant View? Millions of links being sent over IM every day are being rewritten into new templates created by a third party. Sure, it addresses the speed / mobile accessibility concerns, but it’s also very heavy-handed backend processing that’s a black box to users.
-
-
-
Before clicking your link, I was unfamiliar with Telegram and Instant View, so take this with a grain of salt…
Isn’t this just another version of the same thing? Doesn’t an Instant View prevent clicks to the host domain?
And, conversely, isn’t this all a consequence of business models riddled with terrible ad networks? Dropping AMP or Instant View or any other scraper/viewer doesn’t fix that weakness.
-
More like mix of Facebook’s Instant Articles and Reader Mode from Safari/Firebox (also Pocket). It doesn’t require special markup to put on webpage but it has crowdsourced rewrite rules that remove cruft from webpages. It loads processed webpages from their server though, unlike Reader modes.
At least Telegram leaves links posted to chat as is, looking like links, with underline, leading to original URL, and adds “Instant view” button alongside, which looks like button and opens instant article popup.
BTW, their rule language is crappy.
-
Telegram is/was important in the recent Iran riots.
For example: https://www.politico.com/magazine/story/2018/01/01/irans-telegram-revolution-216206
Unlike Twitter, millions of Iranians use Telegram in their everyday lives—around 40 million monthly users in a country of 45 million overall online users, according to the latest ITU statistics.
-
To my understanding it is - just a different content/service provider that wants to create a platform to give the same experience to its users. There are some differences in the implementation by telegram and the effort that needs to be put by the sites developers, but it is still served by cache that is kept on their servers. In this point you’re getting a good experience loading, say, Medium articles in Telegram - but you don’t get the same experience outside of it.
-
-
-
Ok, so all datacentres will now do irrelevant blockchain operations to their actual goals in order to satisfy Nvidia.
(Or someone just sues Nvidia instead.)
-
-
Or keep the old drivers and avoid the new terms :)
-
-
deankevorkian
7 months ago
|
link
| on:
How to become a part-time programmer: an interview with an expert
I think that beyond the benefits that are mentioned here for working part-time, you are more invulnerable to painful actions taken by faulty management (for example - having or being expected to work extra time). This is a huge factor and sometimes leads to being burnt quickly. Good friend of mine works on a place where they are expected to work extra time where delivery time is near. Not only is he burnt, but he’s much less productive than if he worked a reasonable amount of time daily. There’s a sweet spot that any individual should know or find, of amount of hours you want to work before you take a break.
I get your main point(s) but I don’t think WebAssembly is a “weapon” that’s deadlier than JavaScript nor is it the worst idea since JavaScript… The problems that exist in the Web world are not in JavaScript or its implementation (there are problems with these but they are irrelevant to the topic). The problems are in its use in browsers which are the weapons themselves. There’s a reason browser heavily limits operations and APIs for developers to use. I think Web assembly doesn’t make the situation worse, it only makes the current situation better for developers as they are not limited to a specific language, and allows for further optimizations and performance in browsers. What makes this statement stronger is the fact that the WebAssembly project is being pushed forward at huge steps by teams at mozilla - on the browser side and on Rust that aims to be one of the first citizens of Web assembly. So I don’t think mozilla will be the first to stop this unpleasing situation.. There are many other security problems that have nothing to do with these. And I think that with time and experience and, of course, huge scandals like Cambridge Analytica things will get more balanced… Until next time. Just like everything in life and everything in software.. Easily and comfortably serving code remotely to be executed on a target machine is a challenge.
I do not agree.
I’ve had to debug optimized binaries without having the sources in the past (produced by GCC with -O2 and no debug symbols) and I often have to debug minimized and obfusced JavaScript on several browsers.
I do not like JavaScript, but debugging binaries is way more expensive.
Most web browsers are not weapons. They are HyperText renderers.
Just mainstream browsers are weapons. Remove all scripting languages from web pages, and you will get pretty decent tools. And secure ones.
And almost entirely useless ones.
Users want applications, not just linked documents.