News for hackers. Stuff that matters.
Re:Apple deprecates Java by rmc on Thursday October 21, 2010 @06:33AM (#1814908)
X11 is horrible on OSX. Applications that use it (e.g. The GIMP on OSX), are terrible and have many usability flaws, such as no clipboard between an X11 application and a normal application.
Re:Apple deprecates Java by celias on Thursday October 21, 2010 @08:21AM (#1815104)
Have you tried xquartz from http://xquartz.macosforge.org/ ? I am able to copy/paste between WingIDE and GIMP and native OS X apps using xquartz. There are issues such as switching between X11 and native apps, but it works better than the X11 distributed with OS X.
Re:Apple deprecates Java by jm4 on Thursday October 21, 2010 @08:42AM (#1815155)
True, but would you rather not have it at all?
Re:Apple deprecates Java by gaustin on Thursday October 21, 2010 @08:51AM (#1815168)
Definitely. Unusable software is as bad as none at all. Unless someone is paying well, I'm not going to deal with the issues.
Re:Apple deprecates Java by jm4 on Thursday October 21, 2010 @11:22AM (#1815810)
Umm... Just don't use it. No one is forcing you to. Some of us are happy to have it, even if it does have some quirks.
Re:Apple deprecates Java by _delirium on Thursday October 21, 2010 @05:48PM (#1817587)
Well, if you have a choice, sure. But if you're working in a team where everyone uses Eclipse, it's really nice to have the ability to run Eclipse.
Re:Apple deprecates Java by nikster on Friday October 22, 2010 @11:00PM (#1822440)
Eclipse should be fine since it's using their own SWT for the GUI. They're not using Swing.

Iv'e developed Swing for 10 years and I think it's basically botched. Sun had no clue about UI development, and Sing is the expression of that. Compared with the UI frameworks on OS X it's like night and day. But I digress - I think SWT is a much better approach in any case.

Re:Apple deprecates Java by rmc on Thursday October 21, 2010 @11:06AM (#1815713)
I'd rather not have it. I tried running OpenOffice under X11, and the fact that I couldn't copy and paste text around the place did my head in, and I couldn't use it.
Re:Apple deprecates Java by masklinn on Thursday October 21, 2010 @07:18AM (#1814987)
Yeah, OSX's X11 is utterly dreadful.
Re:Apple deprecates Java by bnastic on Thursday October 21, 2010 @10:07AM (#1815384)
Be it as it may, but xterm/X11 still kills Terminal.app in text rendering speed. Also, MacVim is, on my Mac at least, visibly slower in text rendering than the naked vim under xterm.
Re:Apple deprecates Java by astrange on Thursday October 21, 2010 @01:45PM (#1816594)
I'm assuming this isn't so slow it shows up on a screen recording (of course, if it IS, that would be interesting), but either way could you please file a bug at http://bugreport.apple.com/? It will reach someone who cares.
Re:Apple deprecates Java by varikin on Thursday October 21, 2010 @12:47PM (#1816285)
Text rendering speed? I type a letter Terminal, it appears. What are you doing that text rendering speed matters?
Re:Apple deprecates Java by jdub on Thursday October 21, 2010 @12:54PM (#1816332)
Running any kind of build process would be an easy first example. :-)
Re:Apple deprecates Java by aidenn0 on Thursday October 21, 2010 @07:18PM (#1817853)
Builds. sbcl in particular is insanely verbose and is often limited by slow terminals. The readme for bootstrapping it even specifically suggests using xterm over gnome-teriminal/konsole.
Re:Apple deprecates Java by borland on Thursday October 21, 2010 @08:28PM (#1818071)
I get slowdowns caused by text rendering in terminal when rsyncing large numbers of files. It's easily worked around though, just minimize the terminal window
Re:Apple deprecates Java by bnastic on Thursday October 21, 2010 @07:26PM (#1817884)
Try scrolling large amounts of text in MacVim, where the whole screen is refreshed, and then try the same in xterm+vim. MacVim is painfull to watch doing this, feel like working over a 300 baud modem. xterm/X11+vim are VERY fast combination for pure text editing, and that matters to me greatly. Same applies to Terminal.app (and it refuses to work in 256 colors, unlike xterm)