Geekly Articles each Day
📜 ⬆️ ⬇️

Post reinforced retro


Friday post dedicated to how and what people thought a few (ten? Twenty?) Years ago, regarding web development.

It’s worth starting with Joel Spolsky’s blog article; it symbolically goes through all the things that are considered the cornerstones of the stumbling block (puns) of the modern web.

... Here are some examples of things you cannot do well in a web application:
  • Create a quick drawing program
  • Develop a real-time spell checker with a wavy red underline (can we now ??)
  • Warn the user that they will lose all their work if they click the cross on the browser window
  • Update a small part of the view (display), based on the change from the user, without sending data to the server and back
  • Create a fast, keyboard-oriented interface that does not require the use of a mouse.
  • Allow people to work without a permanent Internet connection.


Original
You can not well in a web application:

  1. Create a fast drawing program
  2. Build a real-time spell checker with wavy red underlines
  3. If you’re going to
  4. It makes it a little bit more round
  5. Create a fast keyboard-driven interface
  6. Let people continue working


')
And here is an excerpt from the HTML style HTML from Stefanos Peperoglu

Have you seen our main page in new browsers? Did you like the markup? Think this is a table? No, this is the markup, that's right, but it is made with CSS!

Original
Have you seen our front page with a new browser? Do you like the layout? Think that's a table? Nope It's layout, alright, but it's done with CSS.


A demo of an interactive learning application from ... 1998.
But a particularly interesting sample from the era when Scram did not exist.

... Although there is still no agreement on how the life cycle of a web application should look like in a generalized case, the scheme of activities involved in creating it can be obtained through interpolation of the life cycle of classical information systems and the concept of hypermedia.


Just see, the incarnation stage is separated from the subsequent support stage. This is just a masterpiece!

And here is a fragment of the CSS review (yes, the very first version)

... Take a look at an example of using CSS, suppose you want all h1 tags to use the Verdana font, which is ten points high. Instead of designating it explicitly, you can simply use CSS:


H1 {font-family: Verdana; font-size: 10pt;}


Using CSS gives even more, CSS is able to distribute page content to the very last pixel. By giving you full control over the image of your page, it gives you full control over the text. In fact, CSS will replace some old HTML tags in future versions of browsers ...

Original
Let's take a quick example at a usage of CSS. Suppose you want your H1 tags to have a 10-point Verdana font. You can just use CSS:

 H1 {font-family: Verdana; font-size: 10pt;)


CSS usage goes far beyond that. If you’re liking this page, you can’t make up for it. In fact, CSS will replace some older HTML tags in future browser versions.


Continuation of the same article promises us that JavaScript will be used on the backend. And this is 2002.

And the following excerpt can be cited as an answer to yesterday’s post on HTML6:

... Conclusion. HTML is not effective in itself to develop a myriad of predicted applications. Being expanded with the help of server and client programs, while remaining strange and not closing the issue of performance and security, the task is nevertheless accomplished.

Original
Conclusions. HTML is a web-based application envisioned. It’s not a problem, so it’s not a problem.


Have a good weekend everyone, and remember the main thing - the world will never be the same!

Source: https://habr.com/ru/post/258579/

More articles:


All Articles