skysight-inc/HackerNews huggingface dataset:
To try and define an entire nation of people in one article/comment with a few fancy words is down right silly.

I've lived the last 10 years around Øresund, in various places, and the best explanation of the danish lifestyle I've heard was that they don't expect success so they get more happier when they have it.

But I only enjoy that explanation because it fits into my little belief of how I want people to be. It says nothing about how people actually are. It's ridiculous to believe that there aren't people who strive for success and material wealth in a place so well developed as Denmark.
Even if passive income is easy, it's not for everyone. I've been doing consulting work the past couple of months and can have 1-2 days of straight work pay for my entire week. Unfortunately, the free time isn't as fun as you'd think since almost everyone I know is working full time jobs. Maybe I'm more social than most but having free time without being able to enjoy it with others isn't something to strive for.
It doesn't matter. The old domain issues a HTTP redirect, so it's effectively dead from a marketing perspective.
Would they have been able to retrain existing employees to fit those new positions?
There are a few open source libraries for managing CoreData from a higher level now (like NSOperation for GCD).

This post by Mattt Thompson (of course) on NSHipster has links to wrappers, adapters, synchronizers and utilities for working with CoreData: http://nshipster.com/core-data-libraries-and-utilities/

I highly recommend reading that before starting any CoreData project, and reading over that whole site in general to add new tools/concepts to the Objective-C and iOS Framework toolbelt.
And you can still run OSX on it...

This is my current setup (minus the drives / SSDs I own already): http://pcpartpicker.com/p/1mjxn

Runs OSX 10.8/10.9, Arch linux and Win7
A month ago, in a similar thread like this one, someone posted their side project [1]. It looks a lot like what you described. Sort of like flattr for musicians. Me personally, hope that it will get bigger exposure and gain traction. It seems like a viable model.

[1] http://musiclove.rs/
Juiiicy, the holy grail
Not a professional musician, anyway. As you imply, most musicians are never paid for their art, and that has always been true.
The scary thing is, I thought it was legit until you pointed that out. The worlds take on surveillance makes me sad.
That "totally fair" $10/month figure is the problem.

Spotify's benefit to the consumer is they pay less for listening to the same music. Compare that to iTunes which doesn't save you any money, it just makes it a whole lot more convenient. (As an aside, I was far more appalled by the discrepancy between retail albums and iTunes albums: Both cost the consumer $10, but the label gets 5x more from iTunes while the artist gets slightly less than the $1 they get from retail.)

You can save the consumer a certain amount of money by cutting out middle-men, but at the end of the day if consumers are paying less money the producers are earning less money. It only makes sense to the producers if it doesn't cannibalize their existing revenue streams.
"English pub food is paid for at the bar with your drinks, that you yourself walk away carrying."

In my experience it's more normal that you order your food at the bar, and a member of staff then brings your food to your table. A tip isn't normally expected in this case.

In a gastropub your order would normally be taken at your table and you'd tip just as if you were in a restaurant.
> I guess it'd also be interesting to exclude devices by other characteristics, e.g. exclude all <4.0 devices because maybe you don't want to support them anyway.

Android 2.3 has around 40% of the Android market. I doubt many players can do it. Some companies still want IE7 or IE6 support.
Pretty sure they're referring to the cost of the computer + parts...Also, its like $400-500 for parts unless you have a [fairly] recent graphics card just sitting around
> The report does not have any findings about what MIT "should" have done

Well then what's the point of the report other than allowing MIT to wash its hands? Great timing on the release as well since it will likely be forgotten and hidden due to another big event today.
the conclusion seems odd when the test actually exploits typoglycemia
I'm sure that euphemism is based in experience, but as a Canadian, I've found that most of my compatriots (myself included) feel it's only polite to tip at least 20%, and we're VERY IN TO BEING POLITE. :)
That isn't at all what he said. He said that if people stopped making music professionally, people would still make music. Professional, commercial music is a relatively recent phenomenon. Music wouldn't stop existing if it stopped being sold.
Or just UK orientated news for ex-pats like myself.

