Live data from Hacker News

Why I Wrote a Programmer's Text Editor

rsms.me

11–20 of 59 posts

Re: Why I Wrote a Programmer's Text Editor

#11
post #8

I can attest to the awesomeness of both Kod and Rasmus. Especially Rasmus, I coded up the whole indentation feature and he had to completely rewrite everything I made because of efficiency issues (I'm not that great with objC yet) and he didn't even complain. Great guy.

Don't sell yourself short. Just having a working prototype can be a god-send, no matter how inefficient.

It happened to be my second time ever coding in objC, so I'm fairly certain it was crap.

My later patches (think I've made two or three so far) got accepted without change :)

Hope I have time soon to make the automagic indentation feature that's possible with the new AST thingy. Also hope somebody hasn't beaten me to it yet :P

Re: Why I Wrote a Programmer's Text Editor

#14
post #12
post #9

Earlier quoted context omitted.

I disagree. Don't mix it. Just make port for linux so normal people can use it.

People who use Linux on the desktop are, statistically speaking, not even close to normal.

This is a programmers editor. From the population of people who use such editors, using Linux really isn't all that uncommon.

Re: Why I Wrote a Programmer's Text Editor

#15

Can someone explain the relationship between Kod and node.js? The Kod website says it is "based on node.js", but I don't quite get that. I'm familiar with node.js as a server-side platform, but are we about to see a bunch of node.js desktop apps?

It's scriptable via javascript (because people generally get how to script with that) and is using node.js internally to run said javascript.

Re: Why I Wrote a Programmer's Text Editor

#16
I'm really looking forward to seeing this project develop. It has the potential to spawn a whole host of "webby" editing components..

As Rasmus aluded, in-browser editors aren't really tractable right now, but if everything about Kod but the runtime is written in JS, you could imagine all sorts of interesting browser ports or hosted options down the road.

Re: Why I Wrote a Programmer's Text Editor

#17

Look really nice. Too bad it's just OSX and as jjcm and xtacy pointed out, too bad it doesn't support vim or emacs bindings/integration in some way. I really like your UI choices borrowing so heavily from Chrome, though. Really do... updates personal notes

> too bad it doesn't support vim or emacs bindings/integration in some way.

Well the bindings could probably be added[0], it's OSS and probably rather small still.

Emacs integration on the other hand, that would be rather harder.

[0] actually, since it uses standard Cocoa (text) controls it already has some Emacs-type bindings (C-a, C-e, C-f, C-b, C-k, C-p, C-n, ...) and you can define more (or redefine existing stuff) via DefaultKeyBinding.dict, just about any NSResponder action message (and there are quite a bunch of them) should be available for binding [1] And it even allows you to bind multiple actions to a single keystroke or to bind key sequences (à la Emacs's C-x C-s)

[1] http://xahlee.org/emacs/osx_keybinding.html

Re: Why I Wrote a Programmer's Text Editor

#18
Nice, just found Kod yesterday while browsing around Github and gave it a try. Really like the dark syntax highlighting, looks very pleasing. I seem to have a font-rendering issue though, the text looks kinda blurry.

Re: Why I Wrote a Programmer's Text Editor

#19
post #12

Earlier quoted context omitted.

People who use Linux on the desktop are, statistically speaking, not even close to normal.

This is a programmers editor. From the population of people who use such editors, using Linux really isn't all that uncommon.

Sure. But for the power user, for the full-time developer, there's no point in going for something like Kod. Learning vim or emacs is actually not that hard.

As Rasmus points out in this blog post, he's aiming for a different crowd: people for whom programming is a secondary activity.

Post reply on HN