jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
For most of the lay users I help in the community 4tb is immense.
For most of my colleagues (I work on Kubernetes cluster backbends for large companies running streaming services you likely use, among other 'big' data companies) 20-50tb is if you run your own all time backups (usually with ZFS and the like so divide that by 3 for total usable space).
The guys that are running IPtv or other sketchy video streaming and scraping software are hovering around 100TB-200TB in their NAS and none of them actually run user grade hardware... I'm honestly very surprised to hear it referred to as 'smallish'.. At most I'd say 100TB is about middle of the road now days for media horders and small for media content producers.

Now my buddy that worked on the CEPH storage backed at CERN would laugh at any of these numbers... but that's a different ballpark all together..
> Somehow, we seem to be forgetting how free speech benefits us all

In normal times, I would agree. Philosophies and ideals like this effectively discourage people from taking action. That makes a lot of sense during times of peace when our asses aren't actively on the line.

However, these are not normal times. We are facing a threat that might just overwhelm our society and rob us of our way of life. We must act now to neutralize the threat or risk going extinct. We can sort out the ethics of it all later.
Which is pretty much the reason that my use of Twitter and Reddit is pared down to super specific niches because once you leave your bubble and go to #general it’s an absolute dumpster fire.

If they could actually rein that shit in I would use it more. Just having the tools to filter that stuff out of my feed would honestly be enough. TikTok is pretty much where I go for discovery now because it learned really quickly to not show me any political content.
Alternatively, perhaps people are responding because they are having (or have had) similar experiences. Personally I have been very frustrated with iOS in the past year or two due to crashes and other bugs. Granted, a good number have been resolved in recent patches, but I'm still getting way more crashes than I used to several years ago (weekly+), and shaking off the previously frustrations and regaining trust is a time-consuming process.

Perhaps it's also lack of QC for new releases. When iOS 7 and 8 were released, pretty much everyone I knew were experiencing frequent crashes and other issues.

As someone else pointed out, there is more surface area for bugs to occur. Hopefully QC will step it up.
every interesting, are there any part-time position ?
His TED talk about charter cities: http://www.ted.com/talks/paul_romer.html
Here's the thread discussing the survey:
http://forums.penny-arcade.com/showthread.php?t=119908

The overall consensus seems to be that the attendees would rather have people who know the product well at the booths as opposed to eye candy. Several mentions in there of a game developer who was also dressed in full costume being OK.
I'm not talking past anyone -- I'm just choosing to ignore the silly aspersions to my intelligence. It's possible to make an argument without calling the other guy stupid.

What you're seeing here is really just the usual battle between ideology and reason that seems to pop up on HN on the weekends. We've got a fundamentally silly article that wants to take all of computer science to task, based on a corner-case analysis of worst-case performance of a single algorithm, in a single, exaggerated context.

You're right that the author wants to rely entirely upon the OS cache replacement policy for Varnish and that's fine, as far as it goes. But this ideology leads directly to the problem observed (namely: some rarely used things that really should stay in memory are evicted, because the OS has no ability to discern the semantics of memory use by the application). Rather than acknowledging this limitation, the author has decided instead that the algorithms are all wrong, and that the Stoopid Computer Scientists are all a bunch of short-sighted eggheads.

Again, it's not a question of who's right, and who's wrong -- it's a matter of philosophy. You can assume that the OS memory manager is the all-knowing, all-powerful Wizard of RAM, or you can give it some guidance. In this case, locking an 8MB heap into RAM is hardly a trade-off, when you're talking about a system that is actively managing several orders of magnitude more memory on a regular basis. Spending days of coding time optimizing a basic data structures for worst-case memory access patterns is short-sighted, when the alternative is an mlock() call.
I see what you're saying, and broadly, I agree with you.

I think we have different definitions of article creep. The things you talk about are real problems. The problem for me is that when I have encountered the term "article creep", it has mostly been with respect to articles about episodes from highly-notable television series. Really, we have two different types of article creep:

Firstly, we have the pure vanity cruft, new articles created without any references which simply are impossible to verify, or have been created by sources too close to the origin. These genuinely do polute wikipedia, since they typically do not attract new editors, and rarely get linked to (both internal and external to wikipedia).

Secondly, we have genuine quality writing that is well-researched, clearly verifiable, useful to a wide audience, and can be well-linked. This second category would attract editors, maintains itself, and is generally useful. Yet, for various reasons these can get accused of ruining wikipedia.

Part of the issue is that most wikipedia editors have been untrained, and seeminly have not even had and understood something akin to GCSE history. A significant number joined to promote their point of view, rather than to develop a quality resource. The easiest solution to the problem, given this, is as you support. The best, however, is a different matter.
"We will be updating the TOS to require you to check t.co and register the click."

