Am 18.05.2016 um 20:58 schrieb Hardy Ferentschik:
I am usually also against asking questions, but this might be the only
way to get a user to at least read the question. We can write it in as
many places we want, unless we literally force the user to make a
choice, we will have people running into this problem. Since who read
documentation, right? --Hardy
A question like that at first start will not work, as noone would
understand it. I certainly wouldn't have.
The underlying problem here is that we are very much cli-focused. This
works well when someone has read through all the documentation and knows
all the syntax, but it is not discoverable. If I don't know something is
there, I will never know how to find out about it.
We have some tooling for Openshift in Eclipse, but for any but the
trivial things, we fall back on text editing. This shifts the burden of
knowing Openshift configuration syntax to the user.
<rant>
The learning curve for Openshift is about as steep as the north face of
the Eiger. If you have no previous knowledge of docker, kubernetes,
networkding architecture, etc. you're totally up shit creek without a
paddle. I would peg the effort at about 3 weeks of straight reading. The
tools don't really help: when I do a "oc describe pods", you get about
10 pages of technobabble which no sane person can parse. Of course it
takes you an hour to find a simple misconfiguration!
</rant>
/Thomas
_______________________________________________
Devtools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/devtools
