Formula 1 World Championship 2015 Season Discussion


  

57 members have voted

  1. 1. Who do you think will win the 2015 Driver's Championship?

    • Lewis Hamilton
      44
    • Nico Rosberg
      6
    • Daniel Ricciardo
      0
    • Daniil Kvyat
      0
    • Felipe Massa
      1
    • Valtteri Bottas
      0
    • Sebastian Vettel
      3
    • Kimi Raikkonen
      0
    • Fernando Alonso
      1
    • Jenson Button
      0
    • Sergio Perez
      0
    • Nico Hulkenberg
      0
    • Max Verstappen
      0
    • Carlos Sainz Jr
      1
    • Romain Grosjean
      0
    • Pastor Maldonado
      0
    • Will Stevens
      1
    • Roberto Merhi
      0
    • Marcus Ericsson
      0
    • Felipe Nasr
      0
  2. 2. Who do you think will win the 2015 Constructor's Championship?

    • Mercedes AMG Petronas F1 Team
      48
    • Infiniti Red Bull Racing
      1
    • Williams Martini Racing
      2
    • Scuderia Ferrari
      3
    • McLaren Honda
      1
    • Sahara Force India F1 Team
      0
    • Scuderia Toro Rosso
      0
    • Lotus F1 Team
      0
    • Manor Marussia F1 Team
      1
    • Sauber F1 Team
      1


Recommended Posts

That whole penalties-after-last place thing is a lot of confusing nonsense. Any drop in places that overflows past the end of the grid should result in points being taken off in the constructors championship. Why can't they do that?

Because that makes no sense whatsoever. Try doing something that only affects the race, not the amount of money each team receives at the end of the year.

Because that makes no sense whatsoever. Try doing something that only affects the race, not the amount of money each team receives at the end of the year.

 

Like what? In the current "Mercedes + Ferrari vs everyone" else, just sending teams to the back is pointless and makes things more confusing for viewers. It's teams who do the engineering, not the drivers, so they need to bear the responsibility. Using drivers as proxies to punish the teams is not fair. Besides, if a team takes a new engine or another important new component, it doesn't just affect that race, it also affects the next race and maybe even the subsequent ones. So punishment only in the context of one race does not fit the scale of the crime.

The penalty I reckon that needs to be changed is the unsafe release one; unfair to punish the driver for their pit crew's mistake.

 

Driver and team win and lose together, that's the nature of the sport. You only need to witness a botched pitstop where a wheel isn't screwed on properly to see that.

What would you do, issue fines?

 It's only been a problem this year because the limits on power units are so tight. Don't change the penalties - sending people to the back of the grid is a big disadvantage, even if we have seen a few people come all the way through the field, because most don't. Arbitrarily knocking points off doesn't just affect subsequent races, it affects the whole season. So what I would do is relax the limits on engines. The cost of a couple of extra power units is a drop in the ocean in F1, and if they're going to be used anyway, it's not saving anything at all. Teams will still aim for reliability because an engine letting go during a race is enough of a punishment as it is.

 

And what if teams who can afford to put on the new components because they want to as opposed to because they have to? Especially in last few races of the season, say they are neck and neck with another team in constructors', it could give them an unintended advantage. Clearly, this year, some teams did not get reliability as much as they wanted, so it's a lesson learnt for next season. My main gripe is with how messy the penalties situation gets once drivers cannot serve all the places they have been relegated.

And what if teams who can afford to put on the new components because they want to as opposed to because they have to? Especially in last few races of the season, say they are neck and neck with another team in constructors', it could give them an unintended advantage. Clearly, this year, some teams did not get reliability as much as they wanted, so it's a lesson learnt for next season. My main gripe is with how messy the penalties situation gets once drivers cannot serve all the places they have been relegated.

Then it's no different to previous years, there's just a few more bits involved.

If a team couldn't afford to use their full allocation of power units then I'm not sure they'd be allowed to enter the championship in the first place?

If a team couldn't afford to use their full allocation of power units then I'm not sure they'd be allowed to enter the championship in the first place?

 

But who defines what constitutes full allocation? What if the smaller teams say that they cannot afford extra components beyond a certain quantity. Some of existing restrictions are also targeted at attempting to controlling costs.

