News for hackers. Stuff that matters.
Re:AWS CodePipeline by ebbv on Thursday July 09, 2015 @11:56AM (#9858646)
What's up with the Amazons spam? There's 5 different submissions on the front page right now. They could have all been one. Bad form, AWS team.
Re:AWS CodePipeline by dang on Thursday July 09, 2015 @12:54PM (#9859109)
The major tech cos bundle their big announcements on their annual conference day. Amazon, Apple, Google, Microsoft all do this, and all have had multiple stories on HN's front page at the same time. As long as the announcements are significant and HN-worthy and they do it rarely, it seems ok. A story doesn't become spam just because it's coeval with others.

If one or two of the stories are noticeably weaker than the others, or especially if they've appeared on HN before, we'd appreciate users pointing that out, since we can penalize those.

Re:AWS CodePipeline by andyjohnson0 on Thursday July 09, 2015 @12:01PM (#9858692)
AWS Global Summit [1] is taking place in NY at the moment. Hence the new product announcements.

[1] https://live.awsevents.com/

Re:AWS CodePipeline by ebbv on Thursday July 09, 2015 @12:09PM (#9858764)
That is not addressing my question; why are they posted as 5 separate submissions instead of being 1 LiveBlog post or something?
Re:AWS CodePipeline by ceejayoz on Thursday July 09, 2015 @12:13PM (#9858784)
Each one is a separate post, about a separate service, which would logically generate separate, product-specific discussions.
Re:AWS CodePipeline by andybak on Thursday July 09, 2015 @12:29PM (#9858911)
I agree. A single post would just end up unmanageable and dominated by whoever had the top comment. (I always yearn for a 'by date' sort for HN comments as often the top comment hijacks the discussion on a tangent and it's annoying to find people discussing the primary topic)
Re:AWS CodePipeline by dang on Thursday July 09, 2015 @01:21PM (#9859316)
> I always yearn for a 'by date' sort for HN comments

We can't make a big flat list and sort those by date without losing the threadedness of the comments and thus their context. But we could sort siblings by date at each level of the tree, including the top level. Is that what you mean?

Re:AWS CodePipeline by andybak on Thursday July 09, 2015 @02:02PM (#9859611)
> without losing the threadedness

Sometimes this would be a good thing. Top-level (and in general 'higher up the tree' comments completely dominate. It's rare for the direction of a HN thread to shift much after a reasonable number of comments as everything gets buried quite far down.

I'd really like a 'what changed since i was last here' button. Quite often I come back to a long thread I was especially interested in and I'm completely unable to find out if anything of value has been added.

> But we could sort siblings by date at each level of the tree

More options = better. The intended audience of HN can cope with a few more things to click. Treat us like power-users.

Re:AWS CodePipeline by dang on Thursday July 09, 2015 @04:52PM (#9860607)
HN has always treated users like power users. That's part of its design. But there are other considerations, such as its minimalism and the fact that there is a single shared view of the content.
Re:AWS CodePipeline by andybak on Friday July 10, 2015 @04:13AM (#9862809)
> a single shared view of the content

So is the lack of options to resort and reorder comments an intentional thing?

It would be interesting to hear the reasons for it and what benefits you consider it brings.

Re:AWS CodePipeline by derwiki on Thursday July 09, 2015 @12:13PM (#9858786)
I don't think it's fair to assume that this is spam from the AWS team. Many of us use AWS services daily and like to keep up with new offerings.
Re:AWS CodePipeline by ebbv on Thursday July 09, 2015 @12:15PM (#9858798)
If you look at the profiles of the submitters, at least one admits to being an Amazon employee.

Yes, lots of us are interested in AWS (I am too), but that doesn't mean each separate announcement should be its own post. And I don't think the nearly uniform submissions we see would have happened organically.

Re:AWS CodePipeline by andyjohnson0 on Thursday July 09, 2015 @12:11PM (#9858776)
Because they were posted by different people who didn't take your preference for a single post into account.
Re:AWS CodePipeline by ebbv on Thursday July 09, 2015 @12:13PM (#9858785)
At least two of them are posted by the same guy. And at least some, if not all of them, are being posted by Amazon employees.

So again, I say, the AWS team is spamming HN and it's in poor form. It should all be one submission.

Re:AWS CodePipeline by WaltPurvis on Thursday July 09, 2015 @01:37PM (#9859428)
No, it should not be all one submission. These are separate and distinct products, and I want to read separate and distinct HN discussions about them.
Re:AWS CodePipeline by kordless on Thursday July 09, 2015 @12:47PM (#9859055)
Note that you are also getting voted down. Lot's of Amazon employees to hit down votes on people who say anything against them. This text may be grey. :)
Re:AWS CodePipeline by WaltPurvis on Thursday July 09, 2015 @01:39PM (#9859441)
He's getting voted down because he's completely wrong and semi-slandering Amazon employees with no factual basis, as are you.
Re:AWS CodePipeline by tedunangst on Thursday July 09, 2015 @12:57PM (#9859136)
Welcome to the future, where it is now required that you organize your website to conform with the HN submission process.