Gregory's Server@tty you could also iterate through the language design in a similar way to how you're learning a framework, the more you better understand the problem you're trying to solve, you can either learn some new library function, or shape the language to address that issue.
|
3 comments
 @tty I think it's the opposite, because so few people actually write accessiblity code due to heavy use of libraries, people don't know how easy it can be, or at least it could be if more people were actually working on the problem space instead of trying to connect ad hoc modules.  @neauoire I'm surprised to hear you say so, actually! To me, the prospect of figuring out how to add unicode (or some other i13n scheme) and also all of the a11y that modern OSes provide to a uxn program sounds incredibly daunting! :o |
@neauoire I wonder what it would be like if most people wrote languages instead of libraries. I think it would make sharing code a lot harder? And there's such a huge body of basic code needed just to make internationalization and accessibility happen, it'd be rough for each person to need to implement it themselves. And of course a language tends to need a community in order to survive & thrive, which might be a lot harder if everyone wrote their own langs.