skysight-inc/HackerNews huggingface dataset:
I started by learning what the company used; Java, PHP, Ruby, Bash, C. From there I picked up Javascript, Go, etc.

Personally, I pick the thing I'm most proficient in and enjoy building with. In a certain context certain languages make sense. Dynamic scripting can be useful for rapid development. Javascript is usually a must for frontend or simplifies code sharing longer term. Backend you usually need something more performant so after much searching I finally found Go to be a perfect fit but again thats a personal preference.

If working with a team I think it complicates things slightly. Now you must take everyone's skills and opinions into account. If working within a company you need to think about hiring and longevity of the code base. That's where normally you agree on 2-3 languages, again based on context and what's fit for purpose.

If you're just building something for yourself, go with what you're proficient in. If you want to learn a new language, pick one and build something to learn the language. If you're working with a team, democracy usually wins.

Hope that helps a little. Just my opinions and what I'm used to. Not gospel.
Yep. Same for Bitbucket. Or just support all git repos that are accessible via the public internet.

Github's pricing model means that lots of people can't use it for private repos - 'per repo' pricing isn't fun if you prefer lots of small repos.
Disabling the FM chip function doesn't make 3rd party radio apps any less discoverable.
Meet the San Francisco startup that's creating a future for Polaroid
1. Which language you know the best.

2. How well this language is suitable for a given task.

3. If language you know the best is not suitable, pick second language you know best and repeat 1. and 2.

For example, you wouldn't really use Go to write big, but traditional web application. You'd use something like Ruby, Python or PHP (maybe Java too). So pick among these.
That would be super cool but you would have a battery life of like 60 minutes.
Why Most Startups Suck at PR and How to Fix It to Get More Press Right Now
What is the churn like from GOOG to startups?
If the problem is programmer bound, I use Ruby / Rails.
For CPU and memory bound problems, Go.
For very JSON and HTML centric APIs (Elasticsearch, documents), or for those the involve executing JavaScript from untrusted sites (scraping), I use NodeJs.
They couldn't think of a good one, or they don't want the hassle of changing it.
Them gauging technical competence solely through personality traits like "curiosity", "discipline" and "fearlessness" raises a red flag.
A year ago or so, on the front page, there was a post saying that the minimum salary increase after the suit might be done so that there would be less liquid assets (cash in the bank) to split. Because, if I remember well, Lucas wanted to get a share of it. Or something similar, which would make the increase not such a philanthropic thing as it seems at first.

My memory might be failing, or the post back then might have been not based on facts (IANAL, nowhere near that). But that's what I remember :)

Maybe somebody can correct me?
Agreed, I'll definitely the ability to move your dependencyci.yml file into a .github folder like the issue and pull request templates: https://github.com/blog/2111-issue-and-pull-request-template...
CEO of JPMorgan Chase: Why We’re Giving Our Employees a Raise
Well it depends the nature of the project you're starting from scratch. If it's a new project at your employer, there could be factors like "how easy would be to hire / train people to work on this project in the future?" or "how mature this technology is / how likely is it that unknown problems will bite us in the ass in a few months or years". But if it's for personal use, I guess it's a matter of what your main motivations are for it. Personally, if I'm building an MVP or in other words, my main reason for building it is to get it in front of customers ASAP, I probably go with the stack I'm most familiar with. But other times I start a project just to play around, learn or get more familiar with a new stack, so then I do just that.
> I suppose long term FM is dead, but meanwhile it has its uses.

If true, this is really unfortunate. I've written about this before, but FM is a really great technology, and in a lot of ways it's only suffering because of the content. The sound quality of digital "equivalents" (XM Radio, HD Radio, Internet Radio, etc.) doesn't even come close to a clear FM station.

Not to mention there are millions of vintage radios that still work perfectly today with this technology.

For being invented in 1933 it's pretty amazing.
Facebook serves to mobile phones in third world countries.
I use a language that I enjoy hacking. These happen to correspond to languages I understand very well in case I need extra features.
System default would be leaving the font family unspecified, no?
Currently only supports GitHub but bitbucket and gitlab are on the todo list as well
All the deals Apple made with the cell co's to get their users to suck up the bandwidth, duh. Cellular Data rates being what they are, I fail to see how anyone cannot see the profit motive. If you're listening to Spotify instead of FM radio, you're fulfilling one of the promises Apple made to the cell co's: we will give you users who will use our phones to suck up Cellular Data ..
> people are not aware of the health implications of
> being overweight

> others may call "bugging me about my own choices"

I believe that I will bear the health and related collateral costs of obese people via my contributions to my country's tax system.