When I worked at BBC News we split the site into "UKFS" (uk facing site) and "IFS" (international facing site) but let readers pick via cookie which they wanted.

Since I left they changed it to always set to your region, which is always frustrating.
Flat or not, this is how I feel about UIs built by programmers before Bootstrap was available: http://www.youtube.com/watch?v=-MC7GrDS8TE
> Is there a reason I should still try clojure?

Probably not if you want to keep that Haskell background. I feel Lisp/Haskell have very different philosophies and you might not like Clojure's.

OTOH, stepping out of your comfort zone is always a great way to expand your views (even if you hate Clojure at the end).
Probably GeoIP. Visiting bbc.co.uk from abroad always weirds me out because of the ads, restricted content and international centricity.
No, it wouldn't. Minify the css and gzip it is more than enough. The best you can do to reduce page load times anyway is to reduce the number of requests, so the best strategy would probably be to aggregate all of the css files into one, and do the same for the javascript, to minimize the number of requests.
Cyclemon / Experiment
The sbt site ( http://www.scala-sbt.org/ )is still impenetrable to anyone trying to understand wtf it does in under 15 minutes. (Why do I need this? How is it different than the scala compiler? Is it a package management system? Is it a REPL?)
Ask HN: How does one write clean database access code without an ORM?
Many on HN have branded ORMs harmful, suitable only for toy projects where performance doesn't matter and complexity is low. I understand that hand-crafted SELECTs can be more efficient for complex queries, and when things get hairy with an ORM I almost always use its find_by_sql (or similar) functionality.

But a lot of HNers say ORM should be avoided entirely, and I am inclined to believe there's some truth to that. I'm fairly comfortable with SQL and know where to look to learn more, so that side's not a problem for me. But I have a couple of questions:

1) Why shouldn't I use my ORM for the simple CRUD parts of an application, and only reach for raw SQL when doing complex SELECTs?

2) How does one write clean, efficient, maintainable code for dealing with results of SQL queries? Am I supposed to be iterating over row.next to fill an array and identifying columns by numerical array indices like when I first learned to write spaghetti PHP, or what? Should I be using these all through my business logic, or am I supposed to invent my own crude ORM for that?

3) Very smart programmers have asserted that relational data is not object-oriented and we shouldn't try to make it object oriented. But there are so many cases where Django ORM and ActiveRecord idioms just seem perfectly natural, and anything involving the words Cursor and ResultSet don't. I understand that raw SQL can shine in terms of specifying the query, but what is an example of a case where it's cleaner to process database results manually?
They're making strong progress on this by making the Play services independent of the OS and with all their other apps on the store. Android is still much more modular than they're making it look though, and it'd be great to see their launcher, lock screen etc all as downloadable, individually upgradeable apps too.
This is so perfect, a parable for our age. A man with balls but no guts, deferring to the sort of terrible decisions made in boardrooms everywhere. Even when he knows what he wants, he wants the decision to come from someone else.
It's a terrible system

I believe in pay for performance in all professions so I certainly would prefer such a system for a hospitality industry. The minimum I've ever given anyone for a tip is 15% and honestly the service has to be terrible for me to give that. If the service is good I give 20% and if the service is remarkable I'll give more.

The way I think of it is that the cost of the meal is at least 15% to 20% higher than what is on the menu. If I don't want to pay that, I eat at home.

I don't get wanting to pay 15% to 20% more on the menu and then having no ability to give an incentive for people to perform better.
Maybe this depends on your age. A lot of people learn to code as a child, and at that stage you're really not doing anything full time.

Starting as a 10 year old, I began learning to code and spent maybe 20-30 hours / week on it combined with school and friends. All of that time was during nights and weekends.

I think having a real project you want to build is a good start. I also think that a keen interest in the topic and a passion for learning will overcome most other obstacles.
You didn't look far enough. There are Androids and Windows Phones / Tablets to the right.
Sure, but what's that got to do with hardware fragmentation? All those problems were caused by Windows itself and the lack of updates and solutions, not because Windows ran on tons of different hardware.

