This new .1 look is awesome and really brings osnews into 2008.
Thank you for your continued hard work and efforts

Post a Comment
Sure, 4.1 looks better but there are still a few things in need of improving IMHO. F.ex. the number of comments on a story is too light color, you have to look a lot harder to see it and it's not possible to just have a quick look on the front page as to which stories generate a lot of discussion. And well, I also think the content area should be separated more clearly from the sidebar.
Otherwise it looks pretty good, nice work 
Cleaner, but now even SMALLER text - and WELL below accessability minimums at that, while the inputs are STILL in a dynamic font...
Meaning large font users have a choice, have input text absurdly oversized, or have content text absurdly undersized.
/FAIL/ /FAIL/
Remember, anything smaller than 12px is almost guaranteed to be USELESS to 'large font/120dpi' users (or 100dpi *nix users), an increasingly common setting with smaller laptops at higher resolutions.
The original theme at least was all dynamic fonts. All these px metric fonts are ****ing stupid. It's not 800 friendly when there is NO content that couldn't at least work in a semi-fluid layout, (and before someone chimes in with "Most people are 1024 or higher" ask what percentage of users actually run their browser full width?)
... and it's still at least three times the markup it should be. 253k main page in 64 files - wow, welcome to 20 seconds overhead on BROADBAND before you even figure in transferring data.
... and it's still at least three times the markup it should be. 253k main page in 64 files - wow, welcome to 20 seconds overhead on BROADBAND before you even figure in transferring data.
It loads in about 3 seconds here (4Mbit connection). Maybe you should use a computer instead of a printer to view OSNews !
What's your ping time to OSNews?
I'm averaging 114ms here, which with at LEAST two pings per file on first load, that's a minimum overhead on the OSNews main page of 14.952 seconds, a real world actual of 21.88 seconds. Once it's cached it's a LITTLE better coming in at about 4 seconds overhead... WITHOUT EVEN TALKING about filesizes.
It's called a handshake - to be getting a 3 second pageload you're cache probably isn't verifying files for changes (status code 304), AND you are likely having ping times around 30ms... which is three times what the average DSL user sees.
It's actually one of the biggest causes of slow loading/painful to watch pages, and the least discussed or understood by web developers. When the browser requests a file it has to send the request, receive back that the file is available, THEN acknowledge to start sending. Due to overlap and the ability to start another request while listening to the first this can reduce it to about 1.5 times the ping time total, if server connection limits are maxed out or local connection limits (like XP SP2's little 'connection limit reduction) are maxed, you can see up to three times the ping time overhead PER FILE
If nothing else, it makes it painful to watch all those images tick by, especially in browsers like firefux with their piss poor handshaking and caching models.
Try 1% of mac users since MacOS doesn't have a real 'maximize', 5% of users running resolutions higher than 1280x960, maybe 10% of users at 1280x800 (since increasingly people are setting their taskbar to portrait mode on the left)
There's more out there than 'Joe Windows' running 1024x768 small fonts.





0