TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

XEmacs is Dead! Long Live XEmacs!

38 点作者 bgutierrez大约 17 年前

8 条评论

tx大约 17 年前
Also I don't quite get his desire to "live in" some giant all-in-one software package. I think it should be obvious now that Unix philosophy of many little specialized tools proved to be more flexible than uber-environments.<p>I am not sure if anybody here remembers, but back in the early 90 people believed that <i>"future belongs to integrated environments"</i>, that's right - to IDEs and not just for programming. And now he's talking same thing again.<p>For those working for a web-services company (or living in SV these days) it may be natural to think that <i>"everything is in the browser"</i>.<p>But is it? I still can hear PG's voice from Startup School in my ears: <i>"Stop using the Internet please, my presentation won't open!"</i>
评论 #176062 未加载
评论 #176441 未加载
评论 #176210 未加载
评论 #176048 未加载
justindz大约 17 年前
I was most intrigued by the thought of code editing as a serious part of Firefox. I don't know much about XUL, so I will need to read up, but I thought it would be quite sexy if I built an editor which binds to Heroku using the API. A local code editor extensible via javascript that works directly against the remote in-cloud data would be a pretty swift alternative to the Git approach.
Xichekolas大约 17 年前
Honestly I'm a fan of good old gedit... but this makes a good case for trying emacs one more time.<p>I haven't really understood the appeal of the single, monolithic, do-everything editor up until this point, but looking at it from a self-modifying point of view does make it somewhat more appealing (and I need time to ingrain the key chords into muscle memory and learn some elisp).<p>I think the exciting idea was that of a the browser-as-editor. Where is the browser that acts as an editor and has all it's plugins written in javascript (as opposed to elisp)? Of course, once we had that, the next goal would be to replace bash with it... browser as terminal ftw.
评论 #176092 未加载
jrockway大约 17 年前
As an elisp developer, I would like people to stop using XEmacs also. But the thing is, it seems like most of the more experienced extension developers are using XEmacs. I'm not really sure why, since I'm only active in the GNU emacs community... but there must be some reason. (I bet not having to sign copyright papers for every 10 line patch is one.)
tx大约 17 年前
I just found myself, an avid vim fan, reading that whole thing to the end for some reason. Stevey got me again! :)
jrnewton大约 17 年前
I'm 1/4th of the way through this article and confused already... Steve writes:<p><i>I never managed to use XEmacs for very long, because it crashed a lot</i><p>but then<p><i>XEmacs doesn't crash any more often than Firefox</i><p>and<p><i>XEmacs may crash even less than Eclipse and IntelliJ</i><p>For me Firefox and Eclipse are rock solid. So what is it? Does "a lot" mean every 6 months? Or every day?
评论 #176569 未加载
JesseAldridge大约 17 年前
You know wxPython has a widget that can render html. It's not full featured, but I was pretty amazed by it. There's definitely a lot of potential there...
newt0311大约 17 年前
I have two major gripes with GNU emacs right now. THe mandatory signing over of papers and the lack of dynamic C library loading.