Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

Heh, I was helping a colleague with some question, and I wasn't really sure about the answer, so we Googled and checked out the top hit on StackOverflow. Wound up being a question that I had answered a couple of years earlier, and forgotten the answer in the meantime.


I've actually done the next stage: researched a problem, found a really helpful Stackoverflow answer, which it turns out I had written, which was a reply to a question which it turned out I had also written.

The only disappointing thing being that due to causality constraints, I was unable to upvote past me's answer or further past me's question, which was a shame as they were both really useful.


Most of these LucasArts graphical adventure games were written using a game engine known as SCUMM (https://en.wikipedia.org/wiki/SCUMM) that was able to target different platforms, which was ported to the Mac and so ran on 68k and later PowerPC Macs. There is now an emulator that can play SCUMM games on almost any platform known as ScummVM (http://scummvm.org/).


> People who won't see it don't but if you are at all open to it it's easy to reproduce.

So, have someone who is "open" to it go and view something that they haven't otherwise had a chance to perceive in person, then when they wake up tell the experimenter what it was. If it's easy to reproduce, then they should be able to do that, and it should be easy to verify that they had an out of the body experience.

Instead, you just get anecdotes, of people repeating past experiences with no controls to blind it. Human memory is surprisingly faulty, people can fill in details later on in their memory, and so on. So it's very easy to think that you had a dream in which you saw something for the first time, and then later recognize it while you're awake; but it's also possible that you brain just filled in the memory when you saw it later. Or maybe you had seen it in the past but didn't have conscious recollection. And so on.

Simply hearing people say that they had OOB experiences in which they saw things that they never saw in person is not particularly credible.


Came here to say this. In fact, I think every language that they give 5 stars to has some form of "foreign pointer", "raw pointer", "unsafe pointer" or the like that is nullable, for FFI and other low level tasks.

I think that anything which has no null in normal, idiomatic code, outside of "unsafe", "ffi", or similar subsets, should get 5 stars. The distinction is really about whether you need to worry about any possible value, or any possible reference, being null, which you do in languages like C or Java where all references are nullable.

Giving Java and Rust the same 4 star rating because they both have some form of null and some form of Maybe/Option is a bit misleading. In Rust, Option is what you use in any normal code, and so you don't need to check for Null everywhere. In Java, it's the other way around; nullable references have existed since the beginning and are not segregated in any particular way, while Optional is a recent addition.

Likewise, I think that in Scala and Swift, null is only present for compatibility purposes, and idiomatic code does not use them. I'm not sure about F#. Clojure does use nil idiomatically, and also has '(), which may even count as "multiple NULLs" according to this rubric, though I guess that in Clojure '() is just treated as an empty list, rather than a null value like it is in other Lisps.


> Likewise, I think that in Scala and Swift, null is only present for compatibility purposes, and idiomatic code does not use them. I'm not sure about F#.

I believe though that with the exception of Swift, null can infect these language's quite easily via the FFI, and the guarantees aren't as strong. I haven't used them much though, so I could be wrong.


Yeah, I guess it depends on how often you use the FFI, and I'm not familiar enough with these languages in practice to know how often that comes up. Part of the point of each of these is that they can utilize an existing ecosystem in which null is common (Java/JVM for Scala, C#/CLR for F#, Objective-C/Cocoa for Swift).

I know that in practice in Rust, the general approach is to write safe wrapper around any C libraries you're using, so the use of nullable pointers is generally confined to those wrappers.


Hmm. Some interesting data, but it doesn't really cover anything like the full "pipeline", which goes past the PhD to postdocs and then to faculty positions. And of course, that's only covering academic exits, while going into industry is another avenue, and there has been no analysis of whether the pipeline from bachelors to industry has been leaky in STEM fields.

Now, hitting a cap on the percentage of people entering the "pipeline" does mean that there's only so much effect that the "leaky pipeline" could have. The self-selection that happens even upon entering a bachelor's program is a pretty large factor, which needs to be studied; is it due to differences at the high school level? Difference in perceived job prospects, perhaps due to problems further down the pipeline like postdoc and tenure positions? Even if the pipeline is only getting a small percentage of women up front, it's possible that feedback from further down the line is what is causing that disparity.

Anyhow, it is good to have some concrete numbers on at least this portion of the pipeline, to inform where efforts should be spent. It sounds like the bachelors to PhD portion was fairly leaky in the past, so efforts to improve that have helped, but now effort would be better spent on looking at other aspects of the system.


I'm not sure there necessarily is a "consensus" on HN.

However, in general, people feel that you shouldn't take a very large salary cut just for a few options. Most startups are not going to have a significant exit. Some (like Zynga), will manage to find a way of screwing you out of options if they do have a substantial exit. Only a few will have options that have a very large upside.

So, if your options only add up to some very small percentage of the company, they shouldn't be given in lieu of a very large amount of salary. Sure, you're working on something exciting at a startup and there is some potential upside, so maybe take a 10% salary cut and a few options to compensate for it. But don't take a 50% salary cut (or a 100% cut, where you're only paid in options), and look at your options and say "it's worth it because these have a chance of being worth millions."


