[Feedback needed] Atlas, the next version of Neowin


Recommended Posts

That is some crazy good design. I really like it a lot. Needs some dash of colors here and there, but overall really good. I think Neowin is one of the best designed sites out there. And the best thing you guys always try to improve yourself despite having a killer design.

I like it a lot :). The ad placement is a lot better than the current site layout IMO.

Yeah, I originally said I disliked the ad. placement, but I have since changed my mind; after having used it for a bit and got used to it, I seem to automatically skim over the advert.

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).

post-1912-1253302455_thumb.png

Yeah, I originally said I disliked the ad. placement, but I have since changed my mind; after having used it for a bit and got used to it, I seem to automatically skim over the advert.

but aren't the ads hidden for mods like they are for subscribers^2?

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).

I noticed that too.

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).

The squared version looks utter crap :/

True you are but even a 24" screen is merely 300 euros nowadays and even on that it must be extremely small - I prefer to have the wide version, that's a matter of opinion of course. Naturally a fluid dynamic webpage would be even better - that way everyone would win, too bad it's so hard to implement.

I'd agree, I prefer content that stretches to fit

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).

So you are deliberately designing a more crappy version for opera users? what the hell :/

It's not on purpose. We are using the border-radius CSS property, rather than having a bunch of images sent to you. It cuts down on the amount of HTML sent, too.

Opera is set to include border-radius in Opera 10.1, if I remember correctly. Hopefully Internet Explorer 9 will include some early CSS support, too, so IE users get a cleaner style too.

We did not make the decision quickly, and we didn't want to cut some members out. So we designed around it. The site looks a bit squared in Internet Explorer and Opera, yes. But it doesn't look that bad. And the bandwidth and load savings for you and for us make it worth it.

We're trying to move web standards forward that should have been in place long ago. I know someone will come in and say "CSS3 isn't finalized yet" - and we know it isn't. But it's been too long, and the benefits to using border-radius and drop-shadow are too great for the majority of our users to not use them.

I hope that clears it up a bit. We're not picking on certain groups of people; if we were, we'd put ads for Firefox, Chrome and Safari all over the site. Instead, we degraded the experience gracefully. It does not impact the usability of the site in any way.

One note about our use of border radius and drop shadows: by using them, Neowin downloads more than twice as fast as before. During heavy load, this will be a huge advantage for everyone, but even under regular load, you won't be waiting for images and extra HTML to be downloaded.

One note about our use of border radius and drop shadows: by using them, Neowin downloads more than twice as fast as before. During heavy load, this will be a huge advantage for everyone, but even under regular load, you won't be waiting for images and extra HTML to be downloaded.

Combine that with a FAR more efficient back end too (recoded from the ground up), pages render faster on the server, are delivered to you faster, and will display in your browser faster :)

It's not on purpose. We are using the border-radius CSS property, rather than having a bunch of images sent to you. It cuts down on the amount of HTML sent, too.

The HTML difference will be tiny per page, you'd save more space by removing all the whitespace in the HTML! As for images, shouldn't they be cached?

Opera is set to include border-radius in Opera 10.1, if I remember correctly. Hopefully Internet Explorer 9 will include some early CSS support, too, so IE users get a cleaner style too.

Opera 10.1 is basically Opera 10 with Unite included. The border-radius won't be added until Presto 2.3 which won't be very soon. As for IE9 when will that get released?

We did not make the decision quickly, and we didn't want to cut some members out. So we designed around it. The site looks a bit squared in Internet Explorer and Opera, yes. But it doesn't look that bad. And the bandwidth and load savings for you and for us make it worth it.

How did you design around it? You did nothing! It also looks very squared (not a "bit") and the tiny amount of data saved hardly makes up for the crappy look of it.

The HTML difference will be tiny per page, you'd save more space by removing all the whitespace in the HTML! As for images, shouldn't they be cached?

Opera 10.1 is basically Opera 10 with Unite included. The border-radius won't be added until Presto 2.3 which won't be very soon. As for IE9 when will that get released?

How did you design around it? You did nothing! It also looks very squared (not a "bit") and the tiny amount of data saved hardly makes up for the crappy look of it.

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.

It's not on purpose. We are using the border-radius CSS property, rather than having a bunch of images sent to you. It cuts down on the amount of HTML sent, too.

Opera is set to include border-radius in Opera 10.1, if I remember correctly. Hopefully Internet Explorer 9 will include some early CSS support, too, so IE users get a cleaner style too.

We did not make the decision quickly, and we didn't want to cut some members out. So we designed around it. The site looks a bit squared in Internet Explorer and Opera, yes. But it doesn't look that bad. And the bandwidth and load savings for you and for us make it worth it.

We're trying to move web standards forward that should have been in place long ago. I know someone will come in and say "CSS3 isn't finalized yet" - and we know it isn't. But it's been too long, and the benefits to using border-radius and drop-shadow are too great for the majority of our users to not use them.

I hope that clears it up a bit. We're not picking on certain groups of people; if we were, we'd put ads for Firefox, Chrome and Safari all over the site. Instead, we degraded the experience gracefully. It does not impact the usability of the site in any way.

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

Every browser should get the same experience.

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

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

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      169
    3. 3
      PsYcHoKiLLa
      119
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      69
  • Tell a friend

    Love Neowin? Tell a friend!