skysight-inc/HackerNews huggingface dataset:
How does that compare, though to a raided SSD tied directly to the PCI board?

I've been led to believe that 300k IOPS is possible using sub-$1000 gear from OCZ [1]. Combined with an agressive backup to spinning disk, this sounds like it'd scream like a monster and be stable to boot.

[1] http://ocz.com/consumer/revodrive-3-x2-pcie-ssd
Ads / RTB Hacker? Perfect Audience is hiring a full-stack dev
Perfect Audience (YC S11), San Francisco or remote, Full-time.
We're looking for full-stack developers. Perfect Audience is a self-service ad platform that lets businesses get more sales and conversions by retargeting lost visitors on Facebook. We're developing a real-time bidding platform that companies outside the Fortune 500 can get value from without needing tons of handholding.

http://perfectaudience.com

What we are looking for:

* Ability to architect, develop, and test key infrastructure

* Understanding of performance and design tradeoffs, without compromising quality

* Experience scaling up webapps and services for rapid growth is a plus

We offer a generous salary and equity grant, free lunches, your choice of snacks in the kitchen, and a desk in our sunny, beautiful office in downtown San Francisco.

Office pic: http://i.imgur.com/aL4Mc.jpg

Recent coverage in TechCrunch: http://techcrunch.com/2013/03/20/perfect-audience-apis/

Want to know more? Write to jobs@perfectaudience.com
That's awesome to hear...glad you found it helpful!
Chill out dude and stop thinking about market adoption. It's about the journey, not the destination, remember ?
This is clearly a new creative process that should be treated with respect. This may open the door for seeing other languages in the browser where chrome might like say be bundled with v8, mruby, python vm, etc.

Your children one day will laugh at you saying our parents only had javascript in the browser.

Stop thinking about market adoption.
> anything that differs from the standard liberal playbook on race or religion

... and economics. You forgot that point :) If you happen not to agree with the Welfare State Theory and Keynesians, you are bound to get downvotes, too.
Um, you might try actually stating the city instead of assuming everyone knows (or cares to parse it out).
Look at the way we treat prisoners who have been found guilty of a capital crime: lethal injection.

That was because drowned, hung, shot, or electrocuted was considered inhumane. Even the first of 3 of the cocktail puts the prisoner to go unconscious.

Now, treat the animals that we eat similar. Nitrogen gas suffocation is known to be the least traumatic death yet. Some executing prisons are going to that as well.
I am a mere small fry employee at Heroku. I nearly exclusively work on the efforts concerning Postgres.

If you stopped using Heroku's product because you thought it would not pragmatically meet your needs: I'm all for that.

However, by description, it seems though you were more unhappy with the handling of the situation than the quantitative implications to an application. So, I'd like to expand on that line of inquiry:

I'd like to think that trying to expose the implementation problems at Heroku would allow for more well informed decision making (e.g. what is the problem, how severe is it, what barriers exist to fix it, how long might it reasonably take to improve things, how can it be mitigated in the meanwhile) rather than being seen as only apologetics.

I realize the point of Heroku is to abstract a lot of detail, but all abstractions are leaky, and it seems like people might want to know more, especially as ongoing experimentation yields information.

I don't personally feel an opaque mea culpa is the most useful way to go about this. Do you disagree? Is there some other path you would have thought better overall, or in all respects altogether?

In general, I compare this to the many support requests I have responded to over time about things Postgres does not do, or could do better, and (very roughly, unless already committed) how likely it would be that they would receive attention in a semi-near-future release. Generally, people seemed happy to be informed of that, but the dynamic is very different there. Nevertheless, it's the closest thing I've got in my immediate experience.
Why not use Dart?
> The fewer sites this works with, the quicker developers will fix it.

That turned out really well in the past.
Would Google Reader get an exception, or is this Firefox version being released after that shuts down?
To give the complete picture though, recent Windows warn you before applying the changes to the file extension.

Although the users would still blindly click "Yes" even if the dialog asked for their firstborn child.
I blame it on 2AM-brain. Thanks for catching that.
It was actually about merging half a dozen tables into one (a fancy denormalization), and at the same time precalculating some fields. We had gone as far as we could with indexes. The write volume is not a big deal because writes are rare on a reservation system.
I don’t want Twitter 2.0 — I want to be disrupted
I'm flattered to know that you think we're the only competitors in the space. However, given that you have several times as many full-time developers as we have part-time developers and my code was/is the basis for critical features in your product, I think you're really overstating the caliber of your developers. As for your "critical mass of users" that we supposedly lack, I suggest you consult Google Insights.

While I don't know the specific details of your agreement with Elsevier that make you so "well positioned to dominate," I do know that your target market's principles are more closely aligned with ours than with yours, and that they aren't stupid. You can't really preach open access for years and then sell yourself to the OA movement's greatest enemy and expect that no one will notice.

In any case, I welcome the competition, although I hope that in the future it comes in the form of shipped code and not more lies about the viability of free software.

FYI - I'm a member of the Zotero core team, but I'm also a graduate student in neuroscience at MIT.
You can stay on my couch but I live in Australia, is that going to be a problem?
Why is Windows 8 so hard to Power Off?
Trying to propose remote working where I work at. Opinions?
Yeah, I had some CSVs backed up in a dark corner they couldn't touch the first time, but I didn't have a full dump because, honestly, I thought they'd never use it again, and it was highly unlikely they'd ever find someone who can do SQL after I left.

The second time was some messy issue with encoding so the backups nor CSVs wouldn't load in. After trying absolutely everything I could find, I just build a script that wrapped all the backed up data in INSERT clauses and sent a raw .sql file over. I couldn't physically go in at the time, so I was trying to be phone support on my own trashy product.
It's a bit of a commute, so I'll have to get back to you. I appreciate the offer though!
CSSCSS — a CSS redundancy analyzer
Divorcing Evernote to marry Google Keep?
Bitcoin Wallet on Android makes it pretty simple, at least for me.

15 seconds? Including your address and phone number? With a PS3 controller?
Learn the fundamentals not the frameworks. The frameworks will come and go but the fundamentals change much more slowly. For example in this case, if you don't already, learn how long polling works, and what the alternatives are, learning how web sockets work, learn how comet works etc. It will lead on to how TCP/IP works at a basic level anyway.
If facebook does whatever you are proposing, don't you think you'll be blown out of the water?
we definitely won't send any credit card information to a hoodie server. Instead we use a service like stripe, but then receive the payment notifications or errors, which lets us notify the user if payment worked or not.
Report on Sunday’s Outage
How feasible would it be to get this working in the browser using WebRTC?
It's actually fairly good now that most of the improvements in 1.1 can be used with browser support like pipelining, compression, keep-alives and so on. However it isn't perfect SPDY is better still as it allows for things like muxing and pre-emptive resource downloading.
> on a solid, proven base

[Citation Needed]
There might be hope. Remember the days when people said "I'll Xerox that for you!" or "AIM me!" or when there was Word Perfect and Lotus?

I know it feels like a stretch after MS has dominated for so long, but if I could think of a viable alternative, I would ship it.
Why people share exported PDF's not their LaTeX files?
Interactive Map: North Korea's missile capabilities
It would kill your business eventually so it may me a naive question but : do you need volunteer work to help identify and warn those insecure networks ?
HP Launches Their Low-Power Moonshot Servers
> How to give something as flexible as Excel that is not Excel?

This is our problem; if we can't, then obviously Excel is the right tool for the job.

> I think that they'll gladly switch is a myth.

Ok, I think you're right. What I meant by "gladly" was more like "they won't be desperately trying to copy the data from the application to Excel and work the old way".

> Athere is no incentive for them to get better educated in this regard.

AKA. they won't change, because they have no reasonable reason too. So why do we (as developers) seem to expect them to?
For most applications the startup time is irrelevant. The startup time of a server app which runs for months is not an interesting data point. The throughput in requests per second is far more important and this is where the JVM has been very strong (3x faster than Go 1):

http://www.techempower.com/blog/2013/03/28/framework-benchma...

Memory consumption is often not a major concern on modern systems, saving 50 MB or even 500 MB is seldom as important as the ability to process more requests per second.

I'm busy learning Go, and am very impressed by the performance gains in 1.1 (and GC improvements). My main concern at the moment is how much less expressive the language is relative to Python, Scala and Ruby. Go is fast, but so is Scala, and Scala is also very expressive compared to Go.

Go has a definite edge in environments where memory footprint is important and simple interfacing with native libraries is critital. Scala and the JVM are still more appealing to me in most other areas.
I've written memqueue (https://github.com/halayli/memqueue/) for similar purposes.

Memqueue is a revision-based queue server with a REST API. Multiple consumers can poll the same queue at a different pace by using revisions. A revision is sort of a cursor that allows a consumer to specify where to poll from in the queue. If a connection drops it's not a problem, you continue from the revision you stopped at after you reestablish a connection. Each time a new message arrives to the queue, the revision is bumped by one and consumers are expected to poll from the new revision.

It also allows you to specify message & queue expiries so you don't have to manage memory growth.
In my experience, if you want reliable info (NOT Crunchbase nor companies who just crawl/spider them and resell it to you, you know who you are right below) use PrivCo, what I use in VC. It's reliable, confirmed with the VC firms and the startup founders. Rarely find anything off (crunchbase if way off as all the HN crew already has figured out).

Just do a search for VC firms and specify what date YOU want their last investment to be...everyone has different critera. If you think if it's been more than 6 months it's a "zombie VC" (I personally disagree, because without getting technical depends on age of the fund...a new 10-year fund invests most of its money in the first 2 years in a nutshell) then pick 6 months on PrivCo VC firm search for last investment. If you think it's 12 months search for 12 months. 18 months, search for that. Don't go by this nonsense list with arbitrary 13 month "cutoff", especially when many of these deals aren't announced - so they do have deals as evidenced from fellow HN crew discussion below missing, so the "no deal in 13 months" is wrong to begin with - you need a dedicated firm like PrivCo (or DowJones VentureSource) to diligently find those deals day after day. Just 1 missing VC deal for a firm throws off the entire "13 month zero deals" input there = output worthless.

Long way of saying search for venture capital firms in my humble opinion using PrivCo and the search criteria: last investment must be within X months, plus must have made investments in the precise sector you want, etc. Then you get the results, export to Excel, and it even has updated names and direct emails of the partners. It's a beauty. Might be others I haven't used too but this is what I personally use:
http://www.privco.com/investors

