skysight-inc/HackerNews huggingface dataset:
The odd part about this “get off my lawn” article is that PHK has already shown how to fix the problem: Varnish is both a very good tool and one which has gotten attention and compliments for rejecting obsolete convention (e.g. relying on the VM, requiring a C compiler to be installed on a server, etc.). I would love to see autoconf massively simplified or outright avoided for most projects and the best way to do that would be to start providing good examples of how unnecessary it is even for major projects.

The way to address oversights in the bazaar model isn't to cram everyone back into the cathedral but to build support for change by showing where something is clearly better.

One area where PHK might see this is the way Linux has flown past FreeBSD - not due to endlessly-debated questions of kernel superiority but rather because Linux distributions like Debian provided a clearly superior experience for the overhall system by rejecting the decades of accumulated hacks (i.e. the ports system, monolithic config files, etc.) which had been the status quo for years and building better tools to reduce management overhead.
I think the big problem with all the copy paste code is that you wind up with many redundant dependencies and equivalent pieces of software in varying qualities. Granted that it's open source, you can't rely on any kind of competitive (ie market-driven) mechanism to improve all of these redundant pieces of software over time. This is an inefficient part of how things are done....but that's not to say there's an obvious, more-efficient alternative to what we're doing now.
Using C# dynamic objects to perform runtime text templating
Protect Your Website with White Hat SEO
Google to Include Gmail Info in Search Results
Right and a lot of the lean manufacturing (and 8-hour work day) research that lead up to MMM came from stuff done by Ford and Toyota before World War 1. If there hadn't been two world wars and the cold war since then I imagine this sort of knowledge might have spread around faster.

You are being overly optimistic about the pace of human cultural development. The rest of the world is only just starting to realise again that perhaps we have cultural issues that lead to low quality results. Bell Labs have numerous advantages over the rest of the world when it came to fostering the sort of culture that produces high quality results. Just reading the history books really isn't enough for that to come about.

TLDR; I blame Windows ME on World War 1.
Can you tell me the reason you'd want to run a load balancer in front of a single instance? I read the feature spec for the elastic load balancer and can't it out.
Pretty cool, something simple like this built-in to phones would be great. If your friend knows much about the iphone he can go to the maps app and "share location" with you via text or e-mail. Is there something similar in Android?
One idea might be to charge per usage rather than on a monthly basis. So let's say I'm starting a project I pay a one-time fee to use the application for a certain amount of queries, days or weeks. Like skyhook_mockups said it's not something I'd use everyday but rather a couple of times a year when I start a new project or pivot.
OK, I'll make a couple of general observations here.

First: It would be a big help for this discussion, if we could have the informal convention that people who were employed in an IT job before 1990 marked their post. I think it would show a quite clear divergence of attitude.

Second: It's very obivious, that a lot of you have never been anywhere near the kind of software project posited in the "cathedral" meme, instead you project into the word whatever you have heard or feel or particularly hate. That's not very helpful, given that there is an entire book defining the concept (I belive it's available online on ESR's homepage, how about you read it ?)

Third: No, I'm not of the "either you are with us, or you are against us" persuation. The bazaar is here to stay, but having everybody in need of transportation buy the necessary spareparts to build a car is insane.

Fourth: Related to point two really: A lot of you seem to have little actual ambition of making things better, I guess that is what happens if you grow up in a bazaar and never even experience a cathedral. I pity you.
Whether or not that's true, it is a concrete difference between Python and Java. Python is not a superset of Java.
The simple interface of Vagrant is intentional. It is built on the Rack spec, which uses middleware that builds on top of each other. There is a talk called "Rack Middleware as General Purpose Abstraction" where John Bender, the lead developer on Vagrant project, explains why he chose to use that interface. You might want to watch it.

http://www.youtube.com/watch?v=fcNaiP5tea0
See my remark below.
Lion's Lair 2012: Our Pitch Deck
These are some creative structuring ideas. In addition, you could keep the 50/50 split and structure some sort of "promote" or disproportionate share of the company after a return of capital or above a certain value. For instance, you guys could be 50/50 up to a $10 million valuation. After $10 million, you could be entitled to an extra X% as an incentive.
You always can use JS/Python/whatever in your java application as a scripting language.

In such case like web crawler, the main issue with Java is the scalability or rather lack of it. You need to code it yourself, but that's not any different than other languages and platforms.
So you don't count the iOS and Android OS'es as cathedrals ?

Have you never wondered about their surprisingly coherent APIs and wondered why that was so different from, say, UNIX ?

