0 Members and 1 Guest are viewing this topic.
IMO yes, but the benefit is tiny compared to the benefit you get from the current team's C++ experience, the advantages are not worth it
Let me put it this way, I think c++ is one of the *worst* languages ever invented for *anything* and still have no problem using it for this project. It doesn't matter that much.QuoteC++ is a horrible language. It's made more horrible by the fact that a lot of substandard programmers use it, to the point where it's much much easier to generate total and utter crap with it. Quite frankly, even if the choice of C were to do *nothing* but keep the C++ programmers out, that in itself would be a huge reason to use C....C++ leads to really really bad design choices. You invariably start using the "nice" library features of the language like STL and Boost and other total and utter crap, that may "help" you program, but causes: - infinite amounts of pain when they don't work (and anybody who tells me that STL and especially Boost are stable and portable is just so full of BS that it's not even funny) - inefficient abstracted programming models where two years down the road you notice that some abstraction wasn't very efficient, but now all your code depends on all the nice object models around it, and you cannot fix it without rewriting your app.Linus Torvalds
C++ is a horrible language. It's made more horrible by the fact that a lot of substandard programmers use it, to the point where it's much much easier to generate total and utter crap with it. Quite frankly, even if the choice of C were to do *nothing* but keep the C++ programmers out, that in itself would be a huge reason to use C....C++ leads to really really bad design choices. You invariably start using the "nice" library features of the language like STL and Boost and other total and utter crap, that may "help" you program, but causes: - infinite amounts of pain when they don't work (and anybody who tells me that STL and especially Boost are stable and portable is just so full of BS that it's not even funny) - inefficient abstracted programming models where two years down the road you notice that some abstraction wasn't very efficient, but now all your code depends on all the nice object models around it, and you cannot fix it without rewriting your app.
c++ should be fine for it's core. Wrappers will be created eventually to support higher level languages and ease of use. I will give a go at creating .NET wrappers once we got a steady 'base DAC' but I do have to dive into the existing code a little bit more.
Quote from: jae208 on March 24, 2014, 06:16:28 pmAnyone on here know if the Wolfram Language can be used to create future DACS? Would it be faster than C++?https://www.wolfram.com/language/https://www.youtube.com/watch?v=_P9HqHVPeik&list=UUJekgf6k62CQHdENWf2NgAQMathematica is for symbolic reasoning. I don't expect this Wolfram language far from that.
Anyone on here know if the Wolfram Language can be used to create future DACS? Would it be faster than C++?https://www.wolfram.com/language/https://www.youtube.com/watch?v=_P9HqHVPeik&list=UUJekgf6k62CQHdENWf2NgAQ
You're still thinking of it like AI, but a DAC is just an agreement with a ledger. We are optimizing for a totally different set of constraints. Sent from my SCH-I535 using Tapatalk