Damn. Looks like URL shorteners are here to stay, permanently, and twitter is crowding out all existing link shorteners.
I really like Nginx, but my current setup is Apache for no specific reason other than that it was already there and very familiar to me. The sites I'm running don't pull enough of a load that memory usage matters at this point.
You're right about concentration/volume. The marine ecosystem deals with a certain amount of hydrocarbons. It's when there's more than it can deal with that we get problems.

Researchers at the University of California at Santa Barbara are studying some of the most readily accessible natural seeps in the world right off of campus:

http://convergence.ucsb.edu/article/goo-and-gas

http://seeps.geol.ucsb.edu/

http://convergence.ucsb.edu/news/ucsb-scientists-document-fa...
Say what you will, the majority of us can totally relate to at least one of his paragraphs.

The more access I have to information, the more I find myself thirsting and craving for it. As with anything, it requires serious discipline to control it. But these little data and information pushing devices are exactly what makes it so difficult!
They wouldn't be surprised that it was crammed uncomfortably full of people; that doesn't mean they'd do anything about it though.
I can't wait until they announce the LLMUA.
Looks like they're going to wrap existing shortened URLs with t.co:

If you are already partial to a particular shortener when you tweet, you can continue to use it for link shortening and analytics as you normally would, and we'll wrap the shortened links you submit.

http://blog.twitter.com/2010/06/links-and-twitter-length-sho...
I've been following this course (to refresh my informal knowledge of electronics, which I haven't touched since I discovered it was way cheaper to write broken code than build a broken circuit back in my teens) and it's pretty good. I like how they mix the theory with practical experiments showing it in practice.

I don't recommend the Kindle version though, the formatting is really lacking.
Is it possible that your habits are partially trained by the device's strengths? It's easy to install from the app store so that's what you do. Don't you think that if you could install apps from the web you might do so after getting used to the feature?

It's a new feature for Android, so this article is really just hitting on how to market to users. It's saying play to Android's strengths, don't try to market the same way you market on iOS (which involves getting on the featured app list). The Market is much more algorithm driven in it's rankings so that approach doesn't work. But if you can spread your app in a viral manner on twitter and facebook with a link straight to purchase/download, how can you say that's not good advice?
remember though, the l33t letter replacements are in the dictionaries for common passwords, and used in brute-force algorithms.
Can you really get an original paper written at a price that's at least conceivable for a high school student to pay? Nuts.

Oh, absolutely. I see 400-level programming and engineering homework assignments crop up on vworker from time to time; they go for about $15. And copywriting is way cheaper than that.

High school english papers are what, five paragraphs? People pay about $1.50 for comparable web copy on Mechanical Turk.
I have the FBI message currently for UB.COM and Absolutepoker.com so yes I think it's DNS related.

edit: confirm for PS and FTP also, you can check with that webproxy: http://www.fasterthree.info/index.php
http://www.whatsmydns.net/#A/fulltiltpoker.com

Shows the propagation is underway.
Argh, I hate reading slides without the accompanying audio/video, because I feel like I miss out on 90% of the context.
I'm willing to bet that the set of 8-character full-ASCII passwords is comparable in cardinality to the set of 8-word sentences, even accounting for Markov information density.
Every time I see a HN story about "how i made my site handle lots of traffic" it's people re-learning the same lessons. We really need a basics-of-building-big-webapps FAQ.

Step 1: Make your site as static as possible, or at least relying as little as possible on server-side processing. Pretend your app is made of Java and thus assume it will hog memory, be slow and crash every other day, so plan to handle those kind of 'reliability' issues.

Step 2: Get a CDN or a buncha cloud-hosted servers (like, 100). You may need 5-10 of them to serve static content using a caching web server solution ala Varnish (or just Apache proxying/caching; yes, it works fine), and 50-100 for application and database processing.

Step 3: Make sure as little of your site as humanly possible makes use of database calls, and for gods sake try not to write too much.

Step 4: Use a lightweight (I SAID LIGHTWEIGHT!) key/value memory store as a cache for database elements and other items you might normally [erroneously] get from disk or network or database.

Step 5: Don't rely solely on 'cloud' resources. Eventually you will get bitten because they're not designed to scale infinitely and probably do not care about you (especially if you don't pay for them or pay very little).

Step 6: (optional) Re-create this solution on a different hoster in a different datacenter on the opposite coast of your country. Not only will you end up with a DR site, you'll see load and latency improvements for many users. How to effectively and cheaply replicate content between datacenters cross-country is left as a lifetime career goal for the reader.
"Uh, I was there at the time"

Can you verify what I was told in business school in the late 70's (Wharton). I remember reading a case study that said that Smith was considering flying passengers on the deadhead by installing seats between freight runs. Was there any discussion of that?
Then write a parser to regenerate all the targets! It's a good thing make is turing complete. :-)
You're right. All of those things are already here. We're even better off than we were then.
It's something like the 'facebook like' button, but it's more like an experiment for my graduation. I want to become an intern at Valve, that's why I've made this website.

If you have any feedback, please let me now :) Thanks!
I don't mind the core of spring but the full spring stack is nearly as bad as Java EE - I was reading through what was suppose to be a simple minimalist tutorial on how to implement CRUD operations in spring the other day and my jaw dropped at the amount of duplication, verbosity & incomprehensible config involved:

http://www.adobocode.com/spring/adding-crud-capability-to-sp...

I'm personally into much simpler stuff like Stripes & Guice.
How times change - when we started in '95 the fact that we were doing a server side application in Java was seen as a very cool thing.

However, at some point about '99 or so Java seemed to endure a culture change where Java became popular as an "enterprise" platform and the values associated with that culture started to dominate a lot of discussions about how to do things. Suddenly everyone wanted to use every feature of J2EE in every project (largely for CV padding as far as I could see) - with predictably awful results.

However, Java has always been a pretty decent platform - we wrote search engines in it and things like Lucene continue to work pretty well. There are a lot of fascinating libraries for Java and performance can be excellent - it could be pretty fast in 2001/2002 and I assume it hasn't got slower....

If you can use Java and focus on "Keep Things Simple Stupid" then I can't think of many reasons not to use it - it might not be fashionable any more (those days are long gone) but it sure is capable.
Not arguing for or against it because the whole thing seems way too muddled for me.

But have you ever considered that the difference between your arguments (i) to (v) (with exception of (iii) maybe) is the intention of the humans involved not the suffering or the dead of the respective animals? This kind of moral reasoning is human and can be seen in other areas as well. For example, we care a lot more about the comparably "few" deaths caused by terrorism vs. the many caused by traffic, because presumably in the former there is intention of bad guys involved whereas in the latter its merely bad circumstances and chance. The result is the same: an animal or a human is killed. However, the moral reasoning is different. Just saying ...
Source is a joke/hoax/satirical site; flagged.
Are any of these cross-platform like make?
You know that. It's unlikely that all of the rest of the people who join Discord because "all of their friends are on it" that your presence there influenced know that, and in many possible future scenarios, you and others' presence there directly contributes to the harm that may befall them as a result of their loss of privacy thereby.

https://www.brainyquote.com/quotes/cardinal_richelieu_183310

It's also impossible to effectively self-censor in the present for potential content-based threats in the future.

Discord also bans certain entire domains from being sent as links in DM, as an antispam measure, and requires in their ToS that people give up their civil rights to join. It's not polite to ask friends to submit to third-party censorship of private conversations just to talk to you.
I'll take your word for it then, since I have seen similar opinions expressed before, but when you say "serious" what particular qualities are you thinking about?
I think a lot of the issues here (particularly around version management) are more advising against frameworks that aren't firmly established as popular.

If you're using something like Rails, a lot of the issues are minimized to a huge degree:

- Work required from updates to Rails itself, while sometimes painful, usually has a lot in the way of community support, and it hasn't been really bad since Rails 2/3/4.

- Libraries are highly, highly incentivized to keep up to date with the latest version of Rails, since so much of the ecosystem revolves around it. Not supporting the latest version of Rails basically signals you've abandoned the project.