See my other comment about knowing what a cathedral is to begin with.
The 7-11 Mashed Potato Machine
All the investment banks I have worked in have enforced this to greater or lesser degrees. i.e. always for the front office, and varies whether it applies to Technology or not.
Companies that have security pages and contact details are also companies that understand the importance of security issues. the problem here is that most companies do not understand the issue and tend to react defensively

One solution might be using an agent - setup a clearing house for security issues run by a couple of trusted people. You log the issue, the clearing house gets in touch with the company and gives them access to the issue details.

It keeps the person reporting the issue one step away from the company and any potential trouble.

Once the company acknowledges and fixes the issue it is made public with an optional credit

If they don't acknowledge the issue it becomes public anyway after x days.
مشاهدة فيلم تيتة رهيبة 
مشاهدة فيلم تيتة رهيبة

مشاهدة, فيلم, تيتة, رهيبة, اون ,لاين, كامل

http://tube.sbayaa.com/1456
But that agreement would be based on our current best understanding of how computers should work. When you factor in the future (and evolving an existing codebase is a huge problem) we have to assume any understanding we have now is incomplete and flawed.

That's why things like libtool or autoconf evolved (or, better, were "iteratively designed") to be able to grow and encompass varying and different goals.
That "stripped down version, one not built on M4" exists and is called CMake. I've used it and it's very, very good.
How is this different from Flowapp?
> I’ve heard whispers of a time when people could talk shit at pubs and not be audited by wikipedia on the spot.

Talk "shit" or "bullshit"? The latter we could stand to reduce. The former...well, I guess it is annoying that any dolt can Google up a list of 500 comebacks. So I guess the emphasized skill is in delivery rather than wit.

> Where cognitive energy would need to be spent to work out your bug, instead of copying and pasting the error.

I don't even know how com sci algorithm courses pose a challenge anymore. Google was barely a thing when I took it and when we occasionally stumbled on obscure papers with it (or Excite), it was like finding the teacher's answer book out in the open.

> Where you had to actually call your friends or family to see what they were up to.

This is not such a loss. I think back when you had to call people, your conversations had to be more deliberate (i.e. I'm calling Jane to break up with her/give condolences about her dead mother) and planned. Not planned out in what you were going to say, necessarily, but planned out in that you wouldn't just call up a non-close friend and have a lengthy conversation with them. Whereas with online chat and Facebook, I've had long rewarding conversations with people whom I may never had the temerity to cold-call about anything.
Just curious, where do you live?
soma.fm

Favorite stations:

-Space Station Soma

-Secret Agent

-Suburbs of Goa

-Groove Salad (though oftentimes sounds like porn music)
Actually, the nicest thing about HN for me is that I get to see my words evaluated on their own merit rather than what people know about me. HN has made me a better thinker and better communicator. Over the past year or so that I have contributed, I have clearly seen the way my thoughts diverge from the reality of what others believe. Sometimes I disagree and stop convincing people, other times I present arguments which are stubborn, but backed up.

You took the time to write a long essay, and present a novel idea. A lot of posters here disagree with you, but the mindset on HN has been to build first ask questions later. Convincing people in a single day to change their world view would be a huge undertaking regardless of whether you are thinking about it correctly or not.
I've been fairly happy with GQueues. The lack of nested tasks is a killer for me for taskup, but I see you commented elsewhere that that feature is coming soon.
Related Stores about Gen X:

>They don't want to spend a lot of time talking about things or having meetings. They want to get in, do the work, and move on to the next thing. If you're looking for someone to deliver a report every week, you don't want an Xer. I recently brought up the subject of understanding twentysomethings during a coaching workshop. Immediately a manager complained, with a lot of emotion, that kids today don't want to work and will only stay for a week or so and then leave. Well, the job was very repetitive and offered little challenge. No wonder!

http://www.coachingandmentoring.com/Articles/ (click on x's at the bottom, link wont display correctly on HN due to the single quote)

http://www.newbizs.com/pubs/GenX09-02.pdf
It was a simpler time. You could misinform just about anybody about anything. Yoko Ono? Sure, her influence in the Beatles would arguably ruin them forever, but after John Lennon's death she went on to invent Skittles.

It's an art now though. You have to pick little tidbits that SOUND plausible but you can never really verify.

I, for example, told my (American) flatmate months ago that no living person other than current sitting monarch can appear on a British postage stamp. Had to backtrack when the Royal Mail announced every British gold medal winner at London 2012 would get their own stamp.
I was at an academic conference recently where an researcher I respect was talking about paper reviews at a top journal much the same way. His point, if I can attempt to do it justice--was that we sometimes get so caught up in proposing ways to "polish the diamond" that sometimes we forget that it's a diamond we're polishing. Some things are good in their own right, and while yes, they are likely improvable, we as "reviewers" don't usually offer enough recognition of the submission's value, or do it only in a token way in order to excuse the criticism that follows.

The researcher used as an example a recent submission with a novel research method. The other reviewers were caught up in the minutia of the paper, and missed the forrest for the trees: the method itself was more than a worthy enough contribution to the field to be accepted, and they were arguing about significance of the results. Over the course of the next couple of review rounds, this researcher's focus shifted from reviewing the paper to defending it to the other researchers. In the end, after multiple rounds (and likely a couple of years), the vote was 2-1 to reject. At this point the Senior Editor stepped in and published the paper without further revision.

Do we do the same with submissions here?

That conversation was hit me pretty hard, and I hope it will change the way I review.
What you might "gain" in reduced complexity by getting rid of the arm you loose massively in being able to power the whole system efficiently in one go. If you split the 10.6 pounds of plutonium across N smaller drones you would need to duplicate N Radioisotope Thermoelectric Generators (RTPs), power electronics, batteries, radios, cameras, computers and probably a half a dozen other things I haven't thought of yet. This probe is going to be going for at very least 10 years - probably quite a lot longer, all because of the design choices around how it's powered.
Sorry, I don't see the article saying that a company innovates because it was copied. What it says is that being copied doesn't stop innovation — which is the whole premise of the IP system (if I can't recoup my R&D costs, then I can't afford to innovate).
If that is the only factor, it might have as well been closed source.
OnLive's Breakdown Gets Detailed: New Company Formed, Hiring Prior Staff
checkvlist is excellent and we're going to release a project management level feature that lets you group tasks and set up inheritance as well, coming out in the next few weeks!
Thomas Fuchs's vapor.js -- The World's Smallest & Fastest JavaScript Library
It seems overzealous, until you're the one whose IP has been published in a mainstream media outlet, resulting in bored crackers probing around to see what's there.

In an age where television shows regularly incorporate "real world" tie-ins and easter eggs, it makes perfect sense to use an invalid IP address to save everyone some trouble. Not to mention, if someone were really attacked as a result of their IP address being randomly used on some television show, the lawsuit that follows would be unwelcome.
yet efficient system.

Citation needed. :) What metric did you use to measure the efficiency of the software bazaar?
it's a prominent example of the "cathedral" model.
More accurately, it went multi-cathedral: major vendors were building temples to their self-perceived importance and unless you were a major customer they weren't interested in borrowing a better idea from someone else.

