568 karma · joined April 27, 2017
Note, I’m not in any way an expert on the legality of it, but this seems like a silly argument to make. If anything, being more up-front with the model may open alternative methods of monetization (subscription-based, etc).
You can classify anything as a 'waste of talent' when looking through this lens. Are you a software engineer? If so, then doing literally anything apart from developing software is a 'waste of talent'. Cleaning dishes? Gardening? Exercising?
The time period in which these movies were made is a lot of what makes them so special. That's not to say that what we'll have next won't be special, but 1974 (and 2008) was a different time.
https://pgloader.readthedocs.io/en/latest/
Great tool, I can't recommend it enough.
I'm looking to switch, but the ties to Kong make me nervous investing in the platform. Presumably because they might eventually make it always for-pay and/or focus on more enterprise-y features that I'm not interested in.
I would love to hear what others think.
For myself, the 'practicality' of GraphQL would be more on complexity of the implementation, training of engineers, potential re-implementation of client logic, ease and depth of debugging, performance, etc. It seems these days that the size of the response is not typically a limiting factor in most applications I've interfaced with (though maybe I've never been exposed to that world before).
Can anyone speak to how a migration from REST to a GraphQL went? My biggest concern is around the complexity of the thing. It just seems so much more complex than REST, but maybe I haven't spent enough time with it.
Toddlers, on the other hand, are little balls of pure energy that get into anything and everything they can touch.
'Frustrating' doesn't do enough justice, based on your story. I'm terribly sorry for your loss.
Your option is better, but XML is very (maybe too) flexible and is bound to be made a mess of.
Your first example is an Ansible convenience feature, it's not extending or changing the YAML syntax in any way. You can simply specify `cmd` values as lists or strings, since working with one or the other may be easier depending on the use case.
The templating is unfortunate in some areas, especially where the jinja2 syntax conflicts with what YAML expects (for example starting an object with '{'). That's due to a combination of templating engine choice and YAML, though, and not some custom implementation of YAML. Unless I'm misunderstanding?
I do think going with YAML was a trade-off for Ansible, but it's hard to see Ansible getting to where it is today if it had gone with a custom DSL (or JSON, thank god). I'd take Ansible's YAML over Chef's Ruby or CloudFormation's JSON any day.
One thing I think Peterson could do better (though I imagine he wouldn't do this purely on principle, if he was even capable) is adapting his speech and rhetoric to meet his target audience. He was answering her questions in a calm and well-meaning manner, but just the tone and vocabulary of his explanations was going completely over her head, making her draw the wrong conclusions from what he was saying. That is, assuming that she wasn't trying to be combative on purpose.
> Who's the pretty girl with Cringely? Learn more about Anina and 360fashion
Both provided links are dead, but I was able to find a Wikipedia page:
https://en.wikipedia.org/wiki/Anina_(model)
Looks like she is (or was previously) a model.
Do developers need to be on-call to handle purely ops-related activities (low disk space, high system load, etc)? Absolutely not. Should developers be responsible for their "production-ready" code when it breaks? Definitely.
A billion still seems like a lot, though.
The only thing that at-rest encryption would prevent is someone walking into a datacenter (or wherever the drives are physically stored) and nabbing one. An attacker is much more likely to gain access to a live system, where the data would be readily accessible.