skysight-inc/HackerNews huggingface dataset:
I'd be interested in meeting some business-minded people in and around Cleveland. I currently live in Akron, but I am moving back to the Parma in two weeks. I'm just learning how to program for Android, but I my background is in financial engineering.

If people are looking for a solid idea to build out, I got some ideas in the financial realm. I'd be glad to talk with people about them. I simply don't have the time to implement things by myself.
Hand coded widgets and Backbone. No frameworks like jQuery. When last I used these frameworks they were too heavyweight to load quickly over a mobile connection.
This thread from that forum

http://arclanguage.org/item?id=15529

may give the OP some idea of what processes are involved.
We did have it going the other direction at first, but it didn't feel right.
That's fantastic news re nginx! The last I heard was that they were evaluating it and it's good that they are now committing to deliver support for SPDY.
which is to be expected with a TLS connection. OTOH you get to drop all the extra TCP handshakes, you get better congestion control, you get header compression, and that encrypted connection is often a really good thing.

http://bitsup.blogspot.com/2011/09/spdy-what-i-like-about-yo...

But yes, there remains no silver bullet, and you'll have to pick the right tool for the job.
I understand the difference between the two. The point I had is that stripe.js depends on the api. I don't understand why there is a separation in the status output. If the api is down, stripe.js is also down, you can see the reference to the api in the .js file.

The way that my business works is that we take a large number of orders in a short amount of time and then it tapers off. If my site was down because their api is down for 4 minutes (and I don't know when it is going to come back up), that would really affect my sales.

If you are at a cash register and pull out your credit card and the swiper doesn't work, chances are you can just hand the person cash. The internet doesn't work that way. 4 9's for a payment processor really isn't good enough. Also, that stat is just across 90 days, not 365.

I really like Stripe and what they are trying to do. Now that I can visually see it, I just worry about their uptime performance.

Update: Some one just sent me email calling me an asshole, which seems rather undeserving. This is their ip address pool-173-49-2-60.phlapa.fios.verizon.net.
Spdy is not great.

For instance header compression using a shared prefix dictionary saves only a handful (~100 bytes) over TLS compression -- worthless, not to mention it's already had several versions of the prefix dictionary.

Spdy developers didn't even test against HTTP tunneling, which in practice as seen in current Firefox and Opera works just as well. The 'head of line blocking' is not a big deal in practice.
Request HN: Boycott Apple until it increases worker audit compliance by 11%
I'm over in Toledo - nice to see Ohio on the incubator map!
Why is this important? Why are you telling this to people? Why is this news that a Hacker should know.

I might not get it, but IMHO if its not something of general interest, it shouldn't be on HN (even though the company might be PG's portfolio).
It assumes that all employees are informed about other employees playing a quit game. From a management perspective, it may be good strategy to make the counter offer, if you could ensure that it is kept quiet from office gossip. Also, an individual employee has no incentive to broadcast the fact that he is using the threat of quitting, and is likely to play into that stratey if he receives what he wants in pay/status/hours etc.
Thanks for the honest feedback.

Also, what is up with all of that downtime? I think I'd expect my payment provider to have better uptime. Makes me wonder how quality the backend really is.

While all downtime is bad, we think 99.99% is decent.

The best service providers -- including the services that might power your site -- tend to have guarantees in this range. Amazon EC2 and Google App Engine both have SLAs for 99.95% uptime.

More generally, this is part of the point: other payments companies don't tend to talk about their availability at all. We think that this is harmful. What should count as acceptable uptime performance is a fair question. As a first step, we think we should all make our uptime public.

Is it just me, or is this really confusing? Which services are responsible for taking payments? If the website goes down, does that affect taking payments? Isn't stripe.js part of the API? If the API goes down, doesn't that affect stripe.js?

