experimental
Disable: Google Updater Google Toolbar FlashBlock if you have NoScript
That's weird, that's what happens to me in Chrome, not Firefox.
They're also looking at a multi-threaded DOM in Rust.
In case anyone hasn't been keeping up with it, Flash was already sandboxed months ago, before Chrome implemented it (this is different from Out Of Process Plug-ins).
I recommend you disable the Google Updater plug-in which takes up memory and doesn't really do much of value considering it shouldn't be in Firefox in the first place. NoScript has a click-to-play for Flash built-in so if you're using Flashblock get rid of it because it conflicts with NoScript.
If you're using TabMixPlus, there may be an add-on that gives you better performance.
Some of the languages available: C, C++, Python, Ruby, Perl, Lua, Haskell, Scheme, Squirrel, Yabasic, bash (comes with a bash shell), zsh
Some of the developer tools available: Paladin (its own IDE), Git, Hg (Mercurial), GNU Compiler Collection, Vim, QEMU, Bochs
Some of the technologies used: Multi-process WebKit browser, OpenGL, OpenAL, SDL and Qt libraries, Gutenprint and CUPS for printing, FreeBSD network drivers, Haiku Vector Icon Format
On the way: An ARM port, Clang with the already working LLVM, OpenJDK, Gallium3D, package management, more language bindings for the API
Included below is ways to contact, lessons and software sources:
freelists.org/list/haiku
freelists.org/list/haiku-development
haiku-inc.org
haiku-screencasts.blogspot.com
www.haiku-os.org/blog/darkwyrm
www.osnews.com/story/24945/A_Programmer_s_Introduction_to_the_Haiku_OS
haikuware.com (back online shortly)
bebits.com
There's also a wallpaper contest going on. I am not affiliated but I'd love to see more people get involved in this great OS! :)
These are just a few things Google has copied from Mozilla. I don't go around complaining about all the thing Google has copied from Mozilla, but the record has to be set straight, Mozilla is not following Google, they are going there own way. They implemented sandboxed Flash first and compartments which Chrome is missing.
Funny that Google haven't updated the Google toolbar.
"It doesn't take a conscious effort to make software incompatible. All you have to do is not work too hard at fixing bugs—which, if you're a big company, you produce in copious quantities. The situation is analogous to the writing of "literary theorists." Most don't try to be obscure; they just don't make an effort to be clear. It wouldn't pay." - Paul Graham http://paulgraham.com/microsoft.html
Embrace, Extend, Extinguish.
Also I'm not sure early adopters is a good description, Firefox users are more likely to care about usability, security, privacy, extensions that aren't possible with Chrome or that Google considers not important or don't want it (something like NoScript or RefControl) and open source (which Chrome is not, sure Chromium is but the distinction is important because of real world implications and other reasons). These things do tend to be more important for some early adopters, I'm not sure I'd grant "technical proficiency" to mere "tech enthusiast".
The problem with these grids or "tests" (like the Acid3) is that they are being used to prove a point - but they fall short of the real goal - showing what is agreed to be implemented and has been implemented (the Acid3 test written by Google's Ian Hickson hasn't removed the W3C non-recommended SVG fonts).
- The W3C chose IndexedDB over Web SQL so it's no wonder IE10 doesn't support it.
- Mozilla has been working on WebGL for years now (piece by piece?), and Chrome just got it very recently (is it complete?).
- Web Sockets, wasn't that disabled for security reasons until a fix is found?
- Chrome is considered the pinnacle in this blog post and yet there's no mention of ECMAScript 5.
Chrome's development started in secret and took some Mozilla engineers in the process and even though Chrome is mostly developed out in the open, Crankshaft (new V8 engine) and WebM were not. I'm not going to say IE hasn't been marketed a little bit unfairly, but I think a little transparency should be welcomed no matter who it is. Remember all businesses present incorrect facts to benefit (I'm merely stating, not excusing), an example being Chrome never actually downloading the web page in the promotional video a while back, it rendered from a local file.
You're welcome to correct me if I'm wrong.
Can you elaborate on this/reword?
Does this mean if a crash occurs, the whole process of nginx will crash? Whereas Apache's processes can be restarted?
/Genuinely curious
Apache, nginx and Cherokee also work on Haiku as well as a bunch of other native ones (e.g. PoorMan http://en.wikipedia.org/wiki/PoorMan and RobinHood). nginx fits well with it because Haiku performs well under heavy load for responsiveness, is lightweight and fast.
- In 10.6 Snow Leopard, hold Space to zoom in on a window in Exposé.
- Not a hint exactly, but there exists at least one unnecessary dissatisfaction people have of Finder. In real life, you cut text and paste it in a scrapbook, but you don't cut an object like a folder with scissors in order to move it. You usually use a hand or two. Therefore the inability to "move" an object using "cut" (Cmd+X) is the correct behavior. Secondly it prevents you from accidentally pasting a file elsewhere, then needing to remember if you meant to do that, or undo. Adding visibility in some way is not enough, and you can still move by dragging the object to the desktop or wherever else.
Note: Edited for spacing.
This is a interaction design mistake. On Windows, if you click inside an unfocused window you can perform an action otherwise unintended, Mac OS X's way and Haiku's (www.haiku-os.org) is correct. Interestingly Firefox follows the Mac way, but on at least Windows Chrome does not, and if you happen to unintentionally select the close tab button, you're tab close and if you're in Incognito mode, you lose that tab because there is no history.