skysight-inc/HackerNews huggingface dataset:
With respect to garbage collection only and ignoring things like reliable debugging support, the primary thing it does is compaction.

If your memory manager does not compact the heap (i.e. never moves anything), then this implies a couple of things:

1. You can run out of memory whilst still technically having enough bytes available for a requested allocation, if those bytes are not contiguous. Most allocators bucket allocations by size to try and avoid the worst of this, but ultimately if you don't move things around it can always bite you.

2. The allocator has to go find a space for something when you request space. As the heap gets more and more fragmented this can slow down. If your collector is able to move objects then you can do things generationally which means allocation is effectively free (just bump a pointer).

In the JVM world there are two state of the art collectors, the open source G1 and Azul's commercial C4 collector (C4 == continuous compacting concurrent collector). Both can compact the heap concurrently. It is considered an important feature for reliability because otherwise big programs can get into a state where they can't stay up forever because eventually their heap gets so fragmented that they have to restart. Note that not all programs suffer from this. It depends a lot on how a program uses memory, the types of allocations they do, their predictability, etc. But if your program does start to suffer from heap fragmentation then oh boy, is it ever painful to fix.

The Go team have made a collector that does not move things. This means it can superficially look very good compared to other runtimes, but it's comparing apples to oranges: the collectors aren't doing the same amount of work.

The two JVM collectors have a few other tricks up their sleeves. G1 can deduplicate strings on the heap. If you have a string like "GET" or "index.html" 1000 times in your heap, G1 can rewrite the pointers so there's only a single copy instead. C4's stand-out feature is that your app doesn't pause for GC ever, all collection is done whilst the app is running, and Azul's custom JVM is tuned to keep all other pause times absolutely minimal as well. However IIRC it needs some kernel patches in order to do this, due to the unique stresses it places on the Linux VMM subsystem.
I'll never understand why people hate on Java. Writing in Java is nice and easy, debugging is easy and getting support online is easy.
Location: Europe (Turkey)

Remote: Yes

Willing to relocate: Yes

Technologies: JavaScript/Node.js, HTML5/CSS, Python, C#, MySQL/MongoDB, CI

Résumé/CV: https://dogancelik.com/cv.html

Github: https://github.com/dogancelik

Email: hn (at) dogancelik (dot) com

Hello, I'm Doğan. I have more than 5 years of experience in web and software development. I prefer front-end work. I have experience in Express.js, socket.io, Angular, MongoDB. I'm familiar with build tools and preprocessors like Gulp, Jade, Sass and Browserify.
Lays off thousands of workers... still doesn't profit.
> I can't fathom how football still exists today as a popular sport

