luckydude

7 ms·

1.
by luckydude 2y ago
Rick saying "I worked on BK" is the understatement of the century. He showed up and looked at my code, I had done things in a way that you could have walked the weave and extract any number of versions at the same time. He was r
2.
by luckydude 2y ago
I fished today, 3 halibut. Fish tacos for the win! If you cook halibut, be warned that you must take it off at 125 degrees, let it get above that and it turns to shoe leather.
3.
by luckydude 2y ago
I don't like cheaters. If Tridge had done what he said he did, go him, I'm all for people being smart and figuring stuff out. But that is not what he did and it disgusts me that he pretends it is. There is absolutely zero chance
4.
by luckydude 2y ago
This is completely untrue. There is no way that you could make a BK clone by telneting to a BK and running commands. Those commands don't tell you the network protocol, they show you the results of that protocol but show zero insight
5.
by luckydude 2y ago
My issues with Git - No rename support, it guesses - no weave. Without going into a lot of detail, suppose someone adds N bytes on a branch and then that branch is merged. The N bytes are copied into the merge node (yeah, I know, git look
6.
by luckydude 3y ago
It might not have happened if it wasn't for me and avb. I need to write that up but the short story is that FDDI was the path to 100mbit, I wanted 100Mbit ethernet, the sun hardware engineers thought I wanted to signal over copper the
7.
by luckydude 6y ago
Tim was cool, he said add "The Perl logo is a trademark of O'Reilly Media and is used with permission" and we're good. Now I have to remember how to get into that VM :-)
8.
by luckydude 6y ago
I think the most productive thing I could do is write up how the weave works. People don't seem to understand that, if they did, nobody would be talking about patches. I'm sorry if I pissed off the other guy, but I'm retired
9.
by luckydude 6y ago
Pretty sure Tim doesn't care but I'll track him down and ask. Edit: sent an email to him, we'll see.
10.
by luckydude 6y ago
I've built two commercially successful systems, NSElite that was used to develop the Solaris kernel and was productized as Avocet/CodeManager/TeamWare (don't blame me, I didn't name it), and BitKeeper which was, at
11.
by luckydude 6y ago
Who owns it? OReilly?
12.
by luckydude 6y ago
I sort of agree with this. I'm not a lisp fan, I don't think lisp is bad, it's just not how my brain works so I struggle. But I understand lisp enough to agree with you and I think that is what John was trying to do.
13.
by luckydude 6y ago
I just realized I didn't give credit to all the people who worked on Little. So here goes. Tim Daly did the first pass. Oscar Bonilla stepped up, I still remember him saying to Tim "we need an AST" and Tim said I can do th
14.
by luckydude 6y ago
Little returns undef for OOB and for in bounds not set. Tcl returns "" for both. The thing that GP was asking for, an OOB error, is not a thing in a language where there are no bounds.
15.
by luckydude 6y ago
I think if you are asking this question either I have completely failed to explain why weaves are cool or you haven't read what I said about why weaves are cool. Patch based systems are idiotic, that's RCS, that is decades old tec
16.
by luckydude 6y ago
I wrote most of my first source management system (NSElite, mentioned elsewhere in this thread) in perl4. I was learning perl at the time and my first and second efforts were awful. Perl really lets you get sloppy and create unmaintainabl
17.
by luckydude 6y ago
You are kind of making my point. In tcl, they'd just give you "", but you can't tell the difference between "past the end of the array" or an element where you said set foo[i] = "" In Little you can
18.
by luckydude 6y ago
You seem bound and determined to not hear that tcl auto expands arrays as needed. There are no bounds. So there is no error to catch. We just thought it would be clever to return undef if you were out of bounds, which tcl code would see
19.
by luckydude 6y ago
Richard is awesome. He also did sqlite. As for Fossil, I'm a fan of his UI and code, but haven't looked in detail at the design. I'm pretty sure it is patch based with everything stored in sqlite. It's an OK way of d
20.
by luckydude 6y ago
I don't see the array access as any different than a null pointer dereference, in both cases you are asking for something that isn't there. In Tcl, stuff just gets auto expanded on assignment and returns "" (I think) on
21.
by luckydude 6y ago
That was me as well, though I wrote it in perl4 and C. My version was called NSElite. The Solaris kernel was developed under NSElite, some stuff is here: http://mcvoy.com/lm/nselite 2000.txt documents the first 2000
22.
by luckydude 6y ago
In Tcl, everything is a string. The string rep of undef is "" so Tcl gets "" but doesn't know that it is undef. So yeah, there is some sloppiness there. Tcl tends to use "" as sort of a null or undef so
23.
by luckydude 6y ago
Without providing an example of how to do it better, I'm not sure I see your point. Yeah, I see the problem you point out. Consider char *p = 0; some complicated code that should have set p but didn't... char c = *p; /&#x2F
24.
by luckydude 6y ago
http://www.tcl.tk/man/tcl8.5/TclCmd/upvar.htm That man page isn't the most clear. upvar gives you a way to modify a variable in the calling context (and I think it can go up more than one stack frame).
25.
by luckydude 6y ago
We obviously liked it because upvar is how Little passes by reference. I don't know why someone thought upvar was bad, it is useful.
26.
by luckydude 6y ago
I would think so but I haven't done it. People embed tcl all the time, perl/tk is perl with a tcl interpreter embedded just so they can get at the tk part (gui stuff).
27.
by luckydude 6y ago
I think it was recorded, I'll go look. Apologize for saying BK is quality? None needed, we prided ourselves on producing a quality product. And great support, our average response time, 24x7, was 24 minutes. It was only that "s
28.
by luckydude 6y ago
I remember Pike, I looked at it. It was too far away from C for me. I'm a died in the wool C programmer (I started as a kernel programmer and formed some strong opinions there). I get that C is not for everyone but for me, it's
29.
by luckydude 6y ago
It's based on patches. I'm perhaps not going to win any friends, but I think that is ill-advised. Patches are great for emailing around, they are a horrible idea for an SCM. Perhaps I need to write up how weaves work in more det
30.
by luckydude 6y ago
Believe me, I would do backflips if someone wanted the BK source base, it's got almost 2 decades of my work in it, north of 140 man years. It's a lot to just let fade away. But I assembled a team of people better and smarter than

More ›