On 2015-03-07 at 07:51, Russel Winder via Digitalmars-d-announce wrote:
> Many C++ > projects are returning to it, Go enforces it if you let it,
> many Python projects are starting to use it in spite of PEP-8.

Now, that you mentioned Python, it was one of the main reasons why I moved away from tabs. I was used to tab-completion in the shell and Python's interactive interpreter (and didn't want to rebind that feature to some key combination on every system that I worked with). Whenever I copied chunks of tab-indented source code into the interpreter, it got screwed up, because the indentations had vanished, so eventually I switched to using spaces only and had no problems ever since.

>> I can also say from experience that removing tabs from Phobos source has removed
>> a lot of irritation with messed up code rendering and wasted effort arguing
>> about it. We're not going back :-)
>
> And I am not going to work on Phobos for exactly the same reasons. My
> loss, not yours.

You must be joking. :)

If at all, the problem with Phobos' style isn't with horizontal spacing but vertical space.
Consider the waste of space below. Too much scrolling and I lose focus. Now, *that* is really irritating. ;)


    struct Boo
    {
        int a;
    }

    struct Foo
    {
        int a;
        auto opAssign(Foo foo)
        {
            assert(0);
        }
        auto opEquals(Foo foo)
        {
            return a == foo.a;
        }
    }

    X calculate(Range)(Range r)
    {
        static if (something)
        {
            import whatever;

            auto result = xxx();

            size_t i;
            foreach (e; r)
            {
                doSomething(result[i], e);
                ++i;
            }
            return result;
        }
        else
        {
            auto a = blah();
            foreach (e; r)
            {
                a.put(e);
            }
            return a.data;
        }
    }

On Saturday, 7 March 2015 at 07:20:01 UTC, Russel Winder wrote:

> They are hamstrung by the continued obsession with the text file as the
> primary unit of editing. As soon as they and programmer users get over
> this, the sooner we can get on with better UX for development.

I agree.

On Friday, 6 March 2015 at 20:22:42 UTC, Ben Boeckel wrote:
> And I find that monospace fonts tend to make it much easier to tell the
> difference between 'l', '1', and 'I'. Not so important in English, but
> it can be all the difference in code.

http://abload.de/img/tmpr3uv6.png I see no less difference than in monospace font.

In fact, I failed to find good monospace font for source code, it used to be Courier New 9pt, but it works well only on displays no bigger than 1024*768.

On Friday, 6 March 2015 at 20:22:42 UTC, Ben Boeckel wrote:
> You're making assumptions about the features of your users' editors. These features are not trivial to implement

Implementation of three different word wrapping algorithms in Scintilla took 52 lines of code. For comparison: a rudimentary D lexer is only modest 400 lines.

> requires things like pygments and other tools used to render code to the web with all kinds of logic to handle dynamic viewports of the shown code.

You think too web 2.0, browsers wrap text since the beginning, tools only need to stop fight with them.

On Sat, 2015-03-07 at 12:28 +0100, FG via Digitalmars-d-announce wrote: […]
> 
> If at all, the problem with Phobos' style isn't with horizontal spacing but vertical space.
> Consider the waste of space below. Too much scrolling and I lose focus. Now, *that* is really irritating. ;)
[…]

This is definitely one of the major reasons I cannot bear to read Phobos formatted code. Others seems to like it, it's a world full of acceptable differences of opinion.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On Sat, 2015-03-07 at 12:57 +0000, Kagamin via Digitalmars-d-announce wrote:
> On Friday, 6 March 2015 at 20:22:42 UTC, Ben Boeckel wrote:
> > And I find that monospace fonts tend to make it much easier to
> > tell the
> > difference between 'l', '1', and 'I'. Not so important in
> > English, but
> > it can be all the difference in code.
> 
> http://abload.de/img/tmpr3uv6.png I see no less difference than in monospace font.

That will be because it is a reasonably designed font.

I have to admit though, the glyph widths are a bit large in the example font. I guess I prefer something a bit more condensed.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder