So, there are a lot of package managers already, for various systems. I'm wondering if we should leverage what's been done there already, maybe not to reuse the clients, but to reuse the way the repositories were defined. A good example would be FreeBSD's ports, for which there exist several "clients" like portupgrade, porteasy, etc. This system has proved usable and used for long enough to be worth studying.
P! On 30 December 2013 09:50, Marc Weber <[email protected]> wrote: > Excerpts from Marcel Boon's message of Mon Dec 30 16:19:51 +0100 2013: >> I looked at Zimba and it looks really promising, but it is in early stage. >> Why do you think what you have in mind isn't possible with Zimbu? A > > - compile time hackery like meta programming. Eg have a look at haxes or > Scalas macro feature which allows generate ast at compile time. > Haskell template haskell system is similar. > > Simple use cases are > > db.query("SELECT a,b FROM foo") and have the compile type check the > query and the derive the result type for instance. > > But of course there are many more. > > - also allow pure functional style (maybe lazy like Haskell, maybe not) > > - maybe some record typing (like impredicative.com/ur?) > > - using different memory management systems > > - type classes (like Haskell etc) stuff like that. > >> embedding. > Again - this will always be very very very hard. Yzis failed. And that > was a "rewrite", see here: http://www.freehackers.org/VimIntegration > Read this carefully. > >> Since a rewrite is planned already I think the best way to go is helping >> that rewrite. Most important is finishing Zimbu > No, because Zimbu is yet another language which will only be used by > Vim. I want to think more about this choice before starting to rewrite an > editor - after all Vim does work in its current state. > >> for that, A rewrite will be a lot of work but also a major opportunity. > Well - there is more work to be done. Eg "Yi" is a rewrite (written in > Haskell). Before starting big undertaking we should know what we want > and why. > >> [..] or community will divide eventually. > Community already does - I mean people are switching to Emacs. > >> Rewriting Vim is much better than forking it. Rewriting it twice is >> stupid. > So let's think harder about the programming language first, please. > >> A thing that should change is the community options. Why are we discussing >> by email? Why aren't Vim forums available? > It doesn't matter. Forums suck, too. > > You need both: Forum and/or mailinglist for discussion *and* a wiki like > thing to record the summary. Everything else will become tiresome soon. > > Please stop thinking that "just starting to rewrite an editor" will > solve all issues. You need kind of design, and that does not exist yet. > > You must be able to know why you don't just add "Vim" like mode to jedit > instead of rewriting an editor from scratch, or join Emacs (evil mode) > etc. > > And you must learn that writing a new editor will take a lot of time. > Have a look at history of either Vim, Emacs, jedit, ... > We're talking about a couple of years eventually. > > Marc Weber > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- Français, English, 日本語, 한국어 -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
