131–140 of 146 posts
Earlier quoted context omitted.
> So, now you just need to build a highly-optimizing, C++ compiler instead of a browser? No. You just use gcc. Like everyone else.
The gist of the comment was whether GCC automatically made something like WebKit + JIT + Native Client work on very, different OS by a simple compile. I doubted that was true or that the work was easy.
Earlier quoted context omitted.
There used to be an OS X editor called Pepper that was basically PE for OS X. I don't think it's still around. I can't find it except in very old references. There is Eddie [1], which is based on a BeOS editor and is written by a former Be employee. He's very responsive to feedback. I worked with him in improving its LaTeX support. [1] http://www.el34.com
While I'm not positive (maybe he'll return and post a yes/no), I seem to recall that Pepper's source code was bought by a guy named Jason Slack, presumably the fellow you're responding to. It was my first editor when I went back to OS X myself, although I confess I grew irritated both with it and with the attitude of its (original, pre-Jason) developer, who always seemed to have a chip on his shoulder about, well, ev…
No, Eddie is software that actually is written by a former Be developer. I think he originally wrote it for BeOS and has since ported it to OS X and he has an older Linux port as well. It has nothing to do with Pepper.
I've played with Haiku in a VM in the past. But what is suggested that I do with the OS? Be a daily driver? Does it fit some niche use case? I have an old netbook, I'd load Haiku on the boot partition, I really would. I'm a sucker for something different (given the evils of Big OS and all), and for the underdog. Hell, I might even contribute if I have something (coding wise) to give. So I load 'er up on the ol' boot…
It's a general-purpose OS. Do whatever you normally do on it. More importantly, it's a learning tool. It's been part of many courses and many rounds of Google Summer of Code. It's an embeddable kernel + OS free of the cancerous GPL, under a permissive MIT licence. It is extremely well documented, well tested, and consistent. Writing drivers for it is very simple. This makes it interesting for education, for-profit de…
People that call it cancerous are doing that only because they want to get peoples work and do not want to give back any work they do on the GPL'd software or the software that uses the GPL'd code.
The agency I used to work at didn't mind using GPL'd software at all, because with one or two exceptions the agency did not distribute software at all. The AGPL was different matter though, so we just didn't use software licensed under AGPL. I am not complaining that software uses the AGPL license, it's all the better for software developers to license it the way they want, there's no point in whining about it.
I would tend to license software under the GPL just so that any improvements made to it go back to the community.
Earlier quoted context omitted.
IIRC, BeOS had networking but no multi-user or printer support. The latter was pretty important for Apple's pro market at the time, which was mostly desktop publishing. Just the other day I found a BeOS Revision 3 manual in a closet. It was the first version that Be released on x86 after getting snubbed by Apple.
It had printer support since at least R4. As I recall it even had some support for printing to network printers. There was an office package called Gobe Productive which was pretty nice for a BeOS application. Similar to AppleWorks or Microsoft Works.
If there is, it readily becomes a usable work environment.
A couple months back I was wondering if there was a good way to tie an RPi to an Apple II and use its keyboard and memory (to display a Linux console) and allow me to have the pleasure of actually working from a vintage computer.
Earlier quoted context omitted.
The last time I used Spotlight (no mac at the moment), it was so slow that I had to disable it globally. The metadata integration in BeOS was different. For example media and email storage in BeOS.
Spotlight is amazing, I use it everyday. It is VERY fast.
Earlier quoted context omitted.
The gist of the comment was whether GCC automatically made something like WebKit + JIT + Native Client work on very, different OS by a simple compile. I doubted that was true or that the work was easy.
I ran firefox on BeOS.
Earlier quoted context omitted.
I can't say I speak for the “Haiku community” short of being friends with some of the developers and hanging in the IRC channel, but … no that's not a common attitude. Haiku prefers non-copyleft licenses, but doesn't avoid the GPL like cancer. Heck the default compiler is GCC (and will be for the foreseeable future) and the web browser uses WebKit.
That's good to know—thanks! Also good to hear that there are modern browsers available for Haiku :) I think I'll try it out on my old netbook.
Earlier quoted context omitted.
Spotlight is amazing, I use it everyday. It is VERY fast.
I feel like I'm missing out. I occasionally use it to search for images in web applications I'm working on, and that's about it. What else is it good for that i could be doing?
Earlier quoted context omitted.
I think you can get by with either/or, although as some have recently pointed out, an empty Android project is 38 mb large with 1000+ files [1]. I think there is probably something to an elegant, small system. In theory, it should be easier to learn, more predictable, and more stable. Even if this is just on the developer end, it should translate to a less buggy, faster, more consistent user experience, or faster tur…
Right, but consider the reason that an empty Android project is 38mb large with 1000+ files. How much does it have to do with the fact that Android uses the Linux kernel? I was under the impression that the (hand-wavy, two-second) explanation for that was "Java nonsense", not "Linux nonsense".