You taking the stance that Mozilla is no different than Google, MS or other Commercial Software Vendors. Thus it should be removed and Mozilla Foundation should be dissolved into the Mozilla Corporation a for profit software vendor making a Commercial Web Browser They do not fight for the open web, they do not fight for user privacy, they do not support the goals stated in the the Mozilla Manifesto. They need to be honest about it and not hold themselves out to be something they are not If they want to make a Insecure, Privacy Invading Browser, that is perfectly fine.
#NETSCAPE NAVIGATOR 2018 FREE#
They are no longer honoring that goal, as such they should lose their Tax Free status, the should stop calling themselves a Foundation, they should stop fraudulently holding themselves out as being For Privacy and the Open web Mozilla Foundation has a Tax Free Status in order to promote the Open Web I am being very objective, The Mozilla Foundation is a Non profit tax free organization that gets that tax free status because they are suppose to be following their stated goal of the organization not to be popular Regardless, the 2D browser was the better approach. I am sure that our current approach to VR interfaces (which is 3d skeuomorphic) is a dead-end there exists a more productive method that works nothing like our reality. The advantage that computers bring is that they don't have to work like the real world. It could maybe work for Ikea, but the markets where this could work are so incredibly niche. Nobody wants to explore a 100 story virtual mall when they can just type in exactly what they are looking for. In 3D I would have to walk over to my new task which could take a significant amount of time depending on how far away it is from me. If I want to switch apps or tabs, I can typically do it with a very quick flick of my mouse. This distinction is crucially important for navigating quickly through interfaces. The mouse is capable of recording velocity (which is why it is used for aiming), whereas the keyboard is binary. I think the problem with them is the keyboard.
#NETSCAPE NAVIGATOR 2018 UPDATE#
They (of course) ran into the typical-MS problem of "we implemented a draft and then they made a major change (to the box model, which ironically later got a configuration flag for and many many people actively prefer the old MS way P) and couldn't update very well as we now had existing users", but what I claim really caused them to stagnate was the massive lawsuit against them, which demoralized the IE team in a company that doesn't force people to work on project teams where they don't want to work (the culture in Microsoft was "if you want to build a new product, poach a team worth of people from other, more boring teams").įor more information and a million references, here is a comment I left detailing this history five years ago:ģD skeuomorphic interfaces were always good in theory. It is better than that: Netscape was actually the browser ignoring standards (and in particular was refusing to implement CSS) and Microsoft with IE came in as what someone from the W3C at the time called the "white knight" with a browser that cared about standards and published their DTDs and really implemented stuff like CSS. From my perspective, IE delayed the emergence of the modern web. IE 4 dominated the landscape so long that, in truth, you couldn't build real dynamic web applications until many years later. With Navigator you could reload timesheets all day long with IE the application became unusable after just a few timesheet changes. Using the DHTML games as a model, I built a timesheet entry and management application for Navigator (layers) and IE (innerHTML) that never reloaded the page. IE 4's innerHTML seemed more powerful but it was just plain unusable in practice. People were building amazing DHTML games using JavaScript and layers in Navigator 4. Arguably innerHTML won because this was the era where Microsoft was throwing its monopoly weight around to push IE and kill Netscape. Layers lost out and innerHTML won the day, but it's a stretch to say IE was more innovative than Netscape. And unlike layers, IE's innerHTML was unusable for dynamic updates because it leaked memory like a sieve and after dynamically reloading content a few times IE would grind to a halt. Netscape Navigator had layers ( ) long before Internet Explorer made the innerHTML property mutable.
0 kommentar(er)
