HNHacker News
TopNewBestAskShowJobs

lkesteloot

407 karma · joined December 1, 2010

submissionscomments
lkesteloot··on Show HN: My Turbo Pascal compiler in JavaScript
Well the error message is confusing (it's trying to cast from an integer (type 70) to a procedure (type 76)), but it's correct to fail to compile. But yeah I'm not sure that my logic there is altogether correct. I re-wrote it a few times as I found new cases that weren't correctly handled. Specifically, I'm not sure whether the type of the identifier should guide the parsing. It's similar to the "x*y" ambiguity in parsing C (multiplication or declaration of pointer variable y).
lkesteloot··on Show HN: My Turbo Pascal compiler in JavaScript
Yep!
lkesteloot··on Show HN: My Turbo Pascal compiler in JavaScript
I remember compilation being nearly instantaneous.
lkesteloot··on Show HN: My Turbo Pascal compiler in JavaScript
The "Compile" option was, I think, for when you wanted to generate a .COM or .EXE. So I don't support that. The "Run" command does compile and run, though.
lkesteloot··on Show HN: My Turbo Pascal compiler in JavaScript
Oh interesting, none of my programs had (input,output) so my parser doesn't support that. It was optional in TP and I don't think did anything.
lkesteloot··on iOS developers: Say goodbye to UDIDs
One problem with both advertisingIdentifier and identifierForVendor is that they are iOS 6+ only. That shuts out 10% of my user base.
lkesteloot··on Show HN: We made an awesome way to browse and search your Chrome bookmarks.
I installed the extension, saw the account creation form, and uninstalled the extension. I agree, I don't need another server somewhere downloading the pages I bookmark. Some of them are even on the intranet at work. Could this work entirely within the extension? Or could I opt out of the HTML-search feature and use the other features?
lkesteloot··on Jig, the first product from Tasty Labs
Good names are a fine use of money because you can probably sell them back.
lkesteloot··on ActiveMQ: Not ready for prime time
They're in the process of doing that. (I no longer work there.)
lkesteloot··on ActiveMQ: Not ready for prime time
This was two years ago. JBossMQ was being rewritten and the new version was too immature. I don't remember HornetQ. We investigated RabbitMQ, which seemed good but still a bit young to bet our company on. We also needed some interesting features that none of these provided. In the end writing our own was the best decision we made my whole time at that company -- it paid dividends the rest of my time there.

I just found a thread I started about ActiveMQ and scaling:

http://activemq.2283324.n4.nabble.com/6000-ActiveMQ-clients-...

Note the last message there. 36,000 threads when using NIO! And these answers were from the people commercially supporting ActiveMQ (FuseSource). I never did find out (on that thread or elsewhere) whether ActiveMQ has ever been used in a situation that large. I suspect it hasn't.

lkesteloot··on ActiveMQ: Not ready for prime time
I believe it was 5.0 and 5.1.
lkesteloot··on ActiveMQ: Not ready for prime time
I used ActiveMQ in a large production environment for two years. It's by a large margin the worst piece of software I've used professionally. You wouldn't believe the number of very serious problems we had with it (including some mentioned here, like negative queue lengths, but mostly broker crashes, missing or wrong documentation, outright broken features, serious threading issues, and poor performance). If anyone's not convinced, just peek at the source code. It's frightening.

We ended up writing a new queuing system from scratch in a month, and in its first week it was already more stable, performant, and bug-free than ActiveMQ.

lkesteloot··on The Lisp Curse
"The solution is for the people who use these tools to become mindful of these dangers, not to get rid of the tools."

Sure, but after 55 years of Lisp, that hasn't happened. If Lisp is unused because programmers find it hard to resist using a feature anti-socially, then it's time to change that feature.

Of course I have no hope that Lisp will change its macro feature. My interest is in making sure that new language designers realize that Lisp's so-called perfection is the very reason that it languishes.

lkesteloot··on The Lisp Curse
Okay, I see what you mean by that now. I might still quibble that calling it a "social issue" (as opposed to technical) makes it sound like it's not Lisp's fault. A good feature that leads to a bad situation is a bad feature. I want to call out macros for what they are: a feature that contributes to Lisp not being used.

Thinking about it more, I might describe macros as "anti-social" in that they help the programmer but hurt the team. This might be what you meant.

Note that I'm not saying that the idea of macros is bad; only that Lisp's decision to make them look like function calls is bad. I once saw a macro system for Lua that made their invocation look clearly different than normal language.

lkesteloot··on The Lisp Curse
It's true that I wouldn't apply it to prose, but that doesn't mean it's not useful for code, where you often want to look at lots of it and get a gist of what it's doing. Also I often do think of a programming language as a user interface, even if it's not actually made of buttons and icons.

I'm not claiming this is the main problem with Lisp; only that it's one of them.

lkesteloot··on The Lisp Curse
I've always suspected that Lisp is write-only. For example, it fails the squint test, which I wrote about here: http://www.teamten.com/lawrence/writings/the_language_squint...

Being write-only would explain why there are so few collaborative Lisp projects.

And I don't particularly buy the thesis of this essay that there are few collaborative Lisp projects because it's possible to do anything with a single person. You can always find sufficiently difficult problems that would require a team. Projects in Lisp should be putting projects in other languages to shame. I think there's something about Lisp that makes collaboration too difficult, and I suspect it's the expressiveness itself.

lkesteloot··on Kevin Rose on the sources of Digg's problems
A "C" coder is someone who writes bad code. It's relatively easy to detect and fire a "C" coder.

A "B" coder is one who for the most part writes good code, but doesn't design a good long-term architecture, or makes many small mistakes that add up in the long run, or leaves the code riddled with small bugs that eventually cause frequent problems. The "B" coders are the dangerous ones because really you should fire them or fix them, but it's too easy to ignore them.

An "A" coder writes solid code and is dependable, but doesn't hit the high notes, as Joel Spolsky says.

A star coder is an "A" coder who hits the high notes.

(I don't know what a "D" coder is, but perhaps our scales are offset by one letter grade.)

lkesteloot··on Kevin Rose on the sources of Digg's problems
A. Because managers, for the most part, don't have the courage to do it. It's emotionally difficult to fire, so they look the other way.
← PreviousPage 3 of 3