skysight-inc/HackerNews huggingface dataset:
I broke my golden handcuffs to join WePay, a fast growing start-up in Palo Alto. I was at my prior company for 10+ years, had lots of unvested stock and guaranteed bonuses...and I was still generally happy. However, I just knew that WePay's culture and growth was pretty awesome and I couldn't pass that up. The way I got over it was that I just had to say to myself was that it was almost like I was going back to school - in this case, getting my BA in start-ups and that the stock I was giving up would be like tuition, an investment. I haven't regretted my decision...and it only takes the handcuffs to be broken once for you to know it can be done again!
James,

did you guys consider (or try out) Eureqa [1] to get a good model for the estimate? It works very well with such kind of data.

[1] http://creativemachines.cornell.edu/eureqa
There's a name for when the churches ran the world: it's called the dark ages for a reason. I'd rather not have to rely on someone's (supposed) piety on top of the questionable scruples of the church to render assistance. What happens if you're an outspoken critic of the church or (heaven forfend) a "sinner" homosexual? At least when the Tea Party criticizes the government, the government doesn't pull the welfare checks of its members.
sorry I meant "perl6 -v"
I'm looking forward to trying Red Tape.

I previously found Metis to potentially be the best, but it's fragile, uses a DSL of vectors and if you e.g. spell one incorrectly it'll silently fail. The DSL isn't very complicated, but the lack of robustness, when something will only fire when input data is wrong, is seriously subpar.
Stamps.com advertise on the radio+podcasts and they added an icon to their front page http://www.stamps.com
DOJ Elevated Its Charges Against Swartz Because Internet Rallied on His Behalf
Impressive, how long did it take you and what were your motivations, if any, beyond fun and learning?
I've never encountered that definition. I've only seen it in terms of "god, the management at Subway sure is full of itself". I think it was the Subway definition that enko was using. Management using a ridiculous fancy term to pretend they care about employees.
after reading both perspectives you learn that:

* you are locked in, no matter if you prefer android or ios
* choose you poison?

come on, it took years and a lot of effort to take us all out of the nightmare of the windows ecosystem lock in.. so we can fall out in the same trap all over again?

and while this is a natural behavior of apple that we should be all expecting, i expected more from google.. because nowadays google is looking like a schizophrenic, working for the web and open ecosystems, creating a lot of awesome opensource projects with one hand, and creating more and more closed ecosystem that try to lock people and developers in.. google looks like dr jekyll and mr hyde..

i hope the open google, the google with the hacker culture, that the "Dr Jekyll" google wins in the end..

but nowadays it looks that google is more in a love affair with its mr hyde side.. i hope it gets cured preety soon
and come back to its hacker spirit roots.. with no traps in their products..

apple will just loose more and more market share, because its acting like if it was the 90´s.. and we see now with microsoft that this way of doing things its a thing of the past.. so it will fall by its own steps..

but google with a candy in one hand, and a knife in the other hidden on the back.. thats a behaviour that should be feared..
Still that is the thing that Node.js lead developer regrets the most. Too late to change it, though.
Checkout C++11. It has lambda callbacks, promises/futures and async with threading.
Medium is for stories.
Nothing happens automatically

If I have a function in Python that used to only return strings, and I re-code it so it returns None in some cases, I don't have to re-declare anything. The code just runs and returns None automatically, without me having to change anything about the function except the actual working code that determines what gets returned. With static typing, I need to re-declare the function's return type; it won't automatically return None if the type system thinks it can only return strings.

With considerably more effort

I don't understand this; you're comparing a test suite on top of dynamic typing, to a "test suite on top of a powerful static type system", so you're expending the effort on the test suite either way.

and with no guarantees that you've come even close to correct.

Static typing doesn't guarantee program correctness either; it just guarantees type correctness, so to speak. You can have a program that gets all its type declarations right but still has faulty logic. So you're still going to need a test suite either way, as I said above.

Eventually you hit the bit of nonsense code your change caused and then the program dies.

Why do you assume the code change produced nonsense code? If it doesn't--if I got the change right--then the program runs fine.

I assume what you really meant is, if I made a mistake, a dynamically typed language won't catch it until runtime, whereas a statically typed language will catch it at compile time. That's true; that's one of the tradeoffs I mentioned between static and dynamic typing. With static typing, I catch a certain class of errors earlier, but I pay for that by having to explicitly declare things. With dynamic typing, I don't catch those errors until later, but I can program faster (at least for certain kinds of applications) because I don't get bogged down in having to keep all the type declarations straight. As I said in another comment upthread, I'm not saying this tradeoff always works out in favor of dynamic typing; but it doesn't always work out in favor of static typing either. I think it depends on the type of application you're writing.
Hack Vine to Upload Videos Shot Outside the App
No

