Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[guitarxe]

I'm just curious to know what language was used to write Dwarf Fortress? Does anyone know?

[G-Flex]

It's written in C++ (not that this means C++ is particularly good for this sort of thing, or that it isn't, but that's another debate entirely).

[Still Standing]

English?

[darius]

English?

Yes plain old English

[guitarxe]

Lol... English, haha 

G-Flex, do you think a game of this type could be made in Java?

[MaDeR Levap]

G-Flex, do you think a game of this type could be made in Java?

Sure it can. Speed will be completely different matter, he, he, he.

[Kholint]

Let's not forget that java comes with a host of powerful concurrency tools and data structures built directly into the core language that make it a lot easier to write parallel programs without any faffing about with external libraries.

Java's inherently slower than C++ (ignore low level micro-benchmarks that put java and C++ on a roughly equal footing - it's the real world usage that counts, and java programs generally use heavier design using lots more objects and so on), but it'd be interesting to see whether a single threaded C++ pathfinding or flow simulation could be outperformed by a fully multithreaded java equivalent on a quad or octocore processor!

[devek]

It isn't even about that.

If you wouldn't use Java because it is slow.. you shouldn't use C either. You should write everything in assembly because it is the fastest language.

[KrunkSplein]

Forget all that noise - what I want to know is how long it takes for a fresh build to compile.

[Creamcorn]

Forget all that noise - what I want to know is how long it takes for a fresh build to compile.

This, I imagine that this is when we wait for the next update.

[ZCM]

It isn't even about that.

If you wouldn't use Java because it is slow.. you shouldn't use C either. You should write everything in assembly because it is the fastest language.

These days a good C compiler will outperform hand-coded assembly.

[devek]

Keep telling yourself that.

[thewonderidiot]

Depends on who wrote the assembly code. Let's face it, unless you're an assembly guru, there are a lot of tricks up the compiler's sleeve that most people would never think of.

That being said, well-written assembly code will always be the fastest.

[Medicine Man]

Ultimate

unRestricted

Internet

Super

Terrific

[devek]

Are you kidding? I rarely see compilers bust out SIMD and some of the shitty ones (like MSVC) don't even make sense. The argument doesn't follow. You can't say that a c compiler will beat a bad programmer. By that logic, Java blows away C because it can implement a hash better than a bad C coder.

I've still yet to see any compiler make a functional program in less than 1000 bytes. If I wrote dwarf foreman in assembly it would be like 10k, and I would love to see any C program touch it for speed.