skysight-inc/HackerNews huggingface dataset:
It matters why the host picked the goat. (Or, more precisely, what the odds were of him doing otherwise when he picked). That we're looking at a goat doesn't tell us everything.

Again, write the simulation. Either the switch strategy will win 2/3 of the time or 1/2 of the time, depending on how you write Monty. Only one of those approaches matches the results we saw IRL - Monty never revealed the car (so far as I'm aware) - but either is consistent with many phrasings of the question, and OP correctly specified the other case above.
What's the time column mean in this dataset (I'm guessing these connections only happen during a certain time range indicated by the ID)?

https://github.com/nicola/tubemaps/blob/master/datasets/lond...
We use

1. Bluebird with longStackTraces, [1] to get complete stack traces for an entire chain of async operations with minimal performance penalty, and

2. node-debug from node-inspector [2] as a debugger (same UI and features as chrome dev tools)

[1]: https://github.com/petkaantonov/bluebird
[2]: https://github.com/node-inspector/node-inspector
Ah RadioShack, where I acquired Jazz Jackrabbit and a circuit board toy with my dad. It's sad that RadioShack isn't as fun as I remember it being, but last time I was in I saw a similar circuit board toy which is nice. It's always sad to hear that a company treats their employees as though they are no more than cattle tugging a plow.
I go to the Fry's Palo Alto store, it has a decent selection of parts/components if you stay to the right half of the store. (Left hand side is all TVs and Sales guys yuck..) If you want a larger selection of electronic components in the Bay Area - HSC is hard to beat and they have a ton of weird stuff too.
Take http://www.gujaratriots.com with a pinch of salt. That website is run by Modi himself.
The problem with life evolving this early is that life absolutely requires the higher-mass elements from the supernovae arising from the first few stellar generations. The early universe was an inhospitable desert of Hydrogen.
http://www.chromeextensions.org/appearance-functioning/backs...
Thank you for sharing, this is a very good reading.
I purchased a book about using buffer overflow to hack stuff. but I'm wondering how those kernel bugs were discovered?
Hmm, the thread for Firefox accepting Bitcoin was ranking high on reddit, and one of the top comments was mentioning that Wikipedia is also accepting Bitcoin. All I can think of.
That's BS. BJP is a political party, RSS is a non-government organiaztion. Founder of RSS was Dr Keshav Baliram Hegdewar, please show any evidence against him regarding any wrong doing, or any of his contemporaries saying anything negative about him.

Modi's government is democratically elected government. In fact, it won by a clear majority which was not seen in India in decades. Unlike other parties, BJP fought election under Modi and pledge that he will be PM if elected. Given that, your argument is that majority of India is extremist!
"If the host picks randomly, and the host picks a goat, and you switch, your odds of a car are 1/3, just as if you'd stuck. There's no point."

1/2, once you see the goat. One of 1/3, 2/3, and 1/2 beforehand, depending on what happens when Monty shows a car: whether you automatically win, automatically lose, or start over from the top, respectively.
The Official Scala Style Guide on Your Open Source Projects
The Social Cloud for Your Things
Can we just get rid of HTML and replace it with JSON while we're at it?
Space ship passes through it = not impenetrable
Homemade, Bond-inspired LaserWatch
Again wrong! read here as well as Supreme Court's decision - http://www.gujaratriots.com. Note, while all these cases happened, central government was openly anti-Modi.

And if you don't believe in Supreme Court then you don't believe in any of their decision. You cant selectively pick decisions as per your liking.
I learned to program in the early 1980s by playing with a TRS-80 floor model for an hour or two at a time while my mom shopped elsewhere in the mall. My first program animated a sine wave in BASIC by printing a single character one line at a time, and letting the lines scroll up the screen. I would've loved to own one of those computers, but my dad refused to buy one because he said it would be too tempting for me. He didn't even want me to have a hand calculator, and gave me his old slide rules instead (which were fun - not complaining!). I didn't have unfettered access to computers until I went to college a few years later.

