[Feedback needed] Atlas, the next version of Neowin


Recommended Posts

New design looks great, very clean and fresh looking :).

In regards to using css to create rounded corners, I think its a lot better than having to create images. I have done the same on some sites I have created recently.

If anyone wants to read up on rounded css property, check out:

http://www.css3.info/preview/rounded-border/

Surely on a site as big as this it makes more sense to wait until features are finalised, and have more wide support to use them. 2 browsers which between them make up about 70% of the world's browser usage don't even support the features being used, that should be a strong enough indication in itself :/
[...] a large portion of Neowin's browser users are having different pages fed to them.

These are probably two of the most absurd statements I've seen in a long time. Firstly, as Timan pointed out, they are the same pages - the same code - it's just that Internet Explorer and Opera cannot render some of the CSS elements, so how does that mean different pages are being fed to the user? It doesn't because they are the same pages.

Secondly, and this refers to the first statement quoted, it's not like rounded corners are a major feature which affects the functionality of a website. How do you even know you'd be getting rounded corners if Firefox, Chrome and Safari didn't support them? For all you know, everything may have been square if no browser supported 'border-radius.' It's a nice perk for those of us who use a browser which supports 'border-radius' though :)

Again, I'm not even defending Neowin here rather my own viewpoint as a web designer.

Surely on a site as big as this it makes more sense to wait until features are finalised, and have more wide support to use them. 2 browsers which between them make up about 70% of the world's browser usage don't even support the features being used, that should be a strong enough indication in itself :/

I really doubt 70% of Neowin users are on IE.

Going by the usual threads and posters I think it is*,

50.11% Opera

95.56% Firefox

3.5% Safari

-30.91% IE

30.41% Chrome

* Yea, I made it up :p

It could be true. IE is the default install browser, and most of the Internet uses IE.

Slot of traffic that comes into neowin is guests.

There should be statistics somewhere on neowin about browser usage.

It could be true. IE is the default install browser, and most of the Internet uses IE.

Slot of traffic that comes into neowin is guests.

There should be statistics somewhere on neowin about browser usage.

It's a tech website, it's going to be much more weighted to non-IE browsers.

On the website I work on (a pretty big one, much bigger than Neowin), which is not as tech-oriented as Neowin, IE has fallen below 40% of viewers. Well over half of viewers would see rounded corners, if we used them.

And, as people say, as the corners are not integral to the workings of the site, they've made a sensible decision. It might be relatively small saving, but it adds up to a lot over time. Everything counts. A small decrease in load times can make a huge difference to user satisfaction (and bandwidth costs).

(Oh, and Neowin already uses stuff IE doesn't support - text shadows. Check out the menu bar on the main page sometime.)

And what have the Neowin developers done? They have got the site to display properly in all browsers. So I ask again, how can you blame the developer in this case? Displaying rounded corners does not constitute "displaying properly". I suppose that could be a matter of opinion but I deem "displaying properly" as displaying in a usable manner.

I'm not even defending Neowin here, I'm defending my own opinion on CSS 'border-radius' and browser support for it.

They should use the standards that ALL browsers support so that EVERYONE gets the same experience when browsing Neowin, segmenting the site users by using elements that not all browsers can render smacks of using iframes back in the 90s that only ever worked properly in IE.

Any half decent webdesigner will tell you that its proper to make the site look exactly the same despite the platform, not doing so is poor form.

These are probably two of the most absurd statements I've seen in a long time. Firstly, as Timan pointed out, they are the same pages - the same code - it's just that Internet Explorer and Opera cannot render some of the CSS elements, so how does that mean different pages are being fed to the user? It doesn't because they are the same pages.

Secondly, and this refers to the first statement quoted, it's not like rounded corners are a major feature which affects the functionality of a website. How do you even know you'd be getting rounded corners if Firefox, Chrome and Safari didn't support them? For all you know, everything may have been square if no browser supported 'border-radius.' It's a nice perk for those of us who use a browser which supports 'border-radius' though :)

Again, I'm not even defending Neowin here rather my own viewpoint as a web designer.

Way to go on the offensive there Calum (Y)

I am merely stating my disappointment that things are being implemented before they are really ready

These ideas have been around for years, we can't wait a few years more to start using them. Again, everything degrades nicely, and a majority of our users will get the round corners.

No one's going to implement things in their browser unless they're pressured into it. We're starting that pressure. Are we a big site? Well, in the grand scheme of things... no, we're not. But there's still a chance that we can push Microsoft and Opera into implementing these somewhat basic features. Opera, we know, will be implementing them in the next major Presto update. Microsoft... we just hope.

Any half decent webdesigner will tell you that its proper to make the site look exactly the same despite the platform, not doing so is poor form.

Nope, any decent web designer will develop a site that delivers the content with maximum usability that degrades well in lesser browsers. which is what exactly is happening here.

Evolution not devolution.

No one's going to implement things in their browser unless they're pressured into it. We're starting that pressure.

Exactly. If no site will use it, there won't be any need for developers to implement it into the browser. And the absence of rounded corners doesn't degrade the site's usability.

Also: http://dowebsitesneedtolookexactlythesameineverybrowser.com/ :)

These ideas have been around for years, we can't wait a few years more to start using them. Again, everything degrades nicely, and a majority of our users will get the round corners.

No one's going to implement things in their browser unless they're pressured into it. We're starting that pressure. Are we a big site? Well, in the grand scheme of things... no, we're not. But there's still a chance that we can push Microsoft and Opera into implementing these somewhat basic features. Opera, we know, will be implementing them in the next major Presto update. Microsoft... we just hope.

