[Feedback needed] Atlas, the next version of Neowin


Recommended Posts

Overall, it's looking very nice! Much more efficient use of the available space...

One thing bothering me though - the rounded corners are only supported by Firefox, whereas IE users will get the non-rounded corners? Argh! Neowin making me switch to IE for browsing purposes? I suppose there's no need to be too dramatic, as long as it's not too difficult to revert to the non-rounded through some simple CSS tweaks!

Apologies if this was mentioned already, but I might've missed it when quickly skimming through the 9 pages.

You can always use Stylish to apply any tweaks you'd like. I'm sure the devs wouldn't mind telling you what to change to remove the rounded corners.

All in all, it's kind of ironic they haven't recognized that technology has moved forward and everyone either has a widescreen monitor or a high res 4:3 monitor, you know since they're doing a solo crusade to force some browser to ugprade to a work in progress standard.

after all the people who don't use a high res 4:3 monitor or wide screen monitor could use one of the low res device(i.e. mobile) layouts.

Not everyone that has a wide screen monitor browses with the browser maximized; I don't. I have Fx open about 3/4 of the way; the remaining portion is either for messenger or yahoo widgets. To me, it seems like a waste of screen real estate to browse maximized.

We're not denying anyone the option of increasing the width of the site via Stylish or a custom CSS file of any sort. What we are saying is that the site does not operate as designed if we offer it.

We don't want to offer options that make the site work in ways we did not intend. If users want to have the width increased, they can do a simple CSS file with the contents #container { width: 100%; }, and be done with it. Otherwise, we have to put the code in to offer a feature which, in our opinion, breaks the site, and requires a lot more support because of it.

Personally, I think that's perfectly reasonable.

I don't understand tho, you guys tried this with the last refresh and got a ton of bad feedback about it. It doesn't make any sense for force it again especially as your *still* getting a ton of bad feedback about it. I think those giving feedback understand *why* you want to do it, but at the same time it's kinda fail to just shun off the feedback in favour of the "vision"

I don't understand tho, you guys tried this with the last refresh and got a ton of bad feedback about it. It doesn't make any sense for force it again especially as your *still* getting a ton of bad feedback about it. I think those giving feedback understand *why* you want to do it, but at the same time it's kinda fail to just shun off the feedback in favour of the "vision"

You do know the current site is a fixed width by default. You have to know WHAT button to click to make it semi fluid/larger width.

(though I agree about the white bg helping it feel wider...)

cnn.com

bbc.co.uk

= Fixed width,

Also, here is the site at a fluid width.

http://qkpic.com/e1e9e

Edited by Timan
you do know the current site is a fixed width by default. You have to know WHAT button to click to make it semi fluid/larger width.

yes... you put that it after the feedback last time and it's worked fine so far. Removing it leads to the dislike seen in this thread.

I don't understand tho, you guys tried this with the last refresh and got a ton of bad feedback about it. It doesn't make any sense for force it again especially as your *still* getting a ton of bad feedback about it. I think those giving feedback understand *why* you want to do it, but at the same time it's kinda fail to just shun off the feedback in favour of the "vision"

Don't forget the views of the silent majority.

Design looks great! Can't wait to use it.

The font in the screen shot that Timan posted (fluid width) seems to work much better than the font in the original screen shot. I actually like the squared design better than the rounded (on Fx) and will use stylish to make it so. I also don't have any problems with the fixed design as i used Fx in a windowed mode.

Awesome work guys!

All in all, it's kind of ironic they haven't recognized that technology has moved forward and everyone either has a widescreen monitor or a high res 4:3 monitor, you know since they're doing a solo crusade to force some browser to ugprade to a work in progress standard.

after all the people who don't use a high res 4:3 monitor or widescreen monitor could use one of the low res device(i.e. mobile) layouts.

So you complain that Neowin disadvantage one type of user by giving them exactly the same experience as all other types of user, but you then suggest that they actually disadvantage a type of user by giving them a worse experience (the mobile skin). I see your logic... I see it, but it's not logical. At least with this fixed-width layout all users are getting the same Neowin experience - no one is getting discriminated against and no one is becoming disadvantaged (you can't call 'extra space at the sides' disadvantaging users when you suggested that some users be given the mobile skin just because they can't afford or do not want a larger monitor...)

It's obvious that you just can't please everyone. Just because larger monitors are now fairly popular amongst the technology enthusiasts, it doesn't mean everybody wishes to maximise their browser window and have it cover the whole screen. I actually see no point in that, especially when most sites tend to be the same sort of width (the width of the current Neowin front page), so surely Neowin can't be the only website that annoys you people by not being fluid? You must get annoyed by a lot of websites... I'm going to get a much larger monitor soon and I am extremely happy that the Neowin developers have designed this new theme with this width in mind because it means I will not have to have my browser window too big and I can have my buddy list, Facebook widget and Zune software (in mini-mode) showing at all times.

This is just my opinion by the way, but I feel strongly about this - I'm getting a bigger monitor so I can do more at once and fit more on the screen, not so I can pointlessly maximise my browser window when I can currently do that just fine, and view all websites perfectly, on my 17" laptop screen...

See I like how InsanelyMac does it. They have the option up top of doing fixed or fullscreen. I am lost as to how a "tech site" wouldn't allow for widescreen monitors.

Here is InsanelyMac.

http://www.insanelymac.com/

See I like how InsanelyMac does it. They have the option up top of doing fixed or fullscreen. I am lost as to how a "tech site" wouldn't allow for widescreen monitors.