I never made a big purchase at RS, but I always appreciated that I could pop in for electronic sundries as needed over the years. My opinion of them started to go south about a decade ago when they began insisting that they needed to know my zipcode every time I bought something. That was very fishy and heralded their sad decline, I think.

RS has been obsolete for years and I really don't know how they've managed to stay in business this long, but I'll miss the name when it's gone.
This writeup, and the first part of this series, are amazing and incredibly instructive.
But they make me embarrassed that anyone still runs or writes code that is so without memory safety that these bugs can exist.
You just contradicted yourself, which is misleading. You started off by saying:

> No one has a single "permanent" Bitcoin address.

And then you finished with:

>So, unless you just happen to leave a single address published publicly as your donation address, you don't have a permanent address.
I'm sorry to be negative but the grammar mistakes in this article were glaring.
It's available on the github repo of the author

https://github.com/hamsternz/IntroToSpartanFPGABook/blob/mas...
No doubt. See seriuslyguys post above. He did it and now agrees.
For me there are certain mental calculations that take longer to process than others. 2 + 2 is super easy. 7+8 is not as immediate. I need a program like this that learns which calculation take me longer, even if it's just slightly longer, and then drills and drills my weak points over and over again. That would be a real mental math trainer.
I wish I could give a brief backstory, but the history of closures in Rust is a long and convoluted one, with many dead ends and failed experiments. :) Suffice to say, `proc` is a relic from a different era (call it "boxed closures 3.0") which always felt a bit out of place, and there was much rejoicing today at its imminent removal.

I think our final design (which might be charitably referred to as "unboxed closures 2.0") is actually really fantastic, and doesn't leave me with any of the lingering dissatisfied feelings that our previous designs did (at least, assuming that all the improved inference mentioned in the OP materializes). I look forward to playing around with them once they're more polished in a week or so.
1) Bitcoin ATM

2) Any reputable exchange (Bitstamp, Coinbase)

3) LocalBitcoins
And while that's expensive by the standards of fossil fuel extraction (with oil at an unusually low price of ~$75/bbl right now), the cost of solar generation keeps falling and seemingly has further to fall, whereas the costs of fossil fuel extraction seem set to keep rising - both because of the increasing difficulties of access and because of increasing pressure to account for externalities, whether at the point of production (like wastewater injection) or consumption (CO2 and soot pollution). We should probably be looking at $126/bbl (at $3/gal) for fossil fuel so as to include the refining costs that would be obviated by this technology (and which have unaccounted-for externalities of their own).

I don't see what's not to like here. You could even use relatively inefficient solar harvester arrays anchored offshore to do most of the processing, and in the event of a spill it would still be substantially cleaner and easier to manage than crude.
I had to read this 2-3 times to figure out what was going on, but I'm still not entirely sure what lead to proposing this change. I guess I'll write what I got out of it and hope I'm crazy and get corrected.

It seems to me that we're restricting what a closure can do when it executes based on the type of closure that it is. Is this in the name of safety? If so, that seems like a good idea given Rust's goals. Right now it feels like a ton of mental overhead but I'll try and play around with it and see if I have an "A-ha!" moment.

Some of the blog post, mainly the part about using a wrapper function so the compiler can still inline monomorphized functions, makes me feel like this is a bit half-baked at the moment. I mean, the very nature of closures is that they give the programmer dynamic abilities.

I really enjoy Rust and the reason I enjoy Rust is the combination of low-level programming and safety. Maybe experiments like this are what gives us that. I hope I'm just confused right now.

edit: Oh, one benefit I see already is that since these are "unboxed" there won't be an allocation.
It amazes me that we're now at the point of standardizing sticking array references inside strings and yet we're still not having a serious discussion about what comes after HTML.
When I was about 8 or so, I had a friend who was all excited about the remote controlled car he found in the RadioShack catalog that advertised "scale speeds of 60 mph!!!". It was only about $40. What a deal!

