|
|
Up |
|
|
  |
Author: andrey mirtchovskiandrey mirtchovski Date: Jul 12, 2006 08:36
i'm having an issue with the new devdraw code. while displaying acme
to a remote terminal, killing the window acme is in without Exiting
acme outputs:
devdraw: X I/O error
but does not kill the process. further ctrl+C outputs:
9pserve unix!/tmp/ns.andrey.localhost:10/acme: Jul 12 09:10:30.471
note: interrupt
acme: interrupt
it's the same for other devdraw apps such as stats. this happens when
displaying both locally and remotely to OSX.
|
| |
|
| | 103 Comments |
|
  |
Author: Andreas KochenburgerAndreas Kochenburger Date: Jul 25, 2006 06:47
On 22 Jul 2006 04:58:01 -0700, "j2thomas@ cavtel.net"
gmail.com> wrote:
>Here's the idea -- a version management system that's optimised for
>open-source Forth projects.
-------
Et ceterum censeo, TV esse delendam.
|
| |
|
| | 1 Comment |
|
  |
Author: j2thomasj2thomas Date: Jul 25, 2006 07:55
Andreas Kochenburger wrote:
I don't know enough about Subversion yet to say. It might be just
perfect, and I've bookmarked the link to study in more detail.
My central thought here is to avoid the problems of project
mismanagement by substituting for them the problems of project
nonmanagement. Everybody does whatever he thinks best, including
changing the specs. WIth 10 developers it becomes 10 projects that
share code and documents etc.
There would inevitably be some duplication of effort and parallel work
that turns out incompatible. My hope is that this overhead might be
less than the overhead of less-than-perfect management. To reduce the
overhead there should be some tools to help anybody-who-chooses-to-look
the things he's most interested in about what everybody else is doing.
Since it won't be known ahead of time quite what those things are,
ideally the project-tools software should be flexible enough to provide
new capabilities as early projects show what's needed.
|
| Show full article (1.36Kb) |
| 40 Comments |
|
  |
Author: wertywerty Date: Jul 26, 2006 14:31
Your top says "Open source" but you then describe how to
"close" source .
You must be a C programmer ( read : Luddite , wants a job that
really does not exist )
NewForth will be free , runs on the far simpler ARM cpu .
You will be impressed with every byte , for it will be written by
NON- C types .
People who enjoy simplyfying to the max elegance ! And of course,
they get speed as a reward !
Programmers have a job cause they can make it appear they've done
magic in 150 megabytes .
Thus NewForth will be written by hobbyists . Do you see any
hobbyists here ?
I see only Wizards here .
You test a "Hobbyist" by asking him the worst/most bloat method
and watch his discomfort ( a WIZARD ) .....
Or ask him how many siminars he gives !!! Or best , is he a paid
teacher !
|
| Show full article (3.68Kb) |
| no comments |
|
  |
Author: j2thomasj2thomas Date: Jul 26, 2006 15:23
werty wrote:
> Your top says "Open source" but you then describe how to "close" source .
I don't see how you read that in. If it's a project somebody's paying
for, they're going to want it closely managed. They'll try to avoid
duplication of effort, and they want most of the developers to do their
assignments and not explore the whole project trying to understand
where they fit in best. That's a manager's job.
I have the idea that doing without an official version would be good on
average for open source projects where it can't be allowed for projects
for pay. And one of the main reasons for that is that the project may
regard any sort of incompetence including management incompetence as
damage, and route around it.
But wait, you're the guy who said you have a Forth system with no
stack, just locals. I think you're a troll. You're just trying to get
people riled up.
|
| |
| 2 Comments |
|
  |
Author: Richard OwlettRichard Owlett Date: Jul 26, 2006 16:17
> werty wrote:
>
>>Your top says "Open source" but you then describe how to "close" source .
>
>
> I don't see how you read that in....
He wears jackets in white with VERY long arms tied in back.
Is often off meds when posting.
|
| |
| no comments |
|
  |
Author: Elizabeth D RatherElizabeth D Rather Date: Jul 26, 2006 18:02
> werty wrote:
>> Your top says "Open source" but you then describe how to "close" source .
>
> ...
>
> But wait, you're the guy who said you have a Forth system with no
> stack, just locals. I think you're a troll. You're just trying to get
> people riled up.
werty is a well-known troll. Do not feed.
Cheers...
--
==================================================
Elizabeth D. Rather (US & Canada) 800-55-FORTH
FORTH Inc. +1 310-491-3356
5155 W. Rosecrans Ave. #1018 Fax: +1 310-978-9454
Hawthorne, CA 90250
http://www.forth.com
|
| Show full article (0.73Kb) |
| no comments |
|
  |
|
Author: Charles TurnerCharles Turner Date: Jul 27, 2006 13:52
|
| |
| no comments |
|
  |
Author: j2thomasj2thomas Date: Jul 27, 2006 20:19
Charles Turner wrote:
> Have you looked at darcs?
I hadn't heard about it at all. Thank you!
|
| |
| no comments |
|
  |
|
|
  |
Author: J ThomasJ Thomas Date: Jul 28, 2006 08:00
Charles Turner wrote:
> Have you looked at darcs?
> Best, Charles
That looks like a very good start. They let everybody run their own
repository, they make branches easy. It's easy to import stuff from
other branches but it looks like they provide no tools for managing
that except diff and you can choose to automatically run unit tests.
I thought that it would be good to arrange a user interface that looks
something like a wiki. Click the name to get a clickable list of pages
that were derived from this one, and a list of pages that point to it.
Connect the code and load pages directly to the specs. Etc. They don't
have that, and they don't have tools to help heal branches, but they've
done a lot of hard work.
And they have a user base.
darcs was written in Haskell. It looks like a lot of hard work to
duplicate their effort in Forth, and there's no proof that anybody
would be interested in using a new system after it was ready.
|
| Show full article (1.73Kb) |
| no comments |
|
|
|
|