> -----Original Message----- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite- > users-bounces at mailinglists.sqlite.org] On Behalf Of david at andl.org > Sent: Monday, June 15, 2015 2:28 AM > To: 'General Discussion of SQLite Database' > Subject: Re: [sqlite] Mozilla wiki 'avoid SQLite' > > I won't abuse the patience of our hosts by prolonging this debate, but > I disagree strongly with this theme. > > I have almost certainly written more C/C++ code than you or most of the > people on this list, and I never choose it first. I am personally at > least 3 times as productive in C# as I am in C (slightly narrower > margin in C++), and computers are far cheaper than brains.
If productivity is important is there any reason why you're not working in F#? I don't know that language myself, but I've seen some impressive demos. -- Bill Drago Staff Engineer L3 Narda-MITEQ 435 Moreland Road Hauppauge, NY 11788 631-272-5947 / William.Drago at L-3COM.com > > This theme is strongly reminiscent of arguments over moving from > assembly language, and it's basically wrong. The best tool is the one > that gets the required job done with maximal speed at minimal cost. > > And just for the record, C# does not compile into byte code. I suggest > you check your facts. > > Regards > David M Bennett FACS > > Andl - A New Database Language - andl.org > > -----Original Message----- > From: sqlite-users-bounces at mailinglists.sqlite.org > [mailto:sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of > Aleksey Tulinov > Sent: Monday, 15 June 2015 10:32 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Mozilla wiki 'avoid SQLite' > > On 15/06/15 01:00, Simon Slavin wrote: > > Simon, > > > Perhaps the next generation of computer languages will be designed by > computer, to let us speak to them in an efficient manner. > > > > I'm sure computer would insist on C, if not, then it's apparently a > software bug. > > On a serious note, i think it's rather question of programming > computers or programming another programs. As you've mentioned, higher > level languages often compiles into byte-code which is then interpreted > by virtual machine. > So you don't speak to machine, you speak to mediator who speak to > machine. > This by definition an overhead, with growing complexity of the program, > overhead will grow accordingly, this is unavoidable. > > I think it's also fair to say that SQL is not for programming machines > (no offense), it's for programming SQLite and other database > implementations. > Even if something is called "virtual machine", VM always behaves > somehow differently from The Machine, thus programmer' > efforts has mediated effect on latter. > > Of course VM could do a good job in a specific domain, but each VM > limits the liberty of expressing yourself to the machine and vice > versa. > > In my opinion best database language would reflect the way in which > database works and best computer programming language would reflect the > way in which computer works, as close as reasonably possible. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users CONFIDENTIALITY, EXPORT CONTROL AND DISCLAIMER NOTE:This e-mail and any attachments are solely for the use of the addressee and may contain information that is privileged or confidential. Any disclosure, use or distribution of the information contained herein is prohibited. In the event this e-mail contains technical data within the definition of the International Traffic in Arms Regulations or Export Administration Regulations, it is subject to the export control laws of the U.S.Government. The recipient should check this e-mail and any attachments for the presence of viruses as L-3 does not accept any liability associated with the transmission of this e-mail. If you have received this communication in error, please notify the sender by reply e-mail and immediately delete this message and any attachments.