He cashed in all his parental good will and actually got them to order it for him. Then it came and the 1:20 scale car basically went about 60/20 mph and we did the math... I felt bad for him, but hey... they didn't exactly lie!
Yea this makes me wish there was a better way to deal with this. JSON is popular because it's simple, but as a result sucks for a bunch of use-cases.
I'll add to that; if you program in C# and functional reactive programming on a single codebase across all native mobile phone platforms sounds of interest then take a look at https://github.com/reactiveui/ReactiveUI and send me an email. I'll get you up to speed / invited into Slack. Contact details are on my HN profile.
UK Government to Pay for Software Engineer Apprenticeships
Better pdf at http://www.gtoal.com/wordgames/jacobson+appel/aj.pdf

Source code at http://www.gtoal.com/wordgames/jacobson+appel/mac/Crab_sourc...
The papers from 2013 are available on the TREC notebook page http://trec.nist.gov/pubs/trec22/trec2013.html . This contains all of the TREC tracks (i.e., microblog and crowdsourcing).

You can find other years here http://trec.nist.gov/proceedings/proceedings.html
This certainly seems like something we need to duplicate for spaceships, to more safely travel to mars and beyond.

I don't know much about the dangers of these particles on the human body. I'm going to assume any environment different to the one on earth poses great risk.
Just listened to this BSD Talk episode yesterday. Matt is doing some extremely interesting work, not only on the kernel and file system research side, but also in terms of their completely customised networking stack, which utilises multi-core non-blocking networking I/O to achieve really high speeds. I would like to see some of that incorporated back into the FreeBSD kernel (not sure if it has been done, but I doubt it).
This thread needs an argument for the case where the host picks a door at random.

The chance for the host getting the car is of course also 1/3.
Then the complement 2/3 chance of the host getting a goat splits the car chance evenly between the two remaining doors as 1/3 for each door.
What's wrong with a human-readable serialization format?
The name "benchmarks game" signifies nothing more than the fact that programmers contribute programs that compete (but try to remain comparable) for fun not money.

The performance of those programs with CPython explains the existence of numpy, and if you look you'll find that numpy programs are shown.
The JSON-based file upload would be nice (AFAIK there's not great way to do this ATM, but I haven't looked in over a year). The rest seems pretty weak-tea though. I can see multiple issues with more defined type (e.g. numeric rather than string values, null rather than blank string), but without dealing with that stuff, this seems of extremely limited utility.
I'm curious why Mozilla needs contributions.

Previously they were getting $300M a year from Google and they were required to spend that every year, from what I've been told from employees that I know. Everything I've heard from them is that Mozilla is a very wasteful company. They spend a bunch of money on things like boondoggles to Europe for the staff, apartments in Paris that anyone can book, employees sitting around with almost no work to do, etc. They also have really lucrative bonuses (>40%/yr) for employees that push salaries over $200k for senior engineers, so I'm just wondering why they even bother with donations? I'm assuming that their contract with Yahoo is even more lucrative than $300M/year, so they must have a lot of money to spend, why worry about donations that might only reach a small percentage of that?
Nothing - I was talking about this:

<input name='kids[1]' value='Thelma'>
<input name='kids[0]' value='Ashley'>
What if you use Node to serve up the client and use Web API as the back end which you make calls to?
I found this on the internet and modified it so you can just change the commented out options to run it under the different scenarios.

car = wins = 0
many = 100000
actual = 0

many.times do
choice1 = rand(3)
car = rand(3)
#host_opts = [0, 1, 2] - [choice1, car] # host knows what is behind
host_opts = [0, 1, 2] - [choice1] # host doesn't know what is behind
#choice2 = [choice1] # don't switch
choice2 = [0, 1, 2] - [choice1, host_opts.first] # switch
if host_opts.first == car then
# Discard? Automatic win? It doesn't actually matter!
# It only changes the denominator.
else
# According to the puzzle, it is decision time!
wins += 1 if choice2.first == car
actual += 1
end
end

