blubbi2

> While fake operator overloading is a fun hack, you probably shouldn’t use it in production code.

> But at the very least, fake operator overloading allows you to impress your friends by unusual-looking code.

Couldn't agree more. Please, please don't use this in production.

Edit: Just wrote the following piece of code:

  coors[0] = ~~cors[0];

Damn.

I'm probably missing something, but what's the advantage of drilling a hole as opposed to "simply" building a kind of drain or sky scraper. I doubt it would be more expensive.

Sure, the pressure-aspect would be away, but besides that...

Hey HN!

I'm Alex. I built this wrapper API since I remembered the "good old days" when fetching a tweet was as easy as doing a getJSON with jQuery. Well, unfortunately those days seemed to be over. So I built this simple wrapper API. Nothing too fancy, but it makes fetching a simple tweet easy again.

It also supports Instagram and the unofficial Vine API.

I actually really enjoy using Yo. I think it's a great idea. But I don't know how the future of Yo might look like. I mean, implementing features would ruin the whole point of the app. I'm wondering how they are planning to spend the $1.5M. I don't think they need a big infrastructure, lots of engineering resources etc. Since running Yo is cheap and there might be actually useful use cases for it, I don't think investing in it is such a bad idea. I don't understand the people trolling here. Someone invested some time in an app that became successful. That's it.

Actually, this is the first time I have ever heard about the word "Klammeraffe" in this context, but according to Wikipedia ( http://de.wikipedia.org/wiki/At-Zeichen ), there are a lot of alternatives to "At".

Affenschwanz: Monkey tail Affenohr: Monkey ear Affenschaukel: Monkey swing Elefantenohr: Elephant ear

Wow! This is great! I've already been to a so-called "Ferienseminar für besonders begabte und interessierte Schülerinnen und Schüler", an event I've been invited to and which I can only recommend, but these links are great! Thank you! Since I'm doing an additional test, I'll try getting into some of these programmes.

I'm currently doing my A levels in a small school in the Upper Palatinate. The problem is - at least in Germany - that some schools have to invest the money they get in fundamental thing only, like sanitary facilities. The school I'm attending doesn't even have WARM water AT ALL! NOWHERE! On the other side, there are new built schools that can invest their money in Smart Boards and video projectors. Another point is that most of the "old" teachers simply don't know how to use these fancy new things (including computers in general) and there are also teachers that are so fascinated by Facebook and BayernMoodle (http://www.bayernmoodle.de/) that they more or less force their students to use it on weekends in order to give them exercises. More or less, when I tell my mother about the lessons (she went to the same school as I do), I often realize that sometimes neither the teachers nor the way eduction is being done changed all. I would be happy about new books, some on mine are far older than myself. Maybe others have different experiences, but there is a lot of room for improvement.

Dijkstra's algorithm ( http://en.wikipedia.org/wiki/Dijkstra%27s_algorithm )

It is a really elegant algorithm and addresses a real-world problem. A teacher of mine once showed us the basic idea behind it:

He connected various bits of wood (=nodes) using strings (=edges). Then he picked up one bit of wood (=starting node) and slowly moved it upwards. Every time when a new node moves, it is an indication that the shortest path between the start node and the new node has been found. He did this until he reached the desired end node. The shortest path between the two nodes is in the end clearly visible, because the path between two nodes A and B that are part of the path between the start and end node is always the shortest path possible.

It is really simple if you think of it as a physical model, unfortunately I could not find a picture of it online :(

I really like the idea, but please include Node.JS or Ruby.

I think docuwiki might be a good solution for you. It's easy to set up and quite flexible. https://www.dokuwiki.org/dokuwiki

That's what I'm going to do next. Thank you.

I'm trying to build a kind of IRC-clone using socket.io. I know that I'll have to reduce the commands to be implemented, but there's still a lot of work to be done. I do not have a specific problem, but sometimes I just don't know how to start. For instance I'm going to implement an in-browser multi-room feature, but currently it's only possible to be in one room using a specific username. I would be really happy about new features or/and ideas. Feel free to contribute. https://github.com/blubbi2/Thor

What about Craigslist? Is Craigslist a special case?

Well, that's no surprise at all: http://en.wikipedia.org/wiki/Efficient-market_hypothesis

I spent a lot of time analyzing charts in the past (using Metatrader, ....), I even created automatic trading systems using MQL4 and I completly agree with this article: YOU CAN'T BEAT THE MARKET! Buy and hold... that's the way to go!

reminds me of the early days of reddit, quite cool and minimal. I like it. I think it would be a nice feature if you could submit text posts...

This leads us to the question why HN is written in Arc. The first version of reddit has been written in Lisp, but later on they realized that Python is much easier to maintain, because there are simply more Python-programmers than Lisp-geeks. HN in some way tries to emulate the early days of reddit, but now it's time to follow reddit's example and rewrite HN in a more common language.