It doesn’t need to be able to entirely automate a job to replace jobs though. If it enables one worker to be 10 times as productive, then the company can hire 9 fewer people (depending on how the productivity of the position scales)
Something that prevents me from adopting a lot of superior modern tools is that I need to SSH into a lot of servers and other machines that don't have the tools installed. I don't want to maintain the muscle memory and knowledge of 2 separate workflows & toolchains for the same tasks on different machines.
I'd like to see something that runs locally with my aliases, keyboard shortcuts, plugins, etc. and translates the commands to a remote backend, maybe similar to VS code's remote development.
Why can't we tackle XSS in the browser, by preventing javascript from executing in the <body> (or anywhere other than <head> for that matter)? There is an old memory protection technique of designating the stack & heap (data portions of memory) as non-executable. It seems like a similar idea should apply to the web, where the DOM is effectively a "data" portion, and separate out all executable javascript into a separate section. I know this breaks things like `onclick=` attributes, but can't those be replaced with event listeners? Of course it would be opt-in by setting an attribute somewhere in the DOM (e.g. <body non-executable="true">)
This seems like a fairly obvious idea to me, but I'm not a frontend developer, so I'm looking for someone to tell me why this doesn't already exist :)
Why can't we tackle XSS in the browser, by preventing javascript from executing in the <body> (or anywhere other than <head> for that matter)? There is an old memory protection technique of designating the stack & heap (data portions of memory) as non-executable. It seems like a similar idea should apply to the web, where the DOM is effectively a "data" portion, and separate out all executable javascript into a separate section. I know this breaks things like `onclick=` attributes, but can't those be replaced with event listeners? Of course it would be opt-in by setting an attribute somewhere in the DOM (e.g. <body non-executable="true">)
This seems like a fairly obvious idea to me, but I'm not a frontend developer, so I'm looking for someone to tell me why this doesn't already exist :)