As for complaining about different distros: that depends. For some time I've tried to solve that problem through a project of mine, Autopackage (now defunct, website gone; it's still on Wikipedia: http://en.wikipedia.org/wiki/Autopackage). But we met a lot of resistance from distribution people and even from users. The view was that each distro is its own operating system and shouldn't bother with compatibility with other distros. Heck binary distribution is only for closed source software, was what they said. In the end there was not enough support.

So no, I've not seen people complaining quite as much about Linux distro fragmentation as about Android fragmentation.
If you peek into the dataset (fragmentation_model_July_2013), these are some of the first few entries:

DIGMA iDs10 3G
!QU SMILE advance
\002\""
(MC605CH)
*#? (^?^)=?
001DL
001HT
003Z
007HW
009Z
06_v89_hjy1
06_v89_jbla768_asx

How on earth is a firm supposed to make sense of nonsense like that to inform their device targeting?
> We understand gravity to staggering levels of precision.

If I understood the parent correctly, the argument was that the brain was still a 'black box' in that we don't understand how/why exactly it works, therefore it's sketchy to use it without the public knowing that it's 'just a model'. The point is not that gravity is anything like psychology, but that they both seem to share the same predicament with regards to their origins. It'd be naive to say that we don't know much about it, but if I'm behind on some findings that detail what gravity is, that would be helpful feedback.

> This is partly because psychology is such a young science in comparison

Exactly. This is why discrediting it as a legitimate science when it needs all the cross-disciplinary help it can get is so unnerving. We aren't gonna make inroads into understanding ourselves too quickly if we raise a generation of people to dismiss it like that.

>I am not sure if it's psychology/neurology or relativity/QM you lack a firm grasp of but it appears to be at least one or the other.

Both my good sir! (academically speaking anyway). The point I was emphasizing was the relationship, not either science -- thus, unless I'm wrong and we're convinced the effects of relativity are not emergent from QM, I'm not sure how it makes a difference? What seems to be disingenuous is dismissing the metaphor (read: literary analogy) for not being in complete 1:1 correspondence in practice -- it was a conceptual point. I was talking about forests, and you seem to be talking about trees. But if you feel I lack some critical knowledge about said trees, please do try to clarify your point, because I've received a fair number of upvotes for that comment so I think a good number of us 'laypeople' would benefit from such an analysis.
I'm not sure where the term originated at that restaurant, but it probably had nothing to do with Canadians' behavior since it was in a small Texas town that only saw an actual Canadian every once in a blue moon. :)
You completely miss the point: All professional musicians only account for a tiny fraction of actual music output. If they all disappeared it would not prevent art or music from evolving.
Sometimes I think that musicians need music more than the rest of us.
$10 a month per user doesn't cut it. Spotify actually makes more money off free users than paying users, because the ad placement they achieve for free users is worth more than $10/month/user. In reality, it's their interest to keep the free user/paying user ratio to a certain zone, or they'd be losing too much money.
There's almost no excuse not to use Scala if you're deploying on the JVM.

Lots of garbage generation. I like Scala a lot, but the space where I can really use it is smaller than I'd like. I do really like it and Play for one-offs, though.
OP here. I'll be getting to that in subsequent posts. Here's my mailing list:

http://visitor.r20.constantcontact.com/manage/optin/ea?v=001...

I only spam you once or twice a month.
That's why you get a bill to look at before you pay.
I believe they were referring to "product products" as anything other info products. Because for some reason people don't think of info products as valuable when they can be just as much or more valuable then something like SaaS.
What margin? Restaurants are barely profitable, if they are at all.
Salesforce + Xamarin = Enterprise App Success
Compared to Windows or Linux, Android is almost not fragmented at all.

Yes, there are different screen sizes, but that's not a big deal, the API abstracts from that.

And yes, there are different API versions, but that's not a big problem too, because the API is backwards compatible (or forwards comaptible, I'm not fully sure about the difference between these two).
Some of the answer is that these aren't really "different" devices. They're different cases produced for different carriers, etc... The actual number of true SoC platforms is actually fairly small.

