Earlier quoted context omitted.
By that logic, if I fork chromium and make a custom version of it that's hard-coded to start up HN in the first tab, then I've made a native HN app.
No, you've "made" a native browser that opens HN in the first tab.
Going native
181–190 of 245 posts
Re: Going native
#182Earlier quoted context omitted.
On the other hand, there's Paw, a delightful native app in the same category that has morphed into an unusable tool that hangs every few minutes. Native experiences aren't always better.
Paw founder here. I'm very sorry to hear this. If you don't mind, I'd love to know more details on what's happening. The logs available in Paw menu > "Get Debug Info…" are very helpful. If you don't mind sending these details to support@paw.cloud, we'd be very grateful! Thx!
Re: Going native
#183Earlier quoted context omitted.
>> When we tell people we have a native app, they get it. People go to our apps page, download the installer and see everything exactly as they expect things to be. The term "native" is used to describe apps developed for a specific operating system. By this definition, clearly Electron apps (and hence Postman) are not native apps. Having to download an installer doesn't make it native. On smartphones, all apps are i…
The pedantic force is strong here.
Native doesn't mean browser in a window. Same as realtime doesn't mean "it'll get there faster. Maybe"
Re: Going native
#184These 'native' wrapped apps on desktop and mobile are always less in some way than a real native app. I know there is a cost benefit argument, but I personally avoid them.
Re: Going native
#185Postman founder here HN folks. Great to see the post get featured on the homepage! Lots of discussion about what is exactly native. I have posted some replies but some other points about the choice of words: 1. Postman has 3 million users and about 1.5 million MAUs. When we tell people we have a native app, they get it. People go to our apps page, download the installer and see everything exactly as they expect thing…
If not, I still can't make the switch. :(
Re: Going native
#186On my current job we use the Postman Chrome app to test out apis. I'm looking for a FOSS command-line alternative to it because it's very slow on my laptop (Linux, Celeron, HDD, 4GB RAM) and the UI makes no sense to me.
I know I could just use cURL (which I do) and/or HTTPie but it would be nice to have options.
Is there any alternative that would suit my needs?
Re: Going native
#187Slightly off-topic: On my current job we use the Postman Chrome app to test out apis. I'm looking for a FOSS command-line alternative to it because it's very slow on my laptop (Linux, Celeron, HDD, 4GB RAM) and the UI makes no sense to me. I know I could just use cURL (which I do) and/or HTTPie but it would be nice to have options. Is there any alternative that would suit my needs?
But it's currently geared towards running collections created in the Postman App (i.e, it's not for one-off requests like cURL is).
Re: Going native
#188Earlier quoted context omitted.
The pedantic force is strong here.
Words have meaning. Native doesn't mean browser in a window. Same as realtime doesn't mean "it'll get there faster. Maybe"
Is JavaScript native? JavaScript is interpreted when it first starts, but eventually turns into machine code through JIT by most JS engines. So is JavaScript native because it gets converted to machine code, just as C++ does?
If you say no, then you're saying only AOT compiled languages are "native". So that eliminates Python, Erlang, Java. Even C#, the "native" language on Windows is not AOT (in most cases).
So that doesn't work, AOT has nothing to do with native. JavaScript is just as native as any other language.
So maybe the problem is the UI, right? That's where most people seem to have a problem. So as long as you are using Cocoa on OSX, GTK on Gnome, Metro on Windows, you're native, right? Oh, wait, Metro apps can be written using HTML, JS, and CSS. They are essentially identical to Electron apps. In fact, Microsoft supports (and encourages) you to create .appx packages from Electron apps [1].
Oh, and all of those Qt apps out there (like Calibre, by far the best ebook management software), not native (despite being C++ in a lot of cases).
So yeah, "native" has meaning, but the meaning is as clear as mud.
Re: Going native
#189Postman founder here HN folks. Great to see the post get featured on the homepage! Lots of discussion about what is exactly native. I have posted some replies but some other points about the choice of words: 1. Postman has 3 million users and about 1.5 million MAUs. When we tell people we have a native app, they get it. People go to our apps page, download the installer and see everything exactly as they expect thing…
As a user, I want an application that performs well (which Electron apps typically don't, my main issue with Atom and Slack), and I want an app that fits in well with my platform, which an app designed to be the same on all platforms just isn't good at.
Re: Going native
#190Slightly off-topic: On my current job we use the Postman Chrome app to test out apis. I'm looking for a FOSS command-line alternative to it because it's very slow on my laptop (Linux, Celeron, HDD, 4GB RAM) and the UI makes no sense to me. I know I could just use cURL (which I do) and/or HTTPie but it would be nice to have options. Is there any alternative that would suit my needs?
We have a CLI for Postman: https://github.com/postmanlabs/newman But it's currently geared towards running collections created in the Postman App (i.e, it's not for one-off requests like cURL is).
Oh, btw: I read my comment again right now and it sounds a little bit arrogant. I'm sorry about that... By saying it's slow and that I don't like the UI, I mean no offense to you guys.
Actually, I think Postman is a very useful tool and my co-workers seem to love it. I's just not for me and my crappy laptop hahah.