skysight-inc/HackerNews huggingface dataset:
So, the problem that I have with PostgreSQL isn't that it doesn't have every datastore under the sun, but rather the lack of automated distribution, and fault-tolerance.

This is not a hard thing to build though (continue reading please). I don't mean that it's an easy task, but that the semantics by which you may be able to build a fault-tolerant, distributed database on top of Postgresql are pretty straightforward.

1. Partitioning:
So, Postgresql has multiple notions of partitions. Ideally, this would be done at the database level in Postgres, but the idea is that instead of having your entire database fail at once, a transparent layer in which you SET PARTITION_KEY=X before querying would make this pretty straightforward. It would be nice if there was a semi-transparent proxy layer that this.

2. Replication / Fault-tolerance:
Postgresql today has built-in synchronous master/slave replication. It would be nice if someone built a automated failover system on top this. Alternatively, it would be really interesting if someone had multiple postgresql instances, and then build a WAL log per partition, and performed 3PC between N replicas, and you could have a fully peer-to-peer postgres. I imagine these transactions would either need to be PL/SQL, or fully written-out, staged serializable SQL queries.

3. Co-processors:
One of the biggest benefits a distributed, fault-tolerant Postgresql setup would give you is the ability to collocate your application with the data. Instead of having to do read, modify, write, you can write complex business logic that can run on whichever Postgres partition's master node, and the data doesn't have to go over the network.

I feel by introducing some basic wrappers around postgres to support partitioned, master-slave topologies, and perhaps a slightly different query interface to support this transparently, PostgreSQL could effectively replace most modern NoSQL databases.
Maintainer of zsh-lovers here.

The project is quite old already and could need some love. If someone wants to contribute, it's available on GitHub: https://github.com/grml/zsh-lovers

A more recent project similar to zsh-lovers is http://grml.org/zsh-pony/ - this are the notes from a talk I gave at DebConf 2011 and also covers some nice features of Zsh. Should be easier to go through that than through zsh-lovers if you're interested in an introduction of nifty features.

I guess the reason why no up2date list of "what Zsh can do but Bash can't" exists is that most people who explore Zsh never really look back to Bash once they went the Zsh route. Bash v4 got some features from Zsh but there are so many small things that Zsh still provides that once you get used to them you never want to go back. :)
Record Videos, Post on Youtube, show it off to your friends. Wait, can you record videos using it, I mean recording the commands, and on screen notifications as well?
An example of a game-changing idea that came top-down was the use of the touchscreen interface in the iPhone. Someone thought this would be a cool way to interface, worked down to a cool product and people liked it and used it a lot.
Microsoft shouldn't think about a Twitter acquisition? [2010]
Damn. The "XML. It seemed a good idea at the time" slide caused me to spray coffee on my laptop.
The biggest problem with the lean startup stuff is it results in this ridiculous false dichotomy. There is no "top down" or "bottom up" thing. If you assume you are in one of these two buckets you already lose because you either are abandoning your creative thinking (bottom up) or abandoning listening to what customers are telling you (top down.) I realize the common retort to this is that all startups need to have top down thinking ("vision") but the bottom line is the lean startup philosophy is at the very least poorly communicated because the large takeaway from all the writing on it is that startups should simply perform customer development and let the market dictate most of the actions they take and the products they build.

It's always a matter of deciding when to ship and how much time and resources to commit between data collection points (ie, releases.) This is a higher order function and changes as well in reaction to how you explore the solution space. Different domains have different constraints as to how fast you can iterate. Tesla, for example, is forced to iterate much more slowly than your average social gaming app can. Shipping too early, or shipping too late can result in wildly different outcomes. Drawing the line correctly is a matter of experience, taste, common sense, and luck.

Everyone knows you should try to minimize waste. Everyone knows you should prefer iteration over big releases. The question is always what constitutes "viable". A car that has three tires is not viable, and would be a market failure. The fourth tire takes a little more effort but makes the difference between success and failure. The problem is it takes some intuition to know people need all four tires to be willing to pay for a car. It also takes intuition to know that the three-tired car being a failure does not mean you should throw in the towel. I don't care how many metrics you measure, you can't use metrics to determine where an asymptote is going to appear because it's not going to be a part of any logical predictive model. Disruption is just that, disruption, and usually comes about due to a synergy of several things that were previously unknown to have magical properties when combined. You generally can't hill climb to find to these things, unless you set your step size (alpha) to a "Goldilocks" value: not too large and not too small.

I understand the appeal of creating a mental framework and slapping a label on it to help people think about and communicate ideas clearly. I think there are definitely some important ideas contained in the lean startup philosophy. But in the interest of creating a conceptual framework of absolutes like any other dogma the lean startup philosophy has large gaps in it's methodology that fail to explain for the large number of startups that launched products that many people would consider well beyond "viable", but were successful because their definition of "viable" happened to be the right one.
Going lean and incremental does reduce risk. It also reduces reward.
Sorry. When I read he word "skip" I couldn't resist making the condescending older guy joke. I think the tension between the generations is good for us and keeps us on our toes. We could both learn a thing or two from each other.
Mobile Raspberry Pi Computer: Build your own portable Pi-to-Go
Intel eyeing Israeli gesture recognition start-up
Apple sues Google over open-source initiative
Neat project. Any latency hiccups controlling the motor/reading sensors? NXT-Python has some issues when connecting to the NXT brick wirelessly.
Thanks for the explanation, didn't know that.

Is this true in most modern DBs? (I'm thinking MySQL and Postgres particularly).
No, those are not the facts. That is your interpretation, and it is worded in your vocabulary. That vocabulary means something to you but may mean something else to someone else.

The wiser way to behave here is to realise that your interpretation may or may not be true, since you are working from a highly incomplete data set and therefore tone down the use of vocabulary that may have multiple meanings and instead focus on vocabulary that is less likely to be interpreted as an insult.

For example, you might have said:

> I notice from one of your statements that you seem to be working for a fund yourself. Do you think that this impacts your view of this problem?

Instead of:

> Ah, so you have a dog in this fight. You're not an impartial participant, striving for objectivity. That means I'm wasting my time talking to you -- you're not a scientist, you're a salesman.

All the bits in italics (yes, that's most of your comment) are potentially insulting to the person you're replying to. The first one is a mild character attack, the second one is a direct insult, and the third one is easily perceived as a direct character attack, especially in the context of the other two. Overall, this sentence is the comment equivalent of sneering at someone at a well-to-do party, and loudly dismissing them as a damn fool. If you're the host of the party or someone notable, you may get away with this sort of behaviour, but as a guest, you will be the one led to the door.

The restatement above makes the exact same point, casts the exact same aspersions on the views of the person you're replying to, but does so in a way that is not perceived as an insult.
We don't have official Apple support in our country.
I think they use an installation image, which makes me wonder how the process of upgrading and migrating the database would work in such a case.
The opening two sentences are this:

"The basic idea is that to get a startup of the ground, you don't need much. In particular you don't need much money and its possible and even desirable to grow your startup organically from the ground up instead of trying to get a cash infusion from a VC."

This is incorrect. The basic idea is that you can apply the scientific method to a startup. It has absolutely nothing to do with avoiding investment.
Top down is also covered in Peter Thiel's course under the name of 'determinate optimism'.

http://blakemasters.com/post/23435743973/peter-thiels-cs183-...

Big multi-year projects like Tesla Model S or Tony Hsieh's Downtown Project are much more top down than bottom up.
>If you assume you are in one of these two buckets you already lose because you either are abandoning your creative thinking (bottom up) or abandoning listening to what customers are telling you (top down.)

I find I write better code when I deliberately abandon my creative thinking. It's counterintuitive but it works.
I believe in InnoDB the way text and varchar(X) is stored is exactly the same. They both only use as much space as the data they are storing requires. However if you pass a 101 character string to a varchar(100) it will be truncated. I'd guess that is useful in some cases, but in reality you probably want to do the truncation in your application so you have more control over it.
I'd say the biggest problem with how people approach it is that they fixate on the MVP rather than the cycle. The MVP is just a particular cycle.

It's even worse than that. The problem I see is folks who focus on particular forms of the MVP. Not every damn product starts best with a launch page of some Google Adwords.

Lean Startup is neat. I'm finding a bunch of ideas from it stupidly useful. But it's going throught the Hype Cycle (http://en.wikipedia.org/wiki/Hype_cycle) amazingly quickly.
First thing I remembered after reading the title is http://pgsnake.blogspot.in/2010/04/postgres-91-release-theme...
A fairly obvious analogy, I thought.
I believe that is true for a lot of cases. People seem to overlook this, but I'd guess that is the reason for a lot of cases.

90s though? I think you need to go further back a couple of decades. Royal Bank of Scotland still has COBOL/IMS powering their core system [0].

[0] http://ovum.com/2012/06/27/rbss-core-system-meltdown-assessi...
> It also reduces reward.

How?
All UK financial institutions I have used do this: Nationwide, Barclay's, Natwest (RBS).
Root Samsung Galaxy S4 on Official Android 4.2.2 XXUAMC6 Jelly Bean
Either the submitted URL was changed or you are wrong. The URL goes to the page, not some anchor.
I used a small regional bank until recently and they had both a small (might be 8, I can't remember) character limit and stored them in plaintext. When I was emailed my current password after having to reset it, I left.
Yes, but do you build better products? In my own experience success or failure is essentially non-correlated with applying deep creative thinking or raw hypothesis hill climbing. Both seem to work in different circumstances. The lean startup method claims that it's anti-correlated since you will fall into the trap of acting on poor assumptions. But guess what, sometimes your assumptions are right and you have a unique perspective to create something almost nobody else would think to.

Also, in my experience it's the subset of successful products that involved more creative thinking that I am most proud of and look back on my time working on more positively. Hell, this is even true for some of the failures. The raw hypothesis driven successes were high-five worthy, but not pride-worthy (other than perhaps a pat on the back for demonstrating my faith in the Church of Science), and the failures tended to be fairly painful since the work itself was unrewarding intrinsically and the outcome was negative. Nothing is really worse than hacking out code in misery because, counter to your intuition and your gut, signals point to it potentially driving a metric up, and seeing it fail anyway. You have to resign yourself to the process and tell yourself that, despite being right, your intuition is meaningless -- not a fun exercise as a human.

It turns out, in my experience, that the most successful creators are talented at both: trying lots of stuff and learning from their failures, but also having that sense of empathy, intuition, and taste to simply "not be wrong" more times than your average person. You can't A/B test your way to having an opinion. And you can't let an A/B test let you change your opinion on the things that matter.
But, as pointed out by others, PhD/academia dynamics are heavily skewed by the fact that you have to do a PhD, then work as a postgrad for ages, before you get to run your own experiments. If you don't let anyone do anything but work on other people's experiments until they're 35, of course you won't get many great innovators below 30.

If anything, the fact that the average age of academic innovators is 38 rather than 60 means that there is a large preponderance of innovations in those few years between 30 and 38, to balance out the fact that most academics in a position to innovate are older than 38.

However, that's still using a fairly loose definition of innovator... arguably, people rewarded by Nobel prizes are not innovators, they're inventors. They've come up with something wholly new, and rightly deserve much credit for it. Innovators, however, are often those who take something new invented by someone else and actually bring it to the wider world.

The classic example of an innovator is, of course, Steve Jobs - didn't invent any of the stuff Apple is known for, whether mp3 players, smart phones, tablets, or even the original Apple II (invented by Woz), but damn was he good at getting it market-ready and then getting people to know about it.
You're already on the front page. Don't overdo it.

(Also, the Astroturf is really transparent here. Up your game a little.)
I am always wondering why no-sql has better performance than SQL if we have same simple use case (no join etc.).

If the data is well structured and no join is needed, can I assume that relational database should have better performance than no-SQL?
Huge communities, vast library ecosystem, widely taught, used a lot in industry
This was HSBC in Canada.

I am not a security expert, and realize that this may not be the right thing, and the implementation might be horrible, but if there is a reason to limit password to 8, this was a good enough reason to do so :)
Penis. It's called a penis.
See, now we're well into the realm of arguing by warring definitions.

One of the points of the lean startup book is to go where the evidence points to go. Apple et al throw lots of features at the market and a lot of them die with a whimper.

Touch screens turn out to be really popular, so Apple has progressively doubled down on that.

And that's pretty much what the lean startup is arguing they should do. The main difference is that Ries made it an explicit loop that covers all activities in a company.

To me the most useful analogy is simulated annealing. Each startup is dropping into a chosen neighbourhood of the stupendously large space of possible businesses in possible markets in possible societies. Each strikes off in the direction it thinks is where the optimum lies.

What happens is that if you don't periodically check the slope, you'll run out of money. And if you don't periodically jump around the solution landscape, you may well miss out on a better optima and become stuck in a local optimum.

But like all multi-objective optimisation problems, both the solution and the search for the solution are riddled with unpleasant tradeoffs.
please don't misuse this site..
I posted this on StackOverflow, as advised, maybe they'll answer us there: http://stackoverflow.com/questions/15728319/implementing-rem...
I'm confused, aren't the SBoC blog posts all written by different people? Shouldn't we encourage new users to contribute? I checked it out, looks good to me.
It might be insecure, but not in the way you mention. You only enter 3 or so characters while logging in. Others are hidden. Screen grabber can get only the three characters. Of course, if you login multiple times, the password can be obtained eventually. But this probably for one time login at a public computer.

And yeah, like in many things, these are done to give a false sense of security to the user and some minimal deterrent to the attacker.
About 37% of deposits are owned by foreigners, according to Barclays, and nearly 60% of that belongs to Russians, numbers compiled by Danske Bank (...) indicate.

So, nearly 60% of 37% is about 22%, not 30%.

http://www.forbes.com/sites/afontevecchia/2013/03/18/eu-take...
This is really amazing, nice job.
If you're going to drive your product based on customer feedback, its growth is necessarily going to be slower and more in line with existing conditions in the market. If instead, you drive your product based on a game changing idea, when you hit the market, your product will be completely different than what's available at the time. The statistics will therefore be completely new and in your favor. That's the theory anyways.
What is called red in the US is laughable compared to the socialism going on in Europe. Discuss.
Yeah, it's not half bad. Like I said, I tend to instinctively avoid whatever book is being waved like a bible in HN circles.

So as I say, it was a surprise to see how different the expressed vision of MVP seems to be from what I got from the book. I got the impression that it was the first thing you could actually give to a user and have them use. Even if it was buggy and had a single feature.

The launch-page "MVP" isn't actually a product. It's market research.
You are obviously astroturfing. Push a bit more and your domain will end up on an auto-kill list.
Which is one of the reasons I do not use online banking!
The advantage the DVM has is it's a baseline that developers can work with instead of worrying about hardware.

This was probably very desirable to Google in 2005 as it gave them the chance to court mobile manufacturers with the promise that their operating system can be deployed across a range of devices and theoretically all apps etc should remain functional, regardless of hardware as it's the VM that's the deployment target, not the phone.

Remember that back in those days the mobile OS world was god awful, Symbian was abysmal, JavaME was broken and Windows CE....well let's not go there.
That's a little better. Though for a truly successful facade, you have to tailor the comments to the community. In the case of HN, I would suggest some canned multi-paragraph commentary about the subject of the article, but not too much at once, or else people will start to check profiles and notice that these are new accounts.

Logging in every once in a while and posting different stuff to build credibility would help.
Would be interesting to know which version of MongoDB was used (2.4 also uses V8).

The original slides are at: https://wiki.postgresql.org/images/b/b4/Pg-as-nosql-pgday-fo...

There is also another presentation on the use of PL/V8 (on Heroku) at the PostgreSQL wiki - from last week's NYC talks: http://plv8-talk.herokuapp.com/#1
haha, thanks for posting that. i enjoyed:

"It's time for us to switch to something fresher. I personally would have preferred XSLT, but QUEL is almost as good."
Code Jam problems are in English, but, if I recall correctly, prevailing law in Quebec requires the problems to be in French as well.
Is this some sort of weird PR push for whispersystems.com?

https://news.ycombinator.com/threads?id=calder

https://news.ycombinator.com/threads?id=emblem____

https://news.ycombinator.com/threads?id=abolishme

https://news.ycombinator.com/submitted?id=rhodey
I wonder how easily "de-anonymisable" the stored data is? Handset model/version/OS/OSversion/Carrier/network/(presumaby)ipaddress-resolution-location. Cross that data with the sort of people who might have RedPhone installed - I'd guess that'd resolve better than Zipcode/date-of-birth/gender...
Right, creating new markets. That's fine.

But basically the failure rate on it is atrocious. If you find a different new market that is immediately adjacent, what's the smart move?

When I studied nature-inspired computation, my professor quipped at one point that nature-inspired optimisation algorithms usually show what you got wrong about your problem definition.

Markets are the same. Nobody swoops down like Batman with a flawless plan and mastermind insight that turns out to be perfectly correct. The airport business books might give that impression, but it's total bullshit. What actually happens is that millions of men and women swoop down like Batman and discover that they're not backed by Bruce Wayne and a friendly script editor.

Once in a while somebody stumbles onto something good and then their history is rewritten to fit the monomyth.
Actually, I did post something yesterday. I didn't post anything today though. Just encouraging my colleagues. sheesh, don't shoot!
I recently discovered its a similar case for numbers in Oracle, which slightly surprised me.
Right-wing social policies + state-owned economy = fascism, or national-socialism (nazism), as Germans called it.
I’m always annoyed when Norway is called socialist. It’s social democracy (which I think could be called socialst-capialist democracy). I think the same applies to many european countries.
Then you may be interested in PostgreSQL-XC: http://postgres-xc.sourceforge.net/

It is transparent, consistent, load-balancing and fault-tolerant cluster. Though some of the features of PostgreSQL are not supported yet, eg. triggers.
I think you mean whispersystems.org
>posting different stuff

Key word there.
jQuery animate is terrible for performance. The demo lags at a few frames per second (and I'm testing on a Nexus 4).

CSS transitions are the method for this. Not without their own caveats, but usable. I've written extensively on the subject with this exact implementation of an off-canvas menu: http://coding.smashingmagazine.com/2013/01/15/off-canvas-nav...
Now you have quite a restricted domain, so if your database is compromised there are a lot fewer values an attacker needs to enumerate to try and crack the password.
"I don't have to explain myself" is a reasonable interpretation of "recommended but not required" unless you actually have a case setting precedent on that particular terminology.
Have you considered creating a platform such as http://gust.com/en/ with your design features and the possibility to share links for start-ups? Its free for start-ups (and they can share url links with their contacts) but once you have enough pitches, investors pay to browse through the platform and identify/contact projects relevant to their investments strategies.
Why can't they just use email password recovery like everyone else?...