Live data from Hacker News

Why can't I write code inside my browser?

tomcritchlow.com

11–20 of 624 posts

Re: Why can't I write code inside my browser?

#12

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…

Back in college I would sketch something every day in jsfiddle

Re: Why can't I write code inside my browser?

#14

>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

Re: Why can't I write code inside my browser?

#15
The whole sentiment of this article just comes off a little whiny to me. Nowadays there is so much more information available for learning how to code and set up your dev environment. There are literally coding books for kids at book stores. And StackOverflow!

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!'

Re: Why can't I write code inside my browser?

#16

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…

Mentioned Glitch and Replit in the article - they're great and I love them but there's still something missing about relying on these platforms imho. I think cementing a default coding environment right into the browser would make it a lot more accessible - and actually be much closer to real coding where you're manipulating files and running code.

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.

Re: Why can't I write code inside my browser?

#19

>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 believe node itself s just an environment/blank canvas as well. What is this "standards" you're looking for? There are a million frameworks, templates, etc as well.

Re: Why can't I write code inside my browser?

#20

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…

This was a real question FYI. I don't know what that means.

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 :)

Post reply on HN