Sure, but it's been played in Japan for over 1000 years, which is plenty long enough to have developed "ancient Japanese wisdom".


"Ancient Japanese wisdom" (and art, philosophy, etc) is mostly re-packaged ancient Chinese wisdom.


In some cases, yes, but there is a lot of it that has diverged in the years since. In the case of Go, while it originated in China, it really flourished in Japan and the Japanese developed it a lot further, up through the beginning of the 20th century.

Throughout the 20th century, Go has gotten a lot bigger in China and Korea (where it is known as weiqi and baduk, respectively), and they are now generally favored in international matches, but before then, the Japanese were quite dominant.

As far as other pieces of culture, yes, the roots of a lot of Japanese culture come from Chinese culture. But they have had thousands of years to become distinct; calling them just "re-packaged ancient Chinese wisdom" is pretty dismissive. It is good to recognize the roots, and sometimes the Japanese themselves are a bit xenophobic about that, not recognizing those things that developed from the Chinese, but dismissing their entire culture as re-packaged Chinese culture is equally rude.


Perhaps some people thought this was some kind of racist remark?

I'm not Chinese, and this is a historical fact.

Japanese borrowed heavily from the (earlier and more advanced) Chinese civilization.


so on the assumption that go is a chinese game, japanese cant have a wisdom on it? that would be same than saying: Ok C-UNIX has been made by an american guy so no one can have wisdom on it except americans?


Sure they can, hence the "mostly" part. Of course in the course of centuries they've also diverged, as the once underdeveloped (compared to China) Japan started developing its own identity and variations.

Heck, even the 20th century provided enough rapid variation between the 2 countries.

That why I was talking about the "ancient wisdom" being repackaged.


It is a feature that it caches your authentication for a few minutes. It's not a feature that other processes running as your user, such as something that manages to do a sandbox escape in your browser, are also able to acquire credentials.


Yeah, the difference with the disk full alert and the alarm is that the alarm is emitting a very obnoxious noise continuously while you're trying to debug it; and in the meantime, not actually providing a useful service, like the server is. Trying to debug a problem at 3 AM when you just want to go back to sleep because there isn't anything actually wrong, just faulty alarm hardware, is not nearly so useful as clearing out some space on a full disk when it is in active operation.


I've never seen a Nest product in person. A quick search [0] makes it look easy to replace the batteries in all models. Can't you just remove the battery plate and pop one out quickly before debugging?

[0] https://nest.com/support/article/How-do-I-replace-my-Nest-Pr...


Mmm, no. If the four largest mining pools go for it, but the various exchanges and online wallets do not, then you get a very dangerous fork where you now have two separate currencies, and have the possibility of double spends. The nodes that are not updated to allow these larger block will keep on going along with their chain, just rejecting the other chain as invalid; and the ones that do accept the larger blocks will probably see their chain as longer and so only accept that one. That fork means that until all of the online wallets, exchanges, and anyone accepting Bitcoin directly realize that there are now two different currencies, all kinds of fun can be had with double spending.


Should we assume any update that "fixes" the mining pool problem will be rejected by the pools? If so is a dangerous fork of Bitcoin certain?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: