Programming

17417 readers

76 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

126

Why isn't there a way to make near-native desktop UIs that's similar in ease to browser and electron UIs? (lemmy.ml)

submitted 10 months ago by cyclohexane@lemmy.ml to c/programming@programming.dev

39 comments fedilink hide all child comments

it seems ridiculous that we have to embed an entire browser, meant for internet web browsing, just to create a cross-platform UI with moderate ease.

Why are native or semi-native UI frameworks lagging so far behind? am I wrong in thinking this? are there easier, declarative frameworks for creating semi-native UIs on desktop that don't look like windows 1998?

you are viewing a single comment's thread
view the rest of the comments

[–] MajorHavoc@lemmy.world 14 points 10 months ago (1 children)

Lots of other very pragmatic solutions also seem ridiculous.

Every problem is going to cost either clock cycles or highly skilled programmer time.

Currently, in the world, all eleven competent user interface element developers are occupied with more important tasks.

Until one of those eleven finds some extra free time, the rest of us get to slap electron into everything, and he thankful we can spread our atrocious CSS anti-talents to one more problem-space.

[–] cyclohexane@lemmy.ml 3 points 10 months ago* (last edited 10 months ago) (1 children)

~~Who are these eleven? Didn't realize the number is so small. Who determines who they are?~~

Turns out it was an exaggeration

[–] MajorHavoc@lemmy.world 9 points 10 months ago (2 children)

I am, hopefully, exaggerating on the 11 count. I don't know the exact number, and likely no one does - but it genuinely is shockingly small, considering how critical usability and accessibility are to everyday use of code.

Anyone can study the principles of usability and accessibility, but the number of experts we have really is far too few, and I suspect it's is why we have so much reuse instead of innovation, right now.

[–] cyclohexane@lemmy.ml 2 points 10 months ago

My bad for misunderstanding your exaggeration 😅

[–] bmarinov@lemmy.world 2 points 10 months ago

You are not far off. In my previous project we attempted to rewrite a desktop app and we started with a skeleton crew. Hiring for the frontend was tough, we got one very good xaml (wpf / winui etc) dev in the first year. Then, in the middle of the corona lockdowns, for 12 months we kept only getting mediocre candidates from across the world, with no relevant experience whatsoever. Then we found our second full time frontend dev, who only stayed 3 months and once he saw how clueless management is, bolted.

Funnily enough the aforementioned manager experts started asking what's wrong and why we 'fail to fill the positions'. We were stuck in the native desktop world product-wise, an unattractive and challenging tech stack with difficult problems to solve, with poor management and low budget. That's what was up. Now I'm happily working on the backend / web / cloud side of things and I'm definitely not looking back or picking up another tech lead position for a project with non existent team to start with. /o\