daveroberts's comments

On: Microsoft GW-Basic Interpreter Source Code

[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."

[krylon → daveroberts]

Ah, yes, I should have read the README. ;-)

On: You cannot play Diablo 2 resurrected after 30 days...

[daveroberts]

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.

On: Show HN: With a 9-5 job and 2 kids I have finally ...

[daveroberts]

Well done! Not an easy task

On: Don’t we all just want to use SQL on the front end...

[daveroberts]

> 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/

On: On Repl-Driven Programming

[daveroberts]

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

On: Apple introduces macOS Mojave

[daveroberts]

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

On: Ruby 2.6.0 with JIT now 6x faster than Ruby 2.0.0

[daveroberts]

Are there any good real world benchmarks for Ruby?

On: Sneak Peek: Beyond React 16 [video]

[daveroberts]

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.

On: Amazon announces candidate cities for HQ2

[daveroberts]

> 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.

On: Twirp: A new RPC framework for Go

[daveroberts]

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

But you change the application to require API clients to send the user_id instead of the username.

    POST /api/user/:user_id/update_email

Wouldn't you still need to mandate that all clients are updated regardless of whether you use this tool as an abstraction layer to your API?

[warent → daveroberts]

Recommend reading on what an RPC is: https://www.geeksforgeeks.org/operating-system-remote-proced...

And protobufs: https://developers.google.com/protocol-buffers/docs/proto3

Example, one benefit is that you're defining your API by using language neutral protobufs which then generate code consistently (including types!) into many languages. Your entire communication procedure can be easily and succinctly described in a single small, human readable file.