>Bike with wheels has the same functionality
you ever rode a fricking bike? training wheels change handling entirely, you might as well have a pedal-powered car at that point.
the code generated from those IDEs (at one time) was so horrific and nonsensical that any blocks-style editors damaged reputation still hasn't been smoothed in industry to this day.
tldr garbage in, garbage out
graphical block-based coding isn't as fast as just typing shit, plus you gotta deal with managing where to place your massive 100+ line equivalent blocks. plus plus storing the ocation of blocks takes up extra data than if they were just organized as individual source or scripts
the only reason it's even this popular is due to it's accessibility. it's practicality for real-world codebases is kinda ass.
try reading this shit i made as a kid
> Why isn't blockbased coding more popular? it seems more simple to "Write" code like this.
Correct.
What it's missing is:
(1) template metaprogramming
(2) pervasive use of LABEL: and GOTO: type structures
(3) long-form java imports such as import java.util.factory.factormaker.neighborhood.town.city.cityfactorymakermaker.townfactory.neighborhoodmaker.factorygenerator.instance.singleton
once a common sense language with all of these three features then this will easily be the finest imaginable language, superior to even brainfrick
They are easy for beginners to write but very hard for anyone to read and they are a challenge to change - its much easier to rewrite a few lines of code than to have to pull and replace many parts out of a block stack.
Not exactly programming (very close though) but in DSP space, there are a lot of softwares which is flowchart based editors to chain together signal flow through various operations (filtering, decimation, interpolation, modulation etc)
>Why isn't riding a bike with training wheels more popular?
>it seems more simple to "ride" a bike like this.
Wrong comparison. Bike with wheels has the same functionality. Block coding is gimped
>blocks your path
>Bike with wheels has the same functionality
you ever rode a fricking bike? training wheels change handling entirely, you might as well have a pedal-powered car at that point.
>
It's called functional programming.
is that Scratch?
If it's so great then explain what the pic you posted does
>it seems more simple to "Write" code like this.
>at least 1 magic number inside every block
anon that's why
the code generated from those IDEs (at one time) was so horrific and nonsensical that any blocks-style editors damaged reputation still hasn't been smoothed in industry to this day.
tldr garbage in, garbage out
graphical block-based coding isn't as fast as just typing shit, plus you gotta deal with managing where to place your massive 100+ line equivalent blocks. plus plus storing the ocation of blocks takes up extra data than if they were just organized as individual source or scripts
the only reason it's even this popular is due to it's accessibility. it's practicality for real-world codebases is kinda ass.
try reading this shit i made as a kid
I have a better idea of what ASM is doing at a glance than this shit.
its so popular the wrote linux on it
https://scratch.mit.edu/projects/892602496
>t. can't read
it's a linux running inside an emulator written in scratch
they didn't rewrite linux
Now try doing anything complex
> Why isn't blockbased coding more popular? it seems more simple to "Write" code like this.
Correct.
What it's missing is:
(1) template metaprogramming
(2) pervasive use of LABEL: and GOTO: type structures
(3) long-form java imports such as import java.util.factory.factormaker.neighborhood.town.city.cityfactorymakermaker.townfactory.neighborhoodmaker.factorygenerator.instance.singleton
once a common sense language with all of these three features then this will easily be the finest imaginable language, superior to even brainfrick
Node graphs are an entirely separate kind of crazy.
They are easy for beginners to write but very hard for anyone to read and they are a challenge to change - its much easier to rewrite a few lines of code than to have to pull and replace many parts out of a block stack.
I wouldn't even let a child near this mess. I was writing code at 10 and I'm a fricking moron.
There is absolutely no benefit, none, zero.
Name literally one benefit, you can't.
It's not "more simple", period.
because graphical programming languages tend to make people feel insecure
Not exactly programming (very close though) but in DSP space, there are a lot of softwares which is flowchart based editors to chain together signal flow through various operations (filtering, decimation, interpolation, modulation etc)
I've seen them used in beginner programming classes. Somewhat useful for getting people into the 101 concepts.