No, the Stripe site going down won't impact your ability to accept payments at all. stripe.js is optional, and so we've exposed its uptime separately too. Again, other services like Amazon and Google break out their availability on a per-service basis, and I think this makes a lot of sense.
Or, in more recent conflicts, attacking truck drivers, weapons system maintainers, UAV operators, base entry point security guards, drivers/security for intelligence agencies, etc. At the very least, this forces the military to devote more resources to force protection for these contractors; it also limits operations out with the populace, and drives a wedge between the occupying military and the civilians in which the insurgents can survive.
Psh. They have no goals other than basically, getting back at the bullies who made fun of them back in high school (or in some cases, are still making fun of them in high school).

Having other people be scared of and by them is very obviously their goal based on their rhetoric. They pick random "missions" and make demands, but it's about obtaining compliance based on fear, not about a "philosophy" or "culture."

This is typical because since they were abused and made fun of, and constantly in fear as children, they think that's how you "win"--to be bigger and badder and stronger. Now they have found a way to be seen as big and scary without having to be attractive, strong, and popular like their former enemies--all this takes is...fingers, very rudimentary knowledge of technology (or at least the ability to read and follow directions). They also exploit the fact that so many people are clueless about technology--even the ones entrusted with securing access to systems.
There is lots of enthusiasts who post hyperbole like
https://twitter.com/travisglines/status/163735891964203008
Do You Speak VCili? (like Swahili, but more difficult to learn)
Don't forget iUI. :-) It's minimalist, but very lightweight and fast, and is great if you want a native-like iOS look-and-feel in a web app. http://www.iui-js.org/

Edit: as others have noted, there's some overlap. The project I currently have under development uses PhoneGap, jQuery Mobile, and iUI for different functions.
Time Out From Time Out
Well, didn't he commit a crime? Correct me if I'm wrong.
While I was working at a completely unrelated company that started off as a book store and turned into a global online retailer and PaaS provider there was a period of several months when my team was doing standups every day of around a dozen people (devs, test, mgmt) which tended to last anywhere from half an hour to an hour and a half.
There're costs and benefits both ways. AFAIK, Microsoft and Amazon both use the separate repositories model, and Google and Facebook use a single large repository. Most people I know that have worked at both of these styles prefer the Google/Facebook style.

The biggest advantage of a single repository is pretty intangible - it's cultural. When anyone can change anything or can use any code, people feel like the whole company belongs to them, and they're responsible for Google/Facebook's success as a whole. People will spontaneously come together to accomplish some user need, and they can refactor to simplify things across component boundaries, and you don't get the sort of political infighting that tends to plague large organizations where people in subprojects never interact with each other.

I think if it were my company, I'd want the single repository model, but there need to be tools and practices to manage API complexity. I dunno what those tools & practices would look like; there are some very smart people in Google that are grappling with this problem though.
Educate yourself on SOPA/PIPA
I am going to win an award for nitpicking, which is hard to do around here, but IT BURNS, so:

This story is entitled "They're Made Out Of Meat," just as it was when I first read it over a decade ago. It is not entitled "They're Made of Meat".

Yes, I know. But if you can't understand why someone might care about the difference, dare I suggest that you're not a writer? ;)

