I don't think anyone would use that construction though in the midwest if they only meant the men. If they wanted all the guys to get off the dance floor they would say "Now, all the guys are going to step off the dance floor." "The guys" is much different than "you guys", at least where I live.
Granted, it is murky so I also don't really care about switching to y'all. The only problem I have with "y'all" is that it is such a southern thing that using it to me with my midwest accent sounds forced and awkward (At least to my ears).
That used to be the case, but the build tools have supported lambdas for a while now, and it works even on very old devices.
On the other hand, Java 8 classes like java.util.Stream only exist on API 24+ devices. So if you want to support older classes, you can't use the standard stream library.
It is indeed incredibly unlikely that someone needing a pixel art editor wouldn't want save, I agree with you completely, and I bet @kgwxd does too. But that doesn't invalidate what @kgwxd said. The question "why would you create/edit anything if you can't save it?" was taken literally. @Simpliplant didn't qualify people using pixel art editors, the question said why would you do anything if you couldn't save. As it turns out, people do that all the time. Just not with pixel art editors.
Part of having a productive conversation is using context clues and social norms to help your understanding of what someone means when they say something. Derailing the conversation by taking a comment literally when everyone understands the intent behind the comment is not helpful.
But one of the interesting parts of the paradigm of hierarchically-threaded online discussion, is that only one subthread/reply to a given thread has to be a "productive conversation" (i.e. to continue the thread in the "obvious" way); the other subthreads can be tangents, and tangents do not "derail" in the same way they do in a flat-linear-threaded forum.
I would disagree, because they're still visible and still structurally part of the same conversation, meaning people reading the conversation will read those tangents, or at the very least be distracted by them.
And this is why subthreads in all hierarchical discussion systems are sorted by vote-rank: the subthread that most effectively serves as the continuation of the "canonical" conversation will (almost) always appear first. The only time that doesn't happen is when that subthread doesn't exist—as has happened here. More often than not, when this is seen in a "played out" archived discussion thread, this doesn't suggest that people are "getting distracted by" the tangent, but rather just suggests that nobody is all that interested in continuing the original conversation.
(Unless the tangent leads toward a mind-killing subject like politics. I'm 100% behind you on applying careful consideration before making a tangent from a technical topic to an emotionally-charged one; people see that kind of subthread and never even make it to the rest of the subthreads in the same conversation.)
Another part of having a productive conversation is learning not to make blanket statements, and knowing that most of what you say will be taken literally, and being generous and charitable in your interpretation of others.
For me, the best part of having interesting conversations on HN is reading all the alternative points of view by smart people. Not much "productive" happens, from my point of view, by criticizing someone's show HN project, not much "productive" happens when you make blanket statements about what all people want. And not much "productive" happens by only agreeing with others.
So there might be another hidden motive behind what @kgwxd said. The comment he replied to literally insults the Poxi project, and perhaps @kgwxd was merely defending a Show HN project that's in a very early stage.
In my view, you may be defending the wrong person here. I want to see more show HN projects, and I want people to feel comfortable sharing their projects without fear of getting ripped to shreds, called a joke, and questioned why anyone would ever want to do such a thing. Let's be supportive.
>Another part of having a productive conversation is learning not to make blanket statements, and knowing that most of what you say will be taken literally, and being generous and charitable in your interpretation of others.
So the point was to teach the commenter a lesson by responding unhelpfully?
>In my view, you may be defending the wrong person here.
So, because I was pointing out someone not responding constructively I am by necessity "defending" all points the other person makes? I think that is faulty reasoning.
Wonder if that has something to do with size of America relative to most countries in Europe. Americans just simply have to drive more and for longer distances. Driving doesn't seem so fun in the midwest.
I went through an earily similar process for a game I'd been developing on the side. I fell for the trap of building my own engine because I thought it would be a fun challenge. It was, but I ended up spending 90% of the time working on the engine and 10% of the time working on the actual game. I eventually published the app, but I'm admittedly a bit frustrated with the end result. I wish I had just gone with an engine like libgdx earlier on in the process. If I had it probably wouldn't have taken me over a year to come up with a simple 2d game.
Also as it turns out pixel art is much harder than I thought.
As both a hacker and a brewer this is extremely interesting. Building a temperature controller fermentation chamber is something I want to do at some point.
> They don’t teach rails at uni. So straight off the bat it eliminates that large segment of people inspired by the dot-com bubble to get IT degrees to earn good bucks. Java and .NET developers are a dime a dozen.
Yep, just because you know a certain framework (not even a language, a freaking framework) means that you can pass judgement on how valuable every Java and .NET developer is. This guy obviously doesn't have a clue about what he's talking about. They don't teach any other framework at most universities. It's assumed you can learn that stuff on your own. Just because you went and learned Rails doesn't make you automatically a programming superstar.
Those are specific to the Emacs emulation mode, which you can turn on under "Keys" in preferences. Like a lot of these emulation modes, it gets something like 90% of the key bindings right, and the last 10% will trip you up just enough to drive you crazy if you're really used to Emacs proper.
Granted, it is murky so I also don't really care about switching to y'all. The only problem I have with "y'all" is that it is such a southern thing that using it to me with my midwest accent sounds forced and awkward (At least to my ears).