4 ms·

Re: Page Weight. I spend a bit more than a month studying how to build Nuuton in a way that it did not end up being a front-heavy piece of crap. Looked at a lo

Re: Page Weight. I spend a bit more than a month studying how to build Nuuton in a way that it did not end up being a front-heavy piece of crap. Looked at a lot of differents options. Considered a client side Javascript MVC frameworks. Looked at the CSS side of things. Went as far as thinking about developing our own little app for Nuuton (No browser needed). But at the end, the simplest choice won. I decided to go with flat HTML/CSS. No bootstrap or framework either. Plain old markup and stylesheets. It uses very little Javascript (no Jquery either), just what the simple UI requires (an event listener for the enter key, and an event listener for 4 links). Nothing else. No animations. No fancy scrolling. No caroussels. Nothing like that. Its rendered on the server side (Django), and gets served to you in a very small package. I even went as far as breaking down the stylesheets so that you dont need to download CSS that does not apply to the page you are visiting. And you know what? It works, feels, and looks amazing. Even if the project ends up being a failure, acheiving such little victories are just deliciously fun. Where did I get the inspiration to go against the current industry trends? HN's simple yet functional html setup. My god, its features a million tables, but the damn thing just works beautifully. By the way, Nuuton also uses tables. :)

dpe82 14y ago
Mind telling us what Nuuton is?
- orangethirty 14y ago
  A new type of search engine. We call it an information engine, but just think of it as a seach engine that covers much more meta information than anything out there. nuuton.com to see the landing page. If you want to get an early look at it just email me.
  - dpe82 14y ago
    Landing page doesn't help much. Web search engine I presume? What do you mean by "covers much more meta information"?
nkuttler 14y ago
Fragmenting the CSS doesn't sound like such a great idea, as you will have additional requests on each page? But I guess you had that in mind.
- neumann_alfred 14y ago
  You also have less stuff for the browser to consider when parsing the HTML. Depending on the amount of CSS, I'd rather have that and less memory footprint per tab. And its only as long as the browser doesn't have that permutation of CSS "includes" cached already, basically, once per each "page type" if you will, and only when you change from your current page type to a new one. However, I don't say this from a usability perspective, but strictly from a "this is neat to code" standpoint. If you do it right, you should always be able to fallback to "include all CSS always" at the flick of a switch; so you have to code this first before you can even test if it helps ;)
Benferhat 14y ago
> I even went as far as breaking down the stylesheets so that you dont need to download CSS that does not apply to the page you are visiting Doesn't this just result in five downloads of 1KB CSS files over the course of a five-page visit, when a single download (and cache) of a 1.8KB CSS file would have sufficed? Is that better?

dpe82 14y ago

Mind telling us what Nuuton is?

orangethirty 14y ago
A new type of search engine. We call it an information engine, but just think of it as a seach engine that covers much more meta information than anything out there. nuuton.com to see the landing page. If you want to get an early look at it just email me.
- dpe82 14y ago
  Landing page doesn't help much. Web search engine I presume? What do you mean by "covers much more meta information"?

nkuttler 14y ago

Fragmenting the CSS doesn't sound like such a great idea, as you will have additional requests on each page? But I guess you had that in mind.

neumann_alfred 14y ago
You also have less stuff for the browser to consider when parsing the HTML. Depending on the amount of CSS, I'd rather have that and less memory footprint per tab. And its only as long as the browser doesn't have that permutation of CSS "includes" cached already, basically, once per each "page type" if you will, and only when you change from your current page type to a new one. However, I don't say this from a usability perspective, but strictly from a "this is neat to code" standpoint. If you do it right, you should always be able to fallback to "include all CSS always" at the flick of a switch; so you have to code this first before you can even test if it helps ;)

Benferhat 14y ago

> I even went as far as breaking down the stylesheets so that you dont need to download CSS that does not apply to the page you are visiting Doesn't this just result in five downloads of 1KB CSS files over the course of a five-page visit, when a single download (and cache) of a 1.8KB CSS file would have sufficed? Is that better?