skysight-inc/HackerNews huggingface dataset:
So this is A Dark Room with kittens?

Here's two one-liners for the console to help speed up the process

setInterval(function () { $('span:contains(Gather catnip)').click() }, 5);

setInterval(function () { $('span:contains(Refine catnip)').click() }, 100);

clearInterval() on the numbers given back will stop the auto-clicking
Greece: What Went Wrong? [video]
Can someone explain to me why using a cached value for hashCode in an immutable string is a bad thing?
> Science tells us of bad effects that certain kinds of discharges can have on our children, born and unborn, but we don't seem to see the analogy between a perverted individual sexually molesting a child and an industrial discharge affecting the basic sexuality of a child.

The Making of a Conservative Environmentalist, by Gordon K. Durnil, at p. 43

http://www.iupress.indiana.edu/product_info.php?products_id=...
Israeli Hacker Jailed for Hacking Madonna’s Computer
We can disprove the existence of strong encryption with a wireshark, but cannot prove it.

Entropy of a rot13 message would be much lower than that of a properly encrypted channel. High entropy is not proof of "meaningful encryption", mind you, since a compressed rot13 or plaintext message would have high entropy too.
> Maybe it’s even Satoshi Nakamoto herself.

Well done.
Many of the claims that GC outperforms manual memory management compare running dlmalloc to allocate all data with a well-tuned generational garbage collector on something like the Da Capo benchmark suite. Naturally, they find that the ability to get bump allocation in the nursery of a good generational GC ends up outperforming a malloc implementation that was never really designed for that kind of workload.

But the real question, in my mind, is whether a well-tuned systems-level program that uses stack, arena, and heap allocation with a good allocator like jemalloc ends up being better with a garbage collector. And it's really hard for me to see how that could possibly be the case. Performance-conscious systems programmers will use the stack as their nursery, gaining all the benefits of the nursery without the copying, tracing, or delayed reclamation. Modern mallocs like jemalloc or tcmalloc are incredibly good at minimizing fragmentation and satisfying requests quickly, using thread-local caches to avoid synchronization. Most of the time, the tenured generation needs the same bookkeeping that a modern malloc does, so you're not really gaining anything by using GC for that generation. And a GC always has some kind of mark or tracing phase (not to mention at least a write barrier if you want your pause times to be reasonable), which is pure overhead over manual memory management.
What do you think about Realm Database on mobile?
Really? That was 12-13 years ago.

For comparison's sake, I feel like in 2002, I was thinking of games like the Sierra point-and-clicks (Leisure Suit Larry, King's Quest, Space Quest, Police Quest, Conquests of the Longbow, et al) as retro and most of those would have been in that age bracket.
LiteBSD - Variant of 4.4BSD Unix for Microcontrollers
Still used in pediatrics in the UK. Just the BBC being the BBC.
It's not all fun and games: ketamine will eventually destroy your bladder.
I am not a Programmer. I put up simple websites, and like technology, and enjoy this field. That said, I probally shouldn't comment, but from day one of my computing journey; My biggest gripe with this field has been terrible technical writing. (I put up with it because it was all so new, and figured it will eventually get better.)

I can still remember picking up those 500 page computing books. Flipping through the phone book and putting it back on the shelf.

As to the overuse of acronyms; I think they are overused in this profession. It almost seems fashionable?

Jump to today, things have gotten better. I'm not sure the writing has gotten better, or I just have more presenters of the information(Internet)?

I don't know why you got down voted? The level of technical writing in this field is atrocious? I understand "these are tough concepts!". Yes, in many ways it's like learning a language! I get it. In most cases I'm glad someone took the time to write something down. Yes--I'm grateful.

I do have a problem with entities, with a lot of money/resources, whom publish terrible technical writting. It does seem like a big company, like Amazon, could have done a little better job conveying this product?
During my stay in Bucharest I got to experience a very slight quake, that wasn't centered anywhere near my location (the epicenter was 100's of km south of where I was).

