Programming paradigms that change how you think about coding
brikis98.blogspot.com
Programming paradigms that change how you think about coding
1–10 of 206 posts
Re: Programming paradigms that change how you think about coding
#2In the "concurrent by default" section I would add the hardware description languages like VHDL and Verilog.
Learning Verilog was an eye opening experience for me. It reminded me of the time I switched from unstructured BASIC to C when I was a kid. At first it seems complex and weird then suddenly it clicks and it all starts making sense.
Re: Programming paradigms that change how you think about coding
#3Some notes:
- parallel and concurrent are 2 different things
- the 'symbolic languages' definition seems off. Wikipedia puts it right:
> symbolic programming is computer programming in which the program can manipulate formulas and program components as data
So it's not "using graphs & such to program"
Re: Programming paradigms that change how you think about coding
#4The concurrent by default paradigm looks like it could be really useful for some cases. Does anyone know of any more well-used languages that support it?
Re: Programming paradigms that change how you think about coding
#5The concurrent by default paradigm looks like it could be really useful for some cases. Does anyone know of any more well-used languages that support it?
It's a "well-used language" in academic contexts, but probably not exactly an answer to your question ;) Anyways, in OZ[1] you can just add thread end around code x, and it's concurrent. It will wait for all bindings to be resolved before continuing.
It's a pretty cool language with a lot of paradigms one can easily try out.
[1] http://en.wikipedia.org/wiki/Oz_%28programming_language%29#D...
Re: Programming paradigms that change how you think about coding
#6The concurrent by default paradigm looks like it could be really useful for some cases. Does anyone know of any more well-used languages that support it?
As I mentioned in my other comment Verilog and VHDL are "concurrent by default" since that's how hardware works anyway.
If you want to experiment with them you don't need an FPGA, you can just start with a simulator such as Icarus Verilog[1] and a waveform viewer like gtkwave[2] and get a feel of the language. There are a bunch of tutorials on the net.
[1] http://iverilog.icarus.com/ [2] http://gtkwave.sourceforge.net/
Re: Programming paradigms that change how you think about coding
#7Since 'functional' is not mentioned, I will assume that it is mainstream now!
Re: Programming paradigms that change how you think about coding
#8The concurrent by default paradigm looks like it could be really useful for some cases. Does anyone know of any more well-used languages that support it?
As I mentioned in my other comment Verilog and VHDL are "concurrent by default" since that's how hardware works anyway. If you want to experiment with them you don't need an FPGA, you can just start with a simulator such as Icarus Verilog[1] and a waveform viewer like gtkwave[2] and get a feel of the language. There are a bunch of tutorials on the net. [1] http://iverilog.icarus.com/ [2] http://gtkwave.sourceforge.ne…
Verilog is Turing complete and can do standard IO, so you probably don't even need a simulator/wave viewer.
Re: Programming paradigms that change how you think about coding
#910 Ways Buzzfeed-style Headlines Will Forever Be Annoying
Re: Programming paradigms that change how you think about coding
#10This is a substantial piece of writing with information many here would find interesting; putting it behind a buzzfeed list style headline does it a disservice. One step short of calling it "Six weird programming paradigms that will blow your mind".