It's cool, I would use it. I'd love to be able to set a range of mileage and price, filter by model names, location, etc. etc.
140 karma · joined August 8, 2010
It's cool, I would use it. I'd love to be able to set a range of mileage and price, filter by model names, location, etc. etc.
I plugged this into wolfram alpha:
7639PB / month
Which yields a whopping 23.25Tb/sec (Terabits). So each of 20 households would have to be generating ~1Tb/sec continuously every second of every day.
If so, I think I'm going to need a bigger bandwidth cap.
I also tried 1998's number, but each house would still have to be generating 1.67Gbps.
The argument above about how it's impossible/expensive/complicated/etc. to collect sales tax seems exceedingly bogus to me especially given the nature of HN: Sounds like a business problem to be solved, not some byzantine task. Someone should go make an online sales-tax-computing web service and be done with it.
Oh wait, someone did: http://salestaxwebservice.com/, http://www.avalara.com/products/avatax/calc, et cetera.
Reading this article made me feel like I was shopping in the discount aisle of the pop-psych megalo-mart. This article is cheap shoes. It is poorly written, contains numerous abuses of the English language, and aims low at an obvious insight; the comments have been an order of magnitude more insightful. The author utterly misunderstands the meaning of the main thing he impugns: Frugality. Sorry, but this is a cheap knife with a flimsy blade.
In commercial offerings built around these features, you typically source an SSD that is either write-biased (logzilla) or read-biased, depending on what you are trying to do.
Unless I can understand the ToS, there's no way I'd use such a site.
a) That the customers Sun served in 2004 didn't care about anything ten years away. That their time scale for data on disk was less than a decade. And that marketing to them about how ZFS planned for the future was not effective.
b) That building a 128-bit filesystem (as opposed to a 64-bit filesystem) substantially impacted the amount of time it took to engineer the filesystem or impacted the adoption rate by customers. Clearly those are not facts in evidence. Since we know that an integer behaves pretty much the same regardless of whether it's 32, 64, or 128 bits, it's probably safer to assume the opposite.
I take the opposite lesson: I think when planning your startup, a little thought into "are we representing data in a way which we can extend into the future?" is not a terrible idea, especially when the choice is between a 32, 64, or 128 bit integer.
In the portfolio view (last link): (1) Every company name is elided (ends in ...). That says to me that the column is too small, or needs to be presented differently. (2) Why tempt us with "Show Performance Graph"? Just show it, in miniature, on the page. (3) "Overall" column seems to be useless, it's always "-".
Analysis View: I buy and sell stocks and funds but not too often. So I took up your challenge of "easy to read reports". What does a grade of "A" mean in your system? How many stocks get this grade compared to the total population? I'm not a financial analyst, so some of the jargon on this page was indecipherable to me. DCF, etc. I like the explanation "For every $100 spent, $137.50 of cash is created" (except for the word "create": they are not creating money, only the Fed can do that). When you say: "No earnings power value margin of safety"... I have no idea what that means. Maybe you need to have callouts which explain these things in greater depth, and "show the math". That would be cool. Finally, the stock is "Grade A" but you've given me only 3 reasons to like it, and 4 reasons to dislike it.
In this latter mode, the cheapest seats are black, the most expensive are red (this makes me think red==bad). Bright green (which to me signals "go!") is smack in the middle. And the cues based on circle size are also gone. I guess I initially assumed that red and green would be the two ends of the spectrum in pricing mode. I found the color coding scheme actually caused me to prefer the mid-priced seats because of a preference to avoid red and black. So, I would suggest a rethink of the coloring scheme in this mode.
It would also be nice if you could show the math on what makes a deal good or bad, or at least have some sort of blurb about what constitutes a "good deal".
On the user interface side, it would make sense if any line starting with "/" was interpreted as a command (legit or not). Otherwise, you'll have a lot of "/help" and so forth in the channels. Especially since "/print" is a valid command.
Update: Not sure, but I think someone has now injected some JS which causes everyone else in the channel to continuously spam it with the word "crash". Good times...
I try to self-edit and, I can offer a suggestion from my own experience. I strongly suggest using a pen on a paper copy. This takes you out of the context in which you originally wrote the work-- your computer and keyboard. You can step away from your desk and go somewhere with a different context. A library, coffee shop, or outside under a tree are good places to rethink and rewrite.
And finally, I hope we'll see a revised version of your HTML5 paragraph-- you've clearly hit on an idea appealing to HN readers...
The paragraph's construction makes it hard for the reader to know what the main point is. At the beginning of the paragraph, I was lead to believe that the topic of the paragraph was the lineage and evolution of HTML5 and its emergence from a previous failure. Halfway through, the topic shifts ("Implicitly,") to discuss the implications of the technology. In the third half, it seeks to get to a "bottom line," which seems to be "you should care about HTML5."
The lack of hyperlinks and references has several knock-on effects. The first is that claims made ("Some dismiss") smell like straw man arguments or like hyperbolic statements ("there will be no more versions of html"). Another effect is that the reader is left with no way to learn more, making this a pretty shocking example of the failure to use hypertext (ironically, to discuss hypertext markup technology).
Some recommendations: (1) Print out the paragraph, take a pen, and start crossing things out. Seek to reduce the number of words. (2) Read your work out loud, as you would read a book to a child. Not as you would talk to a buddy over a beer. (3) Review some books on clear writing.