At first I thought I was becoming unwell, I couldn't focus on my computer screen and I felt like falling. Then after a bit I realized it wasn't me but the world (what really helped is that I noticed the lamps were swinging relative to the building).

It only lasted for 30 seconds or so but I've never in my life felt more disconcerted and panicky (whereas normally in a 'bad' situation I'm scarily cool and composed because that's the way to get out of bad situations this hit me in a much more primitive part of the brain).

All I could think of once I realized it was an earthquake was 'get out' which given the general state of construction in Romania isn't a bad idea at all but would have been a spectacularly dumb thing to do once the quake has started because the staircases are amongst the most dangerous places.

Really odd feeling and I sincerely hope to never experience it again.

http://earthquake.usgs.gov/earthquakes/eqarchives/poster/201...

https://twitter.com/jmattheij/status/470134804894470145

I'm going back there in a couple of days and the feeling never quite left me and I'm conscious of it when I'm indoors there.

It's pretty irrational given the chances of a really bad quake while I'm there but Bucharest has had its share of really bad ones:

https://en.wikipedia.org/wiki/1977_Vrancea_earthquake
Still waiting to hear if the El Capitan beta is stable enough for daily use.

I'm with no ability to backup my MBP but the new improvements tempt me to download the beta..
Agreed, most libraries and frameworks have nasty leaky abstractions; that is part of the cost of choosing to add those packages in your architecture. And heck, the browser itself is a clown car full of leaky abstractions, we deal with the problem everywhere.

I think successful open source projects have a pretty good track record managing leaky abstractions since they have so many users. JQuery did a good job in this area over time, papering over many of the leaky abstractions present in the DOM across browsers. Looking at the bug tracker for React, I think they are doing okay too after a rocky start. Haven't really tracked Angular, but I hear Ember is a pretty well run project too.

Shadow DOM does sound pretty good, but not essential to componentization if you're managing your ID's carefully. Honestly, I don't care if a framework or the browser manages my component scopes, I just want it taken care of.

I always thought scoped stylesheets would be more important to non-leaky UI component development, but it seems like that is yet another dead-end experiment that didn't catch on. http://caniuse.com/#feat=style-scoped So we fall back to tooling again, and get something like SASS to manage and build our monolithic stylesheets.

I prefer linking to Joel Spolsky's blog when describing Leaky Abstractions since he coined the term: http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...
Just a little advice for newcomers ( like me ) that are scared but at the same time fascinated when it comes to use javascript. If you choose a framework to work with, stick to it for the entire project, and if you find an error that makes you struggle, don't immediately invent your own solution to patch it:
for all the things that are said in this article, it always easy being attract to the fact that in every framework/code base you can put a simple piece of code that make things simpler for your and let you go ahead when you are stuck. But in my experience, most of the times, it only about being lazy and scared from and understood error. Behaving like this it let you behind, and don't make you improve your skills. And always break the entire logic of the tools you're using.

JS is a scripting language, so it easy 'script' your solution and postpone a problem. But it this way, you will never be able to improve, and your life with JS will remain frustrating and hard.
I've been thinking along those same lines. Is Uber the corporation in any way essential to Uber the service?

I have a feeling this can be done via a worker's coop. But someone will need to take the initiative to start.
I understand that it's disappointing if your PR doesn't gets merged.

If you want to do something big, you should consider writing a proposal first in one of our issue trackers or on feedback.gitlab.com.

In the same line, consider just creating a prototype / proposal or MVP of whatever you're building first. There are many people at GitLab happy to help you get rolling and get the PR merged. At the same time, if you're completely off-track, we'll also tell you that.

The best way to not waste time is to communicate before, during and after any effort.
Thanks, one of the best talks I have seen for awhile
Sure, but I don't see anything ruby-specific about default argument values.
Well a high speed rail like the TGV going ~300-350km/h would cut that down to roughly 2.5 hours, admittedly that is still higher than going by air, but a lot better than 12 hours.
Right. But imagine if Zuck opensourced the exact facebook source from day 1 or day 100. It would have been hacked a long time ago to the point of collapse, and who would that have benefited?
I recently created vdist (https://vdist.readthedocs.org/en/latest/ - https://github.com/objectified/vdist) for doing similar things - the exception being is that it uses Docker to actually build the OS package on. vdist uses FPM under the hood, and (currently) lets you build both deb and rpm packages. It also packs up a complete virtualenv, and installs the build time OS dependencies on the Docker machine where it builds on when needed. The runtime dependencies are made into dependencies of the resulting package.
I heard several survivors that were appalled of the "Think of the children" approach because it is too often used to push an agenda that doesn't help children at all.

For example, internet blocking of child abuse media (hot topic in Germany a couple of years ago) doesn't help children (who aren't abused 'over the internet' but in real life) because it routes resources away from public education on the matter (such as encouraging victims to speak up), social and health support (so victims that spoke up don't fall into a void) and regular police work (so that the perpetrator gets busted).

I guess child abuse on the internet is a popular topic with policy makers because "protecting children" is an easy way to score points in public and "on the internet" hides the fact that this abuse happens somewhere - and closer to any single person than they may be comfortable with.
"internet" became a code word for "somewhere else".

That's a great platform to win an election.

Now, pick any company with > 10000 employees. Just by running the numbers it likely employs a child abuser. You work for such a company? It's likely that one of your coworkers, maybe even somebody you deal with every day, is a child abuser.

That's not a great platform to win an election.
MPAA Wants to Kill Domain Name Privacy, for Some
All the "great" people I can think of have something in common: they believed in something, acted on it, and happened to become great while doing so. Wanting to be great and then looking for a field to be great in seems to me to be putting the cart in front of the horse.

So, question for you: what do you believe in? What do you care enough about to devote your life to it?
This is exactly what I do.

>Use a local PyPi rather than a per-server cache

I stil prefer a per-server cache. A local pypi is another piece of infrastructure you need to keep alive. You don't have to worry about the uptime of an rsync playbook.
I love it, however I have some suggestions:

1. Please, please use the metric system units or at least add both the imperial and the metric when you explain something. For example the Earth's rotation is in mph...you can at least say: 1000mph (1,674.4km/h).

2. On the Sun's chapter, you drew it yellow. Well, this is a common misconception, however the Sun is essentially all colors mixed together, which appear to our eyes as white.

3. There are too many links that forces the reader to constantly deviate from what he reads, thus killing the experience. You can come up with something similar to Apple's "look up" functionality [1]

4. No love for Pluto :(

[1]http://i.imgur.com/CWgjdCU.png
You can map them into higher level constructs that basically are a kind of reference counting on top of GC.

For example, multiple threads sharing a socket connection. Just create a barrier and have a cleanup thread closing the socket when everyone joins.

Similar patterns can be applied to other resources.

Ownership transfer is usually not an issue in GC enabled languages in terms of data structures, specially if every thread keeps the OS resources locally for itself.
This isn't a new idea. David Keys wrote a book "Catastrophe" 15 years ago dealing with the same subject, although in his case he picked a different volcano as the probable cause.

He also looked at the effects on a world-wide basis, not just in Europe.

To quote from the book's marketing literature: "In AD 536, a volcanic eruption meant our planet was enveloped by a cloak of lethal dust which changed the climate for decades. The sun's rays grew dim and total darkness reigned for days. It was a catastrophe of unparalleled proportions."

http://www.amazon.co.uk/Catastrophe-Investigation-Origins-Mo...
Wow! Thanks for taking the time to provide so much valuable insight - I really appreciate it. I'm going to give it some more thought (especially around the psychological aspect of positioning and how we convey the message and price).
> Grenade ownership is fully legal in many or most US states

Do you have a source to back that up? I think you can own a grenade launcher, but I'm quite certain that grenades are very illegal... possibly excepting smoke grenades.
It's certainly not a bad thing, why do you think it might be?
Hard Drive Inspector Professional Crack Free Download
> In particular, C++ (and Rust, etc.) stresses RAII (Resource Acquisition Is Initialization)

But there is no reason that the RAII pattern couldn't be completely orthogonal to memory management.
I remember playing around with overclocking my old Pentium 4 and how it would boot fine into Windows, but then you'd run Prime95 on it and the benchmark would start failing because the FPU was returning incorrect results.
Which is what he said.. they thought this over.
While you're right in theory, it's typically much less feasible to avoid heap allocations in garbage-collected languages. Systems programmers typically manually promote heap allocations to stack allocations in ways that common escape analysis algorithms cannot prove safe (for example, those involving higher order functions).
And that is one country out of ~200.
Thanks for the suggestion. I bought the book you suggested and will give it a read this weekend.

We think we have a clear idea of who the buyer is, but it's been tough trying to actually get our message/brand in front of them as the conventional ways I mentioned previously only get us attention from other people like us.
Without which TextSecure does not work.
Revolutionary new platform for Entrepreneurs and VC's
Press alt twice and type in the title for a partial match of the window title. That is all I ask for.
Yes it will,if you do 5 grams a day - which is a ridiculous amount. If you are doing that much, you might in fact be a horse.

https://en.wikipedia.org/wiki/Ketamine#Urinary_tract_effects
>They're solid state devices, after all, and the only moving parts are electrons.

SSDs are solid state (duh) as well, and yet they degrade over time.
I've haven't gotten around to measuring it yet, but back of the envelope calculation is "between 100ms-200ms" delay from input event sent to h264 frame rendered. This is assuming virtually no network delay, so you'd be doing well with ~300ms end-to-end latency from your browser currently.

This would not work for an FPS, especially when you look at the variance in latency. There are lots of ways to shave milliseconds and stabilize latency though, so that statement is definitely not future-proof.

Yes, Broadway.js ;) Highly recommend though the documentation can be a bit "terse"
My initial thought as an author of "traditional" package manager http://gonuts.io was like your. But then I understand that there is no dependency conflicts. Libraries A and B vendor library C, maybe even different versions C1 and C2 of it. Then your project uses A and B and knows nothing about C. As along as libraries don't do anything stupid like modifying http.DefaultClient, everything is fine.
That seems independent of tracing GC versus manual memory management, though, doesn't it? jemalloc/tcmalloc could stop all threads and flush pools in bulk as well if it decided that it was faster to do so. (From looking at the code, jemalloc doesn't, but it could.)

