Live data from Hacker News

Closing a 30 pixel gap between native and web

blogs.windows.com

171–180 of 313 posts

Re: Closing a 30 pixel gap between native and web

#171

Earlier quoted context omitted.

We're taking about a trillion dollar company who can afford all of the talent and has very limited time pressure. I would prefer they do it correctly.

This misses the point. A trillion dollars goes a lot further when the software is cheaper.

But VSCode isn't cheaper. They had to pour millions of dollars and countless man hours into it. And none of those translated into any meaningful improvements of the platform.

Re: Closing a 30 pixel gap between native and web

#172
post #86

> installed desktop web apps are really starting to look and feel like native apps I think we are having the opposite problem: native apps are really starting to look and feel like web apps, and in many cases, they are. The problem: the web has a terrible UI toolkit for desktop apps. It has clickable links and basic forms, that's all. It was made for documents, not apps. If you want better than that, you have to rewr…

> The problem: the web has a terrible UI toolkit for desktop apps. It has clickable links and basic forms, that's all

I think you're not giving credit to the best part about the web: CSS.

I've been programming GUIs with Java AWT, Swing, and Qt for years. Nothing comes close to CSS when it comes to defining layouts.

Re: Closing a 30 pixel gap between native and web

#173

Earlier quoted context omitted.

The Windows style for bars (both title and status) is way too large. Ditto for the task bar. It's no wonder people are tempted to not use status bars, and shove as much as possible at the title. If applications could exploit the task bar, they would too. (Anyway, you don't need an entire bar for system interaction. But applications aren't designed in a way that allows this.)

The older I get, the more I respect bigger user interface elements and text. It's not even failing eyesight either; I'm still in my mid 30s and have great eyesight and dexterity. I've come to respect bigger interface elements because they are quicker to work with. I don't have to peck for a title bar if it's there, big and empty in front of me. I don't have to hunt for a scroll bar that hides itself and reveals a 1px…

Absolutely!

Unfortunately, the designers all seem to have 72" 8K professionally color-calibrated monitors and a $1000 mouse, and think if it works for them that's good enough.

I saw the start of this in the mid-2000s when the web trend was for grey-on-grey 8px fonts. I went to the designer and asked what the heck he was thinking and he showed me his screen; and yeah it was kinda legible there. Still bad design.

Nowadays the trends are flat UI where you don't even know what's clickable/actionable, hidden things that only appear when you mouseover them, and on touchscreens, secret functions that only trigger if you swipe in just the right way with just the right number of fingers in just the right pattern.

Design has just been getting progressively worse and worse ever since 2000/Windows XP.

Re: Closing a 30 pixel gap between native and web

#174
post #44

I actually wish programs do not put content in the Title bar area. The title bar area is meant for users to move the Window around. Try opening Microsoft Word, make the window narrow and drag the window. You have to hunt for a small bit of empty space in the title bar or you have to understand you could drag on the Title text, Search box and the Sign in Username, but not the Auto Save text, Upcoming Features icon, or…

I much prefer what a lot of Linux desktop environments support, which is holding down alt and clicking anywhere on a window to move it. With that + a keyboard shortcut for closing a window you can get rid of title bars on apps entirely if you want. Sadly Windows doesn't support it natively, although there's another comment on this thread talking about ways to make it work.

Windows has pretty decent keyboard shortcuts for manipulating windows‘ positions, though. Clicking and manual window manipulation should very rarely be necessary, shouldn’t it?

Re: Closing a 30 pixel gap between native and web

#175
post #86

> installed desktop web apps are really starting to look and feel like native apps I think we are having the opposite problem: native apps are really starting to look and feel like web apps, and in many cases, they are. The problem: the web has a terrible UI toolkit for desktop apps. It has clickable links and basic forms, that's all. It was made for documents, not apps. If you want better than that, you have to rewr…

> The problem: the web has a terrible UI toolkit for desktop apps. It has clickable links and basic forms, that's all I think you're not giving credit to the best part about the web: CSS. I've been programming GUIs with Java AWT, Swing, and Qt for years. Nothing comes close to CSS when it comes to defining layouts.

I don't know I tried to understand CSS many times but never managed to get it: I'm a backend developer nowadays.

Re: Closing a 30 pixel gap between native and web

#176
post #90
post #86

> installed desktop web apps are really starting to look and feel like native apps I think we are having the opposite problem: native apps are really starting to look and feel like web apps, and in many cases, they are. The problem: the web has a terrible UI toolkit for desktop apps. It has clickable links and basic forms, that's all. It was made for documents, not apps. If you want better than that, you have to rewr…