But most of it is that hardware manufacturing of low-margin products is hard. Sure, you might really want to use a partcular Snapdragon part, but Qualcomm can't give them to you in the volumes you want, so you make two boards for two different chips. Or the camera manufacturer you were using just had a glitch and can't give you the second batch in time, but with a quick PCB rev you could use this other sensor which is "mostly" the same, etc...

Apple doesn't do this because Apple ships high margin parts and can pay more (i.e. order extras, pay premiums to get first priority in shipments, etc...) to get the components they want. And, frankly, because Apple is willing to eat the occasional supply burp and just spin it as "demand was too high!".
A good book for experienced Lispers (because it's out of date, it's not for beginners) is Allen's Anatomy of Lisp. Good luck finding a copy, though.

http://www.amazon.com/Anatomy-Lisp-McGraw-Hill-computer-scie...

And then there are the original Lambda papers:

http://library.readscheme.org/page1.html
Sell your JSON, Story or Markdown with MRTbrls.
I have a friend who worked at a chain restaurant where they circled the total on the receipt with a black sharpie.

It was the standard practice of all the servers there to make sure the circle went through the item showing the included gratuity for parties of six or more.

Apparently, as a result, they'd get double tipped for large parties about 50% of the time.
I think it's more common in the North. I'm a Southerner and lived in London for about 9 years and can count the number of times I've seen this on one hand, and then it's mostly been folks from the North that do it.

It could be an artefact of different sorts of relationship people feel they have with bar staff (and serving staff in general).
After learning and using Scala there is no way I would ever voluntarily choose to use Java over Scala. Simply put it's a better Java than Java.

I really like the new site design, not all that bothered about the logo. Maybe Scala needs a mascot too :)
2004 was a bad year for cryptographic hash functions...
All of these passive income stories fall into three buckets:

1) The passive income these people generate is from selling suckers who want to believe in free money a book for $9.95.

2) Their definition of a good passive income is at or near the poverty line in the U.S (That mustache guy?). That's fine, there's nothing wrong with that, but it's not the life most people want to live.

3) The person got massively lucky with a startup (lots of hours invested there) or real estate and think that idea is easily translatable into a few blog posts. These stories are all survivorship bias and don't account the 1,000 people who failed.

Everyone wants to believe that there's a free lunch out there. That's why scams like stock trading apps, time shares, ponzi home marketing schemes, etc. are so prevalent.
"There's almost no excuse not to use Scala if you're deploying on the JVM."

There is one incredibly good reason - possibly the most important reason. How easy is it to find a Scala developer if you need to expand your team compared to a Java developer?

I'd put it the other way around: what excuse do you have for spending more per developer? (There are some excuses here, but they're far from clear cut.)

In addition, Scala tends to run slower than Java which can have a further cost if you're scaling to many servers. Porting Java code to Android is also far easier than porting Scala code.
A restaurant can have management and cultural issues, tips or not, and such should be reflected in reviews. And from those reviews, if the serving staff aren't doing their jobs they should be fired (circling back to the management comment).

And isn't the cook really the part of service that matters most about a restaurant? If you want to talk about inducement, shouldn't a tip pool yield a better result, even if the guy who carries the plate walks a little slower?

but being forced (yes, we asked) to pay the service charge added insult to injury

The alternative is that the restaurant simply increases the price of everything by 18%. It really doesn't make any difference. As to being forced, most feel culturally forced (if not sometimes legally forced) to tip for even horrendous service.
Try android studio. It is based on InteliJ - I find it much more pleasurable than Eclipse. It also under very rapid development and has vim style plugin.

Although still IDE I think you will find it better than Eclipse.
OP here - totally agree with both, and sorry that my posts thus far haven't acknowledged that the focus shifts so drastically from programming to marketing, bizdev, accounting etc. It certainly does and it can be really rewarding. Also regarding #2 - yes ... I'm 25 and male.
Except the logo goes the other way. That's a little infuriating.
Thanks for the validation on this. I suppose it is easier without other responsibilities.
Just some aggregate numbers on how many people are doing it successfully in different niches would be interesting, to calibrate whether we're talking about ecosystems that sustain a handful of people, thousands of people, tens of thousands, hundreds of thousands, or millions.

