Re:.NET 6 Released
by ClumsyPilot on Monday November 08, 2021 @10:21PM
(#29157331)
"I would go so far as to argue for deployment of a self-contained webservice to the end users that could be accessed via any arbitrary localhost browser"
Might as well use Unity game engine and write your app inside one.
Re:.NET 6 Released
by cyber_kinetist on Monday November 08, 2021 @11:06PM
(#29157603)
There seems to be some people writing UI applications with the Godot game engine. Given the dismal state of desktop UI frameworks/tools, this seem to make more and more sense (very light binaries, solid cross-platform support, a WYSIWYG toolkit with good scripting functionality, a high-performance 2D renderer, access to C/C++ if you wan to go low-level, you name it.)
Examples:
Re:.NET 6 Released
by ClawsOnPaws on Tuesday November 09, 2021 @07:48AM
(#29161037)
This is an accessibility nightmare. Please think hard before doing this.
Re:.NET 6 Released
by cyber_kinetist on Tuesday November 09, 2021 @09:14AM
(#29161968)
Well, the two applications I’ve linked above are very graphically intensive (the first one is a map designer, and the second is an image editor), up to the point that it will be meaningless to add any screen reader or dictation support. In some cases you’ve got to admit that it’s close to impossible to bring certain features to people with certain disabilities (although I think this should be its own field of HCI research, maybe it can be possible someday?)
Re:.NET 6 Released
by smackeyacky on Monday November 08, 2021 @07:45PM
(#29156312)
For "regrettable" substitute "tire fire"
There are very few applications that simply cannot work in a web browser in 2021. Even accounting for all the inconsistent bullshit between browser vendors, you can still arrive at something that works as far back as IE6 if you are conservative with your footprint.
Do you really need flexbox, webgl2 and GPS navigation for that warehouse inventory management application? Does everything have to live the various app stores? Will your users revolt if there isn't some ceremonial download & install phase of using your product?
I would go so far as to argue for deployment of a self-contained webservice to the end users that could be accessed via any arbitrary localhost browser before succumbing to the Microsoft Desktop GUI framework du jour.