SubJeff on 11/3/2013 at 23:30

---

I think the "best method" would be not to have arbitrary names in the first place.

I'm not preaching though; I hash together stuff so it just works!

Phatose on 12/3/2013 at 01:24

---

As zombe pointed out, you can typically use array indexes or the equivalent. .Net has collections, I'm fairly certain java does too.

It's a bit more cumbersome, but it doesn't involve using eval - and that's a huge plus cause eval is tremendously dangerous. Like little Bobby tables, except it might be able to delete your whole hard drive, and not just your database.



Weak typing is one of those things that seems nice at first, but it's got problems that show up pretty quickly. Even if you discard all concerns coding practices, you still end up with the problem that your dev environment is going to be a hell of a lot less useful. The various shades of useful autocomplete - they call it intellisense in VS, don't know if it's got a general name - makes dealing with strongly typed classes a lot easier, simply because it lets the compiler suggest valid properties. Some environments will try to imply typing, but that's really hit or miss.

Then you have other concepts it's missing - method overloading is a big one, and you just can't do it at all in javascript.

Peanuckle on 12/3/2013 at 02:55

---

Man, I typed up this whole thing I thought would be helpful, then I went back and read the opening post, and it was totally irrelevant.

If you decide to teach a second language, I'd recommend Mexican-spanish or Chinese. Our closest neighbor and biggest market, respectively. I learned French in highschool and have met precisely 2 other people who spoke it, and they were really old folks whom I haven't seen since.

Although I heard a while ago that speaking Arabian could get you a good job with certain government agencies, but with the current political activity you might be better off learning Korean.