Newly Born Person Whose Name Is Gallant Servant

My name is Gallant Servant. Simply, I am nobody. But that does not mean I have nothing to say. For you, I am now a blank slate. Let me fill that with a little bit about technology now.

As you can see, I have a website. I have developed this website. I can write HTML, CSS, and JavaScript.

I know a lot about HTML.

• One HTML page must contain one HTML main element (<main>) and one HTML heading one element (<h1>). No more, no less.
• The HTML button element must have a type attribute.
• There are no disabled links. Do not make them. Never.
• The <section> and <article> elements do nothing unless they are programmatically labeled.
• The <div> markups with CSS are cool.
• React developers love adding <div> elements for no reason.

After learning HTML for five years, I find myself still learning it.

I underestimated HTML. It was easy. I thought I would not need to spend hours to know how to write correct HTML. Now I think about HTML carefully. But I do not want to take it too seriously because that will make me unhappy. Getting a headache because of HTML is not a good idea.

CSS is CSS. It was confusing. Now it is still confusing because CSS gets more power that I probably will never use. CSS nesting, for example, is not useful in most cases. Writing CSS like writing Sass is not nice for me. I prefer a stylesheet that is simple and easy to understand. Nesting makes a stylesheet hard to understand. Deep nesting is a bad idea and a bad action. That is true when we write CSS or Sass. For me, nesting is okay as long as it does not make a stylesheet more complex than it should.

I have no comment on JavaScript.

Next, I do not agree with the idea of replacing HTML with something else. I have read a blog post, but I forget where I found it, proposing to replace HTML. I like HTML. Also, having another alternative markup may make the browser go crazy. Think about this. How does the browser establish new accessibility guidelines for new markup? Even if someone argues to use Markdown and Frontmatter for the metadata, why do we need to have two ways for a browser to render information? Also, Markdown is not flexible anyway. We do not have the beautiful <div> and the gentle <span> elements for layout. I disagree with replacing HTML.

Moreover, CSS frameworks and JavaScript frameworks are tools for me. If you know how and when to use them, they are great. If someone uses them for small websites, they are bad. They add thousands of lines of code unnecessarily. Those lines of code are useless. I use them if I need them. But I prefer writing my own code and using compilers like Sass or Eleventy.

Moving on to the Large Language Model (LLM), I have no problems with ChatGPT. I hate the attitudes of people taking the output of ChatGPT or Gemini or other chatbots for granted. We should not believe everything that LLM spits out. Just like we can not believe what everybody says, we can not believe stupid ChatGPT too.

To wrap up, here are some key points:

• I know a lot about HTML. I have lots of experience writing HTML. I do not want a replacement for HTML.
• I know CSS. I like CSS. But it can be confusing sometimes.
• I skip JavaScript.
• All frameworks are tools. Knowing how and when to use them is important.
• ChatGPT or Gemini or any other chatbots should be trusted blindly.