[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

    • (macOS) Screen zoom was broken for me in beta 1 and it's now working properly in beta 2. In terms of performance and UI design/consistency, these betas are already much better than Tahoe.
    • Less powerful than a PS5 at twice the price! I wonder if they use that for marketing? Totally DoA.
    • Astra 0.6.1 Beta by Razvan Serea Astra is an audiophile music player designed for local music libraries, supporting MP3, FLAC, WAV, AAC, OGG, M4A, OPUS, WMA, AIFF, and more via FFmpeg. It offers gapless playback with pre-buffering, multichannel audio remapping, and Dolby Atmos decoding, ensuring albums play seamlessly while maintaining high-fidelity sound. Astra features real-time DSP visualizers powered by a native C++ engine, including an oscilloscope, spectrum analyzer, and vectorscope. A fully parametric 10-band EQ with live frequency response, built-in presets, and AutoEQ headphone calibration import lets you precisely shape your sound. Playback controls include shuffle, repeat, and drag-and-drop queue management, while the library automatically extracts metadata, album artwork, and supports global search, favorites, and recently played tracking. Additional features include output device selection, delay calibration, customizable themes, fullscreen and mini-player modes, Discord Rich Presence, optional Last.fm scrobbling, and an opt-in local API for integrations. Astra delivers a complete, high-quality desktop audio experience with no telemetry, accounts, or streaming. Astra 0.6.1 Beta changelog: Lyrics Initial XLRC support via @boof2015/xlrc 0.2.0 (#131) XLRC sidecar scanning, manual import, and renderer support Word timing, furigana, translations, voice labels, and translation-priority controls for XLRC Fullscreen lyrics overhaul with additional layout polish Manual lyrics editor with LRC, XLRC, and plain-text modes Drag-and-drop lyrics import plus sync offset controls Clickable synced lyrics for seeking, with popout and transport lyrics updates (#138) Fixed lyrics info sidebar scrolling (#138) Added a workaround for LRCLIB instability Metadata & Library Metadata editor rebuilt as a side panel Virtual DB metadata overrides and optional direct file tag writing Bulk metadata editing for title, artist, album, album artist, genre, year, track/disc numbers, and artwork Undo/redo support for virtual metadata edits Clear overrides action and default save-mode preference Artist page grid view added, with later design and sizing refinements Improved Jump to Playing with smart source, queue, album, artist, and library track targets Fixed smart source jump behavior Playlists Fixed VLC-style M3U import failures (#127) Added playlist export to M3U/M3U8 (#118) Improved imported playlist path resolution and missing-entry preservation Shuffle added to playlist pages (#121) Remove tracks directly from playlist views (#128) Fixed create-playlist-from-track modal closing when clicking inside it (#137) Multi-select quality-of-life fixes Right-click context menus no longer clear multiselections UI & Navigation Fixed UI scaling regressions in sidebar and home surfaces (#122, #123) Fixed transport bar regression (#126) Fixed horizontal scrolling on Home and Library rails Fixed artist grid sizing while searching Updated playlist action buttons and related layout polish Additional fullscreen lyrics visual adjustments Visualization Scopes and visualizers now respect UI scaling settings (#155) Added shared canvas sizing logic for correct DPR/backing-store behavior Canvas sizing tests added for visualizer scaling regressions Discord RPC Discord Rich Presence activity structure refactored Compact status can prioritize title or artist Profile info line can show file info or album Title and artist links can target YouTube Music, Last.fm, or be disabled Optional small Astra badge for cover-art presence Configurable “clear when paused” timing Added Discord activity tests Scrobbling Fixed custom Last.fm2 API profiles being accidentally blocked Expanded scrobbler profile protocol handling coverage Stability & Tests Added/expanded tests for XLRC parsing, lyrics presentation, metadata editor state, playlist import/export path handling, artist grid layout, horizontal scrolling, canvas sizing, and Discord RPC activity building Download: Astra 0.6.1 Beta | 138.0 MB (Open Source) View: Astra Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How does it compare to the "SeeStar S30 Pro" and the "Vespera PRO 2"?
  • Recent Achievements

    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
    • Dedicated
      tuben earned a badge
      Dedicated
    • Week One Done
      mnsgroup earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      +Edouard
      209
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Michael Scrip
      85
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!