skysight-inc/HackerNews huggingface dataset:
It seems to be not OCaml:

First real success was Meteor line 14
driverless metro in Paris: Over 110 000 lines of B models were written, generating 86 000 lines of
Ada. No bugs were detected after the proofs, neither at the functional validation, at the integration
validation, at on-site test, nor since the metro lines operate (October 1998). The safety-critical
software is still in version 1.0 in year 2007, without any bug detected so far.

From: http://rodin.cs.ncl.ac.uk/Publications/fm_sc_rs_v2.pdf
Lost US$5M from sending email to the wrong person
Why on earth would something like this have to involve the NSA? Celebrity cellphones/voice mail/email/instant messaging/whatever have been hacked in the past by 'regular' jerks, no need to involve the authorities in these.
The runtime is not regular Go code, it's tricky Go code that doesn't have access to the standard library, full of pointer manipulations using unsafe, and with no heap-escaped variables. It also has to deal the fact that the C compiler didn't produce stack maps with type information (and even if it did, it would not have been that useful since it abused uintptr's), so Go code must be really careful about when the stacks are allowed to be moved and how pointers must get proper types.

In short, the Go code in the runtime is about at the same level at C code.

Don't forget that this is a straight 1-to-1 translation; this is not the time to introduce new bugs. After it's all done, the runtime code can be refactored and it might become cleaner and smaller.

PS: there are no go errors, and hence no if err != nil statements in the runtime.
anyone has confirmed that the leak is from icloud and thats the way they did it?
Does anyone else prefer to entirely avoid signing up for an Apple ID?

I absolutely refuse to do so, and therefore use only software that doesn't require it. I suspect I'm not entirely alone out here on the sidelines...
Correct, but even software that doesn't cause deaths on failure ends up causing real losses (often invisible).

Consider every time Word crashes and work is lost. There are billions of Word users out there, mostly being paid to use it. How much does that cost over the course of a year?

And the accumulated frustration from unreliable software, causing loss of productivity, resistance to change, stress... How much does that cost?
Well, Mosh still uses OpenSSH for the initial authentication, and during the rest of the connection, all the security is handled by a single layer (AES-OCB, using the reference implementation), which is not specific to Mosh.

That said, it has never been audited.
This is different from any university how?
are those links becoming invalidated after 3month and auto reposted or something ?
This URL must have shown up like 3 times on the front page in the past year alone
A feature history of the modern web platform
one issue ive with mosh over time is that it doesnt timeout properly every time (it does most of the time after a long period). this keeps tmux/screen sessions attached "forever" which can be an issue with some programs that detect if you're detached to send notifications for example
It should be noted that the attack has just been patched by Apple, so no longer works....
A series on Cassandra: Part 2: Indexes and keys
What? Java and Python are great portable languages, and they definitely do not suck on Mac or Linux. The only languages that does not suck on Windows (i'm biased, I really hate development on Windows) is the .NET family of languages.
The Advanced Cave Culling Algorithm – making Minecraft faster
If the water line can be made to change when scaling the boat up, it should be trivial to make a pathological object that will sink when scaled. Just make the shape of a box without a lid, weighted so that the water line is just at the top of the walls. If scaling the shape raises the waterline, then water will flow into the box and it will sink. I still can't intuitively convince myself that the waterline would shift when the model scales.
Well, time to learn a new thingy I guess.

I've used YUI with tons of pleasure over the last 3 years, and am sad to see it go away.

Here's to another 2 years of heavy influx prototyping, refactoring and writing everything over again (I'm an enterprise developer).
Honestly, I just want to see them side by side. We can then debate our subjective interpretations vs. debating pure biases.
> Psychologists very rarely replicate prior work