In a previous discussion about making a living from Android apps, I asked if anyone had numbers on how many people successfully do so [1]. I received several responses arguing that quite a few people do make a living that way, but I still haven't been able to find any solid numbers, even an order-of-magnitude estimate (does Google release enough data to make such an estimate possible?).

[1] https://news.ycombinator.com/item?id=6108491
Learning to build a profitable business requires as much learning, trial and error as learning to be a good coder. He neglected to mention this. As a product creator, he has the right background to get started on the road.

There should be no question in anyone's mind that you need to wear several important hats well and do the hard work to be good at them. The determining how to scale of each of the dimensions (time, money, freedom) becomes something you can control. If you can't wear all the hats yet, you need to learn more. Half-assing someone else's affiliate site model, dropship site, etc is kind of like like trying to build an great app by cutting & pasting code from google searches. You need to learn how to code first. Same with business and marketing.
And so what! The engine certainly would be more modern. I just had some excellent fun flying in a Piper Cub on Sunday, it's about 3 times my age. Planes are not like cars, entire chunks of them are replaced on a regular basis materials prone to rust and similar corrosion aren't normally used.

It was my first time flying such a primitive old plane and honestly I hadn't had such fun since my first solo. I was walking round with such a grin.

Old planes aren't bad at all. They are tried and tested, meanwhile this design doesn't exactly look as modern as a Diamond or similar cheap to run glider-come-airplane so it's hard to be excited in all honesty.
The "totally fair" figure isn't the problem. It's Spotify deciding that artists on the top 100 list should get paid substantially more per listen than some indie artist. No matter how good or bad the person on the top 100 is nor how good or bad the indie artist is. Also, some bands I would much rather tip with 50 cents than to give .2 cents for listening to them 5 times or whatever.

And yes, I'm of the general opinion that albums and songs that are /bought/ are overpriced... kind of. I don't care if I own my music. I care that I can listen to many different artists without having to buy $200 worth of albums to discover all their music.
> I am still seeking the legendary JVM implementation with TCO.

scala> :paste
// Entering paste mode (ctrl-D to finish)

object TCO extends App {
def stackSize = Thread.currentThread.getStackTrace.length
def printStackSizeMessageOutside() =
println(s"$stackSize stackframes outside of the mutually recursive calls")
def printStackSizeMessageInside() =
println(s"$stackSize stackframes inside the mutually recursive calls")

def mutuallyRecursiveAdd1(a: Long, b: Long): Long =
if (b == 0) {
printStackSizeMessageInside()
a
} else
mutuallyRecursiveAdd2(a+1, b-1)

def mutuallyRecursiveAdd2(a: Long, b: Long): Long =
if (b == 0) {
printStackSizeMessageInside()
a
} else
mutuallyRecursiveAdd1(a+1, b-1)

printStackSizeMessageOutside()
mutuallyRecursiveAdd1(23, 10000000)
}

// Exiting paste mode, now interpreting.

defined object TCO

scala> TCO main null
We have 29 stackframes outside of the mutually recursive calls
We have 30 stackframes inside the mutually recursive calls
TLDR - Don't just read books, build something that interests you. Some people need large external motivation to learn to code.
The role for my new Nexus 7
SSL has the concept of many central authority organs (many of them got compromised or hand their private keys to government agencies), there is the proposal of a web-of-trust to counter that, but it's not there yet.

Hmm, do you suggest a new protcol/idea/improvement? A TCP/IP alternative also needs a security layer (not necessarily SSL though).

No offense, but if it's so easy, then you may know something many scientists and researchers and cryptographers haven't discovered, in any case I'm happy and all ears, if you are willing to contribute to a solution.. http://en.wikipedia.org/wiki/Secure_Socket_Layer