More intuitive symbols

[piaste]

From #19

@piaste:

I found the emojis hard to read at a glance, I was constantly having to glance down to the documentation.

@rainbyte:

This received some discussion earlier, and the result was the current emojis.
I'm not sure if these new emojis are more intuitive than the old ones.

Maybe they should give the idea of steps and the idea of greater support?
I mean, being able to order them is important too.

Compare this order (based on how fast you can move):
… ->🚶-> 🚲 -> 🚗->🚀

With this one:
❔ -> ❌ -> ❕ -> ➕ -> ✔️

It is not clear why they are higher level than the others.

Maybe we could just use numbers instead?
? -> 0 -> 1 -> 2 -> 3
In this way zero means nothing, and the rest mean higher level by steps.

Using letters is other option too, in this way:
? -> X -> C -> B -> A
But I think numbers are easier, they are universal.

[piaste]

Using numbers or letters would be great, I think colours are more important though to be able to parse the table at a glance.

[rainbyte]

It is also important being able to see links to websites when they are provided.
Colored emojis hide links (see issue #6), which already is confusing.

[rainbyte]

Some ideas using only ascii chars:

IDE	Syntax highlight	Code Completion	Error Reporting	Lint	Code Format
Current	…	🚶‍♂️	🚲	🚗	🚀
Op1	?	0	1	2	3
Op2	?	-	C	B	A
Op3	…	-	+	++	+++

[pascalpoizat]

I think Op3 is more clear.
Yet, it could also come with detailed information / criteria on why one uses + / ++ / +++ for a given feature.

[rainbyte]

There is a description about the levels below the table.
Please, tell me if it is not clear enough.

[pascalpoizat]

Let me first precise that the table is already very good. I was able to choose Haskero using it and I am very happy with this choice (keeping also the Spacemacs Haskell Layer for other things).
Most of the descriptions are ok but what makes for example having a car vs a bicycle for Error Reporting, or for Code Format?
Precisions that I think could be useful are:

• Code Format: whole document (stylish-haskell) and/or function-level (hindent). I use the two for very different things (imports vs function-level indent / styles). Having both gives a car and only one gives a bicycle?
• Goto Def: within the current file or project-wide (I am just beginning to use Haskero but I have to find where the global search is)
• Find Usages could come with Global Replace. And it may also be limited to the current file in some frameworks and project-wide in others
• I also saw (in the Dev.To forums I think) that some frameworks where ok for small pieces of code but slow for bigger projects. But scalability is a very complicated criteria to give.