Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox.html: Rebuilding Firefox UI in HTML

mail.mozilla.org

Post reply on HN
Print view View original

61–70 of 146 posts

Re: Firefox.html: Rebuilding Firefox UI in HTML

#61

Post by 10098 »

valarauca1 wrote: post #53
paulrouget wrote: post #9

I've built that. Just to be clear: this is a personal project, not a mozilla project (even though I'm a mozilla employee). Also - many people find it silly to use HTML instead of the operating system toolkit library. But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). For example, if you run…

As a guy who works with primarily back end server code. I hate UI stuff primarily because even creating small input UI windows requires jumping though hoops of fire it feels like with strange API calls, and documentation that says, "Just follow the example it'll all be fine in a couple minutes." But I'm 8 inheritance levels deep trying to figure out why my text box isn't rendering. I've often wondered why OS's just d…

no, screw that. My 4GB RAM machine is slow enough as it is with all this html and javascript crap running.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#62

Post by rancur »

jwcooper wrote: post #59
rancur wrote: post #58

Earlier quoted context omitted.

no more software layers please! my PC was much faster when my programs were native. Apps rendered with chrome rendered with webkit...8GB used to be enough, then all these "developers" with their "development machines" who think it's no big deal that their Hangouts implementation takes 200MB when Pidgin takes 20. people used to complain about Firefox hogging memory, I think it's Chrome we should be worried about...

At the same time, it's likely much more expensive to code native apps than it is to just build an html/css/js app using chrome with a lot of the heavy lifting already done for you (at the expense of increased resource consumption). A lot of these apps wouldn't exist if they couldn't have been built quickly and cheaply.

well, we're hitting process node limits (5, maybe 4nm) in 10 years so I think we better stop it.

http://www.chipworks.com/media/wpmu/uploads/blogs.dir/2/file...

You see those little dots? Those are individual silicon atoms from one of a few fins in the gate on Intel's 22nm node.

Also, I Am A C Programmer. I Think Everything Should Be Written In C. C Is Close To The Hardware And Is Faster And Use Less Resource Compared To The JavaSlow and WebKittenz and CSS. But I Like CSS Because It Has C In It. I Am A C Programmer.

Get back to me when we have compressed ZRAM implementations and Same Page Merging everywhere to save memory on each Chrome process and each JS interpreter instance. Don't you want to do the green thing?

Re: Firefox.html: Rebuilding Firefox UI in HTML

#63

Post by JacobEdelman »

rancur wrote: post #58
valarauca1 wrote: post #53

Earlier quoted context omitted.

As a guy who works with primarily back end server code. I hate UI stuff primarily because even creating small input UI windows requires jumping though hoops of fire it feels like with strange API calls, and documentation that says, "Just follow the example it'll all be fine in a couple minutes." But I'm 8 inheritance levels deep trying to figure out why my text box isn't rendering. I've often wondered why OS's just d…

no more software layers please! my PC was much faster when my programs were native. Apps rendered with chrome rendered with webkit...8GB used to be enough, then all these "developers" with their "development machines" who think it's no big deal that their Hangouts implementation takes 200MB when Pidgin takes 20. people used to complain about Firefox hogging memory, I think it's Chrome we should be worried about...

I don't like the idea of developing for current machines. With the constant advances in computers the next generation of applications, "developer apps" should be made for the next generation of computers, meaning that its okay if it's a bit of a hog. I mean, 200MB is just a drop in a bucket now.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#65

Post by pawelk »

ANTSANTS wrote: post #43
paulrouget wrote: post #9

I've built that. Just to be clear: this is a personal project, not a mozilla project (even though I'm a mozilla employee). Also - many people find it silly to use HTML instead of the operating system toolkit library. But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). For example, if you run…

> But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). No troll, I thought that was what XUL was.

I've always conceptualized XUL as something similar to what is now known as Web Components + a native touch.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#68

Post by BuckRogers »

JacobEdelman wrote: post #63
rancur wrote: post #58

Earlier quoted context omitted.

no more software layers please! my PC was much faster when my programs were native. Apps rendered with chrome rendered with webkit...8GB used to be enough, then all these "developers" with their "development machines" who think it's no big deal that their Hangouts implementation takes 200MB when Pidgin takes 20. people used to complain about Firefox hogging memory, I think it's Chrome we should be worried about...

I don't like the idea of developing for current machines. With the constant advances in computers the next generation of applications, "developer apps" should be made for the next generation of computers, meaning that its okay if it's a bit of a hog. I mean, 200MB is just a drop in a bucket now.

In 2006, the next computer was the iPhone with 1GB of memory and the iPhone 6 still has 1GB today. I wouldn't count on everything being a 16GB+ monster rig just to bring a browser up.

Re: Firefox.html: Rebuilding Firefox UI in HTML

#69

Post by tracker1 »

valarauca1 wrote: post #53
paulrouget wrote: post #9

I've built that. Just to be clear: this is a personal project, not a mozilla project (even though I'm a mozilla employee). Also - many people find it silly to use HTML instead of the operating system toolkit library. But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). For example, if you run…

As a guy who works with primarily back end server code. I hate UI stuff primarily because even creating small input UI windows requires jumping though hoops of fire it feels like with strange API calls, and documentation that says, "Just follow the example it'll all be fine in a couple minutes." But I'm 8 inheritance levels deep trying to figure out why my text box isn't rendering. I've often wondered why OS's just d…

AFAIK, Windows 8, Gnome, Unity and others offer desktop html+javascript compositing with support for webservice calls. Some may be more powerful/limited, but it's something already being done.

Even in a thread earlier today there was a post about the state of desktop web apps... node-webkit and atom-shell aren't bad options either.

I always wanted to like XUL, but a shell mode for HTML+JS that can have more control over iframes than is allowed in the browser... it would definitely be interesting. It would be more interesting if it followed node's API (at least for JS-level modules).

Re: Firefox.html: Rebuilding Firefox UI in HTML

#70

Post by fbender »

valarauca1 wrote: post #53
paulrouget wrote: post #9

I've built that. Just to be clear: this is a personal project, not a mozilla project (even though I'm a mozilla employee). Also - many people find it silly to use HTML instead of the operating system toolkit library. But it's not HTML or native. It can be both. In this case, the HTML code define the layout, and we can draw native widgets inside (look at the tag in HTML, it's a native widget). For example, if you run…

As a guy who works with primarily back end server code. I hate UI stuff primarily because even creating small input UI windows requires jumping though hoops of fire it feels like with strange API calls, and documentation that says, "Just follow the example it'll all be fine in a couple minutes." But I'm 8 inheritance levels deep trying to figure out why my text box isn't rendering. I've often wondered why OS's just d…

That's the spirit of FirefoxOS – any other prior concept still used "native" stuff while in FirefoxOS, "native" is the Web!
Post reply on HN