[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

    • 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.
    • Google reportedly set to lose two key Gemini and DeepMind researchers to Anthropic by Karthik Mudaliar Google is reportedly preparing to lose two more prominent artificial intelligence researchers, with Gemini contributors Jonas Adler and Alexander Pritzel planning to join rival AI developer Anthropic. According to a report from Bloomberg, both researchers are viewed internally as important contributors to Google’s flagship Gemini model family. Adler worked on Google’s AI coding efforts, while Pritzel was involved in the process used to train AI systems. Neither company has publicly confirmed the moves. The report also does not say when the researchers will formally leave Google or what positions they will hold at Anthropic. Training a large AI model requires decisions covering its architecture, data preparation, distributed computing infrastructure, and post-training methods that shape how the finished system behaves. Researchers with experience operating at the scale of Gemini are consequently difficult to replace quickly. Both Adler and Pritzel have previously contributed to Google DeepMind’s scientific research as well. They are listed among the authors of the company’s work on expanding AlphaFold protein-structure predictions across entire proteomes, alongside AlphaFold researchers including John Jumper. The reported departures arrive shortly after another important change within Google’s Gemini organization. Gemini co-lead Noam Shazeer is leaving Google for OpenAI, after returning to the search company in 2024 through its deal with Character.AI. Shazeer is particularly well known as one of the authors of the Transformer paper, whose architecture became the foundation for most modern large language models. Anthropic, meanwhile, has been recruiting recognizable figures from other leading laboratories. OpenAI co-founder and former Tesla AI director Andrej Karpathy joined Anthropic’s pre-training team in May. His move, followed by the reported recruitment of several Google researchers, suggests Anthropic is strengthening the research teams responsible for the core capabilities of future Claude models rather than concentrating solely on product and enterprise sales. The competition is complicated by the companies’ extensive commercial relationships. Anthropic competes directly with Google’s Gemini models, but it also relies on Google as an infrastructure partner. In April, Anthropic announced an expanded agreement with Google and Broadcom covering multiple gigawatts of next-generation Tensor Processing Unit capacity. TPUs are Google-designed accelerators used to train and run large AI models. via Bloomberg
    • This article makes my head hurt. Lots of confusing words
  • 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
      462
    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!