Comment unrelated to the article: I knew I know that blog theme from somewhere, turns out it is my own https://github.com/oltdaniel/dose theme. Thanks for using it. Hope you like it.
Comment related to the article: I always wanted to dive deeper into functional programming languages. Especially, because I more and more run into stuff, that is just simpler to model in a recursive pattern. Maybe I'll give it the a new try within the next weeks and see how far I come.
Finally. Really happy with it, except that the explorer/trending and trending page hasn't been updated yet. I hope that will follow to protect my eyes from that brightness contrast at night and in the morning.
Thats why I read the title first, decide whether it is important or relevant to me, if so I check it out. If I like it, I upvote it and if I have something to throw into the discussion I add a comment. Personally, I use the numbers to indentify "quality" and "valid facts". Invalid posts have a large number of comments and less upvotes.
Because they are recommended or have been explored by a lot of people. Would you buy a product off Amazon without seeing the number of reviews? How do you know it is "quality content".
More votes than comments = something worth reading and seems to be valid content.
Less votes than comments = seems to have invalid points with a big dicussion.
HNs "quality index" for each post can be "calculated" by everyone. Without these numbers you don't know these kind of informations. The title of a post should always be in the focus, thats for sure. But thats why it has a larger font.
I wouldn't see a good point for this. HN is focused on these counts, because only they allow you to identify the "importance" and "discussion size". Would be like twitter without a like and retweet counter. How do I know its important? Is it something I support and give a like, to boost its rank?
Something like [1] is more useful than hiding information.
Quick note on this one. ETags have been used for years, but there is a court case from 2011 and before, speficaly noting this ETag technology as undeletable cookies. Was just a click away from the Wikipedia page. So I think anybody using it, would have an huge issue with the laws. Personally, I think the tracking pixels are more interesting to look at.
Personally I think it is connected to adding more features to GitHub. Microsoft is rolling out more and more small but also big changes, and as everyone knows, this always can have a few minutes downtime for each update.
I think, the core system isn't thought through correctly. I mean, as I have see clicking on different facts that habe been checked, I can place one or dozens of votes for my opinion. What if there is a user thaz gained so many vote tokens and just outvotes other opiniond on something?
A vote should be binary. I can or can't vote. Summary: The main idea is kinda ok, but the system to solve it isn't something I would trust.
The point is, that there are so many different standards that allow you to pay with one thing everywhere. And I personally need to pay a fee for a credit card, which is the usual case in the EU. And there are not many uses cases or advantages I have for a credit card over a free debit card. The thing is just, that I want to point out in the article, that the systems we have all want to solve this but always fail. Its 2020, not 1990, We have so much tech on our hands and banks still fail to implement it.
Fair enough. But I don't pay 2€ per month for a credit card from my local bank to buy stuff from a vending machine. The overall point is, that I have not enough use cases to make resonable use of it in the real world over my current free debit card.
Comment related to the article: I always wanted to dive deeper into functional programming languages. Especially, because I more and more run into stuff, that is just simpler to model in a recursive pattern. Maybe I'll give it the a new try within the next weeks and see how far I come.