[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

    • Turbo Pascal was my first real programming experience more than 30 years ago at university. I mostly taught myself from the included examples and help documentation, because the university only taught the basic syntax and philosophy of Pascal, without going deeply into Turbo Pascal’s advanced features. I still remember when I discovered that I could embed assembly language directly into Pascal code, call BIOS functions, manipulate screen memory, use mouse interrupts, and control peripherals from my programs. That opened huge doors for me. Programming back then felt really fun, direct, and close to the machine. What I loved about Pascal was its readability and the almost instant compile time. Turbo Pascal was an amazing environment, but unfortunately Turbo Pascal for Windows 3 did not feel like it fully carried that legacy forward. Later, Delphi got things back on the right track after the messy transition to TP for Windows. Sadly, Delphi suffered from years of uncertainty as it moved from Borland to CodeGear and then to Embarcadero. That instability made many developers lose confidence in it, even though Delphi itself remained a powerful and productive tool. I still work with Delphi from time to time, but I definitely miss the old days of Turbo Pascal.
    • I hope this encodes in to AV1 or AV2 as currently tiktok uses h265 and h264.
    • Qualcomm reportedly in talks to build custom video chips for TikTok parent ByteDance by Karthik Mudaliar Qualcomm is reportedly in advanced discussions to provide custom chip-design services to Chinese tech giant ByteDance, the same company behind TikTok. According to a report from Reuters, Qualcomm could be involved in designing custom silicon tailored for ByteDance's massive data-center workloads. If it goes through, the deal would make ByteDance one of Qualcomm's early anchor customers for its fastly growing custom chip-design division, For years, Qualcomm was the king of making smartphone processors and modems. The company has also been moving into the PC ecosystem and other formats such as on-device AI for Android XR headsets. However, this particular deal is about Qualcomm's custom Application-Specific Integrated Circuits (ASICs). For a platform like TikTok, ByteDance needs hardware that can help it ingest, process, and serve billions of short-form videos daily. Generalised hardware is no longer the most cost-effective and efficient route, which is why ByteDance is trying to develop custom Video Processing Units (VPUs). VPUs designed specifically for ByteDance’s algorithmic needs could drastically reduce data-center power consumption and improve encoding speeds at an unprecedented scale. The underlying tech behind these processors is actually from Qualcomm's recent acquisition of AlphaWave Semi, a high-speed connectivity specialist company. By combining AlphaWave’s high-bandwidth IP with Qualcomm’s architectural expertise, the company could begin mass production by the end of 2026, if the talks go through. All this also comes at a time when U.S.-China tech relations have dwindled. Escalating trade frictions between Washington and Beijing have severely impacted the export of high-end AI chips from U.S. firms like Nvidia, AMD, and Lam Research. Yet, the Qualcomm-ByteDance discussions show that U.S. tech companies are still actively seeking growth avenues and are open to doing business with China, where regulators still permit. Reuters notes that the outcome of this deal could be uncertain, and ByteDance might also seek partners other than Qualcomm. via Reuters | Image via DepositPhotos.com
  • Recent Achievements

    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      456
    2. 2
      +Edouard
      164
    3. 3
      PsYcHoKiLLa
      117
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      69
  • Tell a friend

    Love Neowin? Tell a friend!