Here is InsanelyMac.

http://www.insanelymac.com/

In my opinion that looks awful when using the "full screen" version on my 22" monitor at work (so much white space, logos/search bar positioned horribly), but looks very nice when using the "fixed width" version, on this 22" monitor, with space at the sides. Yes, it's nice they offer that choice because, in my opinion, choice is always a benefit, however, that's because it seems to work for their site (to some extent... it still looks horrible in my opinion). Looking at Timan's screenshot in one of his latest posts, it looks like it wouldn't work for Atlas - loads of white space, the promo image changer only covering half of that section etc.

I'm not speaking for any developers here, but I doubt Timan's screenshot is how the developers would like Neowin to look.

So you complain that Neowin disadvantage one type of user by giving them exactly the same experience as all other types of user, but you then suggest that they actually disadvantage a type of user by giving them a worse experience (the mobile skin). I see your logic... I see it, but it's not logical. At least with this fixed-width layout all users are getting the same Neowin experience - no one is getting discriminated against and no one is becoming disadvantaged (you can't call 'extra space at the sides' disadvantaging users when you suggested that some users be given the mobile skin just because they can't afford or do not want a larger monitor...)

It's obvious that you just can't please everyone. Just because larger monitors are now fairly popular amongst the technology enthusiasts, it doesn't mean everybody wishes to maximise their browser window and have it cover the whole screen. I actually see no point in that, especially when most sites tend to be the same sort of width (the width of the current Neowin front page), so surely Neowin can't be the only website that annoys you people by not being fluid? You must get annoyed by a lot of websites... I'm going to get a much larger monitor soon and I am extremely happy that the Neowin developers have designed this new theme with this width in mind because it means I will not have to have my browser window too big and I can have my buddy list, Facebook widget and Zune software (in mini-mode) showing at all times.

This is just my opinion by the way, but I feel strongly about this - I'm getting a bigger monitor so I can do more at once and fit more on the screen, not so I can pointlessly maximise my browser window when I can currently do that just fine, and view all websites perfectly, on my 17" laptop screen...

Just include a button for it like there is now and everyone is happy.

Noooooooooooooooo! Why do people insist on having all that wasted space on the left and right hand sides? I have a widescreen monitor, I dare say quite a few people here do as well, so let us use that space!

Remember, people read websites in an "F" shape, not a "T" shape =\

I understand the reasonings behind making it easier for the developers, but what about the users? They should be your primary focus.

Just include a button for it like there is now and everyone is happy.

As I have said, choice is always a benefit, but I'm not a Neowin developer so I don't know the ins and outs of the design :p I doubt they would deny users the choice if Atlas looked decent in a fluid manner, but as The_Decryptor pointed out, the design just doesn't lend itself to that, judging by Timan's screenshot. This might not be the reason, but if you'd worked hard designing something which looks really nice, would you like to see it used in a way which, in your opinion, breaks it? :/

but if you'd worked hard designing something which looks really nice, would you like to see it used in a way which, in your opinion, breaks it? :/

I wouldn't care how people use it as long as they are happy. And the users do want the choice myself included. Just add the button there and the discussion is over. And its not impossible to do.

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

    • No registered users viewing this page.
  • Posts

    • 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
    • Google adds built-in computer control to Gemini 3.5 flash by Karthik Mudaliar Google has added Computer Use as a built-in tool in Gemini 3.5 Flash, giving developers a single model that can reason about a task and operate graphical interfaces across browsers, mobile devices, and desktop environments. The feature is available through the Gemini API and Google’s Gemini Enterprise Agent Platform, although it remains a preview feature for now. Computer Use enables an AI agent to examine screenshots and return actions such as mouse clicks, scrolling, and keyboard input. A developer’s application must execute those actions, capture the resulting screen, and send it back to Gemini, creating a continuous loop until the task is completed. Google says the integration can be used for activities including repetitive form filling, application testing, research across multiple websites, and longer enterprise workflows. Gemini 3.5 Flash can work with browser, mobile, and desktop environments, whereas Google’s earlier standalone Computer Use model was primarily positioned around browser interaction. The main change is consolidation. Computer control was previously offered through the separate Gemini 2.5 Computer Use preview model. As Neowin reported when that model was introduced, it was designed to interpret a visual interface and generate actions without requiring a website-specific API. Google later brought Computer Use to preview versions of Gemini 3 Pro and Gemini 3 Flash in January 2026. The latest release now incorporates the tool into the stable Gemini 3.5 Flash model rather than requiring developers to select a specialized model solely for interface automation. Gemini 3.5 Flash itself was announced in May as Google’s latest fast model for coding and multi-step agent workflows. It supports a one-million-token input context window and up to 65,000 output tokens, along with adjustable thinking levels that let developers trade additional reasoning for lower latency and cost. Google also added that Gemini 3.5 Flash received targeted adversarial training for computer-use scenarios. The company is also offering safeguards that can require user confirmation before sensitive or irreversible actions and automatically stop a workflow when suspected prompt injection is detected. Its developer documentation describes configurable protections for areas such as financial transactions and changes to sensitive records. Google isn't the first to bring Computer Use to its platform. Anthropic has made computer control available through Claude, while OpenAI has continued improving computer-use performance in its recent models. Microsoft has also applied the concept to business workflows, including a Computer Use capability for the Researcher agent in Microsoft 365 Copilot.
  • 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
      463
    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!