[Feedback needed] Atlas, the next version of Neowin


Recommended Posts

New design looks great, very clean and fresh looking :).

In regards to using css to create rounded corners, I think its a lot better than having to create images. I have done the same on some sites I have created recently.

If anyone wants to read up on rounded css property, check out:

http://www.css3.info/preview/rounded-border/

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 :/
[...] a large portion of Neowin's browser users are having different pages fed to them.

These are probably two of the most absurd statements I've seen in a long time. Firstly, as Timan pointed out, they are the same pages - the same code - it's just that Internet Explorer and Opera cannot render some of the CSS elements, so how does that mean different pages are being fed to the user? It doesn't because they are the same pages.

Secondly, and this refers to the first statement quoted, it's not like rounded corners are a major feature which affects the functionality of a website. How do you even know you'd be getting rounded corners if Firefox, Chrome and Safari didn't support them? For all you know, everything may have been square if no browser supported 'border-radius.' It's a nice perk for those of us who use a browser which supports 'border-radius' though :)

Again, I'm not even defending Neowin here rather my own viewpoint as a web designer.

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 doubt 70% of Neowin users are on IE.

Going by the usual threads and posters I think it is*,

50.11% Opera

95.56% Firefox

3.5% Safari

-30.91% IE

30.41% Chrome

* Yea, I made it up :p

It could be true. IE is the default install browser, and most of the Internet uses IE.

Slot of traffic that comes into neowin is guests.

There should be statistics somewhere on neowin about browser usage.

It could be true. IE is the default install browser, and most of the Internet uses IE.

Slot of traffic that comes into neowin is guests.

There should be statistics somewhere on neowin about browser usage.

It's a tech website, it's going to be much more weighted to non-IE browsers.

On the website I work on (a pretty big one, much bigger than Neowin), which is not as tech-oriented as Neowin, IE has fallen below 40% of viewers. Well over half of viewers would see rounded corners, if we used them.

And, as people say, as the corners are not integral to the workings of the site, they've made a sensible decision. It might be relatively small saving, but it adds up to a lot over time. Everything counts. A small decrease in load times can make a huge difference to user satisfaction (and bandwidth costs).

(Oh, and Neowin already uses stuff IE doesn't support - text shadows. Check out the menu bar on the main page sometime.)

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.

They should use the standards that ALL browsers support so that EVERYONE gets the same experience when browsing Neowin, segmenting the site users by using elements that not all browsers can render smacks of using iframes back in the 90s that only ever worked properly in IE.

Any half decent webdesigner will tell you that its proper to make the site look exactly the same despite the platform, not doing so is poor form.

These are probably two of the most absurd statements I've seen in a long time. Firstly, as Timan pointed out, they are the same pages - the same code - it's just that Internet Explorer and Opera cannot render some of the CSS elements, so how does that mean different pages are being fed to the user? It doesn't because they are the same pages.

Secondly, and this refers to the first statement quoted, it's not like rounded corners are a major feature which affects the functionality of a website. How do you even know you'd be getting rounded corners if Firefox, Chrome and Safari didn't support them? For all you know, everything may have been square if no browser supported 'border-radius.' It's a nice perk for those of us who use a browser which supports 'border-radius' though :)

Again, I'm not even defending Neowin here rather my own viewpoint as a web designer.

Way to go on the offensive there Calum (Y)

I am merely stating my disappointment that things are being implemented before they are really ready

These ideas have been around for years, we can't wait a few years more to start using them. Again, everything degrades nicely, and a majority of our users will get the round corners.

No one's going to implement things in their browser unless they're pressured into it. We're starting that pressure. Are we a big site? Well, in the grand scheme of things... no, we're not. But there's still a chance that we can push Microsoft and Opera into implementing these somewhat basic features. Opera, we know, will be implementing them in the next major Presto update. Microsoft... we just hope.

Any half decent webdesigner will tell you that its proper to make the site look exactly the same despite the platform, not doing so is poor form.

Nope, any decent web designer will develop a site that delivers the content with maximum usability that degrades well in lesser browsers. which is what exactly is happening here.

