[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

    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
    • AMD releases hotfix for driver install issues on Windows 10 PCs by Taras Buria Earlier this week, AMD released an important graphics driver update. Version 26.6.2 brought AMD FSR 4.1 support to the previous-gen Radeon lineup, the RX 7000 series, giving users better upscaling tech that was previously locked to the newest GPUs. However, the driver turned out to be a little buggy, with users reporting installation issues on systems still running Windows 10. AMD quickly acknowledged the bug and today released a hotfix to resolve the problem. The AMD 26.6.3 Hotfix update is now available for download from the official website. Given that it is a hotfix release, it has only one change in its release notes: AMD announced the update on its official X account and added that a WHQL driver update with the necessary fixes would be released next week. Meanwhile, users can apply the hotfix or roll back to the previous driver using the official AMD Cleanup Utility. You can download AMD Software: Adrenalin Edition 26.6.3 Hotfix Preview Driver from the official website here. It is compatible with all currently supported graphics cards and 64-bit Windows 10 and 11. Full release notes are available on the same page.
    • With Microsoft now listening to its core audience and acting upon received feedback, fans can finally expect a much better version of Windows 11 than what was available five years ago. Here is to five more years, Windows 11! I guess we all need a good laugh now and again...
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!