The issue here, is a misunderstanding about levels of abstraction.
Now, if somebody says, "you can only program a PC Microprocessor with machine code" the quick response will be, "no, I can do it in basic/C/C++ and so forth.
Those are both true. But, they all boil down to machine code instructions; Programming Languages are levels of abstraction.
If somebody says that "the PC only recieves input through it's external ports" people will be quick to say things like "what about the mouse or keyboard" well, they evidently plug into the ports. they are merely a physical form for which to send the data into those ports. Trackballs and mice, as well as trackpads and trackpoints, are all physical abstractions to the same PS/2 or USB interface, and they all behave the same way- they move the pointer.
What was said is that HTML can only really be used for web development.
Guess what? it's true. Sure, you can use your Trillex, or Komposer, or Even microsoft word, but they all output the same thing; the same thing the browser understands. HTML.
Web pages are all interpreted by a browser in HTML. a browser only knows HTML; anything else is Within the HTML (javascript or CSS, for example) referenced by the HTML, or never actually seen by the browser because it's handled by the server (php, asp, cgi). (passing note for XHTML here)
That being said HTML is the only way to control what a browser displays on your web page. How you CHANGE that html, however, is another story altogether. geek saying that trillex is a alternative to HTML is like saying that cake mix is an alternative to baking from scratch; it certainly is an alternative, but the result is still a cake. with Trillex (A.K.A, the mix cake) you have predefined elements. generally, cake mix offers a single option; chocolate, for example. you cannot, under normal circumstances, substitutes ingredients already in the mix. however, with a cake made from scratch, you can add and change anything you please; as long as you know your cake.
Basically, what I mean is, everybody loves cake. I mean, that's why it's a birthday tradition, right? because everybody loves cake.
I mean... umm... The same story goes for HTML. of course the analogy isn't perfect, but in general since a program for generating HTML can only create a predetermined number of permutations of HTML based on it's programming and those permutations far from fit every discernable situation for using that HTML that it stands to reason that learning HTML on it's own can be advantageous for editing the results from these so-called HTML editors directly, (like putting cherries or something in a cake) Or, creating new HTML documents from scratch.
Learning HTML itself is more advantageous to the activity of web development in the same way that learning how to bake a cake is advantageous to the act of making a scrumptious cake. and, with web development, you taste the rewards of your efforts with a web site that doesn't look the same as every grade school student in the country. With a cake, you get a *censored* FINE TREAT! and everybody loves a good piece of cake. therefore, I preclude that everybody loves HTML.
Now, another parallel could be drawn re my last argument about "sameness". a web dev tool like Trillex or whatever- is programmed. it can only have a finite number of outputs for any input. Additionally, since the input is completely predefined (oh! you want bold text! you want italics?) then so is the output (again, finite) (ok, heres a b and an i tag). Since most people generally don't stray too far from the defaults; almost all pages created with a tool look the same.
Take Microsoft word's resume wizard. Anybody who uses this is a tool. I mean, sure, it looks good- but how many OTHER resumes in that pile are going to have been made using word's resume wizard? How will yours look any different from that smelly guy that lives down the street? the answer is, it won't, and it won't attract much attention.
Now, people say, "but it doesn't matter if my site looks the same as a bunch of others! After all, it's the site content that's more important!" Which is right, as well as wrong. You see, just as with a resume, if the reviewer of a resume notices that a good number of resumes use the same default formatting as the default options for the resume wizard, they might not even BOTHER to look at the content. basically, by designing the resume, or a web site, in a professional (which means no trillex or other finite-output tools) manner, you tell people that you CARE about the content, that the content was done with as much care as the site itself. This is not the case with standard boilerplate web sites, where you evidently were more interested in putting the content up then anything else, which, on the one hand, can appeal to people, because you evidently had a reason to post it. But, looking at it, they will notice your excitement came purely because of your discover of the ability to use Marquee and blink tags nested together. Not as tags of course, but as formatting options within your finite output state machine HTML outputter.