Evolution not devolution.

No one's going to implement things in their browser unless they're pressured into it. We're starting that pressure.

Exactly. If no site will use it, there won't be any need for developers to implement it into the browser. And the absence of rounded corners doesn't degrade the site's usability.

Also: http://dowebsitesneedtolookexactlythesameineverybrowser.com/ :)

These ideas have been around for years, we can't wait a few years more to start using them. Again, everything degrades nicely, and a majority of our users will get the round corners.

No one's going to implement things in their browser unless they're pressured into it. We're starting that pressure. Are we a big site? Well, in the grand scheme of things... no, we're not. But there's still a chance that we can push Microsoft and Opera into implementing these somewhat basic features. Opera, we know, will be implementing them in the next major Presto update. Microsoft... we just hope.

Yeah I do appreciate that, sorry if I seemed a bit rude. Isn't IE9 still quiet a long way off though? :/

looking good so far .

i just hope that you make a lightweight homepage for Smart phones

Yeah I do appreciate that, sorry if I seemed a bit rude. Isn't IE9 still quiet a long way off though? :/

hopefully by next year ,along with Sl 4 x64 goodness

Edited by Ci7
i just hope that you make a lightweight homepage for Smart phones

I remember seeing this on Twitter yesterday - http://twitpic.com/i6c39

Also, looking great guys, can't wait to be browsing the new version. Esp with IPB 3 over 2.3.

I like it. The blue isn't as powerful as in the current version of Neowin - Finity - and it's perfect like this. It also has the Web 2.0 looks, looks polished, etc.

Thing is, the version before Finity, Swift I think, was perfect for me. When Finity appeared, I didn't like it at first. I've got to say that this upcoming version - Atlas - is much better and I'm already convinced by it. But do we really need a new theme every year or so? I think the Neowin mobile theme could be improved a lot though. It's overly simplified right now.

No matter what, I appreciate the work you guys do to keep the site updated, but I don't think all of it is necessary.

