01-18-2015, 07:30 PM
Sure ... you can catch a fly with chop-sticks also.
But I'd just use a fly-swatter myself.
Nothing wrong with a language like C++ for hardening parts of a well defined system. But as far as designing a system that is fundamentally wanting to be handled by a lists,sets, tuple based language without the shackles of being strongly typed ... man ... just no comparison at all.
Wings defers to native code (think C/C++) in a number of places where it should ... like compositing things for screen and of course interfacing to existing libraries. Use of jpeg libs, etc.
Use a tool where it excels. Use Erlang and Functional programming to design a great mesh processor ... oh ... that happened 30 years ago with LISP and then 15 years ago with Erlang. OK !
But I'd just use a fly-swatter myself.
Nothing wrong with a language like C++ for hardening parts of a well defined system. But as far as designing a system that is fundamentally wanting to be handled by a lists,sets, tuple based language without the shackles of being strongly typed ... man ... just no comparison at all.
Wings defers to native code (think C/C++) in a number of places where it should ... like compositing things for screen and of course interfacing to existing libraries. Use of jpeg libs, etc.
Use a tool where it excels. Use Erlang and Functional programming to design a great mesh processor ... oh ... that happened 30 years ago with LISP and then 15 years ago with Erlang. OK !