Xye is a puzzle game in which the objective is to get all the gems in each level. The mission is not as easy as it sounds: there are traps, monsters, and very hard puzzles everywhere. The player can interact with objects in the game in a lot of ways, and some of the objects can also interact with other objects.
Re: Seriously, I agree
My first time on linux was to deal with ./configure It scared me out. After some time I got used to it. You can't expect every user to get into it without deciding to go to a more merciful os.
I really think that linux is superior and that's mostly the reason I would want it to be more friendly to new users. It could replace the propietary OSes that are not as good.
I wouldn't live without nautilus' emblems I never had a better organized PC.
Seriously, I agree
I've been programming for 4 years. Let me compare the (minimal) process involved in developing a windows application, releasing it and then when a user installs it in his system:
- You take a compiler+ide combo , code and compile it.
- You then take the .exe and every file required by it and zip it.
- If the app requires some libraries you can just include them in the zip or tell the users to download them and put them in the same folder as the application.
- You go to some server and upload the zip.
- User X downloads the zip, unzips it and executes the application.
Now when it is linux:
- You find a compiler then an ide or get used to just using a text editor and code the program.
- Now you have a problem, first you have to decide if you are going to release it as source, as rpm or as deb . Each has its own issues.
- Releasing as source involves making a good Makefile that could survive the differences of all the platforms, or using autoconf / automake thus having to follow all the requirements they meet. And you will end up learning some oscure scripting language without the intention of doing so.
- Making rpm or deb requires you to know how to make them.
- You upload the tar.gz or the rpm or the deb.
- A user downloads and has to hope the program has .rpm or .deb depending on what distribution he is using.
- He also has to make sure if the dependencies are installed in his system other wise (the process became recursive) he has to install the dependencies required by the dependency then the dependency.
- Now he has to hope the rpm or the deb would work. If he is using ubuntu or debian he is in trouble cause he may not know if the .deb file would actually work in his distro.
- Or if he is using the source package he has to go command line (and probably first learn how to go command line) and do ./configure (if available) or make and hope it would work.
- Of course, he will then need to install or update GCC and probably make
let's say he survived make or "./configure make make install" now where is the program?
* Alternatives are required.
* Binary packages need an standard.
* We could use an X application to handle the installation of tar.gz source file when they use gnu configure, at least getting rid of the command line 50% of the times would be a lot of help.