Multi Commander > Support and Feedback

Java executables treated as archives

<< < (2/2)

Mathias (Author):
If it was another program than java.. yes..  But it is java..  horrible , scary, crappy, dangerous java.. 
Don't ever use java..  Your life will be so much better.. :)

(Sorry I just really dislike java... )

Anyway. The whole system how extensions and virtual file system are connect are going to be change. So maybe when that is redone it might change.. maybe

GrantSP:
hmm... that last comment was both disturbing and promising! :o :)

I actually agree with you about Java, however your/my view on its usefulness as an executable's platform isn't relevant, the standard of its handling is though.

At any rate, it isn't worthy of a lengthy discussion about that, I look forward eagerly to whatever new system you have devised.

Thank you again for your continued support and your fantastic software.

Borg:

--- Quote from: GrantSP on January 01, 2015, 02:26:55 ---Question though. Why are *.jar files added to that extension as archives by default? Surely in the majority of setups *.jar files should always be treated as executables?

--- End quote ---
.jars are archives in default windows environment. No reason to treat them otherwise. They should not be just exec'd 'as are' except if one really knows what he want to do.
Just like treating .doc files as .zip (which they are) would not be that useful either.


--- Quote from: Mathias (Author) on January 08, 2015, 13:34:32 ---If it was another program than java.. yes..  But it is java..  horrible , scary, crappy, dangerous java.. 
Don't ever use java..  Your life will be so much better.. :)

(Sorry I just really dislike java... )

Anyway. The whole system how extensions and virtual file system are connect are going to be change. So maybe when that is redone it might change.. maybe

--- End quote ---
Totally agreed, but sometimes java is a necessary evil, at least until more larger OEMs move away from it.
For example, I have to use this obsolete trash of jre 6 for CISCO DM, since it will not work otherwise and tehres no new version of it.

GrantSP:
@Borg
It is precisely because Windows treats them as archives that I wrote this comment (TBH I'm not even 100% sure Windows does treat them as archives by default, but I'll take your word on it).
Windows will treat them as archives, UNTIL you install Java which then changes that behaviour to have them run as executables. It is MC's secondary step to change that behaviour that is odd.
I think you have completely misunderstood my comments if your response is:
"Just like treating .doc files as .zip (which they are) would not be that useful either."
Who said anything about that? In fact I used those filetypes as an argument against the current MC behaviour.
*.docx, *.odt and other Open-Source document formats ARE archives but Windows won't treat them as such because they are designed to opened by a specific program. So too *.jar. They are designed to be used by the JRE. No one uses *.jar as mere archives! They use *.7z, *.zip or *.rar or any other better compression format.

To summarise.

* People only ever come in to contact with *.jar files when, for whatever reason, they install a JRE, thus causing *.jar files to be viewed as programs.
Jar files are only ever used to act as executables, not as an archive format.
*
At any rate, MC's viability is not dependent on my view of *.jar files and I still consider this to be the best file manager of all, free or otherwise.

Borg:
If you require, you can set the files to be treated as .exe files no matter the file manager you use.

[HKEY_CLASSES_ROOT\.jar]
@="exefile"
"Content Type"="application/x-msdownload"



This makes it executable from anything, including explorer.

I use this tactic to define a custom .exe extension to prevent virus contamination of my command center application.

Navigation

[0] Message Index

[*] Previous page