12
edits
Firefox/Feature Brainstorming: Difference between revisions
Jump to navigation
Jump to search
→Other resources
| Line 1,993: | Line 1,993: | ||
[[User:Anonymous42|Some thoughts]]<br /> | [[User:Anonymous42|Some thoughts]]<br /> | ||
</td></tr> | </td></tr> | ||
<tr><td> | <tr><td> | ||
Decentralized/distributed browsing: in case a website has been slashdotted, Firefox should still be able to reach to its data by using the offline website data which is stored locally at other Firefox users, who were able to connect to it, their disk. Firefox should act as a kind of a torrent client. | Decentralized/distributed browsing: in case a website has been slashdotted, Firefox should still be able to reach to its data by using the offline website data which is stored locally at other Firefox users, who were able to connect to it, their disk. Firefox should act as a kind of a torrent client. | ||
| Line 1,999: | Line 2,000: | ||
<td></td> | <td></td> | ||
</tr> | </tr> | ||
<tr><td> | |||
Please focus more on stability, robustness, and security than on adding fun features. New features are nice, and fixing bugs isn't so much fun, but I find Firefox to be more of a memory hog and less stable than IE, and that's pretty sad. Stop competing against other browsers because you're afraid of losing market-share. The only way Firefox will ever be truly great if it's designed to be great from the ground up. Focus on changes that are less glitzy and more on changes that are fundamental to making a good browser platform. When something needs to be re-architected, re-architect it. Don't assume that bugs will ultimately get fixed; so far, Firefox has added features faster than bug fixes. Rather, focus on design principles that minimize the chances that problems will happen and minimize the consequences when they DO happen (and they will!). | |||
</td> | |||
<td></td> | |||
</tr> | |||
</table> | </table> | ||