@faraday said in What is out there? Hard and soft codebases of choice.:
@Thenomain said in What is out there? Hard and soft codebases of choice.:
@faraday and @Thenomain on opposite sides of an issue. It should be a podcast!
Maybe so since it seems to happen every other Tuesday 
Call me.
how to find the help files so you can translate def switch_set(self, target, files, rhs, isadmin):
into English. I mean, sure, you have to do the same with iter()
, but 'help iter' and boom, done.
Does Evennia have a 'help switch_set'? If not, it desperately needs one!
Uhh... perhaps I'm missing something critical about your point, but with a mainstream (I won't say "real" because say what you will about MUSHCode but it is a "real" language) programming language
there are literally gazillions of "how to do a switch in Ruby" type tutorials.
Step 1: Recognize a built-in function from a defined function.
- In Mushlikes: Is it a u()? No: Is it in 'help'? No: @function/list.
- In Mainstream Languages: ...?
I assume the answer to 1b is to hope the people who put the framework together have made it easy to find out.
Also, before I get complaints about it, I know that what I quoted is the definition of 'switch_set', but what about 'msg()'? How does a beginning coder know where to find the help file on this function, when beset upon by it while frankencoding?
As you say, though:
The critical piece I think is needed for transitioning from MUSHCode to a different framework is a bridge document.
Considering the tone of my comments, I wholeheartedly agree.
The lack of this document is probably why WTFE's "professionals only" statement came in; sure a pro will know where to find what 'msg()' is, starting with context which is so bloody critical in OOP, but even though Mushers bathe in list-based and OOP-based coding it's going to take some Beginner's Guide education to smooth the transition.
But, I mean, you know that.