keslag

I used an amber CRT for 17 years. What this is missing is the mottled browning and yellowing from all the cigarette smoke on the beige plastic case. Now what you really need to be retro is a TTY printer. I used to get my work orders through one. No screen, just a seemingly infinite roll of dot matrix paper and a keyboard.

Science has multiple capitalization rules as well. mRNA is not a name, the same as genus and species are seldom capitalized. If you have a mRNA named Bob, then the name is capitalized.

Stack exchange as a source of fact? I very much could be wrong, but the implication that "because 30 people upvoted something, makes it true" is ridiculous.

The official name of Io.js in English is Io.js as it's a name, it is stylized as io.js. In Canada here, we have a company Telus, which stylizes it's name as TELUS. However, when discussing the company in non-marketing environments, such as Wikipedia, it's called Telus. The rules for English trump a creators stylization rules in many situations.

Look, I could be wrong. I just find it very hard to believe that the man who read and understood the content of over 30 programming and web development books, has only come up with this http://www.sagecreekproductions.com as his company's web page. His github shows he started the first couple pages of a node book, but didn't get past the init commit. https://github.com/sidunn. I don't buy it, and I'm going to stop responding because there is more than enough information out there for people to make their own conclusions. But it's disingenuous at best to have this man review development books.

He sells the books after reviewing them. He gets paid.

If you read in there, Si Dunn won't write the review unless he gives it 4 or 5 stars. He then sells the books he reviews back on Amazon. He doesn't do ebook reviews because you can't sell the ebook. So he gets paid about 65-75% of list. Looking at his reviews and twitter feed, it's a few hundred a month, and for a writer who quotes more than he reviews, probably not more than a few hours work.

https://sagecreek.wordpress.com/about/

People can keep downvoting me, but it doesn't make that 5 star review any more legitimate.

No he doesn't. Si Dunn only gives out 4 & 5 star reviews with the vast majority being 5 star. Si Dunn also isn't a programmer, he's a non fiction author and professional book reviewer. He's a shill, his reviews are all the same formulaic BS. He doesn't understand enough about writing code to actually review the book and instead fills space by using author quotes or lists the definitions of what the technology is.

So, because many publishers have fake accounts that lie, I should give this one a pass? Pete, I encourage you to write a book. The world is far worse than you seem to think.

A book released today with a 5 star rating about how much the reviewer needed this book? Horse shit. If it was your mom, I might buy it. My mom would give 5 stars and babble on about how cute I was as a baby. But Si Dunn rates almost everything 5 stars, and everything is life changing to this manning plant.

The only absurd thing about life, is that through the process, something was created that understood the absurdity of it all.

I liked Ansible a lot; during our evaluation I had a single Ansible file provisioning a sample dev setup in around 50 lines. We need to support windows servers primarily, much to my objection, so the 'blessing' of the machine to automate Ansible on windows required a manual step at the time, which wasn't acceptable for our use case. We ended up picking chef, both for it's more agnostic approach to OS's, but also it's much more developer friendly, regardless of it's overly verbose generators, git repository litter, and quirks that still have me scratching my head.

Absolutely, I should have specified 'a single vm' in my response. I didn't understand that when I was first trying to understand boot2docker, and now I'm using imprecise language to help confuse others. Thanks for clarifying.

I'm talking about running windows inside of Vagrant and having these issues on a Mac. The problems I've detailed have long standing issue logs on github, some closed without resolution. I'm not casting aspersions, I'm explaining my use and my experience. This is valid, regardless of whether you have had the same experience. Regardless, the tool sells itself as working on windows, so it is not only fair, but apt. Providing a counter example is a good rebuttal, but saying my experience is invalid reeks of fanboyism.

I think the reasoning is sound, but this isn't an indication of either language being better than the other. Only that it's easier to look under the hood of Nim. I find Nim easier to read, and then as is with ruby, probably more productive for prototypes, but I'd like to see more use cases before I start to move in that direction. It does make me wonder if we'll ever see a Nim to rust transpiler.

The chef provisioner which comes as part of vagrant does indeed install chef on the target VM. To say that vagrant is not doing this is splitting hairs.

Docker just spins up a VM on OS X with boot2docker so you don't get any real benefit here.

Even if you're deploying to mac, you should use a mac vm. If you manage to get a buggy or corrupt package, it's much easier to revert to a snapshot or reprovision a vm than to reprovision your machine.

Vagrant has been a much bigger time sink for me than benefit. The ssh-agent never works while provisioning for nix servers, only during ssh (which I can do using the -- -A regardless). It often gets confused and the machines need to be destroyed and re-created after 1-2 provisioning attempts. Packers (The tool used to create vagrant boxes) lack of support for winrm on windows systems has also been a bone of contention. It requires a number of workarounds (like installing open-ssh) on the windows VM that in no way would be viable on a production windows server. And that divergence allows for the "It works on my machine" bugs which is really the whole point of using Vagrant. I use chef for provisioning, and Vagrant also downloads the chef provisioner every single provision, I suspect it does this with puppet as well, so if you're developing on the go and need to re-provision, you're either out of luck or require an unlimited data plan.

Homebrew Cask also has no oversight for breaking changes, so use this only as a convenience, not a tool to be relied upon. It frequently looses track of applications, and I can't even find where it decides to put some error logs if they're created at all.

Some of these problems could be my lack of experience in operations, but the documentation for these is far from complete. A VM with snapshots and a good backup strategy will serve you better in the short term. This changes if you're attempting to support multiple dev, but if you're a lone guy, then snapshots are far far less buggy.

Things are always that simple. Humans makes things artificially more difficult for wealth, power, and control. If you put a back door in encryption, the bad guys will stop using that encryption. All you manage to do is make the honest citizen less secure. Nothing changes this fact, and therefore nothing justifies backdoors in encryption. It really is that simple.