Mozilla design choices

Gee we need to show a gallery of open pages in tab view.
Lets write thumbnails of every open page to disk!
Genius.

>>1
I hate firefox
maybe I Should switch to chromium.. but i hate it too

>>2
Just FYI this is fixed by setting browser.pagethumbnails.capturing_disabled == false
I would actually want to write my own browser, but the scope of the problem is too great for very little reward and recognition(basically think of TempleOS treated vs Serious OS).
Google can afford to shill its browser on its search page.
Microsoft bundles its browser with the OS.
Firefox lives because of extensions.

browser.pagethumbnails.capturing_disabled -- true I mean.
We need a browser in non-C/C++ language

Current browsers are megabytes of source code, bloat and enterprise features, following every standard imaginable and supporting dozens of plugins/extension types.
Something simpler and manageable would be better.

>>5
It's your chance to shine!

Shine these primes

Browsers should be made in Scheme. JS, HTML, HTTP, CSS, etc all should be replaced with Scheme as well.

>>8
thats what I've been saying this whole time

>>8
I never understood why there need to be 3 (STAY TUNED FOR MORE!) exclusive languages, each trimmed (and maintained) so it can never be absorbed into another thus ensuring pointless complexity forever.
I'm not a fan of Lisp but goddamn, you'd basically only need a simple Lisp + some small libs to emulate modern web behaviour (tree description like HTML, tree patching/modification like CSS, dynamic behaviour like JS, and then be able to I/O using some libs).
But then there's these dips that say that you need to separate semantics from presentation and structure and whatnot, while in reality everyone just builds a ``WebApp<sup>TM</sup>'' and does his own thing and fucks that shit up anyway, because everyone has their own ideas about separation of concerns anyway. Modern ``frameworks'' even encourage a new style every ¹/₂ year.

>>10
Check these dubs

>>10
Mixing up presentation and semantics gets ugly after a while though. Separation of concerns was a valid proposal, they just picked utterly shitty languages to fulfill such purposes.

>>10
Hey what about flash, silverlight, dozens of DRM video and music formats, SVG, WebGL, etc. Modern browser support many plugins, formats and extensions. Pretending web1.0 is the only thing?

>>12
separation of concerns can be applied without using three separate languages though. even a shitty language like Java allows you to do this

>>11
Cudder is all shitpost and no action

>>15
I'm not even the real Cudder lol

I use vimperator so I don't have this problem.

With that said I want to know if there's some about:config switch to prevent pages from capturing my text input focus on their stupid search bar or login field. How the HELL is that even allowed

>>17
Its irrelevant if you have it enabled you have a folder filled with these thumbnails(actually page screenshots)
https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/Preference_reference/browser.pagethumbnails.capturing_disabled

>>12
How so? You will end up doing everything imperatively if you only allow yourself to use one imperative language. It's okay to have one separate imperative language for programming and one declarative one for structure and presentation.

>>19
Any imperative language becomes declarative after enough person-hours.

>>13

what about flash, silverlight, dozens of DRM video and music formats, SVG, WebGL, etc.

SilverLight is dead (not even MS-related stuff requires it anymore) and DRM formats and WebGL are crap.

Pretending web1.0 is the only thing?

You're implying I meant the web should be reduced to 1 language that should be HTML.
What I really meant was that the web should be reduced to 1 language that should be C or Lisp (or maybe even -surprise- Flash!) executed in a VM and just allow a dev to write their own display engine (or use a 3rd party (open source or commercial) one, as there would literally be hundreds around). Again, modern web services aren't websites (documents that get parsed) anymore but applications (that get run).

You should use Seamonkey. It's the true heir to the Mozilla legacy. Firefox is just a shittier version of Chrome at this point.

Get Silverlight 5

Silverlight is a powerful development tool for creating engaging, interactive user experiences for Web and mobile applications. Silverlight is a free plug-in, powered by the .NET framework and compatible with multiple browsers, devices and operating systems, bringing a new level of interactivity wherever the Web works.
http://www.microsoft.com/silverlight/

>>21
I can understand Lisp as a replacement for HTML but C? having a web browser compile every website you visit would not be convenient for users, and designing an interface in C wouldn't be convenient for devs.

>>24
Not to mention the webpages executing arbitrary code since C is a thing layer on top of assembler.

>>25
to be fair, >>21 was talking about execution inside a sandbox/VM. of course, a bad VM can be escaped from - but this does not necessarily require C (just see how many browser exploits use Java, Flash or Javashit).

>>26
A VM that executes C is basically a security nightmare.
https://en.wikipedia.org/wiki/Google_Native_Client

https://media.blackhat.com/bh-us-12/Briefings/Rohlf/BH_US_12_Rohlf_Google_Native_Client_Slides.pdf

>>27

https://en.wikipedia.org/wiki/Google_Native_Client#Reception

OK, let's disprove these fags one by one:

These native apps are just little black boxes in a webpage.

Zed Shaw already noted in 2012 that "everyone minifies their shit". I also like Open Source but the 'modern web' is already broken and intransparent enough for large news sites to unknowingly distribute malware and users not to notice that. People who really mean it will distribute the sources to their stuff and evil corporations and governments will fuck people over anyway.

native code cannot evolve in the same way that the source code-driven web can. He also compared NaCl to Microsoft's ActiveX technology, plagued with DLL Hell.

Which means that they solved DLL hell by just piling shit on top of shit on top of shit and never get rid of the old shit (except for <blink> -- WOW!). And when you haven't updated your browser in the past 2 weeks major parts of the internet break for you because you always need the newest and most bloated shit.
How about you release a good, portable standard that's usable for 20+ years?!? Like C89, which came out in... '89?!? 27 years and still widely used.
Compare to JS: a new standard every few years and always introducing new issues.

it will bring in complexity and security issues

More complex and insecure than 4+ separate JS engines per browser? Remember that when you can break out of a C VM, you can also break out of a JS VM.

and it will take away focus from the web platform.

This already happened with the advent of 'Apps' and 'Smartphones'. And they did it by doing exactly what I'm asking: having VMs for real languages (C/Java for Android and C/Objective-C for Apple).

Is compiling to a VM's bytecode/minifying that unreasonable? It's the web we're talking about, nobody ever bothers checking the source code for their epic reddit meme websites and everyone would benefit from having an executable optimized for size.

The current model is fucking stupid. Having comments and long variable names in your code shouldn't bloat the final result. You're sending it verbatim through the Internet, for fuck's sake.

This gets brought up every couple months on /prog/ and the threads end with the two words: Remember ActiveX?

>>31
ActiveX is a proprietary OS API on top of a glorified proprietary document processor.

What we're proposing here is a sandboxed VM that runs applications on demand. Could be anything from simple text documents to your favorite gay dating app.

>>32
How about you check these dubs now?