Originally posted by BlackStar
View Post
Not only is this a terrible reason,
java.awt is also the perfect example why adding a UI library to the standard library sucks. It's slow, it's ugly and it produces terrible UIs that no user would ever want to touch with a ten foot pole.
There is a reason why everyone hates Java UIs, and java.awt is a big part of that reason.
There is a reason why everyone hates Java UIs, and java.awt is a big part of that reason.
Human-machine interfaces like mice, keyboards, touchscreens, microphones, cameras? C++ offers nothing of the sort, you must be looking at a different language entirely.
i admit i expressed my self wrong here. i meant the default minimal human interfaces which once where keyboard and a text based console.
though now it is still keyboard (even if it is by virtualization of other ones), a mouse and a GRAPHICAL based console.
we can twist the words around for ever. the point is, there is a need for minimal gui and drawing features for quickly coding some graphical output/gui.
and it is by far not uncommon for many languages to include such features in their standard libs.
end of story.
Comment