(The story is built around this phrase; the repetitions of the refrain in your head in an incredulous voice is half the point of the story. Every syllable must be presumed to be carefully chosen, and I agree with the author's choice.)
I've worked at places with these meetings. I was always talking to people who either already knew the information or didn't need to hear about it every day. In that setting a quick weekly status update would have made more sense.

Two other unfortunate things happened at one place that were I guess more a sign of dysfunction than a problem with stand ups per se. First, there was an arms race of "what I did yesterday" type descriptions that turned stand ups into a 30-minute production. Second, our manager had a habit of calling people out in the meetings in front of everybody (!). It created a stressful situation where people rambled on about nothing at length every morning. Stand ups were probably the least desirable part of that job.
“I don’t really get what you are doing, but if someone really popular invests in you, I’ll follow blindly.” --> I have seen this happen so many times it's not funny
This reminds me of a YouTube video, I saw within the last ten days here, where a stand-up comedian talks about, how the planet does not need saving, it will find out ways to save itself. I can't find it now though.

Scientists cannot find a way to degrade plastic does not necessarily mean plastic is not bio-degradable.

I have found time and time again, that stand-up comedians are the ones who make the most serious points.

EDIT: Found it - http://www.youtube.com/watch?v=eScDfYzMEEw
This is a legit startup idea. I can see my professors, research advisors, and myself using this for sure. Collaborative research documentation is a great idea. I hope others will see what I see, and use your service.

Awesome job BTW.
I'm amazed that nobody has mentioned Hybrid yet: http://www.hybridsoundsystem.com
Arbitrary schedule and bad habits about wasting time on stupid problems aside, I'd agree that a standup for a well functioning, co-located dev team is largely going to be redundant.

The most value I've found in standups are when you have a cross functional team that can communicate status on different things to everyone all at once. BAs, QAs, devs, IM/PM, and product owners aren't all going to stay up to date with each other naturally on most teams.

Of course, if teams are working in very long iterations with out-of-cycle QA then each functional aspect of the team staying up to date with each other on a daily basis yields less value. Such a setup tends to bring about other problems in many scenarios though.

In the end it's all about context. To say a daily standup is a stupid practice without context (implying in any context) is a bit too broad of a statement IMHO.
Hmm that could work for an unsubscribe page, since the user is motivated to make the second click. However, for an email with a sign up link or a subscription confirmation link having an extra step could reduce your conversion rate somewhat.
SEOjs Plugin - Bookmarklet for SEO status of any site
I don't see a SLA for Stripe on the ToS page, why not?

GAE has actually had 100% uptime for the last year.
http://googleappengine.blogspot.com/2012/01/happy-birthday-h...
"If you don't have an iPhone, well: you don't have an iPhone.*

I found those ads particularly offensive.
Sooner or later the lower paid employees are either going to get the feeling that all the necessary secrecy around salaries means they’re getting screwed (because, um, they are) or find out that someone got a raise by quitting, and go about doing it themselves.

A good axiom I've always gone with is that the amount of pressure and process a given company has built into promoting secrecy about pay is inversely proportional to my desire to work for them. If you're asked by management to never discuss salary with your peers, you know they're screwing people.
LaTeX Lab <http://docs.latexlab.org/>; is similar but Share LaTeX seems to have a much cleaner interface.
Working at a financial firm?
I am considering working for a financial firm in NYC as a developer doing performance oriented work on a trading platform.

If I do this, what should I expect wrt. salary and bonus level, amount of vacation and number of hours worked per week? How about dress code? And more generally the attitude towards software developers: Are they considered valuable or just interchangeable-but-somehow-expensive nerds?

Basically, do I want to do this?
Kernel/Android/Chrome/basically anything open-source is different. If the code is going to be open-sourced, it can't have dependencies on proprietary code anyway.
I hope they develop a stop-people-from-switching-to-Chrome system. Other than incrementing their version number faster.
I'd still listen to what they have to say, but I'd consider it to be untrustworthy information, as their insult against those who do things differently would tell me that they have a strong enough emotional investment in their decision that they're unable to rationally consider the alternatives.

Either that or they're being manipulative, which is also a big red flag.
This implies that spending a few hours interviewing is a better gauge of someone's abilities and "worth" than years of working side by side with them.

Do I really need to say that that idea is too ridiculous to be taken seriously?
Some thoughts on paper prototyping
Does it have integration with Dropbox or some other file sharing service? That, IMHO, would be a killer feature!
Algorithmic Complexity Attacks and the Linux Networking Code
Yeah, we already mine tailings from old mines, since the old mining processes were less efficient, and those tailings are now considered economically recoverable ores.
I think it's not so much religion as the usual connotations of the phrase, particularly as seen online (OMG).
Multiple people in this conversation section have asserted that code sharing is way easier when all the code is in a single repo, but from my understanding of sub-modules, it would be a fairly simple matter of setting up your pre/post-commit hooks to update submodules to a branch automatically and get useful company wide change atomicity (after all, changes should only propagate between teams/projects once they have some stability).

Putting aside the question of whether or not an enormous singular repo can be broken up intelligently into modular projects, is there something about the submodule approach that makes it a uniquely unsuitable way for sharing changes amongst projects?
Wow, a country with a ruling party whose strongest support group is young people. Compared to a lot of other countries, I'd say there's hope for Poland.
I'll informally confirm the 60% drop out statistic.

When I first started college (engineering focused school) the dean of undergrad academics had us all stand in a line and did the "look left and look right" thing - chances are that out of the 3 (yourself included), 2 of you will not make it to graduation. I thought he was joking until i got to my 4th-5th semester and a lot of folks i knew were either transferring out or switching to business type majors.

Education in engineering is a lesson in self discipline.
Was it George Carlin, by any chance?
Just a minor clarification - some of the repositories use Subversion (as mentioned in the "Push" tech talk), and some are pure git.
That blog post refers to their high-replication datastore, not GAE as a whole.
I think you're being a bit too hard on Ed.

A lot of things need to be answered.

How many times has this happened that he's had to deal with? How many times has he tried to explain to his boss that things take a lot of time? How many times has he tried to help and only confused them more? How many times has he been reprimanded by his boss for trying to help with these tasks?

Also, how is Ed lazy? The chance of needing to speak up at a given moment is so high he couldn't adequately do another task, especially a programming one, or any task that requires a high amount of focus.
Quality psd to html coding services 
sdtohtml provides the best psd to html services online,get your website coded by us
And also there is 'Rational Clearcase', another centralized
version control system.
Looking for the stat, but it's at least an 80% chance they'll be gone in 2 years; either of their own accord or the company's. So if your boss ever pulls one of these maneuvers either get on their boss's good side or start looking for work yourself because there's about to be a shuffle.
Almost all time-series data is represented with old data on the left, new data on the right. (Stock charts, etc.) The way you have https://status.stripe.com/ set up makes sense to me.
I'm not impressed by this example. You could use the same words to describe nginx to some degree. "Do something that hasn't been done before" isn't a crazy amount of hype, in my opinion.
... or appMobi/jqMobi. You could basically use of any of these frameworks/libs and run your project through appMobi in the same way you would run it through Phonegap.
Perhaps stating the obvious here, but this is one of my favourite stories, so forgive me for feeling sharey. The best part of this is the utter simplicity—the defining quality, I believe, of good writing and good code alike. It turns the point of view around and slaps the unsuspecting reader with the understanding of just how little we can suppose of what life is like capital-E Elsewhere. If and when at last we get the chance to make contact with an intelligent extraterrestrial species—assuming of course that we make it that far—the political and linguistic challenges will be fascinatingly unprecedented, and I can only hope I’m alive for it all.

As a side note, if anyone is hiring for a First Contact Emergency Linguistics Squad, I am permanently available for such a position. ;)
Serious question: What might you want to reuse on the client side?
The scrolling direction change was one of the few changes in Lion's UI that I actually liked; it took me an hour or two to get used to it, but I'd gotten scrolling directions confused between iPad and iPhone and the Mac before that -- especially when the iPad was propped up and facing me, like a monitor.
I agree with you and the parent. It's a conversation you need to have at least once. Explain your workflow, getting in the zone, etc. Explain why there is a ticketing system. Explain the disruption to the productive day that interruptions like this bring.

