Should "Hello world" be standardised?

[sancarn]

It strikes me that many different implementations of "Hello World" are implemented here, many with very different results...

Something like

#include <iostream>

int main()
{
   std::cout << "Hello World" << std::endl;
}

in c++ which prints to stdout, is very different from the result of

msgbox "Hello World"

in vba prints to a Win32 MessageBox (a dialog), which is very different from the result of Blender.py

import Blender
from Blender import Scene, Text3d

text = Text3d.New("Text")
text.setText("Hello World")
Scene.GetCurrent().objects.new(text)
Blender.Redraw()

which draws some 3d text in a scene.

In my opinion it doesn't really make a whole lot of sense to say all of these are the same "hello world". In reality Python's equivalent would be print("Hello world") and VBA's would be Debug.Print "Hello world".

Sure these other implementations are neat, and it's nice to be able to see different kinds of "hello world" mechanisms.

Related to #1527 it might be better to create subfolders for these implementations instead with a standardised naming convention?

root
|- c
|  |- stdout.c
|  |- dialog.c
|  |- lib-qt.c
|  |- ...
|- py
|  |- stdout.py
|  |- dialog.py
|  |- lib-qt.py
|  |- app-blender.py
|  |- ...
|- vba
|  |- stdout.bas
|  |- dialog.bas
|  |- lib-qt.bas
|  |- ...
|- ...

[Tonibrown20]

It strikes me that many different implementations of "Hello World" are implemented here, many with very different results...

Something like

#include <iostream>

int main()
{
   std::cout << "Hello World" << std::endl;
}

in c++ which prints to stdout, is very different from the result of

msgbox "Hello World"

in vba prints to a Win32 MessageBox (a dialog), which is very different from the result of Blender.py

import Blender
from Blender import Scene, Text3d

text = Text3d.New("Text")
text.setText("Hello World")
Scene.GetCurrent().objects.new(text)
Blender.Redraw()

which draws some 3d text in a scene.

In my opinion it doesn't really make a whole lot of sense to say all of these are the same "hello world". In reality Python's equivalent would be print("Hello world") and VBA's would be Debug.Print "Hello world".

Sure these other implementations are neat, and it's nice to be able to see different kinds of "hello world" mechanisms.

Related to #1527 it might be better to create subfolders for these implementations instead with a standardised naming convention?

root
|- c
|  |- stdout.c
|  |- dialog.c
|  |- lib-qt.c
|  |- ...
|- py
|  |- stdout.py
|  |- dialog.py
|  |- lib-qt.py
|  |- app-blender.py
|  |- ...
|- vba
|  |- stdout.bas
|  |- dialog.bas
|  |- lib-qt.bas
|  |- ...
|- ...

[includeRubiks]

I agree. There should be subfolders for different types of hello worlds (3D, text, etc)