almostarockstar

/active is the best for this I feel.

Pretty sure you get two points if you hit it quicker. So if you let the dot rotate around to get the segment the next time you miss out.

I'm not sure any specific pattern or structure could possibly be good for all software.

I have two solutions for you that have served me well.

1. Don't wait for the right idea. Just build a less than ideal idea and iterate. More than likely you will gain insight that leads to a better idea along the way.

2. Copy somebody else's idea. Nobody executes perfectly, and no two founders will execute the same way. There is always room for competition.

I'm fascinated.

It sounds like a pidgin, or literal translation. Can anybody compare the grammar used to that of the original text? Or is it a work of complete imagination?

Dig a bypass canal and leave the ship there.

This sounds like a great action/drama film.

1. You are not a founder. A founder is there at the beginning...when the company is founded. You are a business partner. It's a very different dynamic. The business is a machine in your eyes and a child in your partner's.

2. Are you sure your partner actually wants the business the grow? Sounds to me like you are treating a lifestyle business like a corporation. You are swimming against the tide.

I would hire somebody else who can deliver in the way you expect them to and let your partner keep doing what he's doing at his pace. Build the business around him.

Or...you know...stop wasting your time trying to scale a lifestyle business.

I think the author is referring to the possibility of using a well defined fitness function rather than a vast array of training data.

One of the beautiful aspects of Evolutionary Computation is how you can use it as a generative mechanism. A fairly simple fitness function can produce complex and intriguing outputs.

Not identical, but goodreads.com came to mind as the default book recommendation site.

This could be a fun project. It would require some way of finding the book cover image, and ideally hooking into an existing platform like goodreads for metadata would be cool too.

Followers to a "readlist" could get updates when new books are added. hmm

[edit: booklist.com is available on namecheap for €61,397.59. A bargain at twice the price. Anybody want to spot me?]

Rotating as you suggest would be equivalent of swapping between vertical and horizontal seams. A tall and skinny image with vertical seams has the same problems that a long and wide image has with horizontal seams.

>you can only query one document per-second

That's not true. You can't query any single document more than once per second, which is very different. You can certainly query many separate documents per second.

No. Right now it's just our two weekly quizzes (Tuesday and Friday) from Ireland, one quiz from California (Friday) and a couple corporate quizzes we host for companies, maybe one every two weeks.

This is a wonderful concept. Absolutely love the idea.

My cofounder and I threw together a virtual table quiz platform. We stream the questions on YouTube live and accept the answers through a web app I built.

We've been able to host quizzes with over 250 teams, scoring their answers in real time. The scoreboard is auto generated and players can make a contribution with stripe.

So far we've given over 6k euros to various local charities. I'm very proud of what we've achieved so far.

Except, if that were the case, all of the cars would then be travelling in very close proximity to each other. This would only work if we all stopped at the lights with the same space between stopped cars as moving cars.

Of course, in a fully autonomous road network this is both possible, and mostly unnecessary, as nobody has to stop at traffic lights any more. Apart from pedestrian crossings of course.

Just wanted to echo this post. The start of the OP felt a little like the prospective founders were focused more on image than results, but by the end I was convinced.

My 2 cents would be to forget about YC as a source of seed capital and either get a loan or private angel investment to build a solid, revenue generating success.

Looks like it has less exposed moving parts that a classic bike. Could be easier to maintain / clean / lube.

In that specific example, yes. But in general, I think the "we are all Clever Hans" is right at least to some degree.

It's quite funny, the number of replies in this thread saying: "No, I really do need Y because I'm special!"

Just remember where you are. The XY problem is a far larger problem in a far larger population than HN.

Happiness, satisfaction, contentment, comfort, security...the list goes on.

That was an excellent explanation - regardless of your experience with Pharo (in my case it was none). Real world use cases and visual examples coupled with pretty clear language.

I had heard of bloom filters before but hadn't studies them in any detail.

These go a long way towards what I had in mind. Thanks for posting.

I agree, but we're not really talking about simple components on a screen. If that was the case, everybody would be happy to use tcl/tk, or swing or whatever.

Plus, it's not overkill when you get the browser for free.

We already have browsers installed that are designed to render arbitrary cross-platform GUIs based on HTML/CSS.

Why can't I write a desktop application that just asks the OS for the users preferred browser and provides it with HTML/CSS and UI interaction callbacks / events? Render it in a native looking window.

We shouldn't need Electron at all! It's like we all have this fantastic rail transport network but insist on riding in our own trains.

> Once we set up an array of space telescopes throughout cislunar space (the volume inside the Moon’s orbit) we’ll get pictures of the SMBs in the cores of every nearby galaxy and that’s when the science really gets started.

This gave me goosebumps. That's the kind of stuff that justifies a permanently inhabited moon-base.

Just use half the sugar you usually use and go from there. Your taste will adjust and then you can half it again. If you get as far as one molecule or less of sugar, STOP!

If I understand the situation correctly:

Rails applications benefit from batteries included boilerplate because Rails "owns" the whole stack.

"Modern" (contemporary?) JS applications benefit from separation of concerns, and flexibility because each layer is interchangeable.

So how do we make this better? We can't reasonably split Rails up to match the benefits of JS. The obvious (naive?) solution is to provide a protocol that JS layers can follow. Specific packages/layers can decide to provide the protocol which makes them interoperable. The developer may then pick and choose, knowing that if they choose packages that comply with the protocol, they can use the "batteries included" features.

It would be fairly trivial to identify the major features that most apps reimplement. Getting it all to play well together would not be as easy.

As the OP described, I think Meteor was a great platform, but had some fatal flaws. If "Meteor-the-company" was "Meteor-the-protocol" I think we would have been in a much better position.

Indeed, a terribly interesting read.

I have a couple friends who have a knack of landing on their feet like that. Somehow, they can plan nothing and experience everything in great intimacy and depth. It's a skill. I have no doubt that if the technicians were not there at the same time, some other opportunity would have arisen.

Please don't ask to show me notifications as soon as I load your site. Nobody wants your notifications.