Paw is a far better app than Postman, on a Mac, for no other reason than it is native and behaves as you would expect.
Goodbye, Native Apps
161–170 of 231 posts
Re: Goodbye, Native Apps
#162Here's the thing. Apple, Google, etc are trying to lock developers into specific platforms. This is why Apple has been so hostile towards PWAs. It's totally possible to build a PWA that behaves like a native app but Apple actively tries to destroy them. There will never be a viable hybrid app platform.
If it were so easy, why is Postman pure garbage compared to Paw on mac?
Re: Goodbye, Native Apps
#163Earlier quoted context omitted.
> Windows Forms will work for forever but hasn't been touched in a long time WinForms very recently got HiDPI support, better accessibility features, and was ported to .NET Core where they also fixed bugs in some controls. WPF in the meantime has been arbitrarily declared stable and Microsoft refuses to fix anything. Everybody is supposed to switch to UWP which they already deprecated or WinUI which hasn't been relea…
Windows Forms remains supported, yeah, but there are no marquee feature to make it easier to develop for really. That seems like it's more focused on getting people to bring their existing WinForms work to .NET Core.
Of all the Windows GUI frameworks WinForm has to be the easiest to develop for, for the majority of developers.
Sure writing large apps is not going to be straight forward, but WinForms is super simple to get started with.
Re: Goodbye, Native Apps
#164How is this getting uovoted ? Is nobody reading the article ? A few paragraphs in and I can see the author has terrible writing skills and doesn't know what he's talking about >In fact, writing software with C/C++ was hard because developers had to work with different operating system API(Application Programming Interface). Seriously ? Writing C++ apps is hard because you had to use different APIs ? That's the least…
"Goodbye, Medium articles". That's the article I want to see trending...
Hey, Jeff Bezos' article was pretty good.
Re: Goodbye, Native Apps
#165I don't think it's impossible to have (relatively) lightweight hybrid apps. The article focuses entirely on electron, which ships a whole browser. There are other options, such as pywebview, that use the system native browser. Still means the underlying JS bundle has to perform, which goes the same for websites too. That said, I normally seek native apps where possible (ripcord for slack, sublime), but that's also pr…
Well, HTML/CSS/JS apps can fit into 5mb size even they contain HTML/CSS/JS engine linked in. I've started publishing Sciter.JS builds to prove that: https://github.com/c-smile/sciter-js-sdk Those binaries contain HTML5, CSS 2.1 + some Level 3 modules and full ES6 engine. 4-5mb of binaries is comparable with native hello-worlds of purely native Qt, wxWidgets, etc.
Unfortunately, Sciter is not opensource. Qt and wxWidgets are.
Re: Goodbye, Native Apps
#166Earlier quoted context omitted.
OmniGraffle could be fine; hasn't Figma shown us the way?
Figma falls into the trap of all other claimed high performing web apps, conflating maintaining a 60fps refresh rate with responsiveness. Try dragging any object around (even simple shapes) and you'll see it trail the mouse cursor in Figma. Does not happen in OmniGraffle. The result is a distinct difference in feel.
Can any person in the planet edit the same document than you in real time, for free, running hardware up to 5 to 10 years old, in Because that is the main feature of figma. Latency of mouse issues is a good trade off from my POV.
Re: Goodbye, Native Apps
#167Earlier quoted context omitted.
As a techie I mostly do not care as long as it works either, if I am not writing it myself (and sometimes even then but I care more now than years ago). However; things do not work a lot of the times; my wife is a writer, almost all my friends are non technical and they complain a lot about how crap everything is. And when I check the culprit is always lack of memory and it is always chrome (the browser and in Electr…
> And when I check the culprit is always lack of memory and it is always chrome (the browser and in Electron) that is eating all of it. Are you sure it's not the "150 IQ I-have-20-tabs-open-at-any-given-time" usage pattern that's actually causing this? I just checked out of curiosity and Edge (for lack of an installed Chrome) used "just" ~380MiB for a rather big website. Sure, websites (and especially ads!) taking up…
> just leave 10 bloated websites open on a glorified netbook from 2014 is more to blame than anything else
Sometimes yes, but;
And how are non technical users supposed to know they should not do this? A lot of people do not know how bookmarks or even ‘windows’ work so they leave open the websites they visit so they do not forget them or have to open them again... How would they know that this is bad? The browser supports it and no one told them. For them there is no correlation between tabs and computer slow. Just as many people, when you say ‘your memory is full’ start throwing away picture from their drive. I think you vastly overestimate computer users... I am ‘the computer guy’ of the village because ‘I do stuff with computers’ and I run into the strangest things all the time. There is, for instance, a large stack of perfectly fine laptops in my house because some people just bought new ones because the old one ‘was slow’ and they were fed up.
Also, what do tabs open have to do with IQ?
Re: Goodbye, Native Apps
#168What a confusing title.
Re: Goodbye, Native Apps
#169How is this getting uovoted ? Is nobody reading the article ? A few paragraphs in and I can see the author has terrible writing skills and doesn't know what he's talking about >In fact, writing software with C/C++ was hard because developers had to work with different operating system API(Application Programming Interface). Seriously ? Writing C++ apps is hard because you had to use different APIs ? That's the least…
It was a bit hard to read honestly. A bit of rehash but that is most of the content on the internet anyways. Felt like someone writing for a school assignment.
Re: Goodbye, Native Apps
#170How is this getting uovoted ? Is nobody reading the article ? A few paragraphs in and I can see the author has terrible writing skills and doesn't know what he's talking about >In fact, writing software with C/C++ was hard because developers had to work with different operating system API(Application Programming Interface). Seriously ? Writing C++ apps is hard because you had to use different APIs ? That's the least…
My thoughts exactly. The one problem with native apps is the resources and time you need to develop the same app for several platforms. That's all.