61–70 of 143 posts
Earlier quoted context omitted.
> like honey stained with drops of bird shit. That is a very specific image that I've never encountered in real life. Is it something that only beekeepers get to witness or is there some bird that homes in on honey pots?
FWIW, here in Eastern Europe we have a similar saying that "A spoonful of tar ruins a whole cask of honey" .
Earlier quoted context omitted.
Honestly, if I had to develop a new desktop app for Windows I would seriously think about Electron. It's frustrating that there is no premier desktop app framework for Windows anymore. UWP is too limited, WPF is pretty much deprecated. Win32 has a huge learning curve and finding devs would be very difficult. Pretty sad situation. Maybe their secret plan is to push people into writing web apps with ASP.NET? Event that…
Why not Qt?
Earlier quoted context omitted.
"It's really telling that in Windows 8/10 they "modernised" some, but not all, of the control panel UI. It's basically random as to whether a setting you need will be in a Metro-flavoured window or a Win32-flavoured one." That's really infuriating. Makes me wonder what all these devs they have are doing the whole day. "To me, the trouble with everything after WinForms is that it lacks a really compelling reason to up…
WPF was really nice from what I remember of it. MVVM was super easily integrated with XAML.
Earlier quoted context omitted.
Why not Qt?
True. A while ago I looked into Qt and one problem was that there weren't too many 3rd party components on the market. For WPF and Winforms you can buy extremely powerful components like data grids and tree views (I have been using Developer Express) but I didn't find any for qt.
http://doc.qt.io/qt-5/qml-qtquick-controls-treeview.html
http://doc.qt.io/qt-5/qml-qtquick-controls-tableview.html
Here are all the controls: http://doc.qt.io/qt-5/qmltypes.html
Just 4 months ago they announced they were suspending development of OneNote Win32 in favor of just the UWP version [1] Moreover, they have (had?) an entire multi-year roadmap planned around UWP, including the eventual release of a version of windows which was supposed to substantially reduce day-to-day reliance on Win32 for lower powered devices, codenamed Project Polaris [2], in an attempt to compete with Chromeboo…
Earlier quoted context omitted.
"Very few commercial products are able to drop Windows 7 support (and like, literally zero enterprise products can drop Windows 7 support)." You would be suicidial if you based any product you want to sell to business on UWP. Not only doesn't it Win 7 or 8 but I don't see in what way UWP is better than WPF.
I have found one working enterprise use case. UWP is great if you are exclusively deploying to brand new Windows 10 Embedded devices. (I think this is now called "Windows IoT Core" or something similar). That's what I've been using it for, and that's worked well. It carries a nice side benefit that our sales team all has Windows 10 Pro laptops, and UWP 'just works' there too for sales demos, presentations, and such.…
This would be a great thing for us. But we already have a huge investment into WPF. How do we get this to UWP?
Just 4 months ago they announced they were suspending development of OneNote Win32 in favor of just the UWP version [1] Moreover, they have (had?) an entire multi-year roadmap planned around UWP, including the eventual release of a version of windows which was supposed to substantially reduce day-to-day reliance on Win32 for lower powered devices, codenamed Project Polaris [2], in an attempt to compete with Chromeboo…
What I find most remarkable is that they are still using Win32!
I wonder what the overall adoption rates are for UWP. As someone who's written Windows software since the 90s, I can't shake the feeling that Microsoft just churns out completely new development stacks every few years.
This is exactly what is holding back Win32: there has not been any serious development of the desktop developer story since WPF in 2005 (WPF only received token updates since then, the last major update was in 2010 when they finally added a DataGrid control, lol) - but WPF is not well-suited for many types of software which have to fall-back on “pure” Win32 and the story there is nothing but depressing. Apple got it…
Just 4 months ago they announced they were suspending development of OneNote Win32 in favor of just the UWP version [1] Moreover, they have (had?) an entire multi-year roadmap planned around UWP, including the eventual release of a version of windows which was supposed to substantially reduce day-to-day reliance on Win32 for lower powered devices, codenamed Project Polaris [2], in an attempt to compete with Chromeboo…
What I find most remarkable is that they are still using Win32!
I wonder what the overall adoption rates are for UWP. As someone who's written Windows software since the 90s, I can't shake the feeling that Microsoft just churns out completely new development stacks every few years.