puts "#{(wins * 100) / actual}%"
Sorry, was this a reply to the wrong comment? Can you expand?
Flow isn't mature enough yet, but even TypeScript eliminates pretty much the entire Wat talk.

Also, it compiles to CommonJS, which means it works well with both node and browserify.

Yes, we need a blessed, "batteries included" stack for JS made of components that play nicely together. Here is a nice list to get started with (IMO, ymmv)

1. TypeScript or Flow
2. React
3. Promises: bluebird, when or p-promise
4. Observables: rxjs or most (they play well with promises)
5. immutable-js for immutable data structures
6. lodash and/or Ramda.js
7. browserify
I didn't notice the sexism. It is extremely cringeworthy, though.
Case Suggests How Government May Get Around Phone Encryption
So which site is without bias? Why would you claim tehelka is not biased when Tejpal and Teesta colluded often.
I have a single, permanent Bitcoin address (1jb55g498MEa274Z1YWUXQFxZE5NzvhV7). I don't pretend Bitcoin is anonymous and I always set my change address to go back to the inputs.

I understand the risks of how the address inputs and outputs as probabilistically tied to my identity. If I cared about those things I probably use stealth addresses and dark wallet or something.
Whoa. I missed that. Probably by clicking the link to the serialization algorithm.

That's bad. Really, really bad.
Have the terms of the agreement between Google and Mozilla been made public regarding that? Were they limited to what they could spend that money on?
good guy, doesn't give a shit about the corpo-academic kleptocracy. For the love of math, that is all.
With node, you can run multiple processes per server... the challenges of inter-process communication really aren't any harder, and are very similar to when you have to scale to multiple systems anyway.

As for blocking, if you are doing something that is blocking in your main event-loop, you're probably doing something wrong. Break it off into a req/res queue and let it flow.

Regarding call-back hell... you have next-generation tooling like co/koa as well as ES6 Promise patterns you can use. Not to mention the async library.

You can readily follow functional patterns in JS and Node... just because there is prototype based inheritance doesn't mean you need to use it, and most of the time, I don't.

Also, Node itself isn't really single-threaded... the main event loop is, which is where your JS code runs. The underlying platform calls are running against a thread pool.
>>A somewhat more fair comparison…<<

Well, it would be a different comparison; and I dare say a website showing such a comparison would attract a lot of traffic, if only someone would "please take the program source code and the measurement scripts and publish those measurements."

http://benchmarksgame.alioth.debian.org/play.html#languagex
JSON rendered with react Js using JSX feels to me like the future of html.
The earliest reference to an index in the English language is from 1593 [0]: I don't really think it qualifies as a "A little known hack from Japan".

[0]: https://en.wikipedia.org/wiki/Index_%28publishing%29
This is a fair comment, that a single question can be used test several different aspects of a topic.

However, unless you are specifically testing the student's ability to string the different aspects together precisely, I don't believe that to be an optimal exam question.

Here, for example, you are seem to be allowing the student a 50% passing grade (2/4 expectations met) if they show they understand the text by drawing it out, and remember the formulas from the syllabus sufficiently to write them down without starting to apply them.

That maybe isn't your intent, and maybe your ideal mark scheme would try to avoid over-crediting something like that.

But even if that's not what you intended, that has become the reality: setting expectations for partial credit has led to increasingly simplistic expectations of students and this in turn to rampant grade inflation. Grade inflation has been strongly encouraged by institutions' statistical collation, but has been mostly avoided by the SAT.

I'm not sure that I want students to have access to good grades even if they consistently give wrong final answers, transposing digits and so on. It shows a lack of precision and a lack of full understanding of the question (not able to do effective sanity checking). Precision is a skill that mathematics can help people to learn, in my opinion.