It totally sucks that you can't just be a semi-independent craftsman who works on what comes their way in a nice orderly queue, but that's the reality of today's workforce. If the interruptions keep happening time and time again after having this conversation and following up on it, then at least you know where you stand in this company.
I started this petition/boycott even though I really need to update my iPod touch as soon as the next one comes out--that's how important I think the situation is.

The way I see it, workers will continue to work under worse and worse conditions until people say "Stop--there's no justification for doing that, not even for profit!" If not now, will we still be buying products when a worker dies for every 10 units (of whatever) made? Every 5?

I remember a short story by the great Cordwainer Smith (http://en.wikipedia.org/wiki/Cordwainer_Smith) about galactic diplomats being outraged by the torture of innocent beings on some planet. These beings were tortured because their sweat (under torture) produced the most potent aphrodesiac in the galaxy. The story ends with the two diplomats drinking this liqueur, saying something like "Yes, this is an outrage, but what are you going to do? This stuff is magnificent!"

Please consider signing this pledge. You may say that it's futile in the face of the total number of iPhones sold in 2011 (something like 73 million), but however many signatures this petition gets, the next one will get more, and someday the lost sales will convince Apple (or whatever company is being targeted) that it must change its business practices in order to make more money. It may take five or ten years for this to happen, but there's already a movement talking in this direction.

Please visit the petition (http://www.change.org/petitions/tell-apple-you-wont-contribu...) and click the tab labeled "About this Petition" for more details.

Thank you for your consideration.

Gregg Williams
petition organizer
former senior editor at BYTE magazine, 1979-1988
Apple Direct/Apple Directions editor at Apple Computer, 1988-1998
Nike Air Yeezy 2 Hot Selling
You might be shocked to hear this but the vast majority of businesses in the real world have such huge process issues that you'd diagnose most of the economy as full of "very sick companies that need life support".
we use Google Closure ( http://code.google.com/closure/library/docs/overview.html ). If you are making complex apps comparable in complexity with google docs or gmail, this seems to be the way to go..
> 4 9's for a payment processor really isn't good enough

If 99.99% isn't good enough for you, then you should just store the payment data yourself so that you can re-send it if your gateway is unavailable during those critical 4 minutes.

Payment processors of all sizes experience downtime. Authorizenet was down for almost a day last year despite having redundancy in every layer of their operations -- up to having an entire hot standby data center to fail over to. None of them lost all their customers and went out of business, so 4 9's IS good enough.
Many people on HN are using Stripe to handle payment processing for their startups/projects. How can you argue this information isn't relevant?
"You can’t shoot yourself in the foot in any way" is a pretty silly thing to say, but that seems to be an off-hand, casually made comment. None of this seems particularly egregious.

I'm looking for examples such as people actively promulgating Node adoption with ridiculous claims, people advising folks to use Node for specific tasks where it's completely unsuitable, people selling Node based technologies that aren't that good, people making the claim that Node is a silver bullet very publicly to a large audience, etc.
Here you go: http://www.facebook.com/note.php?note_id=10150121348198920

"We can build a binary that is more than 1GB (after stripping debug information) in about 15 min, with the help of distcc. Although faster compilation does not directly contribute to run-time efficiency, it helps make the deployment process better."
Three big problems with a split up codebase:

1) Instead of doing one large release every week (which facebook does: http://www.facebook.com/video/video.php?v=10100259101684977) you now have dozens or hundreds of smaller releases, a lot more heterogeneity to test for.

2) If you have inter-dependencies on modules you have to grapple with the "diamond dependency" problem. Say module A depends on module B and C, and suppose that module B also depends on C. However, module B depends on C v2.0 but A depends on C v1.0. If they're all split across repositories it's not possible to update a core API in an atomic commit.

3) Now you rely on changes being merged "up" to the root and then you have to merge it "down" to your project. This is one of the reasons Vista was such a slow motion train wreck: http://moishelettvin.blogspot.com/2006/11/windows-shutdown-c... -- kernel changes had to
be merged up to the root, then down to the UI, requiring months of very slow iterations to get it right.