Jake
By the way: in MS SQL Server, one can also do the reverse: use Excel spreadsheets as the backing store for SQL Server queries (http://msdn.microsoft.com/en-us/library/ms141683.aspx).

It is not easy to set up, but way easier than using csv for getting raw data from Excel into SQL Server, or for running a clean-up query on data in Excel.
You bring up lots of good points, but your training would sound a lot better as "start learning Excel."

There is no software you can not shoot yourself in the foot with. There's no point in switching when people will certainly misuse other applications as well.
Jon Rossi makes great shirts, I've gotten hundreds from him: TheStartupShirt.com
The Frontline video of the bombing mentioned in this article is posted now: http://www.pbs.org/wgbh/pages/frontline/foreign-affairs-defe.... Be warned the footage is graphic and quite disturbing.

IMHO this video should be nominated for Pulitzer Prize, the way he captured the chaos and human response to the bombing is incredible. Rarely does a piece of journalism make me feel emotions as visceral and real as this video does. What a terrible conflict going on in Syria right now.
> but what about non-js users or, maybe more importantly, SEO or crawlers

Hoodie is more of a tool for applications, with user authentication etc, so SEO is not relevant here. I wouldn't build a public website with Hoodie.

> Also, something else that really trouble me with javascript client-side is that, often, when something bugs, everything just stop working

Yes. That's something we have to handle if we want dynamic web apps build on web technologies. But there are great tools today that help you 1. prevent JavaScript by automated testing in all the browsers / OS 2. track JavaScript errors, e.g. with errorception. And 3. todays browsers are more relaxed about errors, they try to continue running the app, even if one function errored out.

> Is there a better solution than a hard-refresh? Would a first-level try/catch solve this problem

If you can keep the state of an app and store user's data immediately, there is no big problem to reload the page, I do that in several occasions at minutes.io, the user usually doesn't realize, it's very fast.
"The migration of Byzantine scholars and other émigrés from southern Italy and Byzantium during the decline of the Byzantine Empire (1203–1453) and mainly after the fall of Constantinople in 1453 until the 16th century, is considered by some scholars as key to the revival of Greek and Roman studies and subsequently in the development of the Renaissance humanism and science."

--https://en.wikipedia.org/wiki/Greek_scholars_in_the_Renaissa...
Tell me when go can compete with this:
https://sites.google.com/site/piotrwendykier/software/parall...
Well, buried in your comment is the assumption that the alternative must be equally flexible, and I disagree.

Flexibility is often the cause of data loss at these companies, see "sorting a column but not the whole table" case for example.

People hate constraints, but constraints are exactly what we need to maintain data integrity. If convenience is more important, be my guest -- but I'll quit the moment they're asking me to fix an Excel table. (A bit of an exaggeration, but you get the point.)
Welcome to Hoodie world :-)
From the comments section, by Arram himself: "Learn to program people. A lot of that pain was unnecessary."
Funny thing: while reading I was like 'yes, that's exactly it! I know! That happened to me when...' And probably these would have been the comments I'd have interrupted my speaker with.

Spot on insights, couldn't agree more. It takes a great deal of self discipline to shut up and really listen, but it definitely pays off in long term relationship and reputation.
Don't get blinded by this stuff. It's always moving; it's fun coming up with new ways to do the same thing. Plus, everyone thinks they can do a better job (myself included!). Kinda like how kids think they'll be the best parent or teacher ever when they grow up.

Focus on understanding various modes of thinking, the various key paradigms of programming. Work on understanding basic algorithms, so that given a problem, you can do some rough math and have a general idea of the bounds involved. Spend some effort understanding the low-level stuff.

Long polling's probably been used for over a decade. You should be able to figure out why long polling exists. Think about, for instance, implementing an IRC chat room in the browser, without using any special new features, just HTML and old JS. Once you understand that, you should be able to skim this article, and understand the point and value of the tool without having getting into the details. For me, the point of reading such articles is to see if someone came up with a new way of viewing something, an idea or perspective that might expand how I deal with another problem in the future. Only secondarily do I think I'll use most of the tools I read about (although it's nice to know such a thing exists, for the day you do need it).
It'd be more effort for no gain - and it would encourage me to keep changes locally, which is bad for collaboration.
Your favorite superheroes: How educated are they?
In the current implementation, CouchDB takes care of it. In case of a conflict, both versions are kept, with one winner. The other version can be recovered and the conflict resolved, both automatically with a worker process or by the user.
Prevailing wage in the bay area for one programmer we got was over $100k. I doubt anyone is paying "multiples above prevailing".
The author says he chose to start his company in Canada because, "In the Bay Area, investors, friends, and early adopters are so embracing and supportive of new ideas," and this can actually have bad consequences. It's an interesting notion. I have no startup experience, so maybe this is a dumb question, but isn't the solution just, "Take what investors, friends, and early adopters say with a grain of salt"?
Come to https://twitter.com/jszurich, or ping me at https://twitter.com/gr2m, happy to chat
Looks lovely, but I wish people would focus less on fast development and more on something that better maintainability 2 years down the road.

When it comes to the lifecycle of most applications, the speed of developing something new has a marginal impact on the overall costs, and most tools and frameworks than enable rapid initial development tend to suck once you have a big app on top of them. This is why we fawn over a tool when it's shiny and new, and bitch about how much it sucks 3 to 5 years later.
A friend of mine (a woman) posted on Facebook once saying how she had saved $X by using coupons.

I replied that I saved more than that by not buying the stuff in the first place.

She couldn't understand what I was talking about.
I kind of like the external GPU idea, but they are still so expensive.
In essence i could carry around an Ultrabook with a decent CPU and at home/work plug it into a a Thunderbolt Dock that gives tons of ports an has an external GPU + Dual Screens. That way i can be truely mobile on the go and have a decent workstation and gaming rig at home, without the Laptop GPU Fan going at 100% and also much faster.
I agree that his comment need to provide more data. I also find that HN in general is very quick to downvote comments critical of Go, even well reasoned ones with sources.

In terms of performance data check out quad core results for Go 1 (go 1.1 would need to improve by considerably more than 33% to best the JVM):

http://benchmarksgame.alioth.debian.org/u32q/benchmark.php?t...

Also see Netty (Java) outperforming go by a wide margin here:
http://www.techempower.com/blog/2013/03/28/framework-benchma...

The poster's comments regarding GC, heuristics and code generation are vague, but it's no secret that IBM/Sunoracle and co. have very sophisticated GC and JIT implementations which they have been optimizing for 15+ years and it shows through in the benchmark results.

I like Go, I just think that we need to be wary of expecting it to be as fast as the JVM and even MSCLR straight out the gate. It will likely take years to reach that level of sophistication.
With all due respect, I think you're wrong.

If I'm writing an email in the Gmail app on Android, what I want when I hit send is for the app to save the email locally, and then do its best to try and deliver it. Ditto for, basically, every other app on the phone that talks to a remote server. If I try and send a tweet, I want it to go "sure", and then be able to go on about my business while it works in the background. (And, again, that's how the actual twitter app works.)

And if I'm using some app that lets me take notes about a meeting or interview and syncs them with the cloud, I sure as HELL want to be able to take those notes and save them locally, even if the cloud sync had to be delayed. "Sorry Mr. CEO, but I can't seem to get wifi in this meeting room. Can we go out on the balcony and you just run back over those last few points?"

Now, yeah, I need some way of checking to see if it has actually sent the email or whatever. And if it fails, a notification that it has done so is not amiss. Mobile apps, typically, already do this sort of thing. (For gmail for android, you can check the outbox to look for unsent emails, and I believe twitter for android will notify you if it fails to send a tweet.)

To the extent that you're just saying that the app needs to have a UI which doesn't lie or surprise the user, then I agree wholeheartedly. If the user cares whether or not the cloud has been updated, or the message has actually been sent, don't lie and claim it has when it hasn't!

But if you're saying that as a general rule we need to not handle network sync stuff in the background, I think that's nuts. Nobody wants to sit there with an email draft open hitting send every so often to see if the 3G signal is good enough to talk to the mail server yet. Nor do we want to save a bunch of emails as drafts when offline, then have to go open each one when we get net access again and send them. (Come to that, in your model, could we even save an email as a draft in gmail without net access? Remember, the drafts folder is synced. Do we want the app to claim that a draft has been saved when it's not accessible from your desktop gmail client? Isn't that another case of "pretending we've saved a draft when it's not really saved"? If not, why not?)

TL;DR: Good UI that doesn't lie to the user is important. That's not a good reason to cripple your apps functionality so it doesn't do anything you can lie about.
Move Over, Apple and Google: Apperating Systems Are Taking Over Your Phones
I think it's surprising how many people grow up without the ability to listen to other people. It's a fundamental part of almost all relationships yet I think it's sidelined by many people in favour of having strong opinions and cool stories (not a bad thing either) - especially in a work situation where being right isn't what's always important.

I'm guilty of it sometimes as well, so will keep these in mind. Thanks!
Well, speaking as a college student, I have a fairly neutral view of JCPenny. As far as I perceive things, it's sort of a discount chain, no different than a place like Target, and slightly downscale from a place like Macys.