skysight-inc/HackerNews huggingface dataset:
Yes, everything is mixture of complexity. When an artist paints, she has to decide how simple or complex to make the work. But what we're talking about here is that once you pick up a PHP brush, you're screwed. That's why it sucks. You can't change brushes; you have a big fat crayon. And while that works for filling in the sky, you can't get any detail on the faces, for example. (Choose a fine brush and you have a different problem of spending all your time on the sky.)

What I'm talking about when I say "our abstraction mechanisms are failing us" is the need to use any size brush at any time.

And, as an aside, photo sharing apps are bought for billions for the same reason that tulips used to be worth a fortune. Uploading pictures of your cat is about as valuable as a 'Carnaval de Nice'.
Sorry for the stupid question but how is this even possible for a compiled language? Will the program simply crash without an error message?
I think its a bit dangerous because in general people read these and believe them to be true. People are already misinformed about the fact that Tesla created AC power and the comic only further promotes this misconception.

And really the part about Edison electrocuting animals is horrifying enough on its on merits, but to aggravate that by including that he paid little kids to steal pets so he could do it? What about the part where Oatmeal basically said Edison purposely experimented on humans with radiation and killed his assistant and amputated his arms? I am sure Edison was no saint but the author makes him out to be a monster which I think is irresponsible of the author of The Oatmeal to claim without never bothering to research. It seems as though the author just met someone who was a fervent Tesla supporter and took him at his word.
This seems nice for prototyping, since it'd allow a Lisp-style approach to changes and refactoring, where you can incrementally refactor, and run the intermediate results. Traditionally that's been difficult in Haskell, because if you e.g. change the type of a function, you have to change or comment out all the code that calls that function before it'll compile. That's particularly annoying when doing sketchy speculative prototyping, during which it's common to frequently change your mind about how things should be put together.
I don't know and am not in the biz, but anecdatally, from my memories of the manipulation of SCOX in years past the high afterhours trades are used to bump up the opening price the next trading day.
This is very questionable reporting. The changes that Comcast are making are flat-out improvements. The old plan is 250gb of usage, then dire consequences. The new plans start at a minimum of 300gb usage, and add extra 50gb chunks for a fee if you need to use them. The TechCrunch writer is very worried about hitting bandwidth caps, but hitting those caps is both more likely and more severe of a problem under the old system!

