I must admit as a file system developer everything has seemed reasonably clear and functional. I make my life slightly more challenging by using C instead of Objective-C which has some neat perks in MacFUSE. I haven't had any problem with it that I haven't seen a resolution right here on the list, with a bit of study of the FUSE API documentation from Linux or parts of the relevant Apple documentation.
You're right that developers should be the only one openly using it, I'm yet to see a framework from any vendor that was designed to be some how operated by a non-developer end user - a regular Apple Mac OS X (or even iPhone) user doesn't have to deal with the Core Data Framework or similar and they shouldn't have to either. I don't see why MacFUSE would be any different. So lets go to something more constructive, what is your issue with MacFUSE in particular? Sam Moffatt http://pasamio.id.au On Thu, Apr 1, 2010 at 1:16 PM, wrecca <[email protected]> wrote: > This is a HORRIBLE framework with insufficient tools or instructions. > IT is totally unsafe to use it. It will crap on your mac hard disk if > you make the slightest mistake. > > The devs obviously know this so they have tons of excuses about it > being a framework not an app. It is a totally beta framework and > should not be used by anyone except the developers who need to put a > lot more work into it before letting others use it. > > -- > You received this message because you are subscribed to the Google Groups > "MacFUSE" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/macfuse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macfuse?hl=en.
