3 ms·

To many developers, what the software does is several orders of magnitude more important than how it looks. There are certainly cases where visual design is mu

To many developers, what the software does is several orders of magnitude more important than how it looks. There are certainly cases where visual design is much more critical to what you're building, but there are plenty where it's little more than an annoying distraction.

asjw 7y ago
Use standard html then A select is a select using a native widget An input is a standard OS input widget And so on
- rusticpenn 7y ago
  That does not really work. The whole point of frameworks is to reduce work.
  - DeathArrow 7y ago
    But I can do things faster using MVC on server, ES6 + jQuery on front end, VS having to use something like Angular. It also looks and feels better.
    - yoz-y 7y ago
      > But I can do things faster using MVC on server, ES6 + jQuery on front end, VS having to use something like Angular. That boils down to which technologies you are familiar with. > It also looks and feels better. And this is highly subjective too. Of course looks are very independent from system to system but the feels depend on the tech stack quite a bit.
  - austincheney 7y ago
    The point of frameworks is to provide a common operating pattern (familiarity). Frameworks often increase work at maintenance time due to being higher level abstractions that dictate conventions and practices that limit expressive independence.
  - smaudet 7y ago
    Actually no that was the point of browsers... Where do you think 'select' came from? Long ago we had many UI select boxes in many native frameworks...and decided that was too much work so we made tags...then browsers...most of the disconnect comes because UI controls have so many usages that ultimately you always want to bust out some code. If OpenUI wants to enhance the default behavior of select, input, credit card, etc, cool, if they just want to build anothet framework then I'd rather use svelte or angular or vue. The large libraries already standardize, its just a matter of who 'wins' out, and there are already only a few SPA winners.
  - chinesempire 7y ago
    I guess the OP was answering to > To many developers, what the software does is several orders of magnitude more important than how it looks. Native widgets are still the easier way to produce an UI that looks good enough to work with This link[1] explains how they work on different OS, if they work for desktop apps, why shouldn't they work for web based ones? [1] https://developer.mozilla.org/en-US/docs/Learn/Forms/Basic_native_form_controls https://developer.mozilla.org/en-US/docs/Learn/Forms/Basic_n...
foolfoolz 7y ago
to many customers, there’s a handful of different software choices that more or less do the same thing. so interface and design plays a big role in experience
GuiA 7y ago
If it’s really about what the software does, then the conversation would be about exposing proper APIs that let me view the data, query it, schedule operations on it, etc. But then offering a shinier/slightly more bespoke way of doing that becomes a competitive advantage for your product, and now you get why everyone wants to build their own custom UI. The reason why the aforelinked to Open UI project will never be the One and Only way to build UIs on the web is because there’d too much economic value in being able to do precisely what it can’t do!

asjw 7y ago

Use standard html then A select is a select using a native widget An input is a standard OS input widget And so on

rusticpenn 7y ago
That does not really work. The whole point of frameworks is to reduce work.
- DeathArrow 7y ago
  But I can do things faster using MVC on server, ES6 + jQuery on front end, VS having to use something like Angular. It also looks and feels better.
  - yoz-y 7y ago
    > But I can do things faster using MVC on server, ES6 + jQuery on front end, VS having to use something like Angular. That boils down to which technologies you are familiar with. > It also looks and feels better. And this is highly subjective too. Of course looks are very independent from system to system but the feels depend on the tech stack quite a bit.
- austincheney 7y ago
  The point of frameworks is to provide a common operating pattern (familiarity). Frameworks often increase work at maintenance time due to being higher level abstractions that dictate conventions and practices that limit expressive independence.
- smaudet 7y ago
  Actually no that was the point of browsers... Where do you think 'select' came from? Long ago we had many UI select boxes in many native frameworks...and decided that was too much work so we made tags...then browsers...most of the disconnect comes because UI controls have so many usages that ultimately you always want to bust out some code. If OpenUI wants to enhance the default behavior of select, input, credit card, etc, cool, if they just want to build anothet framework then I'd rather use svelte or angular or vue. The large libraries already standardize, its just a matter of who 'wins' out, and there are already only a few SPA winners.
- chinesempire 7y ago
  I guess the OP was answering to > To many developers, what the software does is several orders of magnitude more important than how it looks. Native widgets are still the easier way to produce an UI that looks good enough to work with This link[1] explains how they work on different OS, if they work for desktop apps, why shouldn't they work for web based ones? [1] https://developer.mozilla.org/en-US/docs/Learn/Forms/Basic_native_form_controls https://developer.mozilla.org/en-US/docs/Learn/Forms/Basic_n...

foolfoolz 7y ago

to many customers, there’s a handful of different software choices that more or less do the same thing. so interface and design plays a big role in experience

GuiA 7y ago

If it’s really about what the software does, then the conversation would be about exposing proper APIs that let me view the data, query it, schedule operations on it, etc. But then offering a shinier/slightly more bespoke way of doing that becomes a competitive advantage for your product, and now you get why everyone wants to build their own custom UI. The reason why the aforelinked to Open UI project will never be the One and Only way to build UIs on the web is because there’d too much economic value in being able to do precisely what it can’t do!