> Traditional Windows apps all use system provided common controls, because they are good, and therefore they have a consistent look and feel, even through OS updates. This hasn’t been consistent since at least Vista and the release of WPF, which does totally custom control rendering. Circa 2006. I think web is taking over on Windows because any of 10 or 15 different design systems can get you to a better app than th…

> Even Office and Visual Studio (not Code) are using web technologies to render substantial parts of the UI.

Any more details on what web technologies are being used in Visual Studio and what parts of the UI are done with web?

Re: Closing a 30 pixel gap between native and web

#177
post #6

With all this Electron and PWA focused development a cannot shake a feeling that we add an extra layer of a "runtime" on top of an operating system, that could be avoided. An extra layer which occupies RAM space and processor time which feels unnecessary but it is where we are headed. I wonder if the reason is simple, that we (myself included) have not provided anything better or the reason is that big corporations w…

I'm gradually starting to see X11/Xlib as a solution for cross platform desktop apps. It is the native GUI API for most UNIX operating systems. Ports exist for Windows(win11) and Mac which makes X11 technically portable to them as well. Its not exactly an elegant solution I have to admit. But the licensing problems with QT make a lot of people nervous, GTK seems to be pretty polarizing, and for whatever reason WxWidg…

I think wxWidgets was pretty big in the 2000's, with quite some programs using it. To name one example, the Code::Blocks IDE uses it.

FLTK has never seen adoption even to the level of wxWidgets I think, but to be honest it is also quite simply hideous. I have not found a proper looking theme for it either, since I was mildly interested in using it to add a simple GUI to a Rust tool.

Re: Closing a 30 pixel gap between native and web

#178
post #28

I want the opposite of a PWA. I want an app which can be compiled into Desktop/mobile builds and also interpreted in browsers. An alternate HTML/CSS/JS with no JavaScript.

So ... Flutter? https://flutter.dev/

Flutter looked cool, until I realised it was a Google product. After being burned by Angular, Material, and all the things killedbygoogle, I'm not sure I can stomach even trying it out. Is that stupid?

Re: Closing a 30 pixel gap between native and web

#179
post #152
post #88

Earlier quoted context omitted.

> For companies like Microsoft making something like Teams, I think it sucks. They have the resources to make native apps and when you have tens of millions of users, adding support for another platform would cost them pennies per user. Back when I worked at Microsoft, 2014 or so, we had serious problems finding Win32 developers. We essentially had to train people up. While I am sure the Windows org had lots of them,…

> Back when I worked at Microsoft, 2014 or so, we had serious problems finding Win32 developers. We essentially had to train people up. Microsoft only has itself to blame for this. They charge an arm and a leg for their dev environment setting it up is a pain no matter what, the stuff you get “free” when you pay for the dev environment is not nearly enough to create anything worthwhile. So why should any CS departmen…

It may be more the myriad of technologies and the fact that they change them out almost as often as their underwear. Same problem we have with javascript frameworks.

What is it that we need 10 years experience in this week? Win32, OCX, DCOM, CORBA, OWL, ActiveX, WinForms, WPF, ASP, SliverLight, .Net, XNA (etc. etc.)?

Kind of amusing that so many people turned to web tech to escape that treadmill and then just totally recreated it in javascript.

Re: Closing a 30 pixel gap between native and web

#180
post #117

Earlier quoted context omitted.

> I don’t think Windows is ever going to be left behind I do, but not for reasons most people think about. The Windows 11 UI/UX is trying to emulate MacOS. Clearly, Microsoft is giving the finger to people that use Windows because it's not MacOS. I can't wait for Windows 12 to happen and all the UX things I hate about MacOS get implemented in Windows. Might as well start training my muscle memory to hit the Windows k…

> so that when Microsoft decides that CTRL-X/C/V should be WIN-X/C/V, I'll be ready Already starting to go this route. While you can still ctrl-x/ctrl-v, most of their newer features implement the windows key, including win-v for paste using clipboard history. While printscreen works, you can use win-s to take a screenshot now too.

Well as long as printscreen key still works, adding another shortcut is fine. And win+s isn't really that bad compared to Mac's ctrl+shift+alt+spacebar+F4+right-click or whatever it is. Mac has the worst, most bizzare 'short'cuts anyone ever come up with.
Post reply on HN