[Feedback needed] Atlas, the next version of Neowin


Recommended Posts

Considering you haven't actually used the site, I don't think it would be fair for you to say the data savings are minimal. When we have all the code finalized, we'll be able to prove it to you.

And we did put effort into it. We wouldn't be doing this if the design we chose looked hideous in Opera and IE. Considering the circumstances, it could be a lot worse. The design was always intended to look good both ways, as we knew it would be seen both ways. Again, it's not fair for you to criticize until you've really seen it and used it in person, and you do need to realize the amount of effort and thought that went into the design.

To be honest, we had it square on our dev sites for a very long time, and it looked fine. Once you see it and use it live, you'll see it really doesn't look worse.

I agree. As you know, Dave, I used Internet Explorer for a fair bit when I first started using Atlas (as I was using IE anyway) and I'd been using it for over a week before I changed to Firefox and noticed it was all rounded. When using Internet Explorer, not knowing the site was rounded in other browsers, I still thought it looked very nice and had no problem with it.

To those complaining to the Neowin developers... why not blame your browser manufacturer? If Mozilla and Apple have been able to include support for the 'border-radius' then so have Opera and Microsoft; they just haven't bothered/have focussed on other features. That isn't Neowin's fault. Why should they be disadvantaged by having to include rounded images just because some browser manufacturers are behind with the times?

And we did put effort into it. We wouldn't be doing this if the design we chose looked hideous in Opera and IE. Considering the circumstances, it could be a lot worse. The design was always intended to look good both ways, as we knew it would be seen both ways. Again, it's not fair for you to criticize until you've really seen it and used it in person, and you do need to realize the amount of effort and thought that went into the design.

It could also look a *lot* better :p It does not look good in squared "mode". If I haven't really seen it, what was the point of showing the image of it?

I have to disagree with Mike's above post.

Eradicating all the extras DIV's and images etc needed to create rounded corners will cut down page load times enormously.

I'd disagree, if a browser takes an "enormous" time to handle a few extra divs it is seriously broken.

Wow I can't believe I didn't see this thread until now. I definitely like the look of the new theme. The only way I can describe it as is...smooth. The subtle changing to a more subdued blue is less striking but a bit easier on the eyes and compliments the overall look.

Wow I can't believe I didn't see this thread until now. I definitely like the look of the new theme. The only way I can describe it as is...smooth. The subtle changing to a more subdued blue is less striking but a bit easier on the eyes and compliments the overall look.

they just opened it up to us normies

I completely disagree that different browsers get a different version of the site.

Every browser should get the same experience.

Well why are you blaming Neowin? They've used the same code to get rounded elements and yet only Chrome, Safari and Firefox display those rounded elements. Surely if every browser should get the same experience then every browser should display the same output using the same code? I'm going by your logic there. Do you see what I'm saying? As a web designer myself, I'm really passionate about this - It's Microsoft and Opera's fault why the 'border-radius' doesn't display rounded elements in their browsers so I find it appalling that people can blame the developer. If a developer can make their website more efficient but still look nice in a browser that is behind with the times, often they will do so. You want rounded corners? Then why not use a browser that can render them utilising the CSS code which was designed to do such a thing?

"A few extra divs" in web design terms is a big deal.

It really isn't...

Well why are you blaming Neowin? They've used the same code to get rounded elements and yet only Chrome, Safari and Firefox display those rounded elements. Surely if every browser should get the same experience then every browser should display the same output using the same code? I'm going by your logic there. Do you see what I'm saying? As a web designer myself, I'm really passionate about this - It's Microsoft and Opera's fault why the 'border-radius' doesn't display rounded elements in their browsers so I find it appalling that people can blame the developer. If a developer can make their website more efficient but still look nice in a browser that is behind with the times, often they will do so. You want rounded corners? Then why not use a browser that can render them utilising the CSS code which was designed to do such a thing?

You blame the developer because they're developing for the browsers out there in use today. The developer is responsible in getting the site to display properly in all browsers, just like a software developer is responsible to ensure their software works with new versions of Windows for example.

You blame the developer because they're developing for the browsers out there in use today. The developer is responsible in getting the site to display properly in all browsers, just like a software developer is responsible to ensure their software works with new versions of Windows for example.

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.

It really isn't...

I think we are going to have to agree to dis-agree here.

I've worked in web development for over a decade and i can tell you that any web developer worth their salt will cut out any extra fluff that's un-needed especially on a busy high bandwidth site such as Neowin.

I commend the developers here for their decision to go with CSS instead of images/nested divs.

I wanted to avoid getting really technical here, but here we go...

The HTML for the latest activity box on Finity: http://min.ie/1QG

As you can see, there are a *lot* of nested divs to create the rounded corner effect.

On Atlas: http://min.ie/1QH

Download time cut down significantly, not to mention rendering time.

If you want to keep this going, pick it up in a PM with me. I don't want to post raw numbers here because our code is likely to change significantly before we release.

I would just like to say, very nice! I think it looks wonderful! You have worked hard on this site, and your hard work shows.

As for the rounded/box corners, while I am one of the ones who uses Opera, and will end up with boxed corners, I think it still looks great.

I like that a tech site is using the latest in programming and design.

