[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

    • Stellarium 26.2 by Razvan Serea Stellarium is a free open source planetarium for your computer. It shows a realistic sky in 3D, just like what you see with the naked eye, binoculars or a telescope. It is being used in planetarium projectors. Just set your coordinates and go. Stellarium key features: Realistic simulation of the sky, sunrise and sunset Default catalogue of over 600,000 stars Downloadable additional catalogues for up to 210 million stars Catalog data for all New General Catalogue (NGC) objects Images of almost all Messier objects and the Milky Way Artistic illustrations for all 88 modern constellations More than a dozen different cultures with their constellations Solar and lunar eclipse simulation Photorealistic landscapes (more are available on the website) Scripting support with ECMAScript (a few demo scripts are included) Extendable with plug-ins: 8 plug-ins installed by default, including: artificial satellites plug-in (updated from an on-line TLE database) ocular simulation plug-in (shows how objects look like in a given ocular) Solar System editor plug-in (imports comet and asteroid data from the MPC) telescope control plug-in (Meade LX200 and Celestron NexStar compatible) The major changes of this version: Added new sky culture Added new plugin: Planes Many improvements in plugins Many improvements in Core and GUI Many updates in sky cultures. [full release notes] Download: Stellarium 26.2 (64-bit) | 456.0 MB (Open Source) View: Stellarium Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      418
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!