http://en.wikipedia.org/wiki/Sturgeon's_Law
$.35 ? Can AMC sell direct to the customer? I'd even pay double that, $.70.
Is the fact that they use callbacks instead of Promises outside of userland a real problem for you (as an application developer)?

You can totally write your node applications using only Promises using something like Q if you feel like it.
I agree. PIP in python is great, but has some extra overhead and difficulty with it, like having to setup virtual environments for each project. NPM by default installs to the local project only and with a quick --save will put it in package.json dependencies (similar to requirements.txt with pip). Node package management is awesome because it is so simple.
> In order for the open file not to be inherited by the new program, we must introduce a new variant of open(2) that can open a file descriptor atomically marked "close on exec."

This is incorrect, because you can prevent fds from getting inherited even without "close on exec". Simply list the files in /dev/fd and you'll see all the file descriptors your program has open, and then you can close all of the ones that the exec'd program won't need. The same thing is done on Linux with /proc/self/fd. The whole facility gets wrapped in a library function (not a standard library function, sadly) since there is a minor trick involved in getting this right.

The problem with close on exec is that libraries would have to be modified to ensure they mark descriptors as close-on-exec. The current system is admittedly arcane and non-portable, but it does work.
great, thanks for pointing it out.
hhmm.. this article make me think..
Curated Content - The Future of Curated Content
Weird conventions, like including index.js by default. It does not play nicely with coffeescript's default behavior of including a module. The modules being a hack built into the language, I have to read library docs and follow external decisions (versus a holistic approach built by the language maintainer). Introducing a variable to contain a library is unconventional and potentially limiting (specifically for meta programming).

Like I said, I didn't spend much time with them. They are a solution. NPM feels like the old rails gems and is certainly better than most package managers. Requiring external libraries and files specifically is a hack and feels as such. I would gladly take any of the languages inclusion techniques I listed above over node's.

Edit: I am not trying to put down the hard work that went into creating the system. JavaScript does not support modules natively, so adding support is a momentous accomplishment. The unfortunate reality is that it will always be a limited solution. JavaScript modules (in any form) are going to be inferior to languages that natively support such a basic part of programming.
Precio del dolar
Noticiero económico de dolares en venezuela
That's single threaded compositing on its own thread.
Wasn't that the original selling point of Node? That it used callbacks for async and that it was easier that way?
I think the issue you are describing really stems from poor semantic versioning. People will peg to specific revisions that they happen to use rather than depending on the general major or minor revision level, so small fixes don't naturally propagate to second- or third-level dependencies. There's no good solution to the problem that doesn't lead to other sorts of hell (imagine asking users to manage the revisions for third-level dependencies)
Dalai Lama's Chinese website hacked and infected
We actually used R, but this looks very neat, thanks for sharing!
man, the air cushion behavior at 1200 km/h (speed of sound at normal pressure, and 1.2 Mach at the proposed decreased pressure in the tube) would be a subject of a lot of PhD works. Or in other words - it will be hell of an engineering (stability of the cushion and parasitic oscillations come to mind - that is with respect to compressor created cushion, and in addition to the compressor created air cushion the cushion's airfoil will be riding its own shock wave between tube surface and the airfoil in front of the cushion's high pressure volume) to make supersonic ground effect from concept into product.
On the Python side there's Lamson and Google App Engine also has nice email handling capabilities allowing you to parse and access from your own code / app.

http://lamsonproject.org/
https://developers.google.com/appengine/docs/python/mail/
Sound good on all those. Completely dropped PHP for Node, no regrets.. Good because those breaking changes in Express v2-3 were annoying..
Only tangentially related, but the "rant" by Ryan Dahl (node creator) when he left Node day-to-day is worth a read:

https://gist.github.com/cookrn/4015437
It is primarily a political manifesto, as he presents it as an alternative (cheaper, faster to build, faster at moving people) to CA's HSR project.

However, in my view, there's nothing that makes Hyperloop and CA's already started HSR project mutually exclusive. Hyperloop just isn't a valid alternative. It does sound awesome, though, and it should be built, too, because - why not? Its cost to build is low enough that private investment and a public private partnership to get it to share rights of way (where necessary / convenient) with HSR, to even share stations... I mean Hyperloop could be conceived of as the express line from LA-SF - a complementary technology, not an alternative. Even if we had Hyperloop, there are still a number of great arguments for having HSR too. And the fact is, we don't have Hyperloop, it's a completely untested, unproven technology. We do have (a detailed plan, approval, and some funding) for HSR. So we should build HSR, check out Hyperloop, and if it's actually feasible we should do it too, and connect them.
Might be worth your while to give it another shot. Npm is so lovely.
Postmark is one I've used in the past that has an incoming mail API (in addition to outbound) that hits an endpoint you set with email data already processed for you, attachments included.
$AAPL spike on tweet from Icahn
I watch TV shows by the season, in one sitting often times. So shelling out $70 for the box set of discs is terrible. Netflix is my kind of product, but I'm still waiting for the next season of Walking Dead. Can they just stop delaying it so long?
I know it works, and I'm very happy for it. Would have taken me a lot more time to land on the Mun otherwise ;)
Some see the main problem here as being moral hazard, which causes social welfare programs to become very expensive, with most of the resources going to people who have been lured in by the promise of 'money for nothing'. This is a normative argument which is what I think you are critiquing here.

