daveroberts

I suspect they'll get zero PRs:

"The files in this repo are for historical reference only and will remain read-only and unmodified in their original state.

Please do not send Pull Requests suggesting any modifications to the source files."

It seems almost self evident the game would not have been greenlit without a form of DRM. Most of the comments here are lamenting the game having DRM, but they're comparing having the game with DRM vs having the game without DRM, not having the game with DRM vs not having the game at all.

Well done! Not an easy task

we should have an SQL database in the frontend

Although not SQL, this is essentially the approach Meteor takes where you have your same DB on the front and back end https://www.meteor.com/

Not Ruby's default REPL, but Pry Stack Explorer provides this functionality to Ruby

Microsoft had an advertising campaign for Windows Vista called the Mojave Experiment: https://en.wikipedia.org/wiki/Mojave_Experiment

Are there any good real world benchmarks for Ruby?

This is very cool. I'm heavily invested in Vue.js, but seeing these kinds of features of the horizon with React makes me a bit jealous.

The APIs do see unintuitive, but as Dan said, they are not finalized yet. I remember trying to implement a drag and drop component in React and having a bit of trouble with complicated APIs. Hopefully this keeps getting cleaner.

William Whyte‘s rule: Virtually all corporate relocations involve a move to a location which is closer to the CEO’s home than the old location.

Of course, it's hard to pick any location farther than Seattle from DC.

I'm trying to understand the problem this solves. Let's say you have an HTTP API which allows users to update their email address:

    POST /api/user/:username/update_email

    POST /api/user/:user_id/update_email

How is TOML not properly nestable?

How did you make / optimize the animated gifs on the front screen?

How did you handle user signup / authentication to your service? Did it piggy-back on VK's authentication?

There are some other issues for users trying to follow along. I hit my next snag from moment.js not being imported, and not having the filters domain, amFromUnix and amTimeAgo not being found. I see you addressed these points later on in your post notes, kind of as an "excercise left for the user". After that point, I just read the article and stopped trying to follow along. Perhaps it wasn't your intent to make a step-by-step type article, but I'm just sharing the experience I had trying to go along one step at a time. I appreciated the article, especially because right now we're starved for Angular 2 content, and there's not a lot out there yet.

Just a minor point, but your first stories.component.html snippet doesn't include {{i}}, so the way it renders in the browser is different than your screenshot

Fails for me pretty early on:

ng set defaults.styleExt scss

Could not start watchman; falling back to NodeWatcher for file system events. Visit http://ember-cli.com/user-guide/#watchman for more info. Cannot read property 'serialize' of undefined TypeError: Cannot read property 'serialize' of undefined

I installed watchman and received the same error

Looks like this has been reported elsewhere: https://github.com/angular/angular-cli/issues/1905

Multiple microservices are supposed to have different data backends, so that they are completely independent. Splitting your data up this way isn't all roses, but ideally the services are isolated so an update to one doesn't affect the others.

One method: My employer has asked me to keep some information confidential, including its employee compensation. I'm sure that you expect your employees to keep a certain level of confidentiality about information as well, including compensation.

What is the "code insight" feature? Is it an intellisense feature of VSCode?

I know very little about the subject, but when multi-core processors were first introduced, I remember that the general wisdom was that server software could benefit, from its highly concurrent nature, but games and graphics would not, because they are generally single threaded. I wonder if the general wisdom at the time was wrong, or if there has been a big shift to take advantage of multiple cores. I'm guessing the later.

The first result from Google for nodejs worker pool leads to this project: https://github.com/jeffmo/node-worker-pool

The project has only 9 stars on GitHub. While it might be a perfectly fine solution that fixes OP's problem, it certainly doesn't inspire confidence as a battle-tested production-ready library. On the other hand, worker pools and Golang go together very naturally.

Thanks. Should any other packages be in core that are not?

How often do you use npm packages which are not part of atmosphere? I remember this not working great. Have things changed?

Go and Rust and included in the Computer Language Benchmark game: http://benchmarksgame.alioth.debian.org/

Nim, and many of the other interesting languages mentioned in this thread are not.

I'm not sure if this is a cause or effect.

For what it's worth, I installed this in my VIM, switching between files took about 4 seconds instead of 1, so I uninstalled it.

Hey, I'm a fan of your recess framework and I wanted to stop by to say I was going to look into this library you published just based on that fact.