Any other decent 3D Graphics Engines besides Irrlicht??

[ent1ty]

I don't have to really, I'll just wait for sourceforge to seize this project.

[sudi]

Btw sourceforge seizing projects. Is there a backup somewhere? can we move to github?

[ent1ty]

I've already done the honors: https://github.com/osense/irrlicht-git. Last time I talked to CuteAlien though, he wanted to wait for 1.9 before making it official.

[CuteAlien]

Yeah, gives me a little more time figuring out how to work with git without swearing all the time (using it now in a project, but still struggling... haven't really figured out yet why so many people prefer this to mercurial).

[ent1ty]

People have said that Git is only for super smart people. Even Andrew Morton said Git is "expressly designed to make you feel less intelligent than you thought you were." What's your response to this?

Torvalds: So I think it used to be true but isn't any more. There is a few reasons people feel that way, but I think only one of them remains. The one that remains is fairly simple: "you can do things so many ways."

You can do a lot of things with git, and many of the rules of what you *should* do are not so much technical limitations but are about what works well when working together with other people. So git is a very powerful set of tools, and that can not only be overwhelming at first, it also means that you can often do the same (or similar) things different ways, and they all "work." Generally, the best way to learn git is probably to first only do very basic things and not even look at some of the things you can do until you are familiar and confident about the basics.

There's a few historical reasons for why git was considered complicated. One of them is that it was complicated. The people who started using git very early on in order to work on the kernel really had to learn a very rough set of scripts to make everything work. All the effort had been on making the core technology work and very little on making it easy or obvious. So git (deservedly) had a reputation for requiring you to know exactly what you did early on. But that was mainly true for the first 6 months or a year.

The other big reason people thought git was hard is that git is very different. There are people who used things like CVS for a decade or two, and git is not CVS. Not even close. The concepts are different. The commands are different. Git never even really tried to look like CVS, quite the reverse. And if you've used a CVS-like system for a long time, that makes git appear complicated and needlessly different. People were put off by the odd revision numbers. Why is a git revision not "1.3.1" with nice incrementing numbers like it was in CVS? Why is it that odd scary 40-character HEX number?

But git wasn't "needlessly different." The differences are required. It's just that it made some people really think it was more complicated than it is, because they came from a very different background. The "CVS background" thing is going away. By now there are probably lots of programmers out there who have never used CVS in their lives and would find the CVS way of doing things very confusing, because they learned git first.

Source: https://www.linux.com/news/featured-blo ... s-torvalds

[CuteAlien]

Yeah, I've read that before. Obviously any interface written by Linus is godsent and better than any alternative anyway. Who's going to discuss with that...

[sudi]

Yeah, gives me a little more time figuring out how to work with git without swearing all the time (using it now in a project, but still struggling... haven't really figured out yet why so many people prefer this to mercurial).

I had the exact same feeling when i started working with git and mercurial. But at somepoint i simply went with git. Not really sure what changed though, its really strange.

[archmagus]

@CuteAlien
My morning browsing found this: https://pcottle.github.io/learnGitBranching/
Its a little game/tutorial that is supposed to teach Git commands, commits, branching, merging, etc

Incidentally, what will happen to this forum if/when Irrlicht moves to Github?

[CuteAlien]

Forum will stay here I guess. Other providers don't offer forum support afaik.

And I get the simple git commands. Just most of them seem to be always slightly less comfortable or a little more confusing than the corresponding hg commands. Maybe get's better over time (I've worked with hg much longer), but so far git just feels like a downgrade to me. But got some good reading material already ... just never time to read it.

[sudi]

you could move the website i guess. Github for example allows website hosting and a wiki

[REDDemon]

Git makes mergin simpler. however you should note that actually tortoise GIT is really bugged and caused more troubles than it solves.. luckily if you are on github you have the Github desktop application wich is even more seamless to use than GIT was originally intended for. (there's also a new desktop app, but unluckily requires Win7, while Github app also run on vista)

I never used mercurial, but used both SVN and GIT and prefers GIT a lot

[CuteAlien]

It makes merging patches from other people's trees easier. Doesn't make merging from developer trees easier. In svn that's in Irrlicht's typical case for example: "svn merge -revisions svn+ssh://account@svn.code.sf.net/p/irrlicht/code/whateverbranch ."
Not really complicated and you don't even have to worry about accidentally creating heads and stuff ;-)

But really the reason I want to switch is so that it's easier for other people's to have their own trees. Everything else is just a bonus. Ah ... and to get away from SourceForge with their recent practice of adding spamware to binary downloads and grabbing people's accounts and adding malware. I really loved the service, but that's unfortunately no longer toleratable behavior :-(

[hendu]

Long command with long URL? Compared with
git merge cutealien/somebranch

I would say it does make it easier. Plus the merging algo is better.

[CuteAlien]

The long URL is "somebranch" - it just happens to be on that server. And the revisions part let's me do partly merges which is often useful. And svn merging is no longer what it was at the time git was created - they have improved it as well since those days.

[hendu]

You still have to copy the base url from somewhere, creating chances for errors and long ugly command lines.