Your first three points make sense, but don't lead to this conclusion at all. People are not going to rationally say "football leads to traffic so I'm not going to watch it anymore." Football is entertaining, which is why it has an audience. Whether or not the negatives you outlined above are funded by the gov't is an entirely different matter.
Thanks. We thought this and are trying to work out what needs changing. Will add some details.
> When I see a founder sell his business, all I ever think is (as I'm sure most do), what a selfish asshole.

You must be new here. Some useful info:

http://ycombinator.com

https://news.ycombinator.com/newsguidelines.html
You're not going to get clean out-of-order processing semantics with any mode of Spark transformations. If you actually take the time to read the article, there's a section discussing the Java/Scala angle. The difference in code size is really secondary (though it is a difference). The difficulty in maintaining and evolving your pipeline over time using Spark is the main point, given the way important concepts become conflated with their API (any version of it). This all comes across much more clearly for those that actually take the time to read the words.
Are you saying this because manufacturers, being gigantic unsympathetic companies, would be sued for much greater damages than at-fault drivers get hit with today? Otherwise it makes no sense, TCO will come out the same whether drivers or manufacturers are liable.
Yah, because we don't need plastics or synthetics. We don't need lubricants for electric motors. We don't need coolant, we don't need lightweight composites and we don't need solvents.

Where do you think all this stuff comes from?
Guess the Correlation: a game of statistics
Do you mind sharing your site?
Anyone got a good tl;dr version?
Seriously, how many times will this be posted?!
Well arguably in every NASA case, there were private contractors proposing astronomical (pun intended) chances of catastrophic errors, whereas internal NASA estimates were always expecting far, far greater chance of such error. So there was always this go, go, go mentality.

So you can ding NASA for bad choices, which is fair, but there's a private business component in all of that too. It's a public-private venture, space.
They have rules to prevent this. See IRC Section 956. In essence, the use of a foreign sub to acquire a US company would be treated as a deemed dividend back to Apple.
It will now only be a matter of time until someone trains a deep neural network to beat the game.
I loved Dropbox for its simplicity, the fact that it has MIT in its genes, it not being Microsoft or Google, and for Carousel.

But my dropbox was super slow in Japan, MS Office products keep spawning conflicting copies, Photoshop randomly pauses batch processing because of sync file locking, and they are shutting down Carousel.

So I am moving to Google Drive. All the frustrations above are not unique to me. Dropbox even has a Japanese web site. But this is what destroys consumer confidence. There were trivial complaints on their support site regarding speed issues and Carousel issues with pages of responses. It is the loyal customers that bother to post, yet the impression everyone is getting is seriously, WTF are they doing?

You can't have it known that you are healthily funded, have hundreds of engineers, not free, and NOT care.
Didn't he say 'NYC' ?
There's a lot of strategy between plays. Because the action isn't continuous it has a different flavor from a continuously played game like the other football. It's sort of a hybrid between a real-time game and a turn-based game, which is cool. I think it would be much more interesting if there were more time on the field, but i'm sure the NFL and their advertising partners love all that time that can be filled up with ads.

I dislike the game because the players get horribly injured, either immediately, or decades later. The NFL is a company that makes money by encouraging degenerative brain disease in its employees.
The G1 collector has a single knob that is supposed to be a master knob: you pick your pause time goal. Lower means shorter pauses but overall more CPU time spent on collection. Higher means longer pauses but less time spent on collection and thus more CPU time spent on your app. Batch job? Give it a high goal. Latency sensitive game or server? Give it a low goal.

There are many other flags too, and you can tune them if you want to squeeze more performance out of your system, but you don't have to use them if you don't want to.
> It can't just be 2X or even 10X safer than humans if the manufacturer is liable for the accident. That would EXPLODE the cost of these cars and bankrupt companies -- even if just a small fraction of today's fatal accidents due to driver error became Google's liability.

Right now, the insurance company is liable for the accident followed by the consumer. It'll just shift the insurance market towards manufacturers buying it [or likely self-insuring] and the cost of insuring a car will be baked into the price instead of bought aftermarket.
There is no explosion. The cost of collisions today is reflected in the car insurance, so about $100/mo. If the manufacturer were to absorb this liability at current incident rates, it would make cars about 30% more expensive (assuming $300/mo loan payments). If Google reduces the (incidence * impact) of collision by 10x, the cost will come down to $10/mo, or about 3% of the total car cost.

And in return for the modest price increase you get a self-driving car!
Trbble: Discover new music by listening to a song’s best part first
Consider, briefly, that the relevant question is what it meant to the OP, and clearly for her it had that impact. Having been through many of the same experiences (I, too, was an early Parse engineer, though I left about a year after the acquisition), I can tell you those feelings are real, and that it's definitely possible to form that kind of attachment to your work in well under 5 years.
No problem! Great motivation behind building the extension (not coincidentally, it's the same reason I initially used the LinkedIn setting!), and a cool project. :)
This is for command blocks right?
> ... Updating our tooling to automatically open issues for the team when new firmware updates are available will force us to review the changelogs against our environment.

That's an awesome idea. I wish all companies published the firmware releases in simple rss feeds, so everyone could easily integrate them with their trackers.

(If someone's bored, that may be a nice service actually ;) )
You're absolutely right.

We should collectively be using incidents like this as an opportunity to learn, much like the GitHub team does. Our entire industry is held back by the lack of knowledge sharing when it comes to problem response and the fact that so many companies are terrified of being transparent in the face of failure.

This is very well written retrospective that gives us a glimpse into the internal review that they conducted. Imagine how much we could collectively learn if everyone was fearless about sharing.
It's an interesting problem.

We don't trust big corporations.

Hosting ourselves is very expensive.

How could this be organized better? 10 people hosting a small server infrastructure together? Can you trust them?

I believe that sandstorm is making the move very much into the right direction. Self hosting will become cheaper and more convenient. In a few years you can drop some little server box off at two friends places and colocate for them and each one will have their own private cluster. With the storage encrypted, of course.

Setting this up will just require doing the handshake between the servers and between the servers and clients and done.
That seems like a mistake. One of these groups, probably the one that uses security holes, will get the upper hand, and the other function will be relegated to the dustbin.

Bruce Schneier has called for the current NSA to be broken up into two agencies, so that no conflicts of interest exist, and both functions actually get done.
Cruelty aside, does anyone else feel that 'proper' food has become a luxury item?

They constantly replace things like cheese, beef, bread and so on with worse and worse imitations until people forget what they even used to be like.

Related joke:

Q: Do you know what they used to call organic grass fed beef?
A: Beef.
> Given the dependency in question is Redis, such a solution is probably exasperated by the fact Redis hasn't really had a decent HA solution.

You can replicate to read-only instances in a secondary DC and failover. It hurts but it is better than an outage imo.
GitHub: A fast and ultra-lightweight chat server library written in Go
I am absolutely venting emotionally, I thought that much was clear. :) But I heard a variant of this in dozens or hundreds of meetings, generally when a project was getting shut down or canned or reorg'd, so it's not true to say that it's not true.

It's not even a bad slogan. Company priorities should come before territorial interests. This is why it's important to work in a place that shares your values at a high level.
Of course it was. I don't know if everybody goes silent after a few days, It's the first outage I'm aware of, but some people at university made see the hypocrisy of using GitHub for open source projects and I feel that if there is a community strong enough to make some impact on GitHub that could be hackernews. Maybe I'm wrong.
Donald Rumsfeld as a Product Manager
JavaScript and Immutability - How fast is fast enough?
> It can't just be 2X or even 10X safer than humans if the manufacturer is liable for the accident. That would EXPLODE the cost of these cars and bankrupt companies -- even if just a small fraction of today's fatal accidents due to driver error became Google's liability.

If the owner/operator bears no liability and all liability is on the manufacturer, it transfers the liability cost onto the manufacturer, but even if it is as safe (not 2× or 10× as safe), that just means the manufacturer rolls the cost to (self-, likely) insure for that liability into the purchase price (but the purchaser doesn't need to get their own insurance, so the total cost of operation to the purchaser is unaffected.)

And, of course, if a company like Google is both the manufacturer and the owner/operator (e.g., using the vehicles in an Uber-like service tied in with Google Maps and Google Now, or using them for Google Express delivery vehicles with smaller robots onboard to deliver packages to the door, or using them for Google Street View camera vehicles, etc.), operator vs. manufacturer liability makes no difference.
You know what else is boring? Comments of the form "I don't understand something, and my ignorance should be compelling"
We're really keen on getting any feedback that you might have, good or bad - we're keen to fix any bugs that get found and improve the app as much as possible.
This completely describes our experience. Thank you.
I still see a big market for a more powerful Parse. I think the whole "infrastructure as a service" is now commodity and wouldn't be a good competitive advantage, but the software orchestrating all the sys admin stuff on top of any IoT would be of tremendous value. The perfect solution would connect all the great open-source building blocks into one "Good Enough Way". I would totally pay for that, but I don't see how that service would stop copycats. In a way, this is what Meteor is trying to get to. Embrace open-source but deal and charge for the hard parts that nobody else is solving.

Ideally, there would be a generalized way to build scalable applications. Similarly to how mostly everyone got behind React, it would be great to have mostly everyone behind such a project. I'm sure it will happen, but I'm not sure when it will. Right now there are hundreds of new libraries in the JS ecosystem, but there are some clear converging trends. I think new languages and libraries will always exist and be welcome, but it'd be great to have one standard way based on years of experience. Similar to how other industries stabilized (i.e. building bridge). I feel we'll be able to move so much faster when we get to that point. Now, every programmer is reinventing the wheel and keep doing the same mistakes that other programmers elsewhere are doing.
There's no way to accuse someone of lying "with absolutely sincere respect", but at any rate: I've actually answered the question you're pressing me on, clearly, elsewhere on the thread --- in fact, you literally replied to a comment where I did that --- and am no longer interested in this conversation.
Super. My firefox 43.0.4 gobbled up all the CPU it could but it was a rare case where I would gladly trade CPU cycles for the pleasure of scrolling through examples.
Human-Computer Interaction for Mobile Development
Cdak by Quite – How? (2011)
Sad to hear the end of Parse :( so I put together a collection of its evolution over time:
http://www.startuptimelines.org/startup-timelines/Parse/

Wishing the team well in any future endeavours
Popcorn Time in the Browser (Torrents Time)
Main dev on the project here (I work for rea-group.com who run www.realestate.com.au, but they've given me a years secondment to the project).

Back in 2013 a team at our hackday implemented the precursor to this app, and the leadership team were super impressed.

It's been amazing working so closely with the sector (we meet/do user testing with representatives from lots of organisations).

This is my first project with react / es7, but I've built a few rich client webapps before. React is definitely the best developer experience I've had with client-side frameworks.
1) Loans are priced based on their risk! Saying student loans are actually less risky than lower priced loans IS saying that they are overpriced.

2) You are correct that most student loans are financed by government programs. That allows them to undercut even the viciously competing private market because the government isn't trying to make a profit. So that makes the loans even cheaper which makes your assertion that they're overpriced more, not less, ridiculous.
"Great" is pushing it a bit. The JVM will not do inter-procedural escape analysis unless the called method is inlined into the callee and so the compiler can treat it as a single method for optimisation purposes. So forget about stack allocating an object high up the call stack even if it's only used lower down and could theoretically have been done so.

That said, JVMs do not actually stack allocate anything. They do a smarter optimisation called scalar replacement. The object is effectively decomposed into local variables that are then subject to further optimisation, for instance, completely deleting a field that isn't used.

Value types will be added to the JVM eventually in the Valhalla project. Go fans may note here that Go has value types, but this is a dodge - the bulk of the work being done so far in Valhalla is a major upgrade of the support for generics, because the Java (and .NET) teams believe that value types without generic specialisation is a fairly useless feature. If they didn't do that you could have MyValueType[] as an array, but not a List<MyValueType> or Map<String, MyValueType> which would make it fairly useless. Go gets around this problem by simply not letting users define their own generic data structures and baking a few simple ones into the language itself. This is hardly a solution.
Shifter Lab 3D Prints Elon Musk’s Hyperloop
I'm from St. Louis. The Cardinals also bilked > $500M towards their new stadium despite being the most profitable MLB team.

The mayor went around telling everyone it was a good idea. Of course the touted economic benefits are usually an order of magnitude above reality.

IMO basically capitalized on a huge inferiority complex.
To be fair, that's a non-insignificant amount of HN comments. People should come here with far more curiosity and far less arrogance than they do.
> Right now, the insurance company is liable for the accident followed by the consumer.

Actually, the driver is liable, but in most states (in order to be legally permitted to drive on public roads) must either have purchased insurance to cover some minimum amount of that liability or have posted a liability bond. But the insurer's obligation to pay is triggered by the driver's liability, not ahead of the driver's liability.
> * I could really care less*

do you mean "couldn't care less"?
It's best understood as a turn-based strategy game with real-time elements during and between moves.
GCS can be used instead of HDFS, Dataproc is shipped with GCS connector installed (https://github.com/GoogleCloudPlatform/bigdata-interop)
That doesn't explain the popularity, strategy is invisible to the viewer. Chess is not a popular spectator sport.
Look at insurance premiums. Premiums go up after an accident because it is more likely that you are a poor driver and likely to have another accident.
You are assuming that, if liability in the US was a critical question, Google would not launch its project in a country with most hospitable weather and more compatible liability rules and from there, lobby for more reasonable principles in the US.
Today I learned! Thank you for sharing!
It's the preponderance of the multiple factors (as cited in the article), along with the immediacy of the flight and the USG's well-documented predilection for pulling similar shenanigans for the sake of far lesser targets, that are sufficient to raise reasonable suspicion.

And it's the immediate dispatch of the plane which strongly suggests that the U.S. wasn't going to wait to go through normal judicial channels to pick up their target.
Very interesting novel...brilliant stream-of-consciousness style that reminded me much of Joyce...

While reading it I sorted the tech he described in his own invented terms and compared them to what's available now...
there are many parallels...

I recommend reading it...

If you need priming listen to his 2013 commencement speech--This is Water--delivered at Kenyon College...

https://www.youtube.com/watch?v=8CrOL-ydFMI
Of course I'd learn from each fender-bender, and I'm clearly a better driver than average anyways! These fancy autonomous vehicles are too dangerous for my family.
I don't know enough about server infrastructure to comment on whether or not Github was adequately prepared or reacted appropriately to fix the problem.

But wow it is refreshing to hear a company take full responsibility and own up to a mistake/failure and apologize for it.

Like people, all companies will make mistakes and have momentary problems. It's normal. So own up to it and learn how to avoid the mistake in the future.
Minor crashes are even more frequent than the article estimates. Thus, the real human accident rate is even higher. Probably between 1 in every 24000 and 87000 miles.

The VTI driving study[1] equipped 100 cars with sensors and was therefore able to measure all crashes experienced. It directly measured 1 crash per 24000 miles. If we extrapolate based on the 17.4% police report rate, that suggests 1 per 87000 miles.

[1]http://www.nhtsa.gov/DOT/NHTSA/NRD/Multimedia/PDFs/Crash%20A...
Next time you pull up to a stop light, look to the left and then right. I'm willing to be the drivers on the left and or right are looking at their phone.

It's getting worse... the phone, blue tooth, the dashboard computer, traffic, impatient drivers. etc...

I for one can't wait these self driving cars, they have got to better than distracted drivers we have now.
I post comments like that to be educated. Some have already offered explanations, so I'm happy to get your downvote if it means learning something.
link [1] is down, in fact several links at senate.gov are down. I don't want to say your claim is disingenuous because you did throw a caveat in there, however Rand Paul did not support handing the internet off to the FCC to regulate if we want to call that defensible. He did however publicly rail against the freedom act and tried to fillibuster it though ultimately that failed.
Do any cities own their own teams? I was thinking about this the other day, and as someone who doesn't really follow sports I think I'd actually be more supportive of things like stadium building if the city were involved more heavily—namely, if the city owned the team(s), or at least a controlling share.

I'd also be way more likely to care about and cheer for "our" team if they couldn't just pull up stakes and move to another city if we don't bribe them enough to keep them. Fan loyalty to commercial teams that don't have any real ties to the home city (they don't even have to give up their name if they leave!) strikes me as bizarre.
Yeah, child labor laws were instituted for a reason: business will exploit anyone they are permitted to exploit. There's a long history of both labor laws and unions, trying to balance out the blood from a turnip mentality a business will try to get away with, again if permitted.
http://webcache.googleusercontent.com/search?q=cache:9UNd6-l...

Cache. Its down for me.