It might help to translate into a different domain. Let's say you're offered the choice between two cell phone plans of equal cost. The first plan has 1,000 minutes, and once you hit 1,000 minutes your phone shuts off and refuses to either send or receive calls. The second plan has 1,250 minutes and an overage charge of $10 per 250 minutes after 1,250. This TC piece is making the argument that the second is worse, because billing you based on how much you talk is a slippery slope that will lead to the elimination of long phone calls, even though the second plan allows you to make more and longer calls if you need to. The problem with that argument is that the phone company is really billing you by how much you talk on both plans, one just gives you fewer options.
How to Install Arc
How to win customers and influence rankings
I'm just wondering how soon someone will push some haskell into production with this flag in place because they can't be bothered to track down all their type errors.
My first startup: "ArtistRequest" booking form app for Facebook
Triple? Easy there, cowboy!
Did the investors get the valuation correct? Is it really a $100 B company ?. I am reading through the prospectus now. http://www.sec.gov/Archives/edgar/data/1326801/0001193125120...
I'm not sure we ever reached the reuse in the OOP sense. That idea it's usually presented on a very small scale (you're going to grab some classes from another project as needed) - at least in theory. The actual reuse in real world happens on a package scale and has nothing to do with the OOP idea. Package/library reuse started the moment we got dynamic linking (or even before if you wanted to buy a good math library for example).

Maybe this can't be proven, but I think that the internet and publicly available projects (not even open, just available) have more to do with reuse than any OOP idea..
Marginalization and subsequent restriction/legislation/oppression is extremely effective in our society, and something that we should always take a stand against.
Unrelated to the OP, most normal people (rightly or wrongly) tend to ignore the value of time in general.

That's why people who otherwise make >$30 an hour will line up for 30 minutes for gas to save maybe $3 when they hear gas prices will go up the next day.

That's also why your relatives think nothing of your time before asking you waste several hours of your precious time to help fix their malware infested PC.
Note the section "Apple's huge profit margins".

Samsung produces a similar product with components costing about $1 lower than Apple's. However, Apple sells their charger for $20 more.
I think the square getting spikier is the salient issue at hand, not the sphere getting spikier. The inner sphere has an ever increasing radius based on the distance from the origin of a unit n-sphere placed at (1, 1, 1, ...). The inner sphere isn't spiky, that point just keeps getting farther away because n-squares get spiky.
I'm confused.

I think most people in the position to receive internship offers from multiple reputable companies are intelligent enough to discriminate on more than money.

Raw salary, too, isn't an indicator so much of 'how valuable the company perceives you to be' as it is a function of competition and cost of living. $10K a month working for a quant firm in New York sounds great, but your living expenses are going to be much higher than, say, Seattle or Boston -- and your per hour is likely to be much lower as well, as you're likely spending upwards of sixty hours a week in the office.
This reminded me of an old Yegge post:

"You do realize that John von Neumann spent the last 10 years of his life singlehandedly developing a theory of computing based on cellular automata? The computer you're reading this blog rant on was his frigging prototype! He was going to throw it out and make a better one! And then he died of cancer, just like my brother Dave did, just like so many people with so much more to give and so much more life to live. And we're not making headway on cancer, either, because our computers and languages are such miserable crap."

http://steve-yegge.blogspot.com.br/2006/03/moores-law-is-cra...
Don't forget airline pilots. And call center employees. And....

Well, I think it's clear enough that people can manage to do their jobs while being constantly watched. I won't say it's necessarily a good idea, but if it's a good idea for anybody, then people who are legally empowered to use force to enforce the law ought to be at the top of the list.
Do we need another Read It Later service?
Pervasive Tech Myths That Are Only Wasting Your Time
This is even more ridiculous than Tesla vs. Edison, because Ritchie and Jobs had almost nothing to do with each other. Their only real relation is that they died in the same month.

The viral facebook picture you cite is comparable to one saying that Ritchie was just stealing the innovations of Turing. Or that Ritchie was just a thief of the game changing ideas of John Backus.

At least Tesla and Edison were working in the same space at the same time frame on similar problems.
LINQ To SQL Vs Entity Framework
Entity Framework is ORM(Object Relational Mapping) introduced by Microsoft. It proves very useful for new developers for it’s simplicity to query against conceptual schema and also has rich feature set. Many time the question has been asked in the interview to explain differences between Entity Framework and LINQ To SQL to the developers who has work experience in Entity Framework. I have made table of differences between these two technologies.
>exorbitant amounts of cash

Really? I can fly to the other side of the world for less than $1,000. That seems like a very reasonable deal to me.

And if the price of being able to explore the world cheaply is surly flight attendants, that's a price I'm willing to pay. As are most people, I suspect.
I haven't worked with Django in a bit so my memory is foggy, but if settings.DEBUG is true, you should be able to do something like:

from django.db import connection
print len(connection.queries)

Put that in a middleware class's process_response() and it should print the query count for every request.
Code coverage and missed requirements
While the article has a fair point it really would be better phrasing to say "Take the highest yield internship offer."

This summer I had the opportunity to choose between a couple of YC-backed companies at different stages, a Founders Fund/500 Startups-backed company and Google. I chose the latter - not because of the pay, but because it was the only offer that would be a truly novel experience. As one of the rising freshmen the post mentions, experiences include:

- A startup that didn't gain traction and went under

- A startup that had its Series A and a liquidity event within 18 months

- A startup that had turned into a scalable, profitable business

While I love the camaraderie with the team and the impact on the product it's possible to have as an intern at a company where the only difference between you and a fulltime engineer is age, it's possible, albeit unlikely, I may enjoy working at a large company and would still be unaware of it had I passed on the opportunity. More importantly, being able to put Google on your resume is a strong signaling mechanism , and the concentration of wicked intelligent, inquisitive people of your age is hard to beat.
It will simply crash with an error message.
And that's good actually.. Projects are likely to gain more by inviting people with a long-term interest than one-off committers. It doesn't mean that one of them it's better than the other, or that the contributions are not equal. It's just much easier to maintain a consistent view of the progress in the core team that way. It prevents people trying to rewrite your project in their way - it may well be a better way if you were starting from scratch, but it's probably not worth it in a mature project (apart from major version increases, etc.)
Preaching to the choir. The chances of a driver reading this and actually doing anything are nil.
Also note market share, consumer satisfaction surveys, brand awareness, average selling price, etc etc.
It sounds like someone should re-read the history books that were not written by Edison. No Tesla wasn't a god, but the fact that most of Tesla's inventions still power your life in a lot of aspects should tell you how awesome the man is.

Judge a man by his work, not by his rhetoric
Thank you! I used PHP and MySQL for the backend and jQuery for the front. :)
Hmmm, you're probably right.
I had in mind something like GenStgExpr[1] that make up the STG type in GHC. I'd imagine with all the optimisations, serialization and code-gen that is based directly off that data structure, any significant change will have at least 1000 line nock-on effect. Perhaps I'm over estimating though. I'd guess it comes down to the size of the project.

1) https://github.com/ghc/ghc/blob/master/compiler/stgSyn/StgSy...
As well as a way to find out things that should be private into something public.