I will also bug you if I see you dropping litter in public places or smoking in an enclosed area that also encloses me.
Pound to Dollar Exchange Rate Forecast: 'Fed Won’t Hike Rates Until December'
In my freelancing career I usually choose the language with the following Q&A to my colleagues ( myself, if it's a side project ).

1. Are there business requirements for the language ( already written project, specs, etc. ) ?

2. What kind of budget does the company has for hiring devs ( killing point for Clojure, Elixir, TypeScript, etc. ) ?

3. What's the most difficult problem that needs to be solved by the product ( you probably don't want to create a 3D Game with NodeJS, right? Or a highly dynamic charting with PHP ) ?

4. Is there going to be a front-end / back-end division in the team ( Having a division makes you more comfortable in choosing the back-end language, since most full-stack devs are using NodeJS/PHP/Ruby ) ?

5. Finally if you are working on your own task and previous questions didn't give you the right answer, you could ask yourself : Do I need to learn something new or I want to build something fast?

At this point you will have eliminated most of the obvious choices. Recently I'm using Isomorphic TypeScript with NodeJS for most of my side-projects, but first thing I will do if something goes above a certain amount of users is to start thinking business-wise and answer those questions on my own.
In fact, they do.
original Playstation used similar copy protection trick - ASCII string SCE(I/E/A) was stored in pregap pre-groove wobble between the leadin and the first track. PSX used Three-beam pickup and was able to track this wobble and extract code from radial tracking error signals. Modchips simply injected same error signal for couple of seconds after closing CD lid, enough for the CD controller to recognize it as "original".
Oh god this is embarrassing to be honest.

There is no one "interest of the people". There is no "people". There are different groups with different interests. Or are you proposing dictatorship of the proletariat? Because we know how that turned out, don't we?

If you want evidence of the above you need to look no further than a couple of weeks back to the Brexit vote. You have it there all.

- There is no disproportionate political influence by the rich. The majority of the rich said "don't do it! PLEASE FOR THE LOVE OF GOD DON'T DO IT!".

- There is no rich vs. poor. One of the richest, most influential people on Earth, Rupert Murdoch, used his media influence to sway the vote in favor of leaving.

- People unable or not interested in forming a balanced opinion. The decision was made because of demagoguery and blatantly false claims.

- Power-hungry, opportunistic politicians riding the wave, no matter what the wave is and then back tracking on their promises and claims.

Same thing happened in the Greek elections. A politician came, promised all sort of things, and in the end did exactly the opposite of what he promised.

So in the end people acted against their self-interest. Because they don't know what their interest is and because politicians tricked them. Story as old as mankind itself. There should be no need to "prove it". If it wasn't self-evident, then you are just out of touch with reality. But here you go, I spent 10 minutes explaining things that should be self-evident, to people who claim that they understand the politics and science of reconciling interests and opinions.
I know plenty, due to both an active family reunion group and due to genealogical research. It can be pretty fun learning about your ancestors.
For a personal project I usually prefer to get done with development as quick as possible so I choose the one which I am most comfortable with.
NATO crawls by Western air borders of Russia  would be a siege?
InstallMonetizer (YC W12) is officially closed
Except this isn't GitHub specific.
The ideal solution is a migration path; retain support for config in project root, but check a configuration directory first.
'Cryptonomicon'. Of course..
FALSE: Everyone knows that the Nazi's aren't on the moon that was just a diversion, they are in the hollow earth...
The Principle of Incomplete Knowledge
This resolution really only has teeth so far as the US Navy is ready and able to enforce it.
I didn't know this wasn't something all phones had. I love random FM radio when I'm on a walk. The moment I hit an ad in just seek and listen to something new.
More dangerous still are garbage collectors.[1]

What is your point exactly? My point is that being a police officer is not as deadly of a job as they insinuate (note that most police officers die of heart attacks and car accidents).

[1] http://time.com/4326676/dangerous-jobs-america/
It didnt. 20 years is a lie/marketing/ignorance. There do exist CD emulators (Rhea) and there did exist modchips during console heyday.
Personally I feel most comfortable in Python / Go / Java - while I have no problem kicking off a project in another language, those three just happen to hit the sweet spot for me for different use cases while not getting too much in my way.

I assume we are talking about some side / hobby project, not starting new projects for a client?

One thing I usually take into consideration is if there are libraries or frameworks that will drastically reduce the amount of boilerplate I have to write.

Starting a web application in golang for example is surely possible, but while deciding on a router, template engine and datastore I can already start writing code in Django / Play / RoR.

If it is not an experiment to get to know a language or language specific features I usually prefer to go with some battle proven libs I can rely on and try to not reinvent the wheel.

Another thing to take into account is what kind of app you are actually going to build. Small CMS for a non profit? Crunching lots of numbers? CLI tool? Will you have to maintain it? Does it have to scale? How much time can you put into maintaining and scaling?

Those questions alone should already reduce the number of choices. For a simple CLI tool you could package a VM or require the user to rely on package manager and language which is installed on the system or you simply use a language that compiles to an executable.

