I had an idea recently. This might make me seem lazy or whatever, but it's an idea nonetheless. Instead of using a .jar file for the Minecraft launcher, you devs out there could make a real package file for Linux. A real package file would strike down a lot of complications from using java. Linux, as many people don't know, has interpreters for many coding languages. Python, C++, etc can be used to code a package file. One thing that might limit you is that there are 2 main formats. That really has no issue, as you can create one file, then alter its source code, and then compile it against a different package format and compress it into a different file type.
The two major formats go to Debian and derivatives(.deb file) and openSUSE, Fedora, and derivatives(.rpm file). Any other OS that isn't derived from those two(Gentoo, Arch, etc) could use a .jar file still, as they don't use the archive formats that the above OS's do. And this would be a one-time thing, as most OS's can use an older package file regardless of their version gap, as long as there wasn't a HUGE change in the OS in question since the file was created.
That's my idea. I hope you like it, and if not, let me know what I can do to revise and make it better.
Thanks for reading
Meh. Good point. I was kinda just putting it out there, and seeing if someone would see what I was talking about. In my opinion it's just a bit tiring to use the command line to launch Minecraft every time, and face the possibilities of Linux Java killing your computer.
And by the way, the most time you'd ever spend on a package file is learning the language you're going to code it in. Like I said, it has interpreters for many languages, so you could code it in most non-web based languages.
The two major formats go to Debian and derivatives(.deb file) and openSUSE, Fedora, and derivatives(.rpm file). Any other OS that isn't derived from those two(Gentoo, Arch, etc) could use a .jar file still, as they don't use the archive formats that the above OS's do. And this would be a one-time thing, as most OS's can use an older package file regardless of their version gap, as long as there wasn't a HUGE change in the OS in question since the file was created.
That's my idea. I hope you like it, and if not, let me know what I can do to revise and make it better.
Thanks for reading
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAgreed, on behalf of all ISU members.
No need for this.
And by the way, the most time you'd ever spend on a package file is learning the language you're going to code it in. Like I said, it has interpreters for many languages, so you could code it in most non-web based languages.