As far as I'm concerned, these records should only be unsealed, and made available for court proceedings. Accountability is important, but so is privacy.
Thanks for the suggestion, I'll definitely keep it in mind.
Instead of failing with an error at compile time, it will emit code that, if run, will fail with a 'type error' at run time.
Long term, Comcast wants to convert the average 100$/month HD package into a 100$/month data usage bill...
In short, compiled type errors are replaced with `assert(0);` (which doesn't return).
I actually think this is a very useful idea.

I'm hoping it goes even further. I'd like my toilet to tell me what is wrong with my diet and if I need to go to a doctor when I'm exhibiting warning signs for some illness (I realize this sort of thing is a little too weird to be a commercial success... but it would be useful.)

Also, as the saying goes, what gets measured gets managed. I imagine if you measured your waist size and body fat percentage every morning after waking up, fewer people would pile on the pounds as their lives get busier and more stressful. Being aware of changes in your body will cause you to think twice before going for that extra helping during dinner.
> Why have the bloody Haskell-Platform if you can't keep up with the compiler releases.

The HP doesn't chase the compiler. It is supposed to mean stable 6 monthly dev cycles, independent of what GHC HQ is up to. It is explicitly not about chasing the bleeding edge GHC.
While the conclusions of this comment are wrong, it is true that many people have a very hard time using breathing machines. This is compounded by the cognitive problems they get when the sleep apnea is not treated, so that fixing the problem is very hard.

The solution is to get help and keep trying. There are humidifiers if your nose gets dried out, and many styles of masks and machines.
Use django-devserver https://github.com/dcramer/django-devserver
Although this situation with the underwriters propping up the price makes Facebook's value pretty questionable and will create a negative sentiment, I believe it's positive for Facebook that the price didn't pop. Facebook already has a pretty steep road to travel to live up to the offering valuation. As a CEO I think I would prefer having a muted, non-volatile stock price than an inflated, volatile one. Inflated prices are good when you're ready to sell but can be a distraction when you're growing. Underwater options and market reactions can destroy employee morale --- look at Yahoo.
That's correct. In my experience, with such high volume opportunities, most semiconductor suppliers will provide their engineering expertise in doing (or supporting) not only the development but the reliability processes.
What you design should be very very simple to someone when she starts to play with it.But as she plays more and more she
should discover gradually(exponentially) the great underlying complexity in order to achieve the simplicity on the surface.

All the great codebases,machines,mathematical equations,laws of nature,even a bacterial cell seem to have this property.
but that does not help if the customer buys a 2nd 5$ charger and uses that e.g. at work. Then the touchscreen will behave less good and the customer will blame Apple...
Prod builds would explicitly disable this (and other dangerous flags) with `-Wall -Werror` and friends. Shipping with this on is like shipping with incomplete patterns, which would be caught by `-Wall`.

Summary: useful for developing, capital offense for production code.
Has some truth to it IMHO. :) Whenever you hear people go on about how innovation is such a social endeavour and how nobody really invented anything you can be sure about one thing: that the author hasn't even tried inventing anything.
Perspective on the billion-dollar exit
it's best used by those with hosting restrictions or people who are just partial to PHP and those who want to use it with large existing projects.

We were talking about if PHP is the right language to use if there is legacy code and hosting does not plays a role.
What Makes a Country Prosperous?
I never have trouble sleeping when I sleep. But I, like many people in this industry, don't let myself. I'll push myself to work till I'm sleeping at 2, 4, 8am... the ultimate consequences are pretty similar symptoms to those you describe, albeit self-inflicted.

And the problem is that after a while it reaches the point where I don't feel "tired" during the day, but I know I'm not performing my best. Recently I'm finding my tolerance of sleeplessness much lower, and like the sibling poster I put it down to increasing age (though I'm still in my early twenties).

I know the existence of 'burnout' (and all the baggage that term comes with) is debated by some, but the physical effects of not having enough rest are all too real. I know you know this already, but - sleep, people. You'll thank yourself for it.
Beautiful site, love the simplicity of it, nice on the eyes.
> I realize this sort of thing is a little too weird to be a commercial success

Nothing's ever too weird. Ten years ago, people were afraid to put their real name on the internet. Standards will shift, as long as customer/user privacy is maintained.
+1 from me. We need more language and framework tutorials to be written with testing in mind. I wouldn't be surprised if the work from this was moved into Django's official documentation very soon.
For kicks, here's how it works for KDE:

a) You sign up at our SSI, KDE Identity (identity.kde.org).

b) Once you've got an Identity, you'll find a form to request developer access in the web app that manages it. That form asks you to optionally name a supporter for your application, and provide a written justification.

c) Our sysadmin team (of which I'm a part) is tasked with screening the incoming applications. What we look for in doing so is evidence that the applicant has already gathered some experience in working with the community, especially in the form of prior patch contributions, which we encourage them to list in their written justification. If the applicant has named a supporter, we check with the supporter to get their confirmation and opinion on the applicant. If we're satisfied the applicant knows the ropes, the request will be granted; if not, we encourage some further social mingling and patch-based contributions first and to re-try later.

In practice, it's relatively hard, but not entirely impossible, to gain developer access without naming a supporter, because evidence of social ties / working relationships with other team members is very important to us. Occassionally a proven track record of successfully getting lots of patches through review will be enough, and occassionally a low-quality justification will result in a rejection even despite a supporter (after conferencing with them on the matter).

The goals here are to make sure every new developer can immediately act confident about their role in the project, that everyone knows the etiquette well enough to work together productively, and that mutual trust remains high as everyone can rely on their peers having been through the same process.

d) Once you have your developer access, that's basically it: Aside from a few sensitive areas that require additional, special karma that must be requested separately (mainly the websites to avoid embarassing and directly public-facing screwups), all of our developer accounts have equal write access to every repository.

In other words, KDE embraces a flat, meritocratic hierarchy and broad access. We certainly make use of review-based workflows (some teams more than others), but they're enforced by social etiquette, not by ACLs. We find that this makes for a lovely atmosphere in the community and a sense of shared responsibiliy over all our products, and consider it key to our longevity as a successful open source project.

Contrasting with the nine month timespan between first patch submission and getting push access mentioned in the linked article, I'd say our average is probably closer to six months. It can be significantly lower than that, and it can be longer, too.
"stop crying over your current device and just upgrade. You'll be a lot happier once you do."

What a waste of time and money. Devices are expensive. Use them until they're unusable (broken or incompatible), and get your happiness from people, not devices.
Ask HN: Favorite HN threads of all time
Have any Hacker News threads ever truly changed your perspective on life, or technology? Post them please.
Wishful Thinking: This Keeps Not Working, So I’ll Keep Doing It…
Comcast won't be destroying Netflix or Hulu anytime soon.

Most consumers of online video services (I work at a company that streams video):

* Can easily mistake 480p for 720p and above

* Don't know or care how much bandwidth they are using

* Value content availability

So if Comcast wants to compete, licensing the best content, which can become really, really expensive, is going to be key. Even so, though, production companies may find it most profitable to license to multiple outlets to maximize profits. So even though Comcast owns NBC, it's probably best for NBC's shows to be on Netflix, Hulu, etc.

I think that a successful Comcast app might be a very good thing because ratings measurements will shift from Nielsen ratings (which can undercount certain kinds of shows) to better data (how many and what kind of people really watched the show). Better data means better analysis and targeting, so, for example ads can fund the shows much more effectively - and thus make shows that were previously niche more viable, or shows that were quirky and constantly teetering on cancellation more secure.
Former Googler Piaw Na writes about his sleep apnea problem: http://www.google.com/search?q=piaw+na+sleep+apnea

He says that many Asians with sleep apnea are NOT obese. They are predisposed by racial variations in anatomy.
Read "Tesla On his work with alternating currents." Tesla was able to transmit electricity efficiently using standing waves in the earth. The engineering precision required to do this is still unmatched today, and in fact it's because even tesla had such difficulty tuning all of the required parameters that radio in the sense it is used today, which requires tuning fewer parameters, won out in the 1910s.

If you read "tesla on his work with ac" you will see his transmitters could be tuned to close to 100% efficiency, minus heat and spark losses from the power plant at the transmitter. This has been replicated using single ground wires instead of the earth at a small scale and at higher frequencies recently in various open source hardware forums on the Internet. Note these smaller devices use higher frequencies which generate much more rf radiation than tesla suggests, thus not being able to achieve the efficiencies tesla was talking about -- tesla was working with a 50 foot diameter by 10 foot tall primary and secondary, plus an extra coil about 8 feet tall and wide and frequencies around 50khz, pretty much unused today.

The secondary and extra coil in the tesla arrangement take the place of straight antennas that are in use for normal communications today. The transmission is effected through the ground, not through the air. If the device is emitting radio waves, then it is not a tesla magnifying transmitter. Most tesla coils built today are hopelessly out of tune... They have far too many turns and are far too tall in comparison to diameter. Each additional turn adds capacitance, and the narrow diameters used make for a small inductance. The capacitances are far too high and inductances too low in these arrangements, and thus they need extremely inefficient drivers.

"Colorado Springs Notes" is of course the definitive resource for this material, although "tesla on his work with ac" exposes the concepts in easier to understand language. The exact schematics and dimensions are given for the Colorado springs experiment. Scaling it down is not trivial, but in the late 80s golka built an exact replica and performed successful experiments.