Re: Pre-Build Season Code Goals

  • From: Cyliss Sehguh <cyliss13@xxxxxxxxx>
  • To: lcec.code@xxxxxxxxxxxxx
  • Date: Tue, 15 Dec 2009 21:58:18 -0800

we'll talk in step tomorrow. yes i agree its good to look at old code... but
i think it would be more efficient to look at what FIRST provides
rather than what Ben has written... considering what it would take to get
the code.

My vote is C++ because there has already been a year of testing on the new
control system with C++ and if I've learned anything about FIRST and code,
is that they don't test their stuff too throughly before they release it to
the teams. There were a lot of problems last year, both code and
mechanically based, which will not be repeated this year because it has not
been run through.

Java will most probably work perfectly or as well as C++, no doubt. I
personally would love it if the code were Java so that I could help a bit.
But from my two years with FIRST, it doesn't wise for a team as young as
ours with all new coders to trying something with little to no community
resources. there's 16 years for C++ and one year on the new control system,
and those resources will be very helpful.

but i'm just one vote. and i dont really know  much code. meh.

On Tue, Dec 15, 2009 at 8:06 PM, Justin Collier <justinjncr@xxxxxxxxx>wrote:

> My vote is Java as well.
>
>
> On Tue, Dec 15, 2009 at 8:03 PM, Luke Cycon <lcycon.lcec@xxxxxxxxx> wrote:
>
>> On Tue, 2009-12-15 at 18:41 -0800, Cyliss Sehguh wrote:
>> > you guys  try whatever you like AFTER you start writing some code from
>> > scratch.
>>
>> Don't get all bent outa shape ;) haha
>>
>> Its really standard practice to look at old code just to get a feel for
>> the API.  Blindly programming with a new API falls very short of a good
>> idea.  Last thing we want is an inadvertent wire fail caused solely by
>> lack of experience with the APIs haha
>>
>> At any rate, I think it would be beneficial to have Ben's old code (Not
>> so much if we decide to go with Java), just to see contextual examples
>> of function calls.
>>
>> Last thing: We are approaching the point where we need a final decision
>> of what language we will be using.  I cast my vote as Java
>>
>> > I talked to Zim and I think thursday after school will work fine. Will
>> > verify tomorrow in STEP.
>>
>> Yay... My day with the most homework... Ah well. Just let me know if its
>> a go.
>>
>> --
>> Luke Cycon <lcycon.lcec@xxxxxxxxx>
>>
>> Anything not nailed down is mine. Anything I can pry loose is not nailed
>> down.
>> At any time, at any place, our snipers can drop you. Have a nice day.
>>
>>
>>
>

Other related posts: