Hacker Newsnew | past | comments | ask | show | jobs | submit | grugdev42's commentslogin

Worth it for what?

The "what" is important.


Neat, but this game seems too simple. I think AI has missed a core gameplay mechanic.

There needs to be something to stop a deadlock. Like an element of luck for the hares?


Think of this as a very old game, with a board simple enough you can trace it on the ground and play with a few stones, with rules simple enough you can explain/understand in 30 seconds. Like tic-tac-toe, mancala, nim, chopsticks... simplicity and portability wins over perfect rules or balance.


Neat as a pet project, but anyone thinking of using this is production is insane.

Rewriten in Rust is becoming a meme now.


Been a meme for a while now. I avoid that noise on principle.


Too little too late. Xbox is dying and PS won.

Try listening to your customers next time.

We don't want to be ripped off with paying for assets we don't own.

We don't want another monthly subscription.

We want the old games, remastered, with fully functioning multiplayer.


> We don't want to be ripped off with paying for assets we don't own.

You do know that PS is literally stopping physical games? You will not own anything.


> Too little too late. Xbox is dying and PS won.

Seems like currently PS is too determined to snatch defeat from the jaws of victory.


crazy second sentence which makes the rest of the comment not make any sense


We should have just added optional body support for GET requests.

So much simpler...


The only valid argument against HTTP GET with a body is that it has privacy/security risks.

Exist stuff (caches, CDN, etc.) could serve private information because the HTTP GET is cached without checking the request contents. The new standard can avoid this because old stuff does not know about HTTP QUERY.


More complex actually


The cofounders will not put your priorities first. Their only goal is to make money for themselves. They will axe you if they feel like it.

They are not hiring a founding engineer because they want to do something nice. They've probably realised this path is cheaper than hiring an external software development company.

Don't think for a second that you will be an equal in this relationship. You will be at their beck and call. You will be forced to write bad code to get early sales.

You'll get paid less to do more. I would stay where you are.


What a brilliant resource.

I think this should be used in schools.

Really easy to understand and instantly captivating.

Please do more topics!!! :)


Two things jump to mind:

1. The best product rarely wins. As much as it pains me, marketing and sales matter more than product. Your competitors are likely better at marketing and selling themselves and their product.

2. It's a bit cliche, but look into the candy, vitamin, and painkiller theory. Your product is not a painkiller and I suspect it's a candy. Candies are very very hard to make a successful business from.

But, I wish you the best of luck. :)


Marketing and sales has always been and will always be the problem of running a successful app or business.

I suggest he stops coding, like he said the product is better than his competitors, which is a great start. He should focus all his energy into solving this cosmic problem of marketing and sales and with time he will have users.

This is how business is runned


Thank you for releasing this for free! :)


The reality is that SaaS is hard to sell these days. It's not 2010 any more, the gold rush is over.

That's not to say it's impossible, but it's so much harder than 15 years ago.

Everyone and their dog is starting a SaaS. Very few are selling them. And almost no one is turning one into a job.

The people who are self employed by their SaaS started them 5 years ago.

Get a job, support your family, and protect your mental health.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: