skysight-inc/HackerNews huggingface dataset:
Instead of the pursuit of freedom, we should dedicate ourselves to obligations that honor ourselves and others

Says you. I appreciate the freedom to sit at home and play a video game on a Saturday without feeling compelled to meet the needs of others.
Please insist on a better script for the next Tron movie.
He's there because he's a coward with no backbone. If he is so sure of his innocence, he'd be facing the court instead of propping up a government with terrible human rights record.
The question is not how you can get users for your app. The question is why would someone want to sign up?

You have to think about competitive advantage. What sets your dating app apart from existing dating sites, already populated with 1000's of profiles?

I don't have a profile on dating sites (happily married), but I can imagine that a big problem for dating sites is people pretending to be different than they really are. That's a problem you could solve, for instance by only allowing profiles that have been referenced by friends/relatives. Heck, you could throw key parties (pun intended) where people could swap their credentials!

Or instead of a traditional dating-app, make a geisha-app. It's not a date, it's company.

Just throwing random ideas out there, but the general idea is either you cater to a niche, or you better have a massive marketing budget to take on the OKCupids of this world.
* But what has really changed?*

I would say being aware of the problem and its scale is a massive achievement. Awareness of the nature and scale of problem is the first step towards solution.
"What do we do, go over all the past laws that have been repealed, pardoning every one who was convicted along the way? That would be insane."

It's insane to pardon a dead person in the first place but, for the currently convicted, why would that be insane? Seems like a massive reduction in sentencing should at least be considered. Sure, they broke a law, but most of us do that everyday. Maybe the reverse wouldn't be so bad either. Could stop a lot of stupid laws from passing in the first place.
Acquia is the commercial company behind the development of Drupal, so understandably they're going emphasize Drupal as a great example of PHP ;)
I know Ruby on Rails isn't!
That is not necessarily an advantage, considering the same semi-technical people leave their websites available for any kind of security breach.
This is not 2001 any more, people should know what they are doing.
Show HN: Countdown – Twitter bot which tweets answers to the Countdown TV show
Ugh...must not take Lord's name in vain. 14 points in almost as many minutes? Is it so easy to get to the top of HackerNews on a holiday with such a loaded question? I can't imagine how many points the OP would've gotten if the title was "Is Ruby Dying Faster than MongoDB?"

That said, as a pro-Rubyist...well, I don't find much comfort in the OP's spurious assumptions about what the data can show. However, for those who think Ruby's time is limited or otherwise hate the language (or more specifically, Rails)...what do you think will take its place? Ruby seems popular because of its readable syntax...which is also a factor in its relatively slow performance...do you see an even more human friendly (and inefficient) language taking its place? Or do you think such a niche need not be filled?

That Ruby is so great for DSLs...I would hope that it can stay in that function as one of the better glue languages we have.
First off, popularity of a language shouldn't be as important as you seem to make it in starting a project. Finding the right tool for the job should be much much more important, new kid in town be damned.
Second off, number of package releases doesn't tell much about maturity of packages, developer involvement, or anything. Ruby's a mature language. It's quite feasible, and arguably desirable, for package releases to slow down in time. Styles have been developed, the urgency for new features to be rolled in Right Now is lessened, and the need for components that doesn't break on upgrades becomes more and more important.
Yes, the novelty is gone. That isn't a bad thing. You know Ruby's strengths and weaknesses, you know how to use it, you know how not to use it. Jumping to a new language just because of all the jibber-jabber is not a practical thing at all.
1. download pictures of female Harvard students using wget and apache index.

2. livejournal your progress.