This is simply not the case - no matter what Feynman said. Just skim e.g. through the Journal of Personality and Social Psychology. Like in any other science you attract attention when you refute a well-known experiment.
Deadly Algorithms
Seems oddly backwards to me, but I'm sure I'm not the only one. If I've bought and am paying for a phone that costs a significant fraction of my computer, it seems like a waste not to use it for that purpose. You can make the argument that disconnecting to a point, or for a period of time, is a good thing, but intentionally crippling your hardware because you can't resist the temptation of having it there seems like it would be better solved by forming better habits in the first place.

It just seems like it would be on par with buying a brand new computer to get your writing done, then installing DOS because the web browser was just too alluring.

All that said, I ended up taking this to the opposite extreme: I've set up my phone to be cross-linked into as many work-related systems as possible, so that I can take better advantage of those little "in-between" moments during my work days. Build's compiling? Get an alert when it's done. Waiting for a coworker to get out of a meeting? Get an alert when they ping your name in IRC/Skype/GChat. Not having to sit in front of my computer waiting for asynchronous blockers to resolve means I can retreat to the porch, or the living room, or the park up the street, without having to worry about coming back to find something's on fire. Additional apps allow for limited on-the-go debugging, interfacing with systems and the like, so that I can continue being away from my computer if the situation isn't severe enough to require my actual physical presence at a keyboard and larger screen.
By 'something like this' I meant pretty much what you just said: Would you do it the same way (your own everything) if you needed a much smaller system, or would you go with something like FreeNAS, like you suggested? I am confident I c an get it working good either way, but I would rather not spend half my days having to tweak and worry about stuff working correctly. I understand that it will need maintenance and monitoring of course, but I would much rather be more of a end-user having a working system than being the sysadmin that has to fix it all the time. :-)

Thanks for the link, I will take a look there.
Linus told a story about a guy, that wrote something for the kernel and
Linus thought in the first place that it was more or less bullshit, but
didn't told it directly to the guy, so when the guy was finished and
wanted to get his stuff merged, Linus had to tell him that he will never
merge this.

I don't know how mucher later, but this guy killed himself afterwards.
Linus told that he doesn't feel guilty about this or thinks that he was
the main cause for the killing, but well, I don't think that such an
experience has no effect on your behaviour, but I can't tell if Linus'
behaviour was different before this event.

I think that Linus told this story in the talk where he showed nvidia the finger.
It's not necessarily a competition thing though, is it. Intermediaries sit on top of them, rather than competing. And they rise in many industries because they can provide value that suppliers can't. In the travel industry, consumers want (for example) the cheapest rates on elements of holidays, hotels etc. So price comparison sites happened. Suppliers can't do anything about this in terms of competition, because the intermediary has a value proposition that the suppliers can't offer which the market wants, and the suppliers want the sales anyway.

With ride sharing, consumers presumably want the cheapest, quickest, cleanest fleet. I doubt fist-bumps really factor in to the experience. Suppliers can improve their fleet, improve their drivers and so on, using their own perspective as a guide. Aggregators can offer the cheapest, quickest, cleanest fleets to the market without having the limited perspective. They get a better view of the market through this too, potentially adding value to the whole supply chain.

Incumbents don't have to allow their own infrastructure to be "used against them", but they will, because this is what the market wants.
No pointers.

Range limited types, e.g.

Type Day = (0..7);

Days = (monday,tuesday,wednesday,thursday,friday,
saturday,sunday);
This article is quite ignorant.

ZFS uses integrated software RAID (in the zpool layer) for technical reasons, not merely to "shift administration into the zfs command set". Resilvering, checksumming, scrubs are all a unified concept that are file aware, not merely block aware as nearly every other RAID. The implications of this are massive and if you don't understand, please don't write an article on file systems.

For various reasons, the snapshots and volume management are more usable due to the integrated design and CoW, and also as pillars for ZFS send/receive.

The "write hole" piece is bullshit. ZFS is an atomic file system. It has no vulnerability to a write hole.

The "file system check" piece is bullshit. Again, ZFS is an atomic file system. The ZIL is played back on a crash to catch up sync writes. A scrub is not necessary after a hard crash.

