Live data from Hacker News

Fuse

fusetools.com

11–20 of 100 posts

Re: Fuse

#11
I really don't see the point.

If you don't need cross platform the best choice is native so you can leverage all the platform goodies.

If you do need cross platform and have the budget you will go with 2 native projects.

If you don't have enough budget for 2 native apps you have a few options.

Cordova is good enough for a lot of apps. Even Apple uses Webviews in its own apps. Also check the Missive mail client all built with web technologies:

https://medium.com/missive-app/our-dirty-little-secret-cross...

We are building a universal app that will work on iOS, Android, Mac, Windows, and Chrome OS with a single code base.

If you need better performance you can always use React Native, NativeScript, or Xamarin.

Why go with this Fuse thing?

Re: Fuse

#12
post #7

Since the submission has no legit title either, I'll just respond with: https://en.wikipedia.org/wiki/Filesystem_in_Userspace

I don't really get the trend of name collisions. First React, now Fuse... what's next, a Linux brand of detergent?

Re: Fuse

#13
post #3

Looks like Electron on steroids. The landing page is nice but it's like putting lipstick on a pig - it's still a pig in the end. Also, I never understood why people hate native languages so much - why do you want to replace everything with Javascript? It's shit - it's a necessary evil in the browser but when the environment gives you something better (Swift, Java, etc) why not enjoy it?

Seems like .NET [1]? Plus weird build tools and binaries in source control 1: https://github.com/fusetools/fuselibs-public/blob/master/.tr... 2: https://github.com/fusetools/fuselibs-public/tree/master/Stu...

Markup looks a lot like XAML

Re: Fuse

#14
post #7

Since the submission has no legit title either, I'll just respond with: https://en.wikipedia.org/wiki/Filesystem_in_Userspace

Oh, I was thinking this http://www.adobe.com/products/fuse.html

Oh, I was thinking this instead...

https://www.redhat.com/en/technologies/jboss-middleware/fuse

Re: Fuse

#16
post #3

Looks like Electron on steroids. The landing page is nice but it's like putting lipstick on a pig - it's still a pig in the end. Also, I never understood why people hate native languages so much - why do you want to replace everything with Javascript? It's shit - it's a necessary evil in the browser but when the environment gives you something better (Swift, Java, etc) why not enjoy it?

> Also, I never understood why people hate native languages so much - why do you want to replace everything with Javascript?

Because people don't have the time, money or expertise to write multiple completely separate code bases for cross platform apps and having to keep these code bases in sync will dramatically slow down your ability to extend and adapt your product...?

Re: Fuse

#17

Why choose this over native apps?

In general, it's a matter of rapid prototyping for POCs or MVPs that don't need much. As an example, I'm currently working on a system that needs a minimal iPhone/Android app. Just a login view and a couple buttons. I'm the only engineer working on this, and I have way more important stuff to do than manage two completely different codebases right now.

So for my MVP, I'm planning to use React Native to build the minimal interface, and then (once funding clears and we can figure out the hiring situation) I'll get one or two engineers to work on building a native app for each system.

Re: Fuse

#18
post #12
post #7

Since the submission has no legit title either, I'll just respond with: https://en.wikipedia.org/wiki/Filesystem_in_Userspace

I don't really get the trend of name collisions. First React, now Fuse... what's next, a Linux brand of detergent?

https://www.linux.com/news/there-linux-detergent-out-there-a...

Re: Fuse

#19

Why choose this over native apps?

In general, it's a matter of rapid prototyping for POCs or MVPs that don't need much. As an example, I'm currently working on a system that needs a minimal iPhone/Android app. Just a login view and a couple buttons. I'm the only engineer working on this, and I have way more important stuff to do than manage two completely different codebases right now. So for my MVP, I'm planning to use React Native to build the mini…

> and I have way more important stuff to do than manage two completely different codebases right now.

But why are they completely different? Surely the UI parts are different, but the meat of the work done internally is exposed by a common API?

Post reply on HN