Here's what you do: go to about:blank, open the console and start typing JavaScript code. Try:
document.write('hello world')11–20 of 624 posts
Here's what you do: go to about:blank, open the console and start typing JavaScript code. Try:
document.write('hello world')I'm curious if the author has heard of sites like: * https://repl.it/ * https://jsfiddle.net/ I didn't see anything like that mentioned in the article, but I think that you can easily write code inside your browser today. Also, web browsers are already extremely heavy and complicated. That complexity is convenient for end users, but it also has costs, like making it very difficult and expensive to create a new compet…
>Here’s my pitch: build a browser that comes pre-installed with node.js, an IDE and a simple runtime environment. https://glitch.com/ https://runkit.com/home https://codepen.io/ https://github.com/features/codespaces Maybe you don't need new browser ? Maybe ?
When I was younger, one had to search high and low on the net trying to find help using shitty dial-up service. Then, you'd end up in some IRC channel asking for help and someone simply says 'RTFM!'
I'm curious if the author has heard of sites like: * https://repl.it/ * https://jsfiddle.net/ I didn't see anything like that mentioned in the article, but I think that you can easily write code inside your browser today. Also, web browsers are already extremely heavy and complicated. That complexity is convenient for end users, but it also has costs, like making it very difficult and expensive to create a new compet…
Plus: glitch/replit are quite slow to do any real coding inside of vs developing locally.
But maybe the future really is in the browser in this way.
>Here’s my pitch: build a browser that comes pre-installed with node.js, an IDE and a simple runtime environment. https://glitch.com/ https://runkit.com/home https://codepen.io/ https://github.com/features/codespaces Maybe you don't need new browser ? Maybe ?
Yeah I love Replit and Glitch (not used the others) but I still think there's something missing. They don't feel like standards that are easy and simple to use. Two more points: https://twitter.com/tomcritchlow/status/1349839954558427136
I take the "wtf is user/local/bin in $path?" to be a question from a non-tech person that is interested in learning to code. I can't be sure though since the author stated he has failed to install Node js. Should Chrome have Node JS loaded into it during install? I don't do web-dev so my answer is no. Should there be browsers made for those learning web-dev that come with these? By all means, sure. Go nuts. This also…
Googling "Making sure /usr/local/bin is in my $PATH" leads me here: https://stackoverflow.com/questions/19202007/making-sure-usr...
So I fire up the terminal and write echo $PATH and then go back to SO to see that it looks like it's all set up correctly. But why do I need to go to SO? Why do I need to fire up the terminal? It just feels too damn hard and too opaque.
I think defaults and documentation and onboarding matter. Not to mention a GUI :)