I really don't understand why this kind of thing can't be done over a video conference, and then printed, stamped, scanned, emailed, printed locally. But, I got a nice little trip to my hometown out of it, so whatever.
649 karma · joined February 18, 2016
I really don't understand why this kind of thing can't be done over a video conference, and then printed, stamped, scanned, emailed, printed locally. But, I got a nice little trip to my hometown out of it, so whatever.
It offers more than one strategy for managing state; there is simple two way binding between a JS object and the DOM, there is the Elm-inspired vuex, and also it can integrate with Redux. http://vuejs.org/v2/guide/state-management.html
The gory details and a few attempts at higher quality scaling algorithm implementations are on SO: http://stackoverflow.com/questions/18922880/html5-canvas-res.... TL;DR: sending the image to the server and having GM scale it is faster and more reliable than your own scaling algorithm in single-threaded browser JS.
For anyone else just starting out, I suggest using readline with the REPL: `rlwrap q`. It gives you history, search, familiar line editing commands, etc.
Not sure if this works well for cities that are large enough to cause world news themselves. And, if you did this for San Francisco, I imagine that you would simply be directed back to HN ;)
I have an idea for a fairly simple possibly: The user just declares that certain features of the scene are interesting and relevant, maybe by "taking a sample", so that the algorithm can boost the weight of inputs that have a relationship to those features. But, I suspect that you have something much more interesting in mind...
Heroku gets expensive quickly at scale, but the engineering required to make "the future" work on AWS was unmeasurable (because it never really succeeded for us).
I don't even know what to blame for the whole episode. Docker's incomplete architecture (2015)? AWS's inability to abstract and manage complexity into something that just works as described on their product pages? The consultants? Myself, for putting faith in that triad of unfamiliar but crucial people, services and products? Whatever, it's no longer a current problem for me.
Recently, I took a short trip that included a few days in Paris, and I made a point of defaulting to French when starting conversations. However, for the most part, as soon as a French person realizes that French is not my first language, they switch the conversation to English, even if their English is worse than my French (according to my perception).
I wonder if this is unique to the culture of France, or at least Paris, that they do not like to hear their language from a foreigner? Maybe the language is part of a group identity, used to identify locals who can be trusted to follow local customs? It was a little saddening. In Africa and the Middle East however, when I am in predominantly French speaking communities, the locals seem quite happy to have conversations in French, even though our accents differ greatly.
My weekend is packed already, but I'll be back to check this out. I'm just starting to take a second look at GraphQL and co. Last time I looked at it, the conclusion was "extremely interesting, but too alpha for work."
Did you notice that Facebook's ad / business manager uses a mix of GraphQL, REST, and RPC over HTTP POST? Watching the traffic in major production applications is fascinating.