I would put forward another criticism of need based programs which is positive, and has recently been made with increasing frequency. This argument is that the nature of many programs induces dependence among the recipients; the principal example of this being US federal disability benefits. These benefits can be permanently forfeited if the recipient earns more than a given amount over a certain time frame, which forces the recipient to consider trading in a long term cash flow (disability benefits) for greater income with uncertain future prospects (a job). The result is that many people with difficulty working, who could do some limited work are disincentivized from ever taking a job; this is especially apparent during recessions. [ http://economics.mit.edu/files/7388 ]

The other problems you can have when you begin to hand out government aid are moral ones, which you may agree with. Those who are lazy and collect benefits get to take from those who work hard; even more troubling is that the workers have no way to force the slackers to do anything, while the slackers can use regulation and taxation to manipulate the workers. This argument does not address people who are unable to support themselves.
Apple propagandists have a way of acknowledging the wrongs of Apple while telling readers to not use Google's products and services:

Google says they like open things. Google had "Don't be evil" as a motto. However, Google does things that aren't open and things that are evil. That is why you shouldn't use Google's stuff.

My strawman isn't perfect, but it gets the gist of what Gruber, Marco et al say: Google tries to present itself as a better company, but they're not, so don't do business with them.

It's a noble point, but it completely glosses over Apple's equally bad behavior under the excuse that Apple, unlike Google, never pretended to be nice.
I used SDL 2 after Sam's "please use SDL 2 and report problems" email about 2 or 3 years ago and it was a pleasant experience and a much needed upgrade over SDL 1 (though most of the docs were still incomplete). So this announcement makes me happy.
Space Glass, new AR Glasses compete with Google Glass
The biggest problem I have with A/B or Split testing is that it makes it easy for inexperienced people to assume there are multiple right answers to every problem and that they all warrant 'discussion' or testing... Most often this is not the case, and people who jump straight to A/B everything are the sort who don't really have/trust any experience and would rather spin wheels and throw spaghetti at the wall.

That said, sometimes there are two (or more) options that warrant testing (say a marketing strategy) and then it works great.

Test strategy, don't test everything, don't test design principles.
Must Every Kids' Movie Reinforce the Cult of Self-Esteem?
Jim: What's an official reply?

Bernard: Well it just says the Minister has asked me to thank you for your letter and we say something like, the matter is under consideration, or even if we feel so inclined, under active consideration.

Jim: What's the difference?

Bernard: Well under consideration means we've lost the file, under active consideration means we're trying to find it.
President Obama's "independent" NSA reform panel will be led by head of NSA
While I like using NuGet packages with C#, I'm not really wild about how they can get magically linked in to a project, and then required. I had nunit and fluent assertions become inextricable from a project I was working on even after all the tests were removed. Just a total mind-f*ck. Python when using pip is a whole lot better but I've had some issues finding things there too. Ruby... it depends. Are we talking Rails gemfile or "gem install $package"? Conflicting versions can become an issue. Java with Gradle has been pretty cool so far. NPM as a whole, has just worked. Packages are referenced in ONE place (package.json) I can do an "npm install $package --save" during development and it gets included automatically.
If you're not thinking about the big picture, you will fail
Are you language-agnostic? Ruby's mailman gem is good.
Video Summarization App
We're following exactly the same track record as before, and this was important in finding the right people to work with in the VC community.

We have already announced AWX, which is commercial software, and you can read about it at http://www.ansibleworks.com/ansibleworks-awx/ -- it's downloadable now and you can use it for up to 10 nodes free.

Basically the cutoff is ansible and ansible-playbook should be completely usable for all kinds of teams, but if you find the GUI useful, or want the REST API, or role based access control -- typically things enterprise companies do want, you have a product you can buy that adds a lot of value add on top.

We're going to continue merging in all kinds of great pull requests and features, and continue to expand the language where we need to, and modules.

One example of this is we recently were able to hire James Cammarata, who has been maintaining Cobbler, to work full time on just the OSS bits!

Another example of this is all of our support guys are also helping out on things like IRC, and helping with producing new example content and modules. All the recent modules for OpenStack are an example of one of these things.

Nothing is going to change in terms of licensing or the community at all, if anything, it allows us to have a lot more resources, help promote Ansible more, and move faster.

But yes, we're going to have a really awesome product as well, and I think lots of Ansible users are going to be quite interested in taking a look at it.
I struggled with this for years. I solved this problem with one simple rule. I don't allow myself to talk about what I am planning, or doing, but only what I have done. It doesn't have to be a whole project finished, it could just be a part of it. So I could not say, "I'm working on this awesome RPG it's going to have blah blah", but I could say, "Last night I got this really cool feature working in my RPG map generator". etc..

That doesn't work for everyone, I know some people that are motivated by telling people what they are working on so they feel like there's pressure on them. But that's just what worked for me.

The other thing that helps me is to set artificial deadlines with "cooling off" periods. So I plan a demo or a release for, say, the end of next month with the self-impose rule that no matter how much, or how little I've completed, or even if I miss the deadline entirely, the day after the deadline I will set the project aside for six months.
You could make this comment useful and worth reading by explaining why.
Think of what I'm proposing as the "Shawshank Redemption" model. Don't focus on box office sales, focus on the complete picture, and focus on compelling storytelling.

Shawshank peaked at #9 at the box office, only making back about half it's budget.

In the home video market, it has just exploded, selling over 5 million copies in the UK alone. (http://www.bva.org.uk/news-press-releases/members-press-rele...). That's kind of mindblowing...about the same number of copies as Sgt Peppers has sold in the UK, and way more than any contemporary album - the closest comparison is probably Oasis's What's the Story? (Morning Glory) at 3.3m units sold.
Looks pretty good, I will check this out in more detail! It looks like a common enough problem that I thought there would be mature frameworks around. I keep finding myself looking for a solution like this for most of my side projects..
you're not factoring in the advertising money they're missing out on with digital downloads.
I believe that good code is the comments. From the sounds of it, this code isn't good in that way. Plus it had comments.
Yes, I am language agnostic. I was leaning towards Python/Ruby solutions. I will check out mailman. Thank you.
And it tries to force the conversation into a binary discussion: Apple vs. Google, iOS vs. Android which it isn't. The OP is basically the same as most of these kinds of things "<insert potentially meaningful issue>, google is bad for this issue, Apple is free from this critique" which is trite and tiresome.
Are you suggesting that they would lie to me or that they would be so incompetent that my apache instance using less bandwidth than streaming radio would affect my neighbor's gigabit line?

I'm assuming some basic levels of competence and a reluctance to flat-out lie when I complain about a provision that can be used to boot people on a whim.

I shouldn't need a business account unless I want a better service level or I'm running a business.
Since when did Google start pushing their projects to Github instead of Google Code? Does dogfooding not apply to the big G?
If String and None are both valid return types for a function, then you tag that so the inference system knows it's a valid solution

In other words, I need to do extra work to tell the type system about the function's return type.

If you know they share functionality, you can declare that they share functionality (any language with type classes)

Same comment here; the language is making me do extra work that I don't have to do in a dynamically typed language. So there's a tradeoff.

This sounds tedious right up until the first time you write a complicated program, get it to compile, and it just runs correctly the very first time.

See, here's the thing: I often write non-trivial programs in Python that run correctly the very first time. So I've had this same experience in a dynamically typed language.

Perhaps a language like Haskell would raise the bar, so to speak, for how complex a program can get and still allow this to happen; but even then, it would only matter if you were writing the particular kind of program that can benefit from the difference.

Lastly, in a language like Haskell, type declarations are almost always optional.

It's the "almost always" that's key here; basically, what the rest of your discussion here shows is that the type declarations end up not being optional in precisely the cases where, in a dynamically typed language, you would just be making changes and running code, not spending extra work on adding type declarations to resolve ambiguities for the compiler. So there's a tradeoff.

As I've said in several comments in this thread, I'm not saying dynamic typing is always better; I'm saying it depends on the kind of application you're writing. There are tradeoffs involved, and they don't always end up favoring static typing.
> And no doubt when they do, you'll be at the forefront defending them? Re-read your 2nd and 3rd paragraphs as a defence of China as a world power. Do you still stand by them?

I don't quite understand how you read what s/he said as a defense of the US' behavior or the putative future behavior of China. An acknowledgment that people in power behave like assholes, sure, but it's in the overall context of criticizing Chomsky's political writings as being somewhat simplistic in how they handle the ethics of power politics. Or perhaps you believe that the black and white view of things is the right and proper one, and failing to adopt it is equivalent to apologizing for misdeeds by those in power.
the real future of space is Hyperloop v2.0 - 20 miles long or something like it, pointed at the end toward the sky with final exit speed of let's say 10 Mach (and this also will help to reach Hong Kong from SF in 1-2 hours)
Trending repositories on GitHub today