On another note, I didn't read the whole thread, but I think it's OK to make the assumption that it will have IPB 3.0 ... right?

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

    • No registered users viewing this page.
  • Posts

    • Motrix Next 3.9.6 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.6 changelog: New Features Clipboard management — App-owned copy actions no longer trigger the Add Task auto-detect popup. aria2 input compatibility — Multi-line aria2-style task input is supported for URLs with per-task options such as out=. BitTorrent IPv6 DHT — Added IPv6 DHT support and related configuration. File category URL patterns — File category rules can match URL patterns with validation and localized hints. Task status tags — Added clearer waiting and sharing states for task cards. Download event bridge — Added an aria2 WebSocket event bridge for faster download notifications. Improvements Improved task list transitions and preserved task state during tab switches. Kept RPC origin access enabled for local integrations. Restored AppImage stripping in release builds after beta validation. Added localized preference guidance across supported languages. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Segra 1.6.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.6.2 changelog: UI: Improved the transition from the loading skeleton to the real content card. Security: Added Segra.dll code signing and automatic VirusTotal upload. Settings: Fixed the settings header to highlight Account when scrolled to the top. Recording: Updated OBSKit.NET to 1.4.1. Download: Segra 1.6.2 | 74.5 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Hey Google, these are the Gemini features I want in 2026 by Aditya Tiwari Google Gemini has been around for over three years. The AI chatbot started its journey back in 2023 (as Bard) when ChatGPT was already a talk of the town. However, it quickly attracted criticism after misrepresenting facts about the James Webb Space Telescope. The search giant spent a year fine-tuning Bard before rebranding the chatbot and its underlying generative AI model to Gemini, drawing inspiration from NASA's first human spaceflight program. Note that Bard was initially powered by LaMDA and PaLM 2; Google has since added several new features and integrations to Gemini. That said, there is scope for improvement and a gap for new features. I have been using Gemini for a while now and have realized that the chatbot lacks several features, making it harder for me to research across topics. These are mostly function-over-form updates that can improve the overall experience. Delete individual messages from a conversation Image via DepositPhotos.com One good thing about Gemini is that it can maintain context throughout the conversation. But things might get chaotic when you want to ask a related question, but don't want it to be part of your conversation in the long run. You can't ask that related question in a fresh chat because Gemini will lose the active conversation context of what you're trying to research. If Google allowed you to delete individual question/answer pairs, you could simply ask about a sub-topic and remove it from the conversation to create a smooth flow of important stuff. Offline mode Image via DepositPhotos.com A big pain of using Gemini daily is that everything loads from the cloud. It takes time for your chats to appear, and you can't view your conversation history while offline. To get a better idea, you can open the Gemini app and see how it looks without an internet connection. While Gemini models run in the cloud, it wouldn't hurt if Google could store chats (at least the text part) on the device so we can refer to them when offline. Google can also offer a lightweight version of its AI model to help with basic drafting, summarization, and other tasks. It has the Gemini Nano model, which can perform on-device processing on Google Pixel, Samsung, and some other Android brands, but it's a system feature and not related to the cloud-based Gemini app. Make temporary chats permanent I can't thank Google enough for taking the time and effort to add incognito mode or temporary chat mode to the Gemini app. It lets you have conversations without worrying that the topics will end up in your chat history or used for model training (at least on paper). Google claims that it doesn't use your temporary chats to "personalize your Gemini experience or train Google’s AI models." However, the data is stored "up to 72 hours to respond to you and to process any feedback you choose to provide." That said, I often start researching something in a temporary chat, only to realize the chatbot's answer is good enough to refer to later. Sadly, Gemini doesn't have an option to make such temporary chats permanent. In other words, I won't be able to follow up on it if I close the temporary chat. I'm left with alternatives like copying the answers into notes or another app. My digital life will get a lot better if Gemini gets a button to make temporary chats permanent. Collapse answers for a cleaner view You're heavily invested in your research game and suddenly feel the need to go up in the chat to recall something. This is when the conversation thread starts to feel like an overwhelming, unending wall of questions and answers. What if Google added a way to collapse Q&A pairs in the Gemini chat thread? It would look quite clean and easy to navigate. You'll quickly get an overview of everything you have discussed with the chatbot. Add buttons to jump between messages Suggested mockup of the feature. This reminds me of a small but useful Gemini feature that Google could add to its chatbot: the ability to hop between prompts in a conversation. Just add simple up- and down-arrow buttons, similar to YouTube Shorts, so people can quickly scroll through the messages. A table of contents or Chat Overview It's hard to get a bird's-eye view of everything you have discussed with the chatbot during a lengthy conversation. This is where a table of contents, or Chat Overview, displayed at the top of the screen, possibly in a drop-down button, might come in handy. You'll be able to get an overview of the chat and jump between messages, serving as an alternative to the up/down arrow buttons. Temporary mode for Gemini Live Image: Google You can use Gemini Live to have real-time conversations with the chatbot, which feels like you're talking to someone in the same room. However, a downside is that Gemini Live doesn't work in Temporary Chat mode, so all your conversations end up in the chat history. Google should consider expanding the temporary chat mode to include Gemini Live. Default to a specific chat One thing that feels somewhat annoying to me is that Gemini always opens in a new chat, whether on web or mobile. Sometimes, you want to return to your last chat. Google can take cues from web browsers, which let you choose whether you want to go to a new tab or a specific web page(s). Gemini can also have options to default to a specific chat when reopened. That said, generative AI chatbots have endless possibilities given the vagueness of their work. You can mold them the way you want by attaching different connectors, adding custom instructions, and including source files. It remains to be seen what Google has in store for future updates and whether anything from this wishlist gets the green light. The search giant released a stream of new Gemini updates in recent months, including Gemini 3.5 Flash and Gemini Omni Spark, adding that it now has 13 products with more than a billion users each. What do you want to see in the Gemini app? Tell us in the comments.
    • Thank you for the post. Just a FYI that links to an outside site or promoting specific software is considered spamming here. Asking general questions is fine.
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      507
    2. 2
      +Edouard
      181
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!