So I guess my checklist in order I ask myself the questions:
1. Does one of my goto languages fit the project?
2. Are there libraries that would help me build it?
3. Which language of the remaining ones annoys me the least?
A dude with whom I went to elementary school married his first cousin here in USA. This was in a red/"statute bans" state by the map at your link, but I never heard they had any problems from it.
Ask HN: What is the emerging state of the art in fuzzing techniques?
I'm fairly familiar with the popular tools such as afl and Codenomicon Defensics. But I find the academic literature very opaque and don't really know where to start.

If I want to understand the cutting edge of fuzzing techniques, and what will be the emerging state of the art in the next few years - where should I look? Any good papers or books (with at least some for novices to understand), or research projects that are leading towards a new excellence?
There are two obvious objections to that:

1. If a person is uninformed about the consequences of their decision and the alternatives that they could choose from, is that a voluntary decision? I think it would be very difficult to actually defend the position that the majority of software users decide voluntarily to use proprietary software.

Sure, if someone voluntarily buys cigarettes and smokes, I guess they should be free to do so as well. From that it does not follow that you shouldn't object to cigarettes existing (and in particular to them being offered by vendors to the unsuspecting public).

2. Economists know a concept they call externalities. Those are effects that one's economic transactions have on parties not involved in the transactions, like, for example, pollution of the environment that other people live in. Non-free software very often has negative externalities, in particular due to network effects that lead to de-facto monopolies and lock-in. Negative externalities are a good reason to object to what other people decide to do voluntarily.
Pinpointing the phones and launching missiles at them might work better than DoS. I guess from the practical point of view, information on who's doing what helps. At least Turkey seems to have backed off supporting them which helps and may have been influenced by exposure on the internet eg http://www.mintpressnews.com/211624-2/211624/

Also feel free to donate to the Kurds who are the ones on the ground fighting this stuff. I did a not very good website for a charity helping the refugees there http://kurdistanrefugeeaid.strikingly.com/
>If Deutsche goes bust.. winter is coming.

For 90% of the world (ahaha), winter has already been here since 2008. It's about time the banks were exposed to the weather, I'd say.
Saints and Sailors
Depends on a number of factors for me. If it's a small, well-defined project, just go with whatever you're happiest in. If it's a large project or a large company, then go with who you can hire (eg. Java, C#, etc.)

Actual language/subject matter practicality is a relatively minor consideration in comparison. You're usually talking about some sort of performance/dev-time/cost tradeoff and short developer time almost always wins. So small projects go with a quick happy language, big projects go with a "enterprise" language designed for large teams. Ultimately they're both about reducing the total devtime.

It's very rare for any particular task to be tightly coupled to a language. I can only really think of a couple, Erlang and SQL. Maybe C/C++ for high perf jobs. Otherwise, since all Turing-complete languages can technically do anything any other can, you're probably going to waste more time fiddling about in a new language that might be more appropriate, than if you just got cracking in your everyday general purpose language.

Most considerations beyond the above are probably just going to be people's personal opinions about their favourite language. It's like arguing emacs/vim or tabs/spaces, not going to help much ;)
I am no geopolitical expert, but the Chinese seemed to be playing with fire. At which point a war will erupt in the South China Sea, especially when those nations won't take it anymore?
Now we're talking optimizing for a hugely multidimensional system here.

Expressiveness: If you've aiming for a large team, try to work with a language that enables large scale services and large teams - also in the long run, strongly typed languages will work out better for this case, Java / Scala being the obvious candidates. But if you go down a microservices route, other choices might work too.

Niche stars: Some languages have obvious strengths in certain niches, depending on what you want to build. Machine learning - Python, Microservices - Go, isomorphic JS web servers - Node.

Performance: Very many requests -> closer to the machine. Note that JITs have skewed this equation somehow towards being able to use scripting language, but it still generally stands, because if for some reason you can't track, code is falling out of the optimizer after a one line change, you're still screwed. Closer to the machine is more predictable.

Maturity / Current traction / Traction curve: Brand new is shiny and attracting bleeding-edge devs (making hiring easier), but be prepared to be the first one with a problem or having lots of devs around who love tech more than results and are gone for the next shiny thing in half a year. Lots of current traction is good, rather don't choose languages that are great but on the path down (Ruby). Be extra careful in choosing too exotic languages, you won't be the first company dying from not finding any devs for your ageing Groovy on Grails stack.

Availability: PHP and Java are safe bets, but it's much harder to separate the wheat from the chaff developerwise. Languages like Go or Clojure will find you more driven devs usually because they're not usually taught at university. Caveats: see above.

Lots and lots of other variables here, just some of the larger thinks to think about.
It would be cool if it can be used like rtl-sdr, right on the phone.
There are several things I might consider, but this is by no means an exhaustive list:

