I made my first website in sixth grade. I was the only girl in my computer programming class.
I'm OK with procedural code, and the web is a top-down type of problem. It makes sense to me that you have HTML, you spit out a bunch of HTML, then you call a function to do something and then call another function.
All the PHP code I've seen in that experience has been messy, unmaintainable crap. Spaghetti SQL wrapped in spaghetti PHP wrapped in spaghetti HTML, replicated in slightly-varying form in dozens of places.
I was in love with HTML and certain that the whole world was about to learn it, ushering in a new era of DIY media, free expression, peace and democracy and human rights worldwide. That part didn't work out so well, although the kids prefer YouTube to TV, so that's something.
My dad grew up as a computer programmer, so he always had random computer software, and I started opening up editing software at age 12 and figuring out how to build websites.
I think there certainly was a milestone in the '90s with regards to the Internet achieving critical mass. There were several magical factors that came together: the creation of HTML by Tim Berners-Lee, the drop in the price of communications, and all the PCs out there that you could put this software into.
Even if it's not always the best markup, what are Facebook and Twitter? They're web standards with some scripts. They may not validate, but they're still CSS layouts and simple markup, and that's great!
World Wide Web: Proposal for a HyperText Project
This coined the term “World Wide Web”. The co-author of the document was Robert A Caillau.
For most of the '90s and the first part of this decade, content providers who wanted to publish online only needed to worry about the graphical web browser.
I fix things now and then, more often tweak HTML and make scripts to do things.
Flash and HTML have co-existed, and they're going to continue to co-exist.
If someone had protected the HTML language for making Web pages, then we wouldn't have the World Wide Web.
Betting completely on HTML5 is one of the, if not THE biggest strategic mistake we've made.
The prime reason the Google homepage is so bare is due to the fact that the founders didn't know HTML and just wanted a quick interface. In fact, it was noted that the SUBMIT button was a long time coming and hitting the RETURN key was the only way to burst Google into life.
The beauty of HTML was that one-way linking made it very simple to spread because you could put something up and take no responsibility whatsoever. And that creates a society in which people display no responsibility whatsoever. That's the problem.
I learned HTML in high school and then graduated to CSS. It's a great way to exercise my mind. But it's frustrating as hell.
I taught myself HTML.
We're actually helping advance HTML5 in some very concrete ways, such as Edge, which is in beta.
I was really just a hard-core geek, if you will, in 1996, and was building websites as a hobby. I started doing a lot of web design and development and built my first website on the now-defunct GeoCities platform.
If you use the original World Wide Web program, you never see a URL or have to deal with HTML. That was a surprise to me - that people were prepared to painstakingly write HTML.
This is exactly how the World Wide Web works: the HTML files are the pithy description on the paper tape, and your Web browser is Ronald Reagan.
When Tim Berners-Lee invented the computer code that led to the creation of the World Wide Web in 1990, he did not try to patent or charge fees for the use of his technology.
I'm just loving BlueGriffon Editor! XML, HTML5, CSS, ARIA, SVGEdit all built in.
Real web designers write code. Always have, always will.
The kind of programming that C provides will probably remain similar absolutely or slowly decline in usage, but relatively, JavaScript or its variants, or XML, will continue to become more central.