The thing is, code is never perfect and as a language keeps
evolving your latest tricks will soon become obsolete or
deprecated. It happens all the time (Java, Cocoa etc. "use this
instead"). If I look back at the code I wrote years ago, it still
works, but it's no longer up to current standards (my own as well
as the language's). I think including things in the std. library
really makes people (like me) use and thereby _test_ them, asking
(not so) stupid questions on D.learn etc. If I have learned
anything it's that my most ignorant (innocent) questions trigger
responses from people who are more experienced, pointing out this
or that flaw, telling you tricks and workarounds. D is a language
based on practical experience, not on ideology or anything
(that's why I like it). So stdx, while it seems to be a good
idea, would be a limbo for code, eternally in a state of "not
bad, but not quite there yet". And all code is like that. We'll
never quite get there.
- Re: Official stdx Jacob Carlborg
- Re: Official stdx Dicebot
- Re: Official stdx David Nadlinger
- Re: Official stdx David Nadlinger
- Re: Official stdx Jacob Carlborg
- Re: Official stdx Joseph Rushton Wakeling
- Re: Official stdx John Colvin
- Re: Official stdx Kagamin
- Re: Official stdx eles
- Re: Official stdx Dicebot
- Re: Official stdx Chris
- Re: Official stdx Jesse Phillips
- Re: Official stdx barryharris
- Re: Official stdx Robert Schadek
- Re: Official stdx Joseph Rushton Wakeling
- Re: Official stdx growler
- Re: Official stdx eles
- Re: Official stdx Kagamin
- Re: Official stdx Dicebot
