Live data from Hacker News

TrueCraft, An Open Source Implementation of Minecraft 1.7.3

truecraft.io

11–20 of 95 posts

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#11

Should have been implemented in Java :/ > A completely clean-room implementation of Minecraft beta 1.7.3 (circa September 2011). > To get started, sign the Contributor License Agreement to establish that you have not, in fact, ever read decompiled Minecraft code. > 'Clean room design is the method of copying a design by reverse engineering and then recreating it' Not sure why it makes sense to say in the repo you rev…

CLEAN-ROOM implementation, it is even linked to an explanation. this means that he DIDN'T read the source-code.

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#12
post #4

... In C#

Yes? It seems like a good choice. Maybe 6 months ago I would have said it's foolish, but with C# being an actual open language now, I'd say it's a rock solid choice.

What would you have done it in? C, and never get any contributor? Or Java, and do as bad as the original?

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#14
post #4

... In C#

Yes? It seems like a good choice. Maybe 6 months ago I would have said it's foolish, but with C# being an actual open language now, I'd say it's a rock solid choice. What would you have done it in? C, and never get any contributor? Or Java, and do as bad as the original?

Take a loot at some open source projects. The Battle For Wesnoth (c++) has many more contributors than FreeCol (Java). I'm sure that number of C# developers in the world who develop open source stuff is even smaller.

If your main goal is to get as many contributors as possible, perhaps JavaScript would be the best choice.

And I'm still not convinced that Java is the main cause the original Minecraft was bad.

Although I write all my games in C++ (native) and JavaScript (web) I did some Java games for Android and the language is rarely the bottleneck if you are careful about object life-cycles. The main bottleneck is usually the graphics hardware.

I'm not saying that C# is bad choice. Actually I think it is a good choice, just not for the reasons you state.

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#15

Earlier quoted context omitted.

Yes? It seems like a good choice. Maybe 6 months ago I would have said it's foolish, but with C# being an actual open language now, I'd say it's a rock solid choice. What would you have done it in? C, and never get any contributor? Or Java, and do as bad as the original?

Take a loot at some open source projects. The Battle For Wesnoth (c++) has many more contributors than FreeCol (Java). I'm sure that number of C# developers in the world who develop open source stuff is even smaller. If your main goal is to get as many contributors as possible, perhaps JavaScript would be the best choice. And I'm still not convinced that Java is the main cause the original Minecraft was bad. Although…

I'm not looking for a bunch of contributors, for what it's worth. I specifically alienate a large group of potential contributors by forbidding anyone who's read decompiled source from contributing.

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#16

Hi guys, I'm the author of this. Going to sleep soon but happy to answer questions when I awake if you leave them here for me.

No eligible for contribution, sadly, but I really look forward to seeing how far you guys go! I too miss the "glory days" of minecraft. Good luck!

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#17

Hi guys, I'm the author of this. Going to sleep soon but happy to answer questions when I awake if you leave them here for me.

No eligible for contribution, sadly, but I really look forward to seeing how far you guys go! I too miss the "glory days" of minecraft. Good luck!

I hope we can build something that brings those good old days back for you. Thanks for your support.

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#18

Earlier quoted context omitted.

Yes? It seems like a good choice. Maybe 6 months ago I would have said it's foolish, but with C# being an actual open language now, I'd say it's a rock solid choice. What would you have done it in? C, and never get any contributor? Or Java, and do as bad as the original?

Take a loot at some open source projects. The Battle For Wesnoth (c++) has many more contributors than FreeCol (Java). I'm sure that number of C# developers in the world who develop open source stuff is even smaller. If your main goal is to get as many contributors as possible, perhaps JavaScript would be the best choice. And I'm still not convinced that Java is the main cause the original Minecraft was bad. Although…

Fair enough, though I didn't mean to imply those were the only good reasons.

I didn't mean to say C++ would have been a bad choice, I was mocking the recurring mentality that a project is only good if it's in C (or even lower-level languages). It's quite tiresome to deal with it, I'm sorry it didn't quite get through.

Java was definitely one of the reasons the original Minecraft was bad though. It (along with bad architecture) was the reason behind the massive server footprint and why hosting minecraft servers is extremely expensive and completely unscalable.

Hey, remember when Notch said he'd open source Minecraft once he was done with it? I remember...

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#19

Hi guys, I'm the author of this. Going to sleep soon but happy to answer questions when I awake if you leave them here for me.

Hey Sir Cmpwn, this is definitely a useful (and perhaps necessary?) project for a massive gaming phenomenon. Thanks for instigating it.

If you had an army of 100 developers, what tasks would you set them to do to improve TrueCraft?

Re: TrueCraft, An Open Source Implementation of Minecraft 1.7.3

#20
post #19

Hi guys, I'm the author of this. Going to sleep soon but happy to answer questions when I awake if you leave them here for me.

Hey Sir Cmpwn, this is definitely a useful (and perhaps necessary?) project for a massive gaming phenomenon. Thanks for instigating it. If you had an army of 100 developers, what tasks would you set them to do to improve TrueCraft?

I would split them up on the following tasks:

- Building a client with OpenGL

- Implementing world logic (grass growth, door logic, etc)

- Improving terrain generation

It'd be really hard to take on 100 contributors at once, though. In my open source projects, I need time to figure out how each contributor writes code and what they like to work on so I can leverage them appropriately.

Post reply on HN