Look I know it's an ignorant post of mine. But I use CLISP and I am very busy with a lot of things these days. Too many to count...
But my plan is to continue to use CLISP until I become convinced that arc will help me in some way. I have almost 20,000 lines of CLISP I have developed and thus I am quite reluctant to even contemplate a switch.
I will put it bluntly, "what's wrong with common LISP?"
If somehow people don't like all the redundancy, well use the subset you like. That's what I do. Sure it would be nice to have a language that forced some kind of uniformity and consistency in its nature. But these are abstract/fluffy terms. And like I said I have 20k lines of LISP that I am not interested in porting...
But if a crystal clear reason were to emerge, then yes I would do it. I do have an open mind.
>I will put it bluntly, "what's wrong with common LISP?"
PG already covers many of his objections to CL his essays. I will not repeat them here. It might be more fair to ask "What's wrong with Scheme?", as Arc seems much closer to Scheme than CL.
As I see it, one of the biggest reasons to create Arc is social. It doesn't have to do anything CL and Scheme don't already if PG and RTM can build a real community around it.
Yes, sorry I was being cranky yesterday. I had just come off a harrowing (but productive) week on the Job... Publish or perish time for me!
So after my hangover wore off (we went out last night), I decided that I shouldn't be such a grouch and I should take a gander at arc rather than just shoot my mouth off about how I don't want to dick around with my near 20k lines of CLISP code (wc #of lines, which include comments).
I looked very quickly at the tutorial and I have to say that I very much like the feel. And although I am under strict personal orders not to think about code these days, I can't help but to plot out a potential porting path. The first thing will be to build some macros so that my common lisp code looks more arc like. This would force me to clean a lot of things too, perhaps knocking it down to 10k if I am lucky. I also know I am doing a lot of dumb things here and there so perhaps if I am really lucky/skilled I can get it down to 5k.
Then I will see how things evolve and do the port when I get the time. It looks like arc will have good momentum and will breath life into the community, so yes I think it's a great thing.
Comments
Look I know it's an ignorant post of mine. But I use CLISP and I am very busy with a lot of things these days. Too many to count...
But my plan is to continue to use CLISP until I become convinced that arc will help me in some way. I have almost 20,000 lines of CLISP I have developed and thus I am quite reluctant to even contemplate a switch.
I will put it bluntly, "what's wrong with common LISP?"
If somehow people don't like all the redundancy, well use the subset you like. That's what I do. Sure it would be nice to have a language that forced some kind of uniformity and consistency in its nature. But these are abstract/fluffy terms. And like I said I have 20k lines of LISP that I am not interested in porting...
But if a crystal clear reason were to emerge, then yes I would do it. I do have an open mind.
>I will put it bluntly, "what's wrong with common LISP?"
PG already covers many of his objections to CL his essays. I will not repeat them here. It might be more fair to ask "What's wrong with Scheme?", as Arc seems much closer to Scheme than CL.
As I see it, one of the biggest reasons to create Arc is social. It doesn't have to do anything CL and Scheme don't already if PG and RTM can build a real community around it.
Yes, sorry I was being cranky yesterday. I had just come off a harrowing (but productive) week on the Job... Publish or perish time for me!
So after my hangover wore off (we went out last night), I decided that I shouldn't be such a grouch and I should take a gander at arc rather than just shoot my mouth off about how I don't want to dick around with my near 20k lines of CLISP code (wc #of lines, which include comments).
I looked very quickly at the tutorial and I have to say that I very much like the feel. And although I am under strict personal orders not to think about code these days, I can't help but to plot out a potential porting path. The first thing will be to build some macros so that my common lisp code looks more arc like. This would force me to clean a lot of things too, perhaps knocking it down to 10k if I am lucky. I also know I am doing a lot of dumb things here and there so perhaps if I am really lucky/skilled I can get it down to 5k.
Then I will see how things evolve and do the port when I get the time. It looks like arc will have good momentum and will breath life into the community, so yes I think it's a great thing.