151 karma · joined January 30, 2012
Shouldn't the file be moved into different disk fragment first, for that to happen?
Based on the project github page, it seems that this is their version of weird/fun stuff, that is not done as a part of their job.
Did I also contribute to the discussion of the tool?
Like op, more and more people can't get past the idea of starting or contributing to FOSS is no longer worth their time, due to various reasons, such as: their free labor of love was turned into another corporate money making tool.
Perhaps they should put all the water coolers in the executives' offices, so they can listen to all the brilliant conversations that take place at the water cooler.
Is "water cooler talk" the new "open office layout"?
Those plugins would try to point out that the comments that they would preprocessed would look somewhat different from regular comment, e.g.
//this is a regular comment
//#while comments that start with '#' would be preprocessed.
It's still an issue that would shoot the foot of the next person who would maintain your code though.
Hacker News has no shortage of resourceful people that can silently handle the issue by themselves (the first comment even said themselves that they could simply use Reader Mode!). But the main point of my reply is: look at the number of replies that focus on the style of the website, and compare that to the number of replies that focus on the point of the post/article.
Instead of contributing to the discussion related to the post, it's easier to just go "the website sucks."
Any hardware issues (mind you, the failure rate is pretty high, especially keyboards), and you're left with a broken device.
They did hire from places with cheaper labor cost, such as Taiwan. They still got axed.
Or: why should I do my part when everyone's selfish?
The police should/would tell you.
I was trying to create a new project last month trying to put all of these together. One thing that I was stuck in was putting these together:
- non-single-thread-Flask
- Redis pub-sub, subscribe to listen to a channel
- and websocket (such as socket.io) upon receiving redis sub message, pushing the message to client side.
I found out that this was a non-trivial thing to do, as redis subscribe is a blocking function, and I was not able to push websocket message from redis subscribe callback. I wonder how did they do that, if any?