Regarding switching libraries and frameworks, this depends on the scale I think. With React (an example he gave of a library, although I personally think it's in a bit of a grey zone) switching to something else basically means re-writing your front end - even your state management is likely written in something fairly coupled to React. If you're replacing a single-purpose library, sure the impact is smaller, but those sorts of libraries are ones you'd probably be using in a framework world anyway.

For me, the biggest value of frameworks is eliminating low-value decisions. With an opinionated framework, there doesn't need to be arguments about how to structure your project, how logging, or authentication, or database interaction, or one of a million other things with a lot of OK answers is going to work. This eliminates arguments when initially developing things, and massively reduces onboarding time. I can get a git repo of a Rails project and be more or less productive in a few days - with bigger Node apps I sometimes feel like it takes weeks or months to really get how things are structured sometimes.
At least in germany using WhatsApp for anything semi officially is essentially prohibited already due to privacy laws. There is a lot of 'grey' infrastructure
( WhatsApp groups coordinating parent teacher stuff) but this is getting replaced already.
C#, ASP.NET Core with MVC, Dapper, SQL Server, TypeScript. And don't go SPA unless you need it. (Even though my during my day job I use Angular.)
Genuine question: does Facebook own Meta, or does Meta own Facebook? Or is it Meta Platforms[0]? Will Facebook (the product) as everyone knows it continue to be marketed as Facebook (under the leadership of Meta), or is facebook.com going to be re-branded as Meta? I looked the other day and it still comes up as Facebook... and Meta. What the hell?

Addendum: why does meta.com redirect to [1]?

[0]: https://en.wikipedia.org/wiki/Meta_Platforms

[1]: https://about.facebook.com/meta
Direct steering linkages are a major safety feature that isn’t going away because at high speed you need minimal steering input. My power steering died in a 3,000 lb car and I didn’t get it replaced for a few weeks because it was only noticeable at very low speeds.
This is actually a really surprisingly enjoyable game. One cool feature would be to add level numbers/hashes/identifiers so that I could share a particularly fun level with someone.

Apart from that, I really love the lack of points/levels/bonuses/timers/etc, makes it a nice and relaxing game. Also very visually pleasing
Sure, the UX nail can certainly be counter-sunk. But overall I think my estimates are pretty close.

The thing that makes UX really hard compared with features and capabilities is that there's no straightforwardly "right" answer that can be discerned Platonically in isolation.

UX is a matter of taste and people, not algorithms and code. It's not something that responds to the kinds of Moore's Law efficiency gains that can be achieved in the CS realm -- it requires the irreducibly expensive commodity of human time and effort.

The fact that this kind of time and effort investment is irreducibly expensive is why huge mega-corporations like Apple and Google have such an intrinsic advantage in this department. It's easy to understand why they dominate the mobile space -- when you're interacting with a mobile device, your appetite for poor UX is quite a bit lower than when you're sitting at a desktop.
> The free market has spoken

What a crock of bovine excrement. Calling iOS a "free market" is utter lunacy.
I hunt elk in the Idaho panhandle and have witnessed the changes that the wolf packs have brought to the area over the past ten years.

The current situation with controlled hunting of the wolves is vastly preferable to the previous state of affairs where locals felt the need to take matters into their own hands because the Fish and Game authorities were not able to control things (and when given license to do so the state authorities manage the animal populations admirably). The destruction the wolves brought to the elk population isn't as big of an issue (though in our area the total numbers dropped by half when the wolves arrived in force) as the damage they were doing to animal husbandry in the area. Wolves are like humans in that they sometimes kill for sport - in one case a rancher had over 100 sheep killed over the weekend by three wolves, throats ripped out but not eaten. This was an extreme event but not surprising given the extensive low-level damage that farmers and ranchers experienced in those areas.

There was also a growing discomfort in the area due to the wolves' general fearlessness around humans and several threatening incidents which thankfully didn't result in any injuries. They can grow to be seven feet from nose to tail and weigh over 150 pounds - and when you hear two dozen of them howling around you in the woods it will chill your blood in a very special way, no matter how well armed you are. Thankfully now they are much more skittish and are not as aggressive towards people - they are quite intelligent and know that the rules have changed for us. It's actually incredibly hard to fill a wolf tag, the actual success rates for the hunters were at least an order of magnitude lower than predicted in the first seasons. Wolf hunting success rates are less than 1%, whereas elk hunting success rates average more around 20% [1]

One issue is that these aren't even the right variety of wolves that used to roam these areas, before the era of human game management. It would almost be like environmental activists bemoaning the loss of black bear territory in Virginia and replacing them with grizzlies. Once a few wandered into the D.C. suburbs the locals might get a little upset.

Ultimately it boils down to trade-offs. How much economic activity and tax revenue would we mind foregoing in order to maintain an abstract good of environmental balance? This is a hard problem when both sides of that equation are well-defined, but in this case the definition of environmental balance varies radically, especially when trying to reconstruct some unmeasured (by comparable modern methods) pre-existing state.

1 - https://fishandgame.idaho.gov/public/docs/fgNews/2012feb.pdf (page 3)
I find the author's insistence on his thesis - that we must retire Ahmdal's Law - very strange. I don't even think of Ahmdal's Law as being necessarily about parallelism; it's also useful when reasoning about improving the performance of a sequential program.

The reason I find his insistence strange is that the rest of the article is a good explanation of what has changed in the decades since Ahmdal published his paper. But I disagree that all of those matters change the fundamental lesson: your ability to improve overall performance will be limited by the parts that you are unable to improve.
> The problems with the traditional daily standup is a lack of focus and off-topic discussions.

This is not a problem with daily standups. This is a general problem with all meetings and discussions that are not ruthlessly kept on-topic and to the point by someone of authority who should be ready to interrupt as soon as the discussion goes off-track.
One thing I didn't find on the website was a way to get an email with the actual data that was leaked so I can evaluate what's at stake. Showing it online would be poor privacy but sending it to the email should solve that.

Some of the leaks are from companies I don't even know, that work behind the scenes aggregating information. Particularly for those I'd like to see what was leaked. For the services I actually used directly I have a clearer idea.
Yep, that's the reality.

We had a product that was free/paid based on home/work usage and the amount of "home" users coming from corporate IP spaces was absolutely staggering.
Companies must archive invoices for 10 years. But of course that doesn't necessarily require keeping an account for the customer.