Stainless

This is definitely a wonderful browser that runs very well even on old PPC Mac's. I love the interface and simplicity of it. I will say thought that it is definitely under development still. It hasn't reached version 1 yet as the developer (like in the description) intended it as a demo and not a total project. He has however told me via Twitter that this app IS still under active development. He's also stated that he's still in the process of making Stainless open source and that he's going to keep the PPC binary alive.

Stainless has a lot of potential. As mentioned already, it handles Flash better than any other browser I've tried. Why can't Chrome or other browsers run this efficiently? It does lack many features, which makes it a poor choice for daily use, but as a light browser or for viewing YouTube, it is one of the better options.

This browser could be promising but needs: • An ad-blocker. And a serious one that blocks as much as the add-ons available with the major browsers, so look at AdBlock, ABP etc and be good as those for blocking all ads everywhere and have way of blocking the 1 or 2 that get through manually too with a right-click function • 1password support • Gestures. Can't even do a swipe for forward and back with BTT because for some reason it won't work, the only application I can think of that BTT has not worked with when I have tried it • Ability to set desired precise search engine string for location bar • Also seems to have issues with History • Can I just say ad blocker a 2nd time. And if you can't make it very effective indeed should be a way to add a blocking CSS to improve it

This is one of the unsung heroes. This browser has got the best flash player performance and the best processor management. This is a gem... of course lacks of many goodies as FF, Chrome or Safari, but if you are looking for something slim with a fast performance, this is the one.

Stainless is an excellent, light browser that really gives me what I need. I love that, unlike Safari, I can close a tab and recover all memory associated with it. Unfortunately I haven't seen any development since 2009. What I'm missing the most is a more elegant way to organize bookmarks and a 1password integration. I would really like to help getting this project back on track!

Excellent Browser. It is fast and smooth running.

Glad to see this is becoming a full fledged project. The parallel session technology that "allows you to log into a site using different credentials in separate tabs at the same time" is super cool, especially for Web developers. And Stainless already passes the Acid 3 test. Firfefox 3.5 doesn't even do this yet. Certainly it's missing a lot of features that would make it useful as you daily browser, but it's of to a really good start.

I love innovative ideas like this, but what results is that each tab is a process that on average takes around 39MB of RAM. If I were to use this browser as I use Firefox, with 4 windows open, each with about 8 tabs, I'd be out over a gig of RAM, where Firefox manages to keep the memory usage below 300MB, with more features and several plugins installed.

This browser sounds really exciting! I'm a long time Firefox user (since the days when it was called Phoenix) and I'm truly disappointed in how bloated, buggy, and memory-intensive Firefox has become. It all boils down to leadership and the Mozilla Foundation has been operating like a beast with too many heads for years now. I want my lean, mean privacy-conscious browser back -- not this gargantuan, crash-prone imposter who shares a bed with Google. As soon as this browser implements 1Password and a decent ad-blocking program, Firefox's days are numbered.

This is a great browser! Its missing a few features of a full browser but even so I have been using it as my main portal to the intertubes. The bookmark shelf is genius and the load times seem to beat Safari 4. Also biggest plus it doesn't eat memory like safari! And running youtube on a separate task speeds that up immensely. Can't wait for the full release! O and no crashes or hang ups yet...

It really is a new browser experience with release 0.5.4 because I can't get it to display a window, something that wasn't happening with 0.5.3 and earlier releases. Otherwise, it's interesting, but it seems much earlier than the version numbers would suggest.

Ok, I've used it for 5 minutes and.. It's very fast, clean, nice to use, I love this bookmarks bar idea and it hasn't crashed so far. I'm very impressed and looking forward for future release. I'll stay with safari, because it has some feature (1password, glims, safariblock (ok, they're not a feature, they're add-ons)) that I need, but if in the future Stainless will implement -1password -adblocker -keyword search I'll definetly switch.

This browser is really snappy. One cosmetic issue, though. Why are the close buttons on the tabs on the right side, like on a Windows machine, and not on the left?

Lately I've been considering switching my browser. I am a web designer so I use all the big players on a regular basis and they each have their issues. Mostly it comes down to their inability to have a large number of tabs open without experiencing excessive amounts of lag. I find this to be unacceptable. Since I use every major browser regularly I know all their shortcomings and know none of them meet my requirements. Though Stainless is not complete it shows the most promise out of all of them. It's more than a proof of concept, like CrossOver Chromium, it's an actual working browser and it works pretty well. However, it's missing history and bookmark support. Also I'd love to see some 1Password support just as much, though this could be achieved by implementing a plugin architecture similar to Safari's. There are other features that I would love to see added that you don't really find in any other browser without plugins such as bookmarks powered by tags and smart-folders. OK, so it's not complete and still has lots of room to grow. That being said I can't think of a single other browser that I'm really looking forward to the next version of like I am for Stainless. I hope this browser moves out of the beta phase and into real development. I know I'd use it as my default browser if it did.

I can't stand the new icon. Looks like a reptile is about to eat me. Return the old one. Yucko!

Can't wait to see what the novel ideas are for bookmarking and history. (I am being serious)!

I do not see any indication whether or not Google is ignoring support for Tiger users. You must know many Mac users are not (yet if ever) able to "upgrade" to Leopard for wide-range of reasons. Please do not forsake us. It won't be difficult to support Tiger if you go-ahead at this early stage, rather than buck-slipping code at a later stage.

Love it. The interface is slick and cohesive, does what's claimed, and is definitely an interesting project that I'll be keeping an eye on. As has been mentioned though, it's too bad about the window flicker. For the developer, I'm unsure if you're aware of the DNS pre-caching feature in Chrome, but it makes the internet scream. Might be something to look into if you haven't already.

I see the window flicker too, but didn't notice it until was pointed out by the previous review. Otherwise, it's a great experimental web browser and it's great to see how quickly something Chrome-like can be made in a short amount of time by an independent developer on Mac OS X. Project has mucho potential, and I rate it not for what it should be but for the quality of what has been delivered thus far. The rest will come in time.

Stainless is going great; it has potential. I appreciate the rapid updates! It's obviously missing a lot, but I won't burden you with the obvious requests. There is one UI issue that is an ABSOLUTE DEAL-BREAKER though: the WINDOW FLICKER (temporarily switches from being the frontmost window when changing tabs). I'm sure that this bug is related to the separation of tabs into processes, but it needs to be solved before Stainless can ever be a serious browser -- or a serious demo. Right now, all this shows me is that this implementation won't be the answer. Brutal honesty.