This topic is now closed to further replies.
  • Posts

    • Never had a problem with TPM and started using that many years ago in Win10. Through several motherboards and OS versions, it just does what it does without complaint. My games library doesn't even know it's there. Secure boot does a lot more than support anti-cheat, as it came along long before anti-cheat software. I've used it religiously since before I started using TPM, and I always liked it for being able to nullify virus contagions that try their best to come in underneath the firmware during boot, so that the OS doesn't see them, etc. That is its purpose, imo. I'll never understand why people who elect to use another OS feel compelled to run down Windows... I guess they need to do that to feel secure about their choices? I run Windows because it supports all the software (including games) natively that I want to buy, and I've never had to run down another OS to make me feel better about it. (Although it's certainly possible to do that, of course...) Win10 is on a ventilator atm, and Win11 is very close to being free, and I finally got to stop running StartAllBack as I moved to the Experimental/Dev channel and my 26300.8553 build supports the moveable taskbar and it's running fine at the top of the screen! Finally, my last major dislike of Win11 is being rectified! So, I'm not at all surprised to see Win11's share of the Steam survey hitting 70%.
    • I can answer about the Linux bit. I only used AMD GPUs. I currently have a 9060XT (8GB) that fits my needs, I'm not a gamer, so I don't need that much GDDR. But lately, NVIDIA has grown a lot in the recent years. Oh, the horrors of NVIDIA drivers not working. But they have been getting better. I know a lot of members onm here that are running cachyOS and other distros, and are fine with a 4090/5090 variants. Really, though, I would stick with AMD variants.
    • Everything they say you can already do yourself on the registry by changing some things.
    • Artist's renderings are so much nicer to view than the real thing, don't you think?
    • WildBit Viewer 6.20 released; no further updates planned by Razvan Serea WildBit Viewer is a popular, fast, and extensive image viewer offering a comprehensive suite of tools for photographers, designers, and image enthusiasts. It includes a powerful Viewer, Slide Show, Editor, Search, Profile Switcher, and Multi-Screen Viewer. The Viewer provides blazing-fast folder, file list, and thumbnail navigation with customizable headers, full-screen view, and a shell toolbar to organize favorite folders. It supports all major graphic formats (over 70), including JPEG, TIFF, PNG, BMP, GIF, PCX, TGA, and RAW formats. Detailed Image Info shows EXIF, IPTC, and XMP metadata, with rotation based on EXIF orientation, wallpaper setting, image comparison, geo-tag viewing, color labels, and CMS-aware color management. The Slide Show module offers 176 transition effects, multi-monitor support, custom shows with per-image settings, image marking, zoom, rotate, and desktop hiding for a professional viewing experience. The Editor supports advanced image manipulation, including crop, resize, color adjustments, curves, edge detection, effects, batch processing, retouching, layer support, and printing. Users can apply mass renaming, update or clear metadata, and work with multi-page TIFFs and animated GIFs. Search allows filtering by name, location, date, size, attributes, and metadata, while the Profile Switcher saves and loads custom layouts for all modules. The Multi-Screen Viewer opens multiple windows on available monitors, allowing simultaneous image viewing with independent zoom, pan, and rotation. WildBit Viewer also supports portable operation, 32- and 64-bit versions, Unicode, high-DPI displays, and multiple Windows styling options. With its combination of speed, versatility, and rich feature set, WildBit Viewer is an indispensable tool for managing, editing, and showcasing images efficiently. WildBit Viewer key features: Blazing-fast folder, file list, and thumbnail browsing Supports 70+ image formats including JPEG, TIFF, PNG, BMP, GIF, and RAW Full-screen view with multi-monitor support Explorer-style file handling with customizable headers Thumbnail Browser with sorting, view change, and fast size adjustment EXIF, IPTC, and XMP metadata viewing and editing Automatic rotation based on EXIF orientation Shell toolbar for organizing favorite folders Image Compare to calculate similarity between images Mass renaming and batch metadata updates File List Generator (HTML, CSV, RTF, TXT, Unicode) Rating and color labels, CMS-aware color management Video playback (AVI, MPG, MPEG, WMV) Animated GIF, multipage TIFF, Camera RAW support Slide Show with 176 transition effects and custom settings Editor: crop, resize, rotate, flip, canvas resize, and retouching tools Batch processing and image format conversion Multi-Screen Viewer: multiple windows with independent zoom, pan, and rotate Profile Switcher: save, load, reset, delete module profiles Portable operation, 32-/64-bit support, Unicode, and high-DPI ready WildBit Viewer 6.20 changelog: Viewer, Slide Show, Editor, Search, Profile Switcher & Multi Screen Viewer. Updated ImageEn to 15.0.0 version. Viewer, Slide Show, Editor, Search, Profile Switcher & Multi Screen Viewer. Updated Jedi JCL&JVCL. Viewer - Image Geo Info, OpenStreetMap removed. Slide Show Remote Mode removed. Note! This means that WildBit Slide Show Remote is now officially EOL. Editor - Shortcut keys for Capture removed. Optimized code. Note! This version includes help what supersedes all previous releases. plus Lots of bug fixes and changes, check Readme files for details. WildBit Viewer End‑of‑Life WildBit Viewer has reached its final release with version 6.20. As development comes to a close, no further feature updates are planned. WildBit Slide Show Remote reached End-of-Life on 06 June 2026, while WildBit Viewer will reach End-of-Life on 30 June 2026. Downloads will remain available until the end of July 2026 (possibly extending into early August). After End-of-Life, the software will no longer receive updates, security fixes, or technical support. Download: WildBit Viewer 64-bit | Portable 64-bit | ~70.0 MB (Freeware) Download: WildBit Viewer 32-bit | Portable 32-bit Links: WildBit Viewer Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      252
    3. 3
      Steven P.
      71
    4. 4
      +Edouard
      69
    5. 5
      FloatingFatMan
      68
  • Tell a friend

    Love Neowin? Tell a friend!