Now if only Opera would hurry up and get with the latest...

Going to address this now, than later.

Safari, Chrome, Firefox (3+) will get nice rounded corners and drop shadows.

IE, Opera (crap) will get a squared looking site (which still looks nice, but a bit more "lite" like).

Opera basher?:laugh:: Opera is the bestest of the bester of them all. I love squares.

Opera basher?:laugh:: Opera is the bestest of the bester of them all. I love squares.

Hehe, I had to:pp... you have no idea how much of a pain it was to get some things to look right. And there is almost no documentation on css fixes for the opera 9~ versions.

Hehe, I had to :p ... you have no idea how much of a pain it was to get some things to look right. And there is almost no documentation on css fixes for the opera 9~ versions.

No matter. It's a very good design and pleases me very much, round or square.

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 don't understand why people are making such a big fuss over rounded or square corners... The site looks amazing no matter what browser it would be viewed in. It is as simple as that.

Great work Devs!

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 :/

Opera doesn't really contribute a lot towards that percentage.

Opera doesn't really contribute a lot towards that percentage.

So what? The issue is the same for Opera and IE so that is irrelevant, a large portion of Neowin's browser users are having different pages fed to them.

So what? The issue is the same for Opera and IE so that is irrelevant, a large portion of Neowin's browser users are having different pages fed to them.

No, they are not, everyone gets the same exact code. Its just IE/Opera do not render the rounded corners the css specifies.

We'd have to make images for every single corner of ever box (different colors, different styles etc), also means alot more markup.

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

    • No registered users viewing this page.
  • Posts

    • Apple Watch Series 11 GPS just crashed to 30% off in this fast-moving Prime Day deal by Karthik Mudaliar The Apple Watch Series 11 is available for $279, down from its $399 list price, saving buyers $120, or 30%. Amazon labels the offer as selling fast, so the current price may not remain available for long. This GPS model features a 42mm aluminum case, an Always-On Retina LTPO3 OLED display capable of reaching up to 2,000 nits, and an Ion-X glass surface with improved scratch resistance. Apple rates Series 11 for up to 24 hours of normal use or up to 38 hours in Low Power Mode, with fast charging providing up to eight hours of use from a 15-minute charge. Health and fitness tools include sleep scoring, temperature sensing, ECG support, heart-rate alerts, workout tracking, sleep apnea notifications, and hypertension notifications, where available. The watch also carries IP6X dust resistance and 50-meter water resistance. This configuration is best suited to iPhone owners who want comprehensive health tracking, notifications, contactless payments, and workout data without stepping up to a larger or cellular-equipped model. The smaller case should also appeal to buyers who prefer a lighter watch, while the S/M band fits wrists measuring 130mm to 180mm. With the current generation now significantly below its usual retail price, this is a strong time to replace an aging Apple Watch or buy a first model without compromising on Apple’s newest health and display features. Grab the discounted Apple Watch Series 11 (sold and shipped by Amazon) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • The laptop in the bedroom is an Acer with i7-10510U CPU. Acer's website states they will not be upgrading it so I had little choice other than disable secure boot. I know next to nothing on these matters so hopefully it will be fine.
    • GitHub removes manual model selection from Copilot free and student plans by Karthik Mudaliar GitHub is removing the ability to manually select an AI model from its Copilot Free and Student plans, making its automatic routing system the default and only way to choose a model. This means users on these tiers will no longer be able to deliberately select a particular OpenAI, Anthropic, Google, or Microsoft model for a task. In its announcement, GitHub said Copilot Auto will dynamically choose what it considers the best model for each request. Free and Student accounts will retain access to models from multiple families, although the available selection will continue to depend on the restrictions attached to each plan. GitHub did not identify a fixed pool of models that Auto will always use, and its documentation warns that model availability can change over time. GitHub describes Auto as more than a random fallback system. On supported surfaces, its task-optimization technology evaluates the complexity of a request alongside real-time information about model health and availability. Straightforward prompts can be routed to faster and less expensive models, while more demanding coding tasks may be sent to higher-cost reasoning models. The company says this approach should reduce rate limiting, latency, and failed requests. Auto generally selects one model along natural prompt-caching boundaries rather than repeatedly switching models during a session, as GitHub found that mid-session changes increased costs without producing sufficient improvements in output quality. Users can still check which model generated a response. In Copilot Chat, the information appears when hovering over an answer, while Copilot CLI and the Copilot cloud agent display the selected model alongside their output. Auto is available in Copilot Chat, Copilot CLI, and the cloud agent, with the exact implementation and release status varying between supported development environments. The latest restriction follows several months of adjustments to Copilot’s individual plans. GitHub temporarily halted new Pro, Pro+, and Student subscriptions in April as it sought to manage demand and service reliability. It later introduced token-based billing and began gradually reopening individual-plan registrations on June 17. Alongside the picker change, GitHub is retiring the “Preview” label from Microsoft-developed models. It argues that the label is no longer necessary because Auto handles model routing and models are continuously updated behind the scenes.
    • Look up 'inflation' kid. Ask an AI for the numbers between both games.
  • Recent Achievements

    • One Year In
      Philsl earned a badge
      One Year In
    • 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
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      124
    4. 4
      Michael Scrip
      79
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!