The SAT being multiple choice means you have a fair opportunity to correct this type of mistake - a typographical error typically won't fit with any of the multiple choice answers and you'll have the chance to correct it (costing you only the correction time - and teaching you that precision is of some importance). The wrong multiple choice answers tend to fit deliberately with common conceptual errors. This actually illustrates a useful element of the SAT exam design.
really great article - i had read a lot about him before and never come across the fact that he was jewish and didnt believe anti-Semitism existed.
If anything sexualizing and dehumanizing celebrities is the cultural norm. Which isn't about the Internet per se. How cloud providers can have zero liability though...
> choose a single-threaded solution

For stateless web requests (solving the C10x problem), this is not inherently bad for most applications.

> which blocks the whole app if a single function blocks

This is behavior you'll see in many other languages.

Management of execution time is very prevalent in lower-level languages. The only languages not susceptible to this problem are high-level, preemption-capable, and possess some form of green threading/scheduler e.g. Erlang/Elixir.

IMO, if you need to rely on a scheduler to help ensure that blocking doesn't occur in a disruptive fashion, you're in no position to deride those who "began as a webdevs and knows nothing better."

> asynchronous call-back hells

This is a matter of taste, opinion, and necessity.

I personally hold the opinion that "callback hell" is a symptom of poor design, and properly managed callbacks are not unpleasant to work with (I may be subject to Stockholm Syndrome).

Also, try implementing an equivalent non-blocking webserver around an event loop in a lower-level language and let me know what non-callback strategies you come up with for the coalescence of asynchronous events.

As an aside, there are hundreds of different ways to improve or eliminate the composition of callbacks in JS: emulated coroutines via generators, C#-style implementations of async/await, promises, the list goes on.

> non-functional but GC'ed language

Which functional programming languages in common use aren't garbage collected? (again: in common use)

Which other common, productive, high-level programming languages (often tasked for C10K web servers) aren't garbage collected?

What does "non-functional but GC'ed" actually mean? What does the language's programming paradigm have to do with its memory management model in this context?

> I am really too stupid to get it

- People are productive and enjoy JavaScript.
- Browsers, by and large, only run JavaScript code.
- JavaScript on the server-side is a very capable, battle-tested building block for performant web software.
- Admittedly: JavaScript is not a great language when compared to other modern programming languages.
- Aforementioned opinionated gotchas aren't enough to dissuade communities from using JS.
You can also use multiple worker processes for your more intensive cpu tasks, keeping that out of your main loop altogether. Pooling and queue limits can prevent too many of those bound processes from running at once, and you can distribute workers across several systems.
What was the title of the book you purchased? Can you share its name?
The implementation is definitely half-baked at the moment, but will be improving drastically over the next week or two. :)

As for the wrapper function presented in the post, it's only to demonstrate that closures are implemented via traits and act just like any other trait in that they can be used to facilitate virtual dispatch (though IMO you shouldn't strive to use traits in this way if you can help it, given that Rust gives you many tools to help you prefer static dispatch).

Watching closures evolve in Rust over the past few years has actually been really interesting. We had an implementation that was "good" a few years ago, but was ultimately fundamentally inferior to the approach taken by C++ lambdas. The period since has been a fascinating exploration of ways to make closures safe, usable, and potentially zero-overhead in a language without garbage collection. For all I know it may be unprecedented.
Why do people persist in this belief that a kernel is some mystical realm where software-engineering principles don't apply?

Why do you think that these "software-engineering principles" should apply? I think the fact that the Linux kernel works, and it works quite well, is strong enough evidence that they don't matter.

the people who worked on the AIX and Solaris kernels still knew and applied this stuff.

I don't know about AIX, but there's a reason Solaris has been called "Slowlaris"...

If an RTOS for tiny devices can have decent modularity

But is that modularity actually necessary? I've worked with plenty of overly complex applications that were far more inefficient and harder to understand as a whole than they could be, and most of them were the result of dogmatic adherence to principles of modularity, encapsulation, extensibility, etc. (none of which actually improved anything from the point of view of either the users nor the ones trying to figure out how everything works), so maybe that "anti-CS attitude" is a good thing after all...
So it's not an objective comparison because the V8 implementation performs well? :-)