zura

I have an impression that TypeScript (and docs) are somehow separated in its own. E.g. for Windows Store app development there are docs for C#, VB and JS. Also WinJS. So as a someone learning Node.js, it would be great to start directly with TypeScript, be it common patterns, OO, static typing or just plain syntax. Same goes for e.g. Windows app development.

I wish more docs/books/tutorials were available for Node.js with TypeScript.

As someone who got interested in modern Object Pascal recently, any recommendations for influential/canonical books? (Like SICP, Bjarne's TC++PL, etc..)

Hah, nice to hear that famous book (which I've never read so far) coincides with my understanding and behavior. The only motivation for me is that I value people and their feelings much more than any other thing. To be honest, it is not planned or contrived... It is just a natural feedback.

Anyone using this professionally?

Huh, many years ago some Ad company asked me to write a "virus" that when the user opens some particular website, the desktop wallpaper should change after the user restarts the computer... Of course I refused, but I did implement it just for fun - some win32 app launching on system startup. The app itself was transported through ajax, and executed through Shell.Application object, all done in js. This worked in IE, including IE6. Needless to say, that code never left my PC.

Dart is nice. I wish Dart and Golang teams had more intersection...

Interesting, would it be possible to create a Google Play Store merchant account with this? Estonia is in the list of supported countries for merchants.

Did you use any cross-platform frameworks for developing this?

I wish Qt Widgets (C++, not QML) was more mobile friendly... Xamarin will be good when it finally becomes free (acquired by MS?), or at least gains more indie-friendly license.

API-wise, MoSync really stands out. Unfortunately, it is dead now. Same goes for Adobe Flex/AIR.

It would be great if you put more details on actual artwork - how did you make it, what tools did you use, etc...

Exactly. And optimized Haskell doesn't quite look to "that beautiful FP language" anymore, but becomes more imperative.

Oh, I see... I was talking about: Unity is free, Unreal is free, now Source engine from Valve.. So we're waiting for Xamarin's step in similar direction :)

Yes, I think Xamarin is asking too much with regard to indie devs. They could come up with better licensing, e.g. pay after you earn $X...

Technically, why not... but that would be overkill. I'd rather make a regular app with Adobe Flex/Air.

Xamarin, we're looking at you... :)

Can anyone recommend a service with flat-fee only option?

Another interesting question: Who decides in the Enterprise that the given price makes sense? And how it is done...

You mentioned six-figures - it can be low, mid or high six.. So does anybody thinks about this there? :)

>... may be bored and want to leave.

To follow your line, you could reject with the same success persons who have mentioned "Haskell" or "Compilers" (or "Game dev") in their CV, regardless of their age...

(Assuming you're interviewing for "yet another CRUD job")

Unless you're switching from e.g. Java to e.g. Prolog or Erlang (or Haskell...), is it really useful for learning a new language? I mean, when learning a new language, the basic syntax is the easiest part anyway, but the ecosystem/batteries/best_practices is where the main bottleneck is. And I have an impression that Project Euler problems will help you only with the very basics of the language.

As Georgian, I confirm that it is safe here :) except crazy drivers on the road...

Maybe we could even organize some mini HN meetup, here in Tbilisi...

I don't know, I guess it requires a different mindset/discipline. I can't imagine myself happy doing agile coaching. Here in Georgia 99.999% of projects are CRUD, that's one of the reason I work remotely for more than 8 years now. Mostly, C++ related work.

Indeed. Also Groovy++ (aka Groovy with static typing) is worth mentioning.

One more difference: top-down parsing is European and bottom-up - American :)

We also shouldn't forget the genocide of Circassians by Russian empire.

http://www.circassian-genocide.info/

http://en.wikipedia.org/wiki/Ethnic_cleansing_of_Circassians...

Just one thing to point out - there are lots of remote jobs in web and mobile app dev space already. But C++, systems, non-web engineering jobs are rare in REMOTE space.

გილოცავთ შობას! from Georgia

> And plai-typed is anything _but_ an "afterthought", right?

No, no, plai-typed is great. I meant that PLAI book initially used a dynamically typed language (and I guess it is preserved in the printed edition), but you switched to plai-typed afterwards, and I believe you'll switch to full static typed Pyret for this book as well, when it becomes ready :)

("shameless plug": Actually, it was me who notified you about the plai-typed effort and you further developed it, during your online PLAI class at Brown ;))

Agree about a typed discipline, but I meant specifically static typing for the implementation (host) language.

As for preferences, yes, actually Noel has a point - learning debugging type errors in a dynamic languages is a skill useful in a "real world" (unfortunately :))

Shriram, thank you for the PLAI and I'm looking forward to take a look on PAPL as well. But one thing I don't like - types (static typing) for the implementation language is an afterthought in your books. This happened to PLAI, and later it switched to "plai-typed" language (which was a good move). Now we have PAPL, but again using a dynamic language. Although, as I can see, static typing is a planned feature for Pyret. So I suppose PAPL will switch to static typing in the future, but I think it would be better (for readers/learners, novice programmers) to start with (static) types in the first place.

EDIT: just skimmed through the text, you seem to be using "type-like annotations" mentioned in Pyret docs.

Another thing to note - Pyret is much more readable/enjoyable (and I guess writable :)) than the previous lisp languages you've used. Thanks!

Thanks for the good points! Bolt and LMDB seem approachable, and I'm especially interested how ACID compliance is implemented and how to check/prove the correctness of it...