Yeah I do appreciate that, sorry if I seemed a bit rude. Isn't IE9 still quiet a long way off though? :/

looking good so far .

i just hope that you make a lightweight homepage for Smart phones

Yeah I do appreciate that, sorry if I seemed a bit rude. Isn't IE9 still quiet a long way off though? :/

hopefully by next year ,along with Sl 4 x64 goodness

Edited by Ci7
i just hope that you make a lightweight homepage for Smart phones

I remember seeing this on Twitter yesterday - http://twitpic.com/i6c39

Also, looking great guys, can't wait to be browsing the new version. Esp with IPB 3 over 2.3.

I like it. The blue isn't as powerful as in the current version of Neowin - Finity - and it's perfect like this. It also has the Web 2.0 looks, looks polished, etc.

Thing is, the version before Finity, Swift I think, was perfect for me. When Finity appeared, I didn't like it at first. I've got to say that this upcoming version - Atlas - is much better and I'm already convinced by it. But do we really need a new theme every year or so? I think the Neowin mobile theme could be improved a lot though. It's overly simplified right now.

No matter what, I appreciate the work you guys do to keep the site updated, but I don't think all of it is necessary.

On another note, I didn't read the whole thread, but I think it's OK to make the assumption that it will have IPB 3.0 ... right?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Same Internet Archive seemed to grab the new version https://web.archive.org/web/20...d/Setup_MakeMKV_v1.18.4.exe Here's the link to an additional file it periodically downloads https://web.archive.org/web/20260213092148/https://www.makemkv.com/sdf.bin I think update's keys, etc. To manually trigger this update, put the sdf.bin file in the root of where the program is installed. When you launch the program it will pick up the file and import it. Typically put it here: C:\Program Files (x86)\MakeMKV\sdf.bin
    • Windows 11 KB5094126, KB5093998 bugging out Office apps but it may not be Microsoft's fault by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. Although the tech giant did not acknowledge any major problems, some users online reported various issues ranging from OneDrive and Dropbox access problems, BitLocker recovery lockouts, to blue screens and BSODs. You can read about them in this dedicated piece. While there is still no confirmation about those problems from Microsoft the company has admitted to another bug which we did not report on. The tech giant has confirmed it has received reports of an issue in which certain third-party applications may be unable to launch Microsoft Office apps or open Office documents after installing the Patch Tuesday. This affects both Windows 11 as well as Windows 10. The company says the problem impacts a subset of applications that rely on OLE (Object Linking and Embedding) automation to communicate with Microsoft Office programs. According to Microsoft, affected scenarios involve third-party software attempting to open Office applications or documents from within their own interface. In such cases, the Office program may fail to launch altogether, or the requested document may not open. Oddly there may not be any error message, which probably makes the issue difficult to diagnose. The bug affects several Office products, including Word, Excel, PowerPoint, Access, and other apps in the Microsoft Office suite when they are launched through the affected software. These include tax and accounting software such as CCH Engagement and Workpaper Manager, dental practice management solutions like Dentrix and Softdent, as well as the popular research and reference management tool Zotero. Microsoft adds that other applications using similar Office integration methods could also experience the same problematic behavior. To understand the issue it is important to look at OLE, the Microsoft technology involved. OLE allows different applications to work together and share data, while its Automation feature lets one program control another. Thus this enables third-party software to launch Microsoft Office apps, open documents, and perform tasks automatically without requiring users to switch between programs. Because many accounting, healthcare, research, and business applications rely on OLE automation to interact with Word, Excel, PowerPoint, and other Office apps, any disruption can break those workflows. As a result, affected software may be unable to open Office documents or launch Office applications even though the programs themselves continue to work normally. At the moment the company has not provided a permanent fix though it has confirmed that engineers are actively working on a resolution, which will be delivered through a future Windows update. As such additional details will be shared once more information becomes available. In the meantime, Microsoft recommends a simple workaround for affected users whic is to open the Office application or document directly rather than launching it through the third-party program. For enterprise customers and organizations managing larger deployments, Microsoft says an additional mitigation is available. Admins experiencing the problem on their managed devices are advised to contact Microsoft Support for business to obtain and apply the workaround.
    • It saddens me when cars are such dull colours now. Mine is bright metallic blue and I absolutely adore it for standing out in contrast to that depressing backdrop of traffic.
    • Sparkle 2.20.0 by Razvan Serea Sparkle is a free, open-source Windows optimization tool designed to make your PC faster, cleaner, and more private. With Sparkle, you can easily debloat Windows by removing unnecessary apps and services, disable Microsoft tracking to enhance privacy, and apply performance tweaks to boost speed. Its cleaner removes junk and temporary files, while every change is safe and fully reversible. Sparkle also features a modern, user-friendly interface with automatic updates, making system maintenance simple. Explore over 39 tweaks, from disabling telemetry and hibernation to optimizing network and game settings, all aimed at customizing and enhancing your Windows experience. Sparkle supports Windows 10 and 11. Sparkle 2.20.0 changelog: Debloat Tweak has animated border New homepage loading UI New Tweak Modal (Markdown Supported) Refactored GPU Detection Added Tests with vitest Added foobar2000 to apps Added Localsend to apps Updated Modal Styles Added styles for disabled inputs Added Animated Border to debloat-windows tweak Bumped dependencies Refactor System info logic for speed Tweak info modals now support Markdown Added Clear System info cache to settings Redesigned Home Page Loading UI Changed Some Icons around the app Download: Sparkle 2.20.0 | Portable | ~100.0 MB (Open Source) Links: Sparkle Website | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • lol it was a typo, fixed! haha imagine an actual 4TB Gen4 NVMe for $40 in 2026
  • Recent Achievements

    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!