News for hackers. Stuff that matters.

A comment on Why can't I write code inside my browser?. Parent comment

Re:Why can't I write code inside my browser? by aspaceman on Friday January 15, 2021 @07:07AM (#25789931)
Yeah like there's 20 years of programming language research that studies exactly what this person is talking about.

Graphical programming languages, removing barriers to learning, etc. They've been chugging away for decades and visual programming, Blender, Blueprints, Scratch, etc are all we got out of it.

Does the article writer just think research doesn't exist? That CS sprouted from existence fully formed as a web browsing experience?

[ Parent | on HN ]
Re:Why can't I write code inside my browser? by naavis on Friday January 15, 2021 @08:43AM (#25790830)
> Yeah like there's 20 years of programming language research that studies exactly what this person is talking about.

More like 50 years. :)

[ Parent | on HN ]
Re:Why can't I write code inside my browser? by monetus on Friday January 15, 2021 @09:27AM (#25791272)
Relevant alan kay video from 1968 https://youtu.be/QQhVQ1UG6aM
[ Parent | on HN ]
Re:Why can't I write code inside my browser? by Ygg2 on Friday January 15, 2021 @11:02AM (#25792342)
That's impressive demo. But graphical representation literally have an extra dimension of problems. Namely navigation and serialization.
[ Parent | on HN ]
Re:Why can't I write code inside my browser? by alickz on Friday January 15, 2021 @10:36AM (#25792076)
That is extremely impressive.

I'm not sure I want to code like that, but damn is it impressive.

[ Parent | on HN ]
Re:Why can't I write code inside my browser? by phkahler on Friday January 15, 2021 @12:33PM (#25793488)
Everything looks better on a vector display. :-)
[ Parent | on HN ]
Re:Why can't I write code inside my browser? by azinman2 on Friday January 15, 2021 @12:46PM (#25793655)
Nothing in the article said “why hasn’t this been researched by the CS community?” The author was complaining about the state of things, and I don’t disagree. Programming is too hard. Error messages are always funky and assume expertise. And perhaps the node folks should better understand that beginners are often a target of their product and should find ways to make it more accessible to them.

Blueprints and Scratch are widely used and are important tools. Your comment sounds very dismissive, and if you meant to be, then I think you’re unaware of their impact and reach.

That said I don’t fully buy the author’s exact argument:

- node.js local install IS for a traditional programming environment on the CLI - you don’t need node built in when you have the browser - plenty of web IDEs exist that do as the author wishes… run node code in the browser while also editing it.

[ Parent | on HN ]