3. tell your friends to look at the pictures.
Engineering utilizes science. But not many engineers need to know as much as Knuth.
I once answered the question of our launch strategy for OkCupid on Quora (here: http://www.quora.com/OkCupid/What-was-OkCupids-launch-strate...). A few things I can add:

1. You're right in thinking that bootstrapping users will be much harder than coding the site. A dating site requires not just a critical mass of users, but also a critical mass using it in a certain location with enough people that there are internal compatibilities.

2. We loosely categorized our users into 3 groups. (a) those explicitly interesting in dating. (b) those who would consider it, but who weren't ready to make the decision, and (c) those who would never sign up for our dating features. Our early strategy was to (try to) nail all 3 groups, arguing that there was mobility between b and a, and that group c could still be used to spread around dating-related toys without realizing that's what they were doing. All this led us to personality tests and a bunch of other goofy things that attempted to be viral but could also enhance a profile if converted. On average, 10% of our early users became online daters on our site, and the other 90% were spreading the word in one way or another, but we never heard from them again. As we got bigger, we slowly shifted our message towards the dating side of things, as those "growth hacks" diluted our message.

Of course this is not the only strategy. Consider (1) Tinder, a very simple dating app, which has become a phenomenon. I would say it's hard just to invent this phenonmen, though... And (2) pay dating services, which can collect membership fees and then use the money to market. It's an expensive game which requires a lot of cash and marketing knowledge.

Disclaimer: I left OkCupid a year ago.
Wait a minute. I see what you did there. Corporations get to think like the parent article (i.e. offshore programmers and call centers are cheaper, and plenty of outright abuses of labor and customers). Why don't regular consumers? Consumers have to account for morality, but corporations don't? That sounds fishy.
Is _a_ commercial company behind the development. The most important, for sure, but not the only one.
JPEG isn't crude, agreed. But your comments seem off to me.

The core trick isn't DCT per se, it is transform coding, Which both DCY and wavelets are, followed by (usually) quantization and then entropy coding.

Typical wavelets used are orthonormal transforms, no loss there. The "lack of texture and softened edges" are a choice of the model used, not a consequence of the transform. True also of DCT and blocking artifacts. This should be obvious since both approaches allow for lossless encoders.

Typically wavelets will beat or match JPEG in any situation both in terms of psnr and the like, and perceptually (though this latter is much more controversial and poorly defined -- and to be fair I am not up to date on the literature here but I would be surprised of that has changed in the last decade).

The real reason for the huge popularity of DCT in still compression at first and video codecs later is that it is cheap to implement in hardware. And once there becomes very cheap to use.

JPEG 2000 is needlessly complex, at its core a wavelet codec is also very simple and elegant.
>more focused on spying it's citizens than Stasi

How in the world is it possible to post something as ridiculous as this? Is this what you kids truly believe? Snowden might be colour blind, but you sure are tone deaf.
And when you've been writing code for decades, it becomes quite evident that "those other people" can easily be your past selves.
Disagree. Money does not equal freedom. I know plenty of poor people who live freely and plenty of wealthy people who feel trapped. What money really is is a placeholder for time.
For context, Acquia[1] was founded by Dries Buytaert, the founder and lead dev of Drupal.

[1] http://en.wikipedia.org/wiki/Acquia
I think there is a difference, Sacha Cohen (of Borat fame) plays a mega-douchebag but AFAIK he doesn't have a reputation of actually being one.

Their tactic may not be to your liking but they aren't the first to adopt characters as a way to promote their business.

As I said, the critic I have of them is that they're slily indulging in stereotypes and I am surprised they haven't been called out on that.
I actually had something similar a couple of weeks ago. My initial model was just:

val cards = for {
rank <- 'a, '2, [...], 'j, 'q, 'k
suit <- 'h, 'c, 'd, 's
} yield (rank, suit)
val deck = scala.util.Random.shuffle(cards)

which gives you something to play with to validate your model. It's not an api I'd choose to publish, of course, there are many better type-safe ones written here, though I'm sad none of them have used Unicode for suits (I know someone working on a dating app who used a method called ❤ to compare two users: so something like "if (sappho ❤ rhodopis > 95) { ... }")

But my point is that Scala gives you the option, and is tolerant, of working in this slightly dirty way, and then lets you clean it up (and a type-safe compiler will flag up where you are using your old api). I don't know clojure well enough, so, what's the similar workflow there?
I have a mathematical background, and I am not that attracted to Haskell. And I've tried. It seems that Haskell attracts logicians, which are their own particular subspecies of mathematicians, but I think far more mainstream mathematicians are attracted to Python. Sage is a prominent example of how easy it is for mathematicians to get into Python.
I agree that immutability is central to Clojure and the resulting code definitely reflects that. But managing state, as the OP put it, truly is what Clojure is all about - and immutability falls out of that very deliberate design decision.

Let's not confuse the lack of significant STM transactions with refs and its irk with representing the totality of Clojure's concurrency story. Many Clojure libraries make use of atoms, agents, and dynamic scope (which is arguably a concurrency primitive, given the thread locality of the bindings, but not unique to Clojure).

While "concurrency is not parallelism", parallelism is a special case of concurrent programs that is often challenging. Clojure's offerings here too are compelling - we have the amazing Reducers library which allows you to write higher order functions for collections that, as Rich Hickey put it, "know how to reduce themselves" - and get parallelism (without locks, without even thinking about it really) on top of that.

And then there's the lazy parallel functions - pmap, pcalls, pvalues. Check them out if you haven't. I use Clojure often in a machine learning context with Hadoop/Storm, these abstractions are highly valuable in crafting solutions.

Futures/promises are also widely used in Clojure.

I'm confused as to why you think data structure literals are part of Clojure's core thesis. Perhaps I just don't understand what mean - are you saying that the fact that the Lisp reader can read strings as data structures as being part of what Clojure is about? If so, that statement would apply to all Lisps, not just Clojure.
Citing this is such a knackered HN cliché it should mean an instant hell-banning.
Google trends:

http://www.google.com/trends/explore#q=python%20programming%...
I didn't start using Ruby (or Rails) until this year. The language is nice and makes my top 3 language list.

That said, I find both Python/Django and Node.js both more productive than Rails for quickly building API-driven web-apps. More so this has to do with Rails, which has a number of warts and a tendency to require excessive configuration for all its pretty much patently false 'convention over configuration' spiels, than it does with Ruby.

If there's a problem with Ruby, it's the inseparability of it and Rails. As things like node make using non-JS languages server side less appealing, use of Rails will decline, making Ruby decline.

The main reason this hasn't happened is that there's not a standard groupthink-do-it-all toolkit for building things with node yet.

And even when it does happen it will take years and years to go away. Just look at PHP.

I'm going to go ahead and say it: Ruby will be the new PHP...

And yes, I think it's fair to assume that Ruby usage is vast majority tied to Rails.
I think what jerf means is that, being mostly used as a scripting and web language, it's easy to create legacy code in it. Remember ColdFusion? PHP 3?

However, more to your point, there's legacy C and Java code, but that's because those languages have evolved heavily in their time, so late 90s Java looks little like modern Java, and techniques used in C in the 80s would get you laughed at today.

Hell, even in my main language of work, C#, the difference between most code just 4 or 5 years ago and "modern" C# is vast.
It gives you a default that isn't very pretty. Python also has a default that isn't very pretty.
With javascript:
http://www.google.com/trends/explore#q=python%20programming%...
Of course you can write crappy code in any languages, and conversely you can write nice code in most languages (perhaps not in INTERCAL or Whitespace).

Personally I prefer Ruby over PHP for precisely the same reason I don't begin my day by shooting myself in the foot.
Yes, apparently that is the go-to sales pitch.
Have some easy method for people to block or report others who send inappropriate messages.
my question : is ruby trying to get on pair with python regarding machine learning ?
"All I wanted was for the public to be able to have a say in how they are governed".

If these are his words to be remembered by, history will have kind thoughts for him.
Farther, not further, when referring to distance, even if that distance is figurative.
PhD?

God picked me for His temple. He infused me with divine intellect. Go see. http://www.templeos.org If you don't like it, yer a nigger.

God says...
informed heal seems enlightening list daughters Lo sharper
veiled readable wishing mouth drawn stayed spiritual an
hand belongeth tamedst led oracle Powers lust sights achieve
exaltedness treachery greeted off WARRANTY mountains Eve
horns instinct incommutable indigent wedlock disquiet
regular MERCHANTABILITY slackness resend
Not the OP, but I would expect to see still widely used:

* Python - As a programming language for scientists and researchers, replacing Matlab and kin.

* Go or Rust - A well-designed, modern language, easier to use than C++ but almost as fast, for enterprise applications or video games. Not sure about Google, but I hope Mozilla will still be around in 10 years.

* Lua? - Not sure about this one... but it fills a niche -- extremely compact scripting language.

* C - still used in system-level programming

* C# - C# is replacing Java as the OO language of choice for big enterprise systems.
For all that, the more popular a language is the more packages are available and the easier it is to avoid reinventing the wheel and save time and effort.

Even the wrong tool for the job is a nice choice if someone's already done the work of making a square peg fit a round hole for you.
NSA calls iPhone users ‘zombies’ and Steve Jobs ‘Big Brother’
Sounds like you're honoring yourself. Carry on.
Reverse-engineering of Evasi0n 7 by Geohot
That's pretty fascinating...I studied C in college and didn't hate it (in fact, I'd like to go back to C some day)...but my perception since has been that not much has changed because not much needs to change. I'd love to see a paper or article looking at innovations or change in practices in these older languages.
A couple of awkward things with docker:

* Each container is kept indefinitely and it's up to the user to adopt a garbage-collection strategy.

* Images built with a Dockerfile contain the build dependencies even if they're not needed at runtime. That has to be a better way.

* Docker is still single-host. If you want to scale horizontally you need to build another layer on to to run the containers on different machines. But then features like container links don't work anymore.

* Unlike the real physical container it actually matters what's inside the box. You can't run the same container on different CPU architectures.
why did you leave?

[ ] found someone.

[ ] too much ad.

[ ] spent too much time.

[ ] other. Specify ________________.
Cannot agree more with you on that last comment. I personally think - and hope, as a full-time Ruby dev at this moment - that Ruby will "recide" (big quotes here) to a more "humble" spot as a glue language; i.e. Perl's spot 10-15 years ago.

Not a bad spot to be in if I may say so.
Ruby is only dying in the sense that C is dead. It's not that exciting, but instead is widely used, including by companies.

Additionally, I doubt gem releases correlate with language 'vitality'. Fewer releases may simply indicate library stability.
Why is Canada naming its warships after U.S. defeats?
Btw, if you want Lambdas now, you can try this project:

https://github.com/orfjackal/retrolambda

"Retrolambda lets you run Java 8 code with lambda expressions on Java 7 or lower. It does this by transforming your Java 8 compiled bytecode so that it can run on a Java 7 runtime. After the transformation they are just a bunch of normal .class files, without adding any runtime dependencies."
Back in my uni days, aka not that long ago, the scala (which I love)/perl (which I hate) comparison is what made me realise that language arguments are almost always pointless. Any choice you make in a certain class of language is probably going to be roughly equal in terms of ease of use, productivity, whatever; so you might as well just go with what you are comfortable with.
WordPress is great software, even if it isn't written well - from the end user's point of view, it is exceptional.
I live in India. I know that dating sites / apps don't work in India. People are more conservative here.

Can some one from US/ Europe/ South America throw some light on dating scene in their countries. Do the dating apps / sites like okcupid work well ? Or is there local sites that do better ?.
> Do you think that every vendor purposely downgrades the mobile experience(even vendors like samsung which don't have a reason to favor native vs. web apps)? It doesn't make sense to blame mobile safari, chrome, and ie mobile when google, apple and Microsoft put a lot of resources into their development.

They put far fewer resources into the web on their devices than they do the native sdk. For example, last year Google created "Project Butter" because people were complaining about touch performance on Android. There is no Project Butter for Chrome on Android, even though it has touch responsiveness issues too. Why? Because the former costs them sales of phones and the latter does not.

This is why Firefox OS is important. They are putting all of their resources into making the mobile web better which, hopefully, will lead to a better mobile web on other platforms as well.
Smart Entrepreneurs Don’t Overstay Their Welcome
Reverse-engineering Instagram to access the private API
I don't understand the problem mentioned with HTTP Basic, username/password injection
into the uri https://username:password@such-n-such.net works just fine if for some reason you can't set the header explicitly. http://tools.ietf.org/html/rfc3986#section-3.2
Wow, that's really neat!
Yeah, I had the same thought about "Rachel from Card Servives" robo-calls. Apparently those go through more-or-less illegally obtained cut-outs, but the NSA is in a unique position to go after those Card Services jerks.

Then I thought, hey, it's just like bus transit: the rich folks don't ride buses, so that kind of utility gets no money. The NSA, uh, people, don't get robo-calls, so they don't see the problem.
This is it. I'm blown away by how productive I am with rails now. A couple of weeks back I replaced an entire backend, complete with an oauth provider, record versioning, caching etc. and it took 4 hours! And all done with the usual TDD etc. This is all thanks to the gems that are available. Most of them are 2nd or 3rd generation, they're focused, battle tested and well documented. It might not be the right tool for every job but it's damn good at what it does. If the noise has died down it's because we're busy knocking out great apps.
True but:

Code people, should be open to learn theory when needed.

CS people, should be open to understand that writing code is not marginal and takes a lot of time to master.

Probably more cooperation would be needed.
Ruby is maturing, not dying. It has lost much of its fadish hype.
"To be perfectly fair" implies that it shouldn't count. Does the Premii app demonstrate what can be done given the effort?
I think Perl has already reached the state where it's mostly used in legacy code, at least for web development.
Because "no server-side code" means "I can host it completely on a CDN", which pretty much solves the scalability needs. If you need to scale those few lines of php or whatever language, this is gonna be much more difficult.

Plus, you can host it on different platforms such as freenet, gnunet, and have the simplest backup ever (`cp` is enough for having a functioning version on any OS of any kind).
If you are willing to spend some money for an initial burst of users, try advertising on https://ads.pof.com/. Plenty of Fish is one of the largest dating sites and their self serve advertising platform is fantastic. Make a few accounts in various demographics to see what works. (hint, make a targeted landing page to your ad/demographic .. works better than a generic one).

Otherwise, a web property that ranks for certain keywords can still go a very long way. Make a blog dedicated to dating tips and advice. Write posts targeted at people struggling to find dates, or who are not having success with current dating sites. Write about how to use dating sites effectively. How to act on a first date. There's lots of information on the internet already about this, so it doesn't take too much creativity to pool some resources together and make a quick blog post about such topics. At the end of your blog posts, suggest your dating site/app. People who just read your article are filtered to be your target audience and will trust your recommendation about what dating app to join.
No, a corporation will do anything to increase its profits - or more accurately, dominance of its market. Anyone that can pay will get. With an added bonus of obscurity.

As an aside, when you think of corporations try not to think about the imagery they bathe you in. Think of a serial killer sidling up next to you all smiles and compliments. That would be more accurate.
I thought OKCupid was a rebranding of SparkMatch, which in turn used the audience from the spark as its initial userbase.

So wasn't there already an established userbase in their case?
Bingo. You nailed it.
$10M says the NSA is a valued customer.
Hmm I've found the latest versions to already start up very fast. What are you comparing against currently? I use command line tools written in Java all the time and don't really notice it.
Go to the real link and try it out: http://jsxgraph.uni-bayreuth.de/wiki/index.php/Circles_on_ci...
The Next Big Thing You Missed: A Mobile OS That Doesn’t Care What Phone It’s On
Besides the obvious violation of individual rights, I worry about the enormous potential for abuse in these programs that could quickly turn our democracy into a dictatorship.

Systems designed to identify terrorists could easily be used to identify political opposition and supress them once they've been labeled as "terrorists". The lack of due process, transparency and checks and balances here is concerning.