HN user

ynd

197 karma
Posts19
Comments59
View on HN
www.youtube.com 13y ago

Alain de Botton: A kinder, gentler philosophy of success

ynd
1pts0
npcontemplation.blogspot.com 14y ago

A machine that can dream (Live demo)

ynd
7pts2
www.miller-mccune.com 16y ago

Motivating Students Via Mental Time Travel

ynd
1pts0
npcontemplation.blogspot.com 16y ago

Self-Organization and Conway's Game of life (With Interactive Javascript Canvas)

ynd
3pts2
www.folklore.org 17y ago

How the macintosh got it's distintive look

ynd
3pts1
www.artima.com 17y ago

Ward Cunningham: The Simplest Thing that Could Possibly Work

ynd
32pts8
www.laputan.org 17y ago

Designing Reusable Classes, Journal of Object-Oriented Programming (1988)

ynd
2pts0
npcontemplation.blogspot.com 17y ago

Clojure: Genetic Mona Lisa problem in 250 beautiful lines

ynd
66pts31
2009.cusec.net 17y ago

CUSEC Montreal 2009: Dan Ingalls, Richard Stallman, Avi Bryant

ynd
2pts0
blog.bumblebeelabs.com 17y ago

Software is about stories, not code

ynd
2pts0
news.ycombinator.com 17y ago

Startup Marketing Advice.

ynd
1pts2
npcontemplation.blogspot.com 18y ago

Beyond Procedural programming

ynd
2pts0
news.ycombinator.com 18y ago

Ask HN: Are you using computers to augment your intellect?

ynd
6pts7
laserlike.com 18y ago

Discovering the next New New Thing

ynd
5pts0
npcontemplation.blogspot.com 18y ago

Here's why dynamic languages are slow and how to fix it

ynd
4pts3
news.ycombinator.com 18y ago

Ask PG: Can you add a frame to visited pages?

ynd
1pts5
video.google.ca 18y ago

Want success? Tell a good story(Seth Godin).

ynd
1pts0
www.inter-sections.net 18y ago

How tough is your project? 5 leads.

ynd
1pts2
webstyleguide.com 18y ago

Introduction to typography

ynd
1pts0

Bitcoin is not susceptible to market control like eBay. eBay is a single entity so it is easy to coordinate self-serving decision. Bitcoin is multiple agents that have to co-operate. That prevents any one agent from making unilateral decisions.

Another huge difference is that anybody can become a new agent in Bitcoin. You just buy the hardware. You cannot influence or join eBay in the same way.

I think the kickstarter backers are really both investors and customers. They are investors because they do take a risk by paying for a product that doesn't yet exist. This leap of faith from these "customers" allowed Oculus to create a 2 billion dollar product.

People are mad because funding the project through kickstarter created some expectations that were not met. Funding through kickstarter feels like you're investing in grassroots human projects, but this made people realize that it's really just business as usual.

The main thing I take away from this is that he is not a professional photographer. Of course an amateur can afford to give away photos for free! However, I'm not sure he even realizes that what he says doesn't make any sense for a professional photographer trying to earn his livelihood.

His main point is that Common Lisp is better than Scheme when you need to get things done. Scheme may be more elegant, but it's not developed with a focus on practical utility (i.e. no sort function in the standard).

Well I guess one difference between what he's proposing and mysql is that mysql forces you to write data abstractions that can fit into mysql. Same goes for NoSQL DBs. Using his approach you don't have to worry about that.

Not sure that justifies dumping DBs altogether, but it's still an interesting advantage.

37signals are known and celebrated for their design style, and I think it's awesome that they are willing to experiment with new ideas and discard old ones. Particularly because the new designs in the post look nothing like their usual style.

I disagree with you because in some projects technical correctness is not the first priority. So why should you sacrifice everything in favor of it? In some settings, coding an ad-hoc solution is ugly but better in terms of the constraints (i.e. time, budget) of the project. For example, demos and prototypes.

Also, some programmers don't take satisfaction in writing good code, this article will encourage them to stay in their bad ways, so that's not good. I think this article is good for people who take too much satisfaction in writing good code. Good code is not always an end in itself.

I think that that's a breakthrough, because you are always taught to do as much as you can. Always put checks in. Always look for exceptions. Always handle the most general case. Always give the user the best advice. Always print a meaningful error message. Always this. Always that. You have so many things in the background that you're supposed to do, there's no room left to think. I say, forget all that and ask yourself, "What's the simplest thing that could possibly work?"

This habit of trying to do too much makes me inefficient sometimes. I aim for quality and in the end I just get nothing - but a headache.

Brilliant! Much better use of space. I can sort out the heap of information easily.

If I can get voting on there, I'll use this instead of vanilla HN.

Good innovation. He went further than simply displaying a pretty bullet list, like others do(digg, etc.).

Plus he included minors innovations that are very clever. For example, the size of the headlines are proportional to it's number of votes. It allows you to see how liked(important) a piece is regardless of it's rank.

It would be cool if the headlines would keep their current style and become links.

Down-voters, he is also right.

It's common for dynamic languages to embed typing information in pointers as an optimization. For example, CLISP uses at least 2 bits to distinguish between common types. That way fixnum numbers can be recognized and added without slow memory accesses.

The result is that you get less bits for the address. Hence less addressable memory.

I have missed this side of HN. Feels like christmas.

HN should have esoteric/alternative articles like that at all times.

This is not cheating. Nothing surprising here.

Of course you can do statement-based code, like in any language that supports I/O(Haskell included).

That's a hard fact and it isn't what functional programming is about.

I bet they were looking for extensibility.

I wonder if they ever thought of providing two interfaces.

1. The first is the common case.

    Document doc = new DocumentBuilder().parse("test.xml");
2. The second is more cumbersome but provides options.
    Document doc = DocumentBuilderFactory.newInstance(opts).newDocumentBuilder(opts2).parse("test.xml");