Web Application VS Windows Application
-
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
Removing all that fluff can have its advantages. Especially for little utility apps with simple purposes.
Outside of specifically maintaining an OS, which is a unique thing as it's neither business software (it's IT) nor does it have the possibility of being cross platform, what kind of apps do you see taking advantage of this?
I think it's just the principle of the thing.
Less fluff means smaller, faster, easier to distribute, fewer dependencies to test/update or that can potentially introduce security leaks or be hacked or become outdated.
To me this is one of those questions like, why not just get the vehicle with the big frame and all the horsepower and lights and hydrolics? If gas is cheap and they can afford it, why not?
On the other hand, if all you need is to get from A to Z, the expensive gas gets annoying, possibly a liability.I'm old school. I still have "768 megs of RAM yeah!" mindset, where everything should be highly optimized and using as few resources as possible.
People nowadays don't care for that, it's just "I got lotsa RAM, bring on the fluff! Who cares!"To each his own. There always seems to be sacrifice between convenience and optimization.
-
@guyinpv said in Web Application VS Windows Application:
I think it's just the principle of the thing.
Less fluff means smaller, faster, easier to distribute, fewer dependencies to test/update or that can potentially introduce security leaks or be hacked or become outdated.
I'm thinking that it is more like virtualization.... standard abstraction layers add "more stuff" but in standard ways that make development, stability and security easier.
-
@guyinpv said in Web Application VS Windows Application:
I'm old school. I still have "768 megs of RAM yeah!" mindset, where everything should be highly optimized and using as few resources as possible.
People nowadays don't care for that, it's just "I got lotsa RAM, bring on the fluff! Who cares!"To each his own. There always seems to be sacrifice between convenience and optimization.
The thing is, for 99% of business apps, that stuff bring huge limitations and risk. Things that businesses "just expect" these days. Like being able to expose to the outside without needing to send company laptops home, not needing a VPN for app access, linking to common tools, not needing Windows in order to run a business tool, not needing CALs to something unrelated to run a business app, not needing to pay for Windows Server to deploy their own software, not needing to pay for desktop management, etc.
Desktop / native apps create a lot of cost and risk. They might seem small and tight, but that's not the factor that matters 99% of the time. It's just not important. The risks, the limitations that those apps bring can be crippling.
-
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
I think it's just the principle of the thing.
Less fluff means smaller, faster, easier to distribute, fewer dependencies to test/update or that can potentially introduce security leaks or be hacked or become outdated.
I'm thinking that it is more like virtualization.... standard abstraction layers add "more stuff" but in standard ways that make development, stability and security easier.
In theory.
I don't think tools like Electron are this "standard" yet. Could be wrong. I've had plenty of "websites in a box" apps crash on me and do stupid things, screwy UIs and other bugs.
I'm sure they will improve. I'm looking forward to trying Electron myself. I just don't have a project yet!
-
@guyinpv said in Web Application VS Windows Application:
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
I think it's just the principle of the thing.
Less fluff means smaller, faster, easier to distribute, fewer dependencies to test/update or that can potentially introduce security leaks or be hacked or become outdated.
I'm thinking that it is more like virtualization.... standard abstraction layers add "more stuff" but in standard ways that make development, stability and security easier.
In theory.
I don't think tools like Electron are this "standard" yet. Could be wrong. I've had plenty of "websites in a box" apps crash on me and do stupid things, screwy UIs and other bugs.
I'm sure they will improve. I'm looking forward to trying Electron myself. I just don't have a project yet!
It's not a panacea, you still need a good product. Native apps have these problems, too.
-
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
I think it's just the principle of the thing.
Less fluff means smaller, faster, easier to distribute, fewer dependencies to test/update or that can potentially introduce security leaks or be hacked or become outdated.
I'm thinking that it is more like virtualization.... standard abstraction layers add "more stuff" but in standard ways that make development, stability and security easier.
In theory.
I don't think tools like Electron are this "standard" yet. Could be wrong. I've had plenty of "websites in a box" apps crash on me and do stupid things, screwy UIs and other bugs.
I'm sure they will improve. I'm looking forward to trying Electron myself. I just don't have a project yet!
It's not a panacea, you still need a good product. Native apps have these problems, too.
There is something about a native app though. I feel like companies spend requisite time doing actual QA and releasing a stable product. Or maybe it's perhaps that when programming in C++ or C or whatever, the profiling and debug tools are that much better?
Companies that release websites-in-a-box products follow a different mindset, the "hustler" way of "release soon, release often", depending on their failing products to be debugged by their own users who will report their issues diligently and submit bugs to github.
End users should not be QA, no matter what tool or language. But if all you're doing is programming a "website" then updates are a cinch you don't have to worry about your product sucking after release.
Desktop apps crash, but rarely due to stupid UI, UX issues that would have only needed 10 minutes of real QA and testing to discover. Or more robust debugging and compile tools.
-
@guyinpv said in Web Application VS Windows Application:
There is something about a native app though. I feel like companies spend requisite time doing actual QA and releasing a stable product. Or maybe it's perhaps that when programming in C++ or C or whatever, the profiling and debug tools are that much better?
But only Linux products are using C to any degree. Windows is mostly C# and VB.
-
@guyinpv said in Web Application VS Windows Application:
Companies that release websites-in-a-box products follow a different mindset, the "hustler" way of "release soon, release often",
Hardly hustler. It's the only reasonable way. Make it in the dark, throw it over the fence and walk away is so much worse.
-
@guyinpv said in Web Application VS Windows Application:
End users should not be QA, no matter what tool or language.
Unless you want to deliver something for end users and need to know what they want, like, need, etc.
-
@guyinpv said in Web Application VS Windows Application:
Desktop apps crash, but rarely due to stupid UI, UX issues that would have only needed 10 minutes of real QA and testing to discover. Or more robust debugging and compile tools.
What do you feel that they mostly crash from?
-
@guyinpv said in Web Application VS Windows Application:
But if all you're doing is programming a "website" then updates are a cinch you don't have to worry about your product sucking after release.
That's not true if you think about the fact that they might be deployed locally. No more true of one than the other type.
-
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
End users should not be QA, no matter what tool or language.
Unless you want to deliver something for end users and need to know what they want, like, need, etc.
"Features" are different from "bugs".
I sure as shooting "want, like, and need" the product to actually WORK before I start acting as free beta tester for an app. Especially if I've paid for it.
If the app is free, well there is always an out. -
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
Desktop apps crash, but rarely due to stupid UI, UX issues that would have only needed 10 minutes of real QA and testing to discover. Or more robust debugging and compile tools.
What do you feel that they mostly crash from?
That is far beyond my knowledge. I imagine the roots dig deeper into dependencies and OS drivers and so on.
A website-app-in-a-box, well it might crash because Javascript is insufficient as a desktop language and was overwhelmed in some way? I've seen UI elements disappear behind other elements of the boundary of the app's border. I've seen font issues, graphics rendering issues, issues of "flashing" elements and other refresh issues. I've seen the apps freeze up when working too fast and it can't keep up.
I don't tend to see UI issues in a solid desktop app. They are typically built on standard UI libraries from the OS, where all the rendering and sizing and refreshing are pretty locked in.
Again, I use plenty of both types of apps, but here in 2016, I still prefer native, what can I say?
-
@guyinpv said in Web Application VS Windows Application:
That is far beyond my knowledge. I imagine the roots dig deeper into dependencies and OS drivers and so on.
Native apps tend to be much more susceptible to those things. That's one of the specific advantages of more modern methodologies and the same as why virtualization makes for more stable environments.
-
@guyinpv said in Web Application VS Windows Application:
A website-app-in-a-box, well it might crash because Javascript is insufficient as a desktop language and was overwhelmed in some way?
But that's silly. A native app could do the same because C# wasn't up to the task. Both carry the risk, in neither is it serious.
-
@guyinpv said in Web Application VS Windows Application:
Again, I use plenty of both types of apps, but here in 2016, I still prefer native, what can I say?
How many people can even identify native anymore? MS Office has been web for two generations now.
-
@guyinpv said in Web Application VS Windows Application:
I don't tend to see UI issues in a solid desktop app. They are typically built on standard UI libraries from the OS, where all the rendering and sizing and refreshing are pretty locked in.
Canvas is to. If either has issues with that, it's not the language or approach that is the problem. That's an artifact of the developers not making something that looks good. That's a separate issue.
-
@scottalanmiller said in Web Application VS Windows Application:
@guyinpv said in Web Application VS Windows Application:
I don't tend to see UI issues in a solid desktop app. They are typically built on standard UI libraries from the OS, where all the rendering and sizing and refreshing are pretty locked in.
Canvas is to. If either has issues with that, it's not the language or approach that is the problem. That's an artifact of the developers not making something that looks good. That's a separate issue.
I think this conversation is beginning to turn in to "which programming language is better" at this point.
The "native vs. web" idea is lost. What does "web" even mean then? Almost all native apps are connected to the web too. So we're really talking about "web languages" rather than internet-enabled.That means we're talking about JS versus C#, Visual C++, VB etc. Or even further, JIT versus compiled. Or further, higher level versus lower level.
What difference does it make at this point? I appreciate that lower level "native" apps tend to be better tested, require fewer dependencies, are more stable and faster. I also appreciate web-language containerized quazi-desktop cross-compiled apps can be easier to design and distribute and work across platforms. It also offers traditional "web devs" a means to crossover into desktop development.
You said Office has been "web" for two generations. Not sure what you mean here. Yes they have "web versions" that can run in a browser, but they still have their C++ native Windows apps, or Objective C for Mac version. It ain't written in JS in a container!
I've used Word and Excel in the browser, as well as the desktop apps, and FAR prefer the desktop apps still. The web version has crashed on me more times in a year than my desktop Office has ever crashed in my lifetime.
Web is convenient and pretty dang cool, but still has its drawbacks. -
@guyinpv said in Web Application VS Windows Application:
That means we're talking about JS versus C#, Visual C++, VB etc. Or even further, JIT versus compiled. Or further, higher level versus lower level.
No, you are mixing the concept of how the app is delivered versus in what language it is written in. You can write web apps in C# primarily. It's NOT about the language, it's about the ideology and design.
-
@guyinpv said in Web Application VS Windows Application:
You said Office has been "web" for two generations. Not sure what you mean here.
I mean it is a web page. It's shown in a frameless browser. It's a web app like any other. LibreOffice offered this one generation ahead of MS Office, as well.