More broadly, if batched deallocation is indeed faster, you can get that behavior in a manually memory-managed scenario. You aren't forced into prompt reclamation. It's just that prompt reclamation is usually faster for cache reasons and improves memory consumption, so malloc implementations take advantage of the opportunity.
Show HN: Recruiteze – Simple, Modern Recruitment Software for Small Businesses
What's interesting is that you don't even have to be the creator of said project to profit off it. There are companies that provide commercial support and consulting for Tomcat and Postgresql, but they didn't create them. There are a ton of other examples in enterprise grade FOSS.
Encryption on the transport != end-to-end encryption if you consider the users as the ends. The encryption might very well just be from your device to WhatsApp.
Google Glass never died

Yeah, it should born first.
> So the "writer" is performing worst then a summary bot.

That's a pretty good business opportunity for TC then. Fire the "writers", replace by bots, nobody notices any difference (or actually an IMPROVEMENT!).
Once you start applying workshop bonuses to farmers and use the aqueducts you;ll be able to sustain a huge number of kittens with a handful of kittens.
I disagree. The experimental vendoring mechanism introduced in Go 1.5 is simple but powerful. In fact, it's very similar to what Node.js does with the nested node_modules directories. The Go team has provided the fundamental mechanism. Now, the community can provide the tooling to manage the packages and the related metadata (like npm in Node.js or pip in Python, but hopefully without the warts…).
I tend to deduce and eventually blame either gravity or gremlins. I was never wrong.
You're right, that was inelegantly written and kinda conflates two different things. Gates are spread around for fixing design errors as you describe. There is also often redundant logic and memory built in to allow fixing individual chips though.

Here's a quick presentation I found on laser repairs: http://www.ee.ncu.edu.tw/~jfli/memtest/lecture/ch07.pdf
Horribly addictive. You have been warned.
Next time take a camera, perhaps?
It can be a bad thing if all programmers assume that the caching works, and it doesn't. That's where the bit in the article mentions strings that produce a hash code of zero. Zero is used as a sentinel for "hash code not yet calculated", so for those particular strings the code is recalculated every single time.
Cashing in on Kids
I don't think he refers to the caching being a bad thing, but that it probably does not affect performance that much, since most Strings are likely to be small (and the number of times hashcode is called is also likely to be small).

There's also a catch : if the hashcode of the string is 0, the hashcode will be recalculated every time (since the code assumes it has not been cached yet).
> how much money they saved using your pricing model

Ah, that's a brilliant idea!

> If they are looking for a 1-3 page website, the price is going to be an immediate turnoff

That might actually explain what could be happening at the moment. Potential customers are scanning the content and not noticing the headline explaining that its for mobile services.

Our designer is taking all this feedback and making changes, we'll probably roll it out early next week.

Thanks again for your input, much appreciated!
It seems to me that there is alot of muddled explanation going on here, if not muddled thinking.

The goal fine grained parallelism python (fgpp) must be to improve the speed of code for which fat parallelism (user conconcted error prone 'multi-threading' or message passing) doesn't gain much, and for which calling out to an impl in another language or specialised library has overhead or doesn't make sense.

IMHO, the most important part of fgpp must be that it is easily reasoned about, both by compiler/runtime and programmers, so as to maximise scope for transformations and user-driven design decisions (as opposed to VOODOO). It would ideally avoid the costs of premature optimisation, or the often inefficient flattening required for vectorisation.

So I think any propsal should be addressing these questions, with appropriate benchmarks too, before it can be considered seriously.
AMD was particularly fond of selling dual and even tripple core CPUs that were quad core chips with some cores disabled. And people where unclocking these cores for profit, because they speculated that AMD disables core for the whole batch even if it was a single unit from it that failed the test, so there could be possibly plenty of good cores disabled along the way.
You can theoretically reimplement Git Core by only referencing the documentation, which, according to some sources, does not "infect" the new code with GPL.
Agreed on the rollback part.

It is easy to pick the silliness of the kernel reason, but Docker is moving fast right now. They are still getting the basic building blocks in place, and the Docker in two years will look nothing like today's.

We use Docker quite a bit today, but it's immature and it shows. With Composer I feel the basic functionality is finally in place it needs time to mature.

So I think it's quite wise to wait. You don't need to chase every new technology. If you have a product to ship, focus on that instead and use whatever tools are proven to work.
Response from IRC:

http://irclog.whitequark.org/neo900/2015-07-10
The only negative was a small memory overhead.
I'm in my late thirties and was among the first generation of daily cell phone owners once the bulky bricks were replaced by flip phones. I don't recall the same reactions that you do.

There are still a lot of people who don't own or regularly use a cell phone and others who prefer not to be reachable all the time, that hasn't really changed.

Glass's popularity in the consumer market at some point in the possible future will hinge on whatever conversation a future generation has about the expectations of privacy in public spaces. Until that conversation happens, Glass isn't really viable as a consumer product.
His name is Niklaus Wirth, for anyone who might not have known...
It appears to be open source and you can download and run it on your own hardware: https://tyk.io/v1.7/download/
What do wines, code, sending SMS over API‬ to multi-destinations have in common?
Critical Magento security patch for July 2015
You'll have to apply to find out. ;)
Show HN: Filefly – The fastest way to share files from your iOS device