Not quite, it gets you about 90% there. Even with a grammar to use off the shelf, you still need to write queries to make use of it for highlighting, text object selection, auto indenting, etc. These have so far been particular to the editor.
This is surely just the bias of those willing to make a comment one way or the other. If you are so-so about it, you probably don't make the effort to make a comment.
This stuck out to me too. Terraform absolutely does check the current reality of the state and applies changes to do what the HCL tells is to. They are either using terraform in a really weird way, or this article was written by someone that doesn't actually run terraform themselves.
Am I the only one who was extremely confused by the writing? I think the whole effect was just lost on me, because I went from thinking her brother was the one who died, to thinking he was the driver, to finally getting to the part where she actually says explicitly that he was the other boy in the road.
Wow this guy is fucking delusional. I can't believe he seriously thinks his employees are smiling every day, and that they aren't burnt out because they "believe in the mission"
Wow. So you are saying that because I chose not to use Chrome that all software suffers? I didn't realize that there was only one good choice, or that Firefox was "slow and bloated," or that my choice of which software to use somehow contributes to the quality of code that software engineers outside of Google write.
MRU tabs is essential to my usage flow. Sorry if that hurts your feelings. I frequently have many tabs open, and I need to be able to quickly switch back and forth between two or three tabs. People have been clamoring for MRU tabs since Chrome came out, and Google and the Chromium developers simply ignore them. https://code.google.com/p/chromium/issues/detail?id=161960
Wow, judging from the comments in here, there are a lot of people that are in management positions that are horrible judges of technical ability and value. This question asks so many things that it doesn't really ask anything at all. No matter which field they decide dive into, if they can dive into any at all, it sheds no light whatsoever on their ability to solve problems, or their ability to learn new difficult concepts. Moreover, making assumptions about where their specialties lie because of the topic they chose to answer in is wrong--if they answered well, they could be skilled in many other topics as well, and if they didn't, that doesn't mean they're incompetent--it means they didn't know how to answer what is essentially a trick question.
I may do that in the future, once Rust has stabilized. They've recently changed the concurrency model to use native threads, instead of green threads, so their documentation is not accurate at present. And a comparison between them wouldn't really be meaningful anyway, until Rust has stabilized. That said, I'm sure there are plenty of other articles that compare Go and Rust.
Another example of "Wtf were they thinking when they wrote this?" in the Java stdlib is MessageDigest. To build a digester object, you must pass it a string literal to tell it which algorithm to use, and catch a NoSuchAlgorithm exception. Instead of, you know, just using an enum for all supported algorithms.
Even if the numbers are completely made up, I'm not going to be outraged that police decided to enforce laws that cyclists need to be abiding by anyway.
As many others have already said, if you've been programming for 18 years, then yes, you are a programmer. I wouldn't say you're crazy for not liking puzzles, but I would say you're crazy for not liking puzzles and pursuing a Ph.D in (what I assume is) Computer Science, since that is invariably what most research involves, and what most Ph.D level jobs are going to involve.
Hmm, perhaps I haven't been around long enough to experience breakages like this, then. I began using Arch before the switch to systemd, and I use it with vanilla Gnome. The only thing that came close to a breakage was the recent move of java-common, but the email that went out from the mailing list included instructions for the upgrade that made it completely painless. Although I could definitely see that causing grief if you hadn't caught the email before upgrading.
I'm curious about how these web framework crates, like this and IronFramework.io, are dealing with the imminent obsoletion of rust-http. It seems rather strange to build a completely new web framework on rust-http when it will soon be completely replaced with teepee.
"But what about the magic of version control, GitHub, pull requests, forking clones, cloning forks, diffing forks, forking diffs, etc., etc., etc.? None of that matters for someone who works with binary file formats (i.e., user culture) rather than plain-text formats (i.e., programmer culture). There was such a disconnect between the two cultures that it was hard for me to come up with responses to these sorts of “why use X rather than Y” questions without sounding either incomprehensible or patronizing."
1. Is he seriously implying that version control is just some arcane thing that Unix programmers do, and that it's bull shit that students have to learn it?
2. If you can't answer students' questions about why these CLI tools are needed, then that does not mean there are no good reasons--it means you don't know, because you don't understand yourself.
"It's comically absurd that the most sophisticated computer programmers nowadays are still using an interface that's remained unchanged since before humans landed on the moon. What the duck?!?"
"Students are starting to grow suspicious: These instructors are supposed to be expert programmers, but their tools look pretty primitive to me."
This is a problem of perception, both on the students and on the professor's part, not a problem of reality. Do you think there's a reason that programmers still use these interfaces decades later? I'll give you a hint: it's not because they don't like change.