3 ms·
Sorry, but I found http://lunduke-sdk.com/index.php?title=The_Lunduke_Language http://lunduke-sdk.com/index.php?title=The_Lunduke_Language disappointing. It's p
by prodigal_erik 15y ago
Sorry, but I found http://lunduke-sdk.com/index.php?title=The_Lunduke_Language http://lunduke-sdk.com/index.php?title=The_Lunduke_Language disappointing. It's pretty much Integer BASIC plus subroutine parameters, with about thirty years of programming language innovation waiting to be recapitulated. Say I wanted to write an RSS reader that sorts items by date and/or title. How would I store a collection of feeds, each of which is a collection of items, when the only data structure is a map of key/value strings? How would I write a sort that uses a comparator parameter to learn what order two items should appear in? If the list is huge, how do I re-sort gradually without freezing the UI? If some feeds are RSS and others scrape Twitter or something, how do I dispatch to whichever implementation of getMoreMessages is appropriate for each feed? I can't remember the last time I had to write an entire application without being able to do all of these things and more (reflection? plugins? mocks for testing?) nearly effortlessly, and I doubt many people will be willing to do without them.
- BryanLunduke 15y agoThere are, certainly, many new features that can be added to the language itself. What exists now is powerful enough to build some pretty robust applications, but more flexibility and power in a language is always good! One of the (many) reasons this is becoming an open source project... we, as a community, can decide what new language features are most vital and add as needed.