Quite frankly, for any modern RAID you probably should be using ZFS unless you are a skilled systems engineer and are balancing some kind of trade off (stacking on higher level FS like gluster/ceph, fail in place, object storage, etc). You should even use ZFS on single drive systems for checksumming and CoW, and the new possibilities for system management with concepts like boot environments that let you roll back failed upgrades.

Hardware RAID controller quality isn't spectacular, and the author clearly has not looked at the drivers to dish out such bad advice. You want FOSS kernel programmers handling as much of your data integrity as possible, not corporate firmware and driver developers that cycle entirely every 2 years (LSI/Avago). And there's effectively one vendor left, LSI/Avago, that makes the RAID controllers used in the enterprise.

ZFS is production grade on Linux. Btrfs will be ready in 2 years, said everyone since it's inception and every 2 years thereafter. It's a pretty risky option right now, but when it's ready it delivers the same features the author tries bizarrely to dismiss in his article. ZFS is the best and safest route for RAID storage in 2014 and will remain such for at least "2 years".
>Latency often changes the order of keystrokes.

I've never had this experience! And I've used mosh for some time extensively on all sorts of connections ranging from abysmal to horrible. Maybe you used an older version?
How Yoga Changes Your Body, Starting the Day You Begin (INFOGRAPHIC)
I have a feeling this story is far, far from being over.

And I'm very curious as to how the fuck this happens.

I haven't seen many theories in general, let alone theories with much evidence behind them about how this could have happened. Other than iCloud! No dropbox! No NSA!

So while I wait for more technical minds to weigh in, I figured I'd take a stab at an alternate theory for people to ponder (or hopefully more likely tear apart!)

tl;dr

Gaining covert access locally via a potential buffet of attack vectors. Feels like this article, but voyeur not espionage (or necessarily China/state-based obviously)
http://www.nytimes.com/2012/02/11/technology/electronic-secu...

Theory:

- Original hacker is one w/ privileged network access, &/or proximity to sniff, &/or compromise device(s) physically at a place frequented by celebs over a long period of time(years).

- Hotels, spas, coffee houses, studio lots, awards, etc etc.

- Potential for many attack vectors to match any given skill set. From MITM, to malware, to phishing, to gathering PII for social eng to compromised charging stations.

- And gives a window of time to allow for fast data transfer pillaging via LAN.

- Also gives a window where on same network, at same time and place pry helps to avoid tripping some suspicious access detection alarms.

- OG hacker is prob up to lots of nefarious stuff and someone else popped their personal stash.

--
What lead me there and away from a single platform exploit, a la iCloud?

I tried making sense of what was known and a few assumptions.

- If it was a platform exploit, finding even 20 of these girls' actual login emails from which to locate their accounts on a service is a massive undertaking – unless you have some kind of privileged position to harvest them (hotel desk, gyms, award ceremonies, etc etc)
-- I feel like the probability of all these girls having passed through same places – like hotels, spas, sundance, soho house, awards, festivals, etc etc – over the course of 2-3 years is way higher than someone managing to figure out 100 correct login emails for them.

- The attacks appeared to have happened over a long period of time. At least late 2011 to within the last month judging from exif data. So they avoided tons of software and hardware updates for bugs and security patches.

- I assume these celebs have TONS of photos on any of their devices at any given time. Being photographed and taking photographs are part of their lives. So we're talking thousands or tens of thousands. Which takes a lot of time to copy. And like all of us, their photos are unorganized which means it takes a lot of time to find the gems. The longer it takes the attacker to get access and pillage, the more they are exposed. They needed to get in quick and consistently, and get out very fast.

- Given the volume and (alleged) success rate of 100+ celebs, manual social engineering or brute is out.
Well, what founds do you need for the moment? if you were able to make the prototype in your own time can't you find the time to add those features? or you want to focus on it full time?
Saturn's F-ring is twice 3 times as wide as during the Voyager flybys
But the question remains, has anyone used this language?
ah that makes sense, thanks.
I absorb perhaps more than I should, I use it as a kind of positive procrastination from a not completely engaging job. I break it down similarly to you, spend more time on SO style answers as it looks "codey" if anyone can see my screen and answers my own (work or personal) coding Qs.

Midweek sounds about right for me too, it makes me think that actually a 4 day work week, with Wednesdays off, might actually be a better working pattern, but then, I am learning whilst browsing, so, there's pros and cons...
ZFS SLOG (ZIL on a dedicated device) and L2ARC do nothing for data reliability, they are only performance enhancements. Reliability is guaranteed by the CoW and atomic nature of the FS.
I went to a laundromat in Shanghai once. Maybe they only exist around the trendy western-style apartment neighbourhoods, but they do exist.
Nah, that's a famous quote "the playoffs being a crapshoot", which makes the point you attribute (ie, you may well lose 3 games if you have a 55% chance of winning each, despite the probabilities suggesting you wouldn't if you played the same team say, 300 times). Playoff baseball has some changes (for example, the value of a #5 starter is much higher in the regular season than the post-season, because he will never start in the latter; same with a deep bullpen), but that's common in playoffs of all sports - you're less likely to use your depth, and more likely to increase the playing time of core talent.

Luhnow is good, and he did basically play a big role in the Cardinals rebuilding, but Green simplifies this a bit - the Cardinals also happened to have the one of the 3 best players in baseball at that time at well below market value, and the previous GM (Jocketty, who is now in Cincinnati), made some astute trades (Adam Wainright, the pick of Chris Carpenter).

Baseball, for all that I love it, is fundementally a reactionary, conservative sport - unlike the NFL, which changes rules every week (or so it seems), and doesn't seem to bear any burden from the media to provide the "national pasttime", baseball is relatively slow moving and cautious, and seems to carry a higher intrinsic burden from the media and itself. Radical change is thus much harder to pull off in this sport, which is both a good and bad thing.
Yes. I was wondering, faced with an unreliable on-train mobile connection, is there any existing way to improve the content delivery by using a proxy host?

It seemed to me as if the mobile browser kept redoing a whole lot of work, ie. essentially re-requesting web sites from scratch. I'd like to make a single request to a web site, have my proxy host complete the request and deliver the bytes piecemeal to the browser as I go in and out of range.

I think it's possible to do this transparently to the browser, but I think you might need a proxy host with a reliable connection as well as a proxy software running on the mobile device that can deal with the situation by telling the reliable host: I'm back, here's a list of running requests and the last byte I received, please continue.
Screen deals with intermittent connections just fine. I still don't see the need.
You have to wonder how far people are willing to go to declare things defects. At first it's just serious diseases. But then people will want their children to have correct color vision and other nice things.

However, on the other hand, this could actually be a good direction to move in. We can not only eliminate genetic diseases, but also genes that predispose us to other common diseases like cancer.
How does this help me from "Desktop app for tracking stars" or "Video game" application developer perspective that I want to build once, publish once and non-technical users will be able to install simply on(Debian, Ubuntu, Fedora, CentOS, NixOS.....) and not depend on distros packagers?

Like I can do for OSX or Windows?
I wish half of this had been implemented in tmux instead. tmux is already client/server, add local typeahead (which is very cool) to the client and let me run it over whatever transport I want (spoiler: it will still be ssh, because I don't really benefit that much from their reinvention of TCP)
The mosh protocol is specifically designed such that reordering won't happen (since it does use UDP as a base protocol, it requires this protection). I think they'd be very interested to hear about any such bugs you have regarding that.

Also, as far as I was aware, ssh provided no scrollback either. Any such scrollback is a property of the (local) terminal you're using, not ssh itself.
Congrats!

I'll read your blog (later, of course)
Their OO is terrible. Especially ruby's (single inheritance and a half-ass mixin system ... yeah, right).

Perl5's built-in OO is even more terrible, but exposed enough guts for Moo/Moose to be written, which is far, far superior.

Note that there's a MooseX rubygem and an Elk python package, because apparently there are people actively using ruby and python who also miss sensible OO :)

(I can elaborate on what I find superior but you might find it more instructive to see what people have ported than what I miss)
> I feel like mosh is fixing problems at the wrong layer. Instead of making application protocols connectioness, we should make Mobile IP work

I look forward to using regular SSH to connect to my servers hosted in the floating city of New Chicago!
So what is the theory behind the Hawthorne effect? It is relatively easy to replicate those experiments. But effects like this remain 'unfounded' when they are not embedded into a larger theory. The 'larger theories' are the main problem of psychology and social sciences in general. In contrast to e.g. physics they don't have the luxury to produce theories in and for a context-free imaginative ideal world.
It's not clear how you could lock someone into a taxi network - by definition, each taxi journey is a separate purchase, unaffected by previous decisions (once you've installed the app in the first place).

Prepay discount mentioned above is about the only legitimate possibility. There are plenty of not-so-legitimate possibilities (see the Uber vs Lyft poaching discussion)
Sounds like she will do well in Management to me.
A random list of CLs that dealt with conversions.

https://codereview.appspot.com/99380043

https://codereview.appspot.com/140050044

https://codereview.appspot.com/136980044

https://codereview.appspot.com/139930044

https://codereview.appspot.com/139930043

https://codereview.appspot.com/135070043

https://codereview.appspot.com/123700044

https://codereview.appspot.com/126210046

https://codereview.appspot.com/130340043

https://codereview.appspot.com/125610043

https://codereview.appspot.com/98510044
Isn't this simply trading one level of complexity for another?

Maybe the OP is just giving a bad example, or maybe I'm missing something - but one thing I really don't like in his example is that model B's 'waitFor' call needs to know about Model A, and that model A has an appDispatch. This kind of tightly coupled code isn't going to do anything useful for your codebase if you have a large application. It might make debugging easier right now because things are more explicit, but it will make you less flexible in the long term. It also doesn't solve the problem that you still need to understand that A has to finish before B can start - which I suppose most people would simply solve with an additional event. The OP does mention this in the article, but I'm not convinced that the trade off is worth it here. If I'm to explicitly state dependencies within the event handling code, then that means that any time I want to change how things handle events, I've got to remember exactly which of my dependents reference me. This isn't helpful - and in fact it may be more painful than the current situation.

I guess my main problem here is that the benefits this brings just aren't enough (in my view) to offset the potential pain. To me, it kinda just feels like cutting off your nose to spite your face. You might make one area a bit easier to debug, but you lose out in other areas too.

On the surface the code may look more sensible and easier to think about, but in practicality I'm not convinced that this won't introduce additional pain later on.
There are other, less nice implications too.

http://en.wikipedia.org/wiki/Eugenics

Is a good read, also the movie Gattaca (obviously fiction, but raises some interesting questions).
Thank you for the tip with "screen"! I was aware of MOSH but did not know about screen oO. Is there any other line-buffered ssh which does not require Emacs?
My experience with Ada was that it didn't actually make it any easier to make my code correct, because mixing up an int and an enum when you shouldn't is a trivial problem that's easy to fix in C (never mind that the majority of enums are actually labels for ints); the errors that were hard to figure out and costly to fix were the conceptual ones that were independent of language. Ada just made everything clumsier, more verbose and less readable for no benefit. I suspect on a larger project it would start significantly detracting from correctness by discouraging refactoring.
In my experience, the app review process is more meticulous the more you charge for the app. Maybe OP's app is free or fairly cheap while yours is more expensive or has expensive in-app purchases?
That is a great explanation, ill be saving tht one next time someone asks me! Thanks!