* Tech fit -- how does this technology solve the business problem? Have you considered how the overall architecture will look like? You might end up splitting them up to several different components each potentially valid to be written in different languages, depending on their nature. Given that, what do you need to achieve? Perhaps a Rails app is fit for purpose if you're writing a proof of concept. Or you might opt for a language that has established libraries for exposing a RESTful interface and write an SPA on top of that. My point is that it really depends on the business problem and how that is tackled.

* Ecosystem -- are there libraries out there that help you do what you need it to do? Will you have to roll your own?

* How will it be maintained? If you're not working for yourself, then you can assume your code will be maintained by someone else. Is the technology chosen accessible for your intended audience? Like you said, if it is a xyz shop, then it might make sense to write it in xyz. If it's a polyglot shop, then perhaps this is less of a consideration.

* What are the development tooling like? IMO this is quite important for my sanity because I dislike using clunky tools.

* How will the code be pushed out to production. Are there established best practices for pushing the code you're written in xys language into production?

* How easy is it to write tests for the language?

Something to also consider is whether it is good for the future. There is an element of YAGNI here, but it's worth considering the longevity of your technical choices and how easy it will be to upgrade.
Oops. that's what I get for commenting before the first coffee...
We are looking for Beta testers at http://2Factor.in
Hi,

We are looking for Beta testers at http://2Factor.in for our newly launched International OTP Delivery Route.

2Factor so far been focusing on Indian market only, but as some of our users demanded for International OTP delivery, we thought of giving it a try.

It would be great if you can help us in evaluating these carriers and our platform as well. You may register for a TRIAL account at https://2factor.in/CP/register.php

( Drop us mail for enabling International OTP Route )
We have tried to lower International OTP delivery charges by upto 20-30% over the existing well known competitors. ( pricing available at https://2factor.in/CP/2FA_INTL_Pricing_list.php

Your feedback if appreciated.
The thing is, most projects can be solved by most languages and frameworks. Apart from some special cases, there isn't usually that high of an impedance mismatch. This means that you have to look to other factors to decide... things like:
* Tooling support
* Talent pool / ability to hire
* Available resources
* Support / stability

FWIW, the last time I had to make this decision, I went with Python--a language I had never used before. No regrets.
Senate votes soon on giving the FBI warrantless access to browser history
It's more about frameworks than languages.

You're already learning 2 languages a year. That's not so hard. The surrounding tech is the bigger investment.
REDLIGHT-SEDUCTION  Rome Escorts
Show HN: Space Machine:Run Android from Your SDCard.(Semi-Portable OS)
Space Machine : Rooted app that allows you to run Android from Removal SD Card. This supports running mobile apps directly from SDCard, so you can carry the SDCard and insert into another Rooted mobile, start using your apps, contacts, photos, mails just like the original mobile.

You can use multiple SDCard provide different profiles and view of same device. This allows you to customize or hide apps based on the needs. Increased Internal Storage depending size of SDCard. Kind of semi-portable OS on your SDCard. Right now, its available only for Kitkat users.

https://play.google.com/store/apps/details?id=in.co.giis.SpaceMachine . I would really appreciate some feedback! cheers.
Under Beta-testing for other versions: https://plus.google.com/u/0/communities/113253726177871964982
* Golang for something CPU-bound, small apis that should be really really performant

* Elixir/Phoenix for mostly everything else, including REST APIs, regular web-apps, various chats, backends for games, mobile apps.

How? It should be easy and fast to write some functionality, easy to add functionality on late phases of development, it should be "secure by default" (e.g. autoescaping untrusted input, cross-site-scripting protection on by default), fast enough for your task (usually all the langs fast enough but 10x is 10x :) (rails vs phoenix)). You'd also want to check for specific requirements of your target architecture (e.g. processing video, websockets)
Scala is missing from your list, it has a wider adoption than Clojure and battle tested stack of frameworks/libraries such as Play, Akka, Slick, Spark just to name a few.
Elon Musk’s pedestal is crumbling, exposing Tesla risks
Unattended Network Installation for SLES11 SP4
Considering my arguments above, I can conclude that React and Angular 2 have niches that only moderately intersect, so it's not going to be a single winner out there.
I have a personal rule, which I've shared on here before and people seem to think has some merit:

If a project is innovative in a business sense, then choose a boring technology. If it is boring in a business sense, then choose an interesting technology.
JS required? For a list? Seems rather excessive.
This is like asking a group of artisans what is the best kind of timber to make furniture out of, I'm afraid.
Workable. It'd be nice to clean up the global namespace a bit. Especially when it's a single-repo project.
Would you recommend some resources that might help me more understand genome sequencing and its consequences? I too was thinking that the author could have go deeper and explain more in the article. I am computer scientists with high school biology knowledge.