News for hackers. Stuff that matters.
Re:John Carmack: Latency Mitigation Strategies by dman on Friday February 22, 2013 @02:10PM (#5266034)
Would you be willing to pay a recurring fee for using an editor? I have toyed with writing an editor at multiple points but have backed away because I think in the grand scheme of things its a one time sale to a pretty small market (The number of people who care enough about text editing that they would pay for a good editor when they see one)
Re:John Carmack: Latency Mitigation Strategies by Erwin on Friday February 22, 2013 @02:50PM (#5266321)
I pay, effectively, a recurring fee for PyCharm. The personal license is €89 and comes with 1 year of upgrades. As they've been able to release upgrades after that year expired that looked interesting, I paid another €50 for it the next year support.

Personally I'm not keen on a recurring payment unless there's a clear benefit. For an editor, that'd be having a team committed to making it better. The JetBrain guys have shown good progress.

Re:John Carmack: Latency Mitigation Strategies by jiggy2011 on Friday February 22, 2013 @04:08PM (#5266824)
Doesn't seem to be too small a market for sublime or textmate.

What I would pay for would be an editor in the style of ST2 but with a few IDE features like being able to jump to method definitions by shift clicking etc.

Basically a very lightweight IDE with good text editing features (like VIM style keyboard shortcuts). Integrate a terminal into it, but do it in a very slick way with the ability to run "recipe" type commands.

For example if I forget the switches for a git command, I should be able to search for roughly what I want and have a result return which will populate a command in the terminal.

This might mean hyper focusing on a few languages however.

Not sure I would like the recurring model for just using the editor. Since this would likely mean you would have to implement some sort of always on cloud integration into the editor which would annoy me and make me worry about losing access to my editor.

What I might pay for on a recurring basis would be access to a repo of high quality plugins that were well integration with every version of the editor. Also maybe some functionality to allow me to share the editor session with someone remotely.

Re:John Carmack: Latency Mitigation Strategies by dman on Friday February 22, 2013 @04:13PM (#5266866)
I dont want to gimp the user experience or implement cloud features just to get people to pay. At the same time if I am going to be spending 2-3 years to build something I would rather it be something that has a recurring income stream.
Re:John Carmack: Latency Mitigation Strategies by jiggy2011 on Friday February 22, 2013 @04:20PM (#5266914)
What would happen if someone doesn't pay for a month, would you somehow shut off their editor?

It would be extremely annoying for that to happen because a payment got screwed up or something.

If you make an editor so good that everyone wants to use it you can probably make enough from one off sales assuming you set the price right.

By and large when it comes to tools I want to buy them and keep them rather than lease them.

Re:John Carmack: Latency Mitigation Strategies by dman on Friday February 22, 2013 @04:35PM (#5267012)
This is a good question - I dont think I have a good answer. I lean towards not implementing a check or stop your use. Maybe a monthly reminder for one / two months saying you have not paid. After that I would just assume that the user has stopped using my editor.
Re:John Carmack: Latency Mitigation Strategies by jiggy2011 on Friday February 22, 2013 @05:00PM (#5267163)
In order to justify a monthly payment I feel you would really have to be pushing out frequent high quality updates that just kept making it better and better.

If development started to get stagnant I would probably "forget" to renew it after my CC expired or something like that. Or at some point I'd just feel "I've given this guy enough money" and cancel even if I kept using the editor.

Re:John Carmack: Latency Mitigation Strategies by swah on Monday February 25, 2013 @07:24AM (#5278574)
I totally agree about the Lightweight IDE thing. IMO Sublime is close to being great, but some missing features must be preventing people from writing great plugins like those in Emacs world.
Re:John Carmack: Latency Mitigation Strategies by mheathr on Friday February 22, 2013 @04:04PM (#5266792)
Instead of starting from scratch perhaps implement utility in an existing editor that is in demand but not yet available for a fee.

There are a lot of things that would be nice to see in existing programs that a bounty type system would possibly work well to encourage.

Re:John Carmack: Latency Mitigation Strategies by dman on Friday February 22, 2013 @04:07PM (#5266812)
That is a good idea!
Re:John Carmack: Latency Mitigation Strategies by oftenwrong on Friday February 22, 2013 @02:44PM (#5266269)
I might be willing to pay. What would your editor offer that the free, powerful, well-established editors out there do not?
Re:John Carmack: Latency Mitigation Strategies by dman on Friday February 22, 2013 @04:05PM (#5266800)
Since I havent implemented anything I cant make any claims, what I can answer is things that I miss in the current landscape:

a) Fast startup times

b) Effective utilization of multiple monitors out of the box

c) Embedded prompt for dynamic languages

d) Minimal lag in the UI

e) Fast regex search over multiple files

f) Multi file mode - I want to be able to have multiple files mapped to the same buffer and have the ability to quicky seek to files

g) Outline mode that is code aware

h) Integrated lint mode

i) < 10 meg download size

All of the above in the same editor. Currently sublime comes the closest, I have also happily used emacs in the past but sublime feels snappier than emacs currently. I guess if emacs could be as snappy and pretty as sublime what it would scratch all my needs, because modulo some polish it has most of the other features.