I know javascript well enough. Now try to write device driver code with it, or something else equally low level. Or even something mission critical such as engine timing monitoring/adjustment, airbag deployment, or missile/drone guidance.
I know other languages well enough too. C/C++, ASM C# VB.NET, and a few obscure scripting languages hardly worth mentioning. But the point is, you'll never get away with using javscript for everything because somethings for some situations *require* specific languages. Missile guidance for example you're most likely going to have to use ADA. Device drivers, either C, or ASM, and if you're building a Microsoft web server service / backend you're very likely to use C# / VB.NET with ASP.NET. It's not that things cant be done differently, it is that you're most likely never going to get away with it in the field professionally. Not only that somethings are either close to impossible, or do not even come close to making sense. On Sat, Sep 6, 2014 at 1:29 PM, John Syn <john3...@gmail.com> wrote: > > From: William Hermans <yyrk...@gmail.com> > Reply-To: "beagleboard@googlegroups.com" <beagleboard@googlegroups.com> > Date: Friday, September 5, 2014 at 6:01 PM > To: "beagleboard@googlegroups.com" <beagleboard@googlegroups.com> > Subject: Re: [beagleboard] Re: trying to learn enough to get started > > You're preaching to the choir John. Except that I do not feel that > JavaScript is the closest thing to a perfect anything. Again, there is no > one perfect "tool" to rule them all. > > Take a look at Douglas Crockford presentations on Javascript and he will > explain why Javascript is the closest we have to a functional more perfect > language. He explains why JAVA is a horrible language. BTW, I’m a C > programmer, so it took me a while to adjust to the way Javascript works. > Remember, that the original Javascript was written in a few days by Brendan > Erich and that work has plenty of problems and this is why Javascript gets > a bad rap. However, after the work done by ECMAscript language standard, > the language improved dramatically. You are right, the Google V8 engine > made this language fast. > > https://www.youtube.com/results?search_query=douglas+crockford+2014 > > Regards, > John > > > > However, I do feel that because of google's V8 engine, and Nodejs, that > javascript finally is something worth using for high level Rapid > Application Development (RAD). Now, it is more like a Java, or dotNET done > right. Performance wise, it is also very fast, and performs very close to > native C. > > In contrast, python and php are much slower. More so for Python which is > one of the slowest languages around. So, I will agree that it is not always > about what is faster, but n the case of an embedded device. Fast > performance means better efficiency. Which could mean the difference > between a battery lasting 2 hours, versus overnight. > > *Shrug* Anyhow, I will not have anyone telling me what I can and cannot > use, so I will try to return the favor. > > > On Fri, Sep 5, 2014 at 3:18 PM, John Syn <john3...@gmail.com> wrote: > >> >> From: William Hermans <yyrk...@gmail.com> >> Reply-To: "beagleboard@googlegroups.com" <beagleboard@googlegroups.com> >> Date: Friday, September 5, 2014 at 2:43 PM >> To: "beagleboard@googlegroups.com" <beagleboard@googlegroups.com> >> Subject: Re: [beagleboard] Re: trying to learn enough to get started >> >> *Ours is all in python and php with darkhttpd as the webserver. I dispise >>> nodejs, it reminds me of the cluster that ruby gems are. * >> >> And this is why there is no easy guide. At least from a programing >> aspect. No two people are going to agree on how it should be done, and >> what is used to get it done. >> >> Nodejs does however get a bad rap I think. The stigma of javascript comes >> with it. Which is its self often misunderstood. Nothing is perfect however >> . . . >> >> I agree with you William; however, php and darkhttpd don't scale very >> well, because it lacks asynchronous I/O capability. Also, the current >> spec’d Javascript is pretty close to the more perfect language compared to >> C, Java or Python. It also has the biggest user base of any language, by >> far and it is the only true language that works in all browsers and on the >> server. BTW, there are no bad parts, just bad programmers. >> >> Regards, >> John >> >> >> >> >> >> On Fri, Sep 5, 2014 at 1:06 PM, Don deJuan <donjuans...@gmail.com> wrote: >> >>> On 09/05/2014 10:04 AM, William Hermans wrote: >>> >>> *Why compile anything? For the proposed project (Greenhouse control)* >>>> * speed is not any sort of priority so use an interpreted language, the* >>>> * obvious choice on BBB is Python.* >>>> >>> >>> Well, the obvious choice to me is Nodejs, and am betting since this >>> person has 35 years experience in related fields, that C is a possibility >>> as well. >>> >>> I've only been programming for 20 or so years . . . so what the hell do >>> i know ? >>> >>> >>> On Fri, Sep 5, 2014 at 1:51 AM, <c...@isbd.net> wrote: >>> >>>> William Hermans <yyrk...@gmail.com> wrote: >>>> > [-- text/plain, encoding 7bit, charset: UTF-8, 51 lines --] >>>> > >>>> > You need to find and read sources about embedded Linux. Then, since >>>> your >>>> > project could be done using any number of languages, you need to >>>> figure >>>> > that out too. Past that, you're going to have to figure out what >>>> hardware >>>> > you're going to use. Which will indicate if you're using SPI. I2C, >>>> UART, >>>> > onboard ADC's or PWM's etc. >>>> > >>>> > In your shoes, I'd start off with and continue using these >>>> instructions: >>>> > https://eewiki.net/display/linuxonarm/BeagleBone+Black. You can use >>>> either >>>> > Debian or Ubuntu with these build instructions. I've been using these >>>> > instructions since last year ( around 14 or slightly more months ), >>>> and >>>> > they're very consistent. >>>> > >>>> > You could also start off with a premade Debian console image if you >>>> like. >>>> > >>>> > You can definitely compile natively on the board, but if you plan on >>>> cross >>>> > compiling, you're going to need to understand the gcc toolchain >>>> thoroughly. >>>> > For setup and use. >>>> > >>>> Why compile anything? For the proposed project (Greenhouse control) >>>> speed is not any sort of priority so use an interpreted language, the >>>> obvious choice on BBB is Python. >>>> >>>> ... and I am also a long in the tooth software engineer with maybe 30 >>>> years of experience writing C, but I'd still recommend going with >>>> Python on this sort of project. >>>> >>>> -- >>>> Chris Green >>>> · >>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "BeagleBoard" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to beagleboard+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> I actually have done a similar control for aeroponics room setups. We >>> are releasing it public in roughly a month once the boards come back and we >>> finish testing on the new hardware run. >>> >>> Very easily can be adapted to greenhouse control as I am sure you're >>> after the same things, water, temp, humidity, vpd, ph, ppm, disolved >>> oxygen, dew point, flood detection, co2, lumens/lux, uvb, darkness light >>> leak detection and all the rest of the goodness for optimal environmental >>> control. Even the cooling opener could be adjusted/adapted to fit to >>> automate opening roof panels. >>> >>> Ours is all in python and php with darkhttpd as the webserver. I dispise >>> nodejs, it reminds me of the cluster that ruby gems are. >>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
