Add a v2unix driver

[BDisp]

I would like to propose adding a new v2unix driver for Unix systems. It only use native Unix libraries. Old Curses is totally absent in this driver. System.Console is only used in the Suspend method which it's common to v2net and v2unix. Works on Linux and macOS.

[tig]

Why?

[BDisp]

Because in the v2 there is no driver with Unix native library that can be used in their system. The .NET is a cross platform library where almost of the System.Console properties and methods, with Unix limitations in some objects, that can be used in all platforms. But like the Win32 API are used only for Windows, I thought implementing a pure native Unix library only for Linux, Mac, BSD, etc.
It isn't the old curses which has many bugs and incompatibilities, but only pure native libraries that the Unix system know about.

[tig]

What, specifically, does not work with v2net?

[BDisp]

What, specifically, does not work with v2net?

Of course it work with v2net in Unix systems, like also v2net work in Windows. Then, why we need v2win after all? Well I think I made my point.

[BDisp]

Another important reason is the possibility to have one driver specific for each system and a one driver for cross platform systems. This way we can compare the performance of all them.

[tznind]

Then, why we need v2win after all?

This!

I think we should push for v2net as default as it is most csharp and standardised.

I dont see harm in v2win and v2unix but I think they should be 'opt in'.

With regards to performance, I think its good to explore but also bear in mind that differences must be noticeable not academic (e.g. 10ms vs 20ms is not noticeable - 100ms vs 200ms probably is)

[BDisp]

Then, why we need v2win after all?

This!

I think we should push for v2net as default as it is most csharp and standardised.

This was a sensate opinion which I totally agree that v2net should be the default driver for all systems. If somebody complain about performance differences between Windows and Unix system, for sure isn't due to the common code, but perhaps due the console type, in Windows it uses Win32 API and in Unix only Ansi sequences configuration.

I dont see harm in v2win and v2unix but I think they should be 'opt in'.

I also don't see any harm at all. By the contrary it's good to have them for each specific system and who want to use them must pass the driver argument v2win for Windows and v2unix for Unix systems.

With regards to performance, I think its good to explore but also bear in mind that differences must be noticeable not academic (e.g. 10ms vs 20ms is not noticeable - 100ms vs 200ms probably is)

If any of them has noticeable differences, like 100ms vs 200ms, the worst performance driver should be removed immediately.

If you both agree I can write the logic to make the v2net the default driver in the PR #4251. If so, please explicitly tell me here. Thanks.

[tznind]

If you both agree I can write the logic to make the v2net the default driver

Works for me