amithgeorge

Maybe I missed something. How do you account for the VM downtime? The VM containing the service writing to the sqlite db, it can go down without warning. How do you mitigate that?

Powershell currently only runs on Windows. One can't use powershell remoting from a Mac OS or *nix machine. Until someone adds non-windows support for Powershell, they need to have a built-in ssh server that opens powershell as the shell. Btw, even if that does happen, it's still difficult to use PS. Any errors that occur in the remote environment get displayed as XML blobs on the client :(

The Community edition is basically the Professional edition with licensing restrictions. Meaning extensions are fully supported. From the [official page](https://www.visualstudio.com/en-us/products/visual-studio-co...)

Q: Who can use Visual Studio Community?

A: Here’s how individual developers can use Visual Studio Community: Any individual developer can use Visual Studio Community to create their own free or paid apps. Here’s how Visual Studio Community can be used in organizations: An unlimited number of users within an organization can use Visual Studio Community for the following scenarios: in a classroom learning environment, for academic research, or for contributing to open source projects. For all other usage scenarios: In non-enterprise organizations, up to 5 users can use Visual Studio Community. In enterprise organizations (meaning those with >250 PCs or > $1 Million US Dollars in annual revenue), no use is permitted beyond the open source, academic research, and classroom learning environment scenarios described above.

From another [article](http://blogs.msdn.com/b/dorischen/archive/2014/11/12/q-amp-a...)

Q: What are the specific features of the Visual Studio Community 2013?

A: Visual Studio Community 2013 shares the same features as Visual Studio Professional 2013 today and licensing terms determine who can use this product. Based on the target audience for this product, SharePoint, Office, LightSwitch and Cloud Business Applications are not included in the installation.

Edit: formatting, can't figure out how to quote the text.

It might have been a marketing mistake. F# is fully supported. http://blogs.msdn.com/b/fsharpteam/archive/2014/11/12/announ...

I am still learning FP and originally I was only looking at server side languages as I felt Javascript already lets me write code in an FP manner. It was after I read SwannOdette's blogs posts on ClojureScript and CSP that I started getting really excited about it. Couple that with Om and Flux, I think I would love writing apps that way. Meaning I was already sold on the potential of ClojureScript/CSP before even watching this presentation.

My dissatisfaction wasn't with ClojureScript but with the presentation. Given that I saw the presentation out of context (I don't know who the audience at the goto; conference was supposed to be - experienced FP developers looking to move to web or existing js web developers looking for something better). Purely from the presentation, I (who belongs the latter) wasn't really sold on anything. Maybe I wasn't the group being targetted.

Finally, I didn't watch the presentation because it was presented by David (I didn't who he was), I watched it for the title. It wasn't till midway through the presentation I realized SwannOdette is actually David. And that surprised me a lot cuz his blog posts are really good, and as I said really sold me on considering ClojureScript. I didn't intend to pick on David, maybe he just had a sub-par day. Especially after knowing David=SwannOdette :)

I happened upon the video through a different source yesterday. Saw it. Didn't really get the title. Sure he quickly ran through the What-Why-How-Perf-Examples of ClojureScript. Had I not already been interested in Clojure/ClojureScript, I would have walked away from the talk thinking whats the big deal? Other languages also compile to JS and vanilla JS isn't all that bad once you get to know it. So yeah, just by watching the video, I didn't understand what the title meant by 'Lisp's Revenge' or even 'Hoare's Revenge'.

EDIT: Before viewing the presentation I wasn't aware who the presenter, David Nolen, was. I was aware of the online persona "SwannOdette" and his blog posts [1] were a major reason for me seriously considering ClojureScript. During the presentation I realized that "SwannOdette" and "David Nolen" are one and the same. His blog posts [2][3][4] are a lot more convincing than this video.

Some day I will write in vanilla Javascript the corresponding code for the examples in those posts. That will truly help me appreciate the advantages Cljs brings to the table. Incase someone else does that, please do reply here.

[1] http://swannodette.github.io/2013/11/07/clojurescript-101/

[2] http://swannodette.github.io/2013/07/12/communicating-sequen...

[3] http://swannodette.github.io/2013/07/31/extracting-processes...

[4] http://swannodette.github.io/2013/08/31/asynchronous-error-h...

Isn't because after the increment operation, x has the value 4. Thus even if y has the value 3 and equals 3, it doesn't equal x.

As a beginner with knowledge of only F# and Clojure, I feel a lot of his issues are solved with having immutable values.

It's theoretically possible that the 'f()' or 'x' might change between the lazy evaluation of step one and the lazy evaluation of step three million. Trying to prevent that is what we programmers call a 'hard' problem.

and the examples he gives in Myth 3 & Myth 4 where he reassigns `x` to mean something else. Both of these can be avoided had x been immutable.

I agree with the conclusion in Myth 2. I didn't understand the latter half of Myth 3, so can't comment on that.

Am I missing something wrt my assumption of immutable values solving most of the issues?

Just created a twitter handle. @locationmmorpg

@locationmmorpg on twitter

Just created a twitter handle so we can keep in touch and share updates with everyone who's interested.

http://twitter.com/locationmmorpg

We'll come up with a better name real soon.

Thanks for the link! Edited the title of our post. Here's what we think will set us apart: 1) We plan to build this on top of LBS APIs so you can get into the game with minimal effort and check-ins via your favorite service earn you points. 2) This will primarily be browser playable - we don't want to be yet another mobile app jostling for your attention when you're out there in the real world.