Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

I don't see how yet another ui-definition-format will help to make things simpler. And what UI does a manpage need? Manpages are documents, they have no real ui.


sort by: page size:

Damn, why does everything have to be so complex to make a UI

Not if you want a UI.

I think the HN UI is already simple enough as it is :)

My point is that clients who pay money often want complex UI elements.


A UI is not a web app.

The whole concept of separated “content” form “presentation” in UI is a bunch of nonsense. Maybe it works somewhere in some very limited sense, but I’ve yet to see anything complex that separates these things.

This just seems primitive to me, use a UI framework and make ur life easier...

Isn't the point of an UI to have an ... UI after all? The only ones that I can see being headless here are customers buying in to headless UIs, headless CMSs quackery.

It has to look professional for sure. But the UI won't have anything fancy, only some line charts and few forms.

A UI is necessary for users to use your product. That doesn't mean the UI is your product.

It's not clear though. I still have no idea what these columns mean, despite have been actively learning about them multiple times (as in, I have to re-learn every time I need to use them). They don't even have tooltips.

A good UI should be self-explanatory, this is not even close.


A UI. Not “an”.

UI is not part of the package. Thanks for the feedback!

In what universe are content, forms and menus not part of the UI?

Hi Mike,

Why not the UI?


Why aren’t the easier UIs here already? Adobe was able to already roll out an easier UI.

UI to do that seems awfully basic.

> confusing UI

Anything particular you have in mind?


Maybe they mean UI?

Anything other than UI?
next

Legal | privacy