The bazaar at least opened up the option for most users to have some influence over the process.
Let me help you with that. Jacques is correct in his description of activity. I just checked my radiation detection text book to make sure (that would be embarrassing wouldn't it!)

However, "lethal" is a bit of an ambiguous term when applied to the waste from the nuclear power generation. After cooling down, the fuel assemblies will most certainly be emitting ionizing radiation that will be detectable for hundreds of thousands of years, as you suggest. This does NOT mean it is "lethal" for this time period. UNLESS you open one of the assemblies and make an industrial waste smoothie. Most of the long lived isotopes contained in the assembly will be deadly as heavy metals. So there is still danger, but it is easily manageable, just like the waste from many other industrial processes (like making solar panels, or batteries for hybrids for instance).
The first Unix server I've set up was FreeBSD. I was able to go from zero to multiple services working in a sensible manner with next to no Unix experience, using only the Handbook and Running Linux as my guides. Mind you, that was done via command line, not by clicking buttons, so I gained a lot of understanding of how things work in those 3 days.

The core system installs in couple of minutes and runs well on even the crappiest hardware.

There is not WTF stuff associated with runlevels (there are no runlevels).

You can find and install software by navigating a certain directory in the system and typing in one standard command. Great for feature discovery.

FreeBSD has the best documentation among all the software I have ever used: the Handbook, the help screens in the installer, the security emails, the upgrade notes.
I haven't seen anyone link to it yet, so here is that first server (magnet link): https://gist.github.com/3404362

There was a Reddit effort to recover it some months back, as it was believed to be lost. (It's now on the w3.org page, but IIRC, either it wasn't then, or it's a slightly later version published there).

http://www.reddit.com/r/compsci/comments/q4e57/help_save_the...
Best part of the article:

""In the quarter ended March 31, 2012, iPhone had sales of $22.7 billion; Microsoft Corporation, $17.4 billion.""

In other words, iPhone alone made %30 more money than all Microsoft products combined.
Implies that conversations will no longer center on facts. Will we find ourselves talking more about politics, love, art and philosophy?
I just want to see that they can write code and that it isn't awful. When looking at their code you can get a feeling if you would want that person mucking around on your project. If the person is passionate about programming they will have code they are proud of and that can be the start of a conversation.
App of the Week: How safe is your nosh? DineSafe app lets you know on the go
Super Simple Command-line Program for Organizing Music Collections
The reference to autonomy in motivation reminded me of this Dan Pink TED talk I keep coming back to: http://www.ted.com/talks/dan_pink_on_motivation.html

I completely agree with this article. Perhaps we're the first generation to realize the old style of work and business actually negatively impacts productivity and motivation, and we're going to outright reject it. Everything about that is good.

Autonomy, Mastery, and Purpose. People want them because they're the true ways to success, and they know it. The old fake style of business based on carrot-and-stick mentalities and personal image is going out the window faster than an MBA can climb a ladder... or at least we can hope.
It sure is a fascinating wiki. Judging by it it wasn't that far from being implemented, which is mind boggling.
Mobile phone companies can predict future movements of users
"Talking shit" can mean exactly the same thing as "talking bullshit", in the UK at least.
Indeed, that's coming soon :) Hopefully we'll get you to try it out on TaskUp!
Disney writers make strange slur against open-source in TV show for kids
How the first plant came to be
How to avoid horribly sneaky spotify commercials
Is C Pass by Value or Reference?
Codes are machines, not poems!
I think FreeBSD, and the Linux distributions do try to cater to too many different people, and quality and coherence suffers a lot from this. I think we can get past this though. The culture of testing and good code is on the ascendant again in many quarters. You need more people to understand build, packaging and distribution better, sure. You also need autotools to die, as the use cases for it are mainly dead. You can generally write portable code to the systems that matter if you want to now, and it just works.

A lot of the problems are due to poor integration between languages, so for example the JVM people have reimplemented almost everything, as have the C++ people.
sheesh, if you want get better, ditch the books and put the time into learning haskell or something.
It seems to me that it implies conversations will center around truths (or at least googled tidbits) rather than assumptions.
Some children are quite smart - possibly smarter than some adults will ever be. Most are not as smart as the average adult, however, and some will never be. None of this is really surprising?

Whether one is dealing with an adult or child, there's no need to make assumptions about intelligence. I mean, some kids can spell and proof read better than adults, or at least type out the word "airport" correctly :)
Pyjnius: Accessing Java classes from Python
When you hold a bunch of information in your head, you benefit from your brain's penchant for making weird collisions and connections. Serendipity rules.
Design and copy are poetic. Code and data are scientific. Just my opinion...
It seems to me as though this is not so much about removing idioms from code as using only C-family idioms in code (and even then, regressing as closely to plain C as the semantics of the language permit).
Absolutely - it is a problem in that it is inefficient and error prone. And @DanBC - yes, no doubt people shouldn't be writing their own crypto (but to be fair copy/paste is not akin to making their own crypto - it's just a wrong way to reuse.)

But my point was that this isn't a "it doesn't work" type problem, this is a "it can get better" type of a problem - and I've seen many instances where these types of problems are discussed on the mailing lists of several projects and people with an itch to fix it go ahead and do it. It just highlights the differences in perspectives - get it to work first and even if we had to hack it we can make the design better later on if there are enough people bothered by it.
> Not to mention the fact that the bazaar is never going to put a man on the moon.

Spacex's "careers" page has a whole lot of "linux" jobs listed, so the Bazaar at least seems to be contributing heavily to potential future space travel: http://www.spacex.com/careers.php
My "killer features" for a task list are daily recurring tasks so before I go to bed I can scan the recurring tasks and say "oh yeah, forgot to water the plants!"

And also calendar integration. To me an appointment really is just a task with a very firm deadline. I'd like to see appointments mixed in with my task list. But I'd want to be able to keep using my main calendar app (Google Calendar in my case)
Show HN:  Our thick client Java SaaS
Hi Folks,

We've adjusted our networked Java desktop time and expense tracking system (Senomix Timesheets) to provide a cloud-hosted option for our customers and I thought I'd post it up as an example of how Java and Java Web Start can be used in SaaS for Windows and Mac OS X.

In our solution, applications run from user desktops to provide a thick client which works outside of web browsers, with the server component deployed to a host in the cloud. The result provides the connectivity (and centralized web page installation) of a web application while still giving users the speed and responsiveness of desktop software.

Since the client apps use Java Web Start for operation, we were able to reuse an established desktop Java code base in the SaaS system which had already been created for a standard licensed model. The additional development to shift things to the cloud was relatively minimal and the common code base also made it easy for us to continue with a self-installed licensed system in parallel with the hosted SaaS option.

If you have a set of Java applications operating with a desktop one-time-charge licensing model and are wondering how you might add a SaaS business model to that mix, taking a look at Java Web Start might be worth your while. If you'd like to check our solution for yourself, you can find a summary of screen shots, system features and a 30-day trial at: http://www.senomix.com