69 members have voted

  1. 1. Which team will win the Constructor's Championship?

    • Infiniti Red Bull Racing
      39
    • Scuderia Ferrari
      13
    • Vodafone McLaren Mercedes
      4
    • Lotus F1 Team
      6
    • Mercedes AMG Petronas F1 Team
      5
    • Sauber F1 Team
      0
    • Sahara Force India F1 Team
      1
    • Williams F1 Team
      0
    • Scuderia Toro Rosso
      0
    • Caterham F1 Team
      0
    • Marrusia F1 Team
      1
  2. 2. Which driver will win the World Driver's Championship

    • Sebastian Vettel
      29
    • Mark Webber
      0
    • Fernando Alonso
      19
    • Felipe Massa
      0
    • Jenson Button
      4
    • Sergio Perez
      0
    • Kimi Raikkonen
      5
    • Romain Grosjean
      1
    • Nico Rosberg
      1
    • Lewis Hamilton
      9
    • Nico Hulkenberg
      0
    • Esteban Gutierrez
      0
    • Adrian Sutil
      0
    • Paul Di Resta
      1
    • Pastor Maldonado
      0
    • Valtteri Bottas
      0
    • Jean-Eric Vergne
      0
    • Daniel Ricciardo
      0
    • Charles Pic
      0
    • Giedo Van Der Garde
      0
    • Jules Bianchi
      0
    • Max Chilton
      0


Recommended Posts

The poll will be added once all teams are confirmed.

Technical and rule changes

  • DRS is only allowed during practice and qualifying within the same designated zones as in the race session
  • Cars must have enough fuel to make it back to the pits and provide the 1L sample required. If stopped on track there must also be enough fuel in the car for the required distance to the pits as well as the 1L sample.
  • The number of permitted breaks of curfew is reduced from 4 to 2 occurrences.
  • Double DRS is now banned
  • Minimum weight of cars increases to 642kg

Driver and team changes

  • HRT are no longer present on the team roster, after failing to find a buyer, and get enough money to make the entry fee for 2013 in time.

Red Bull Racing
Red Bull Racing RB9 ? Renault RS27-2013
Team Principal: Christian Horner; Technical Director: Adrian Newey
1. Sebastian Vettel (on a long-term deal through '14, perhaps with options)
2. Mark Webber (another one-year deal)

Scuderia Ferrari
Ferrari F138 ? Ferrari 056
Team Principal: Stefano Domenicali ; Technical Director: Pat Fry
3. Fernando Alonso (contracted through '16)
4. Felipe Massa (another one-year deal)

Vodafone McLaren Mercedes
McLaren MP4-28 ? Mercedes FO108Z
Team Principal: Martin Whitmarsh ; Technical Director: Paddy Lowe, Neil Oatley
5. Jenson Button (contracted through '13 with option for '14)
6. Sergio Perez

Lotus F1 Team
Lotus E21 ? Renault RS27-2013
Team Principal: Eric Boullier ; Technical Director: James Allison
7. Kimi R?ikk?nen (contracted through '13)
8. Romain Grosjean

Mercedes AMG Petronas Formula One Team
Mercedes F1 W04 ? Mercedes FO108Z
Team Principal: Ross Brawn ; Technical Director: Bob Bell
9. Lewis Hamilton
10. Nico Rosberg (on a multi-year deal beyond '13)

Sauber F1 Team
Sauber C32 ? Ferrari 056
Team Principal: Peter Sauber ; Technical Director: James Key
11. Nico H?lkenberg
12. Esteban Gutierrez

Sahara Force India F1 Team
Force India VJM06 ? Mercedes FO108Z
Team Principal: Vijay Mallya ; Technical Director: Andrew Green
14. Adrian Sutil
15. Paul Di Resta

Williams
Williams FW35 ? Renault RS27-2013
Team Principal: Adam Parr ; Technical Director: Mike Coughlan
16. Pastor Maldonado (on a long-term deal through '14, perhaps with options)
17. Valtteri Bottas

Scuderia Toro Rosso
Toro Rosso STR8 ? Ferrari 056
Team Principal: Franz Tost ; Technical Director: Giorgio Ascanelli
18. Jean-?ric Vergne (current driver; likely to stay on)
19. Daniel Ricciardo (current driver; likely to stay on)

Caterham F1 Team
Caterham CT03 ? Renault RS27-2013
Team Principal: Tony Fernandes ; Technical Director: Mike Gascoyne
20. Charles Pic
21. Giedo van der Garde

Marussia F1 Team
Marussia MR02 ? Cosworth CA2013
Team Principal: John Booth ; Technical Director: Pat Symonds
22. Jules Bianchi
23. Max Chilton

2013 Race Calendar:

  • 17.03.2013 - Australian GP, Melbourne - Winner: Kimi R?ikk?nen
  • 24.03.2013 - Malaysian GP, Sepang - Winner: Sebastian Vettel
  • 14.04.2013 - Chinese GP, Shanghai - Winner: Fernando Alonso
  • 21.04.2013 - Bahrain GP, Sakhir - Winner: Sebastian Vettel
  • 12.05.2013 - Spanish GP, Barcelona - Winner: Fernando Alonso
  • 26.05.2013 - Monaco GP, Monte Carlo - Winner: Nico Rosberg
  • 09.06.2013 - Canadian GP, Montreal - Winner: Sebastian Vettel
  • 30.06.2013 - British GP, Silverstone - Winner: Nico Rosberg
  • 07.07.2013 - German GP, Nurburgring - Winner: Sebastian Vettel
  • 28.07.2013 - Hungarian GP, Budapest - Winner: Lewis Hamilton
  • 25.08.2013 - Belgian GP, Spa - Winner: Sebastian Vettel
  • 08.09.2013 - Italian GP, Monza - Winner: Sebastian Vettel
  • 22.09.2013 - Singapore GP, Singapore - Winner: Sebastian Vettel
  • 06.10.2013 - Korean GP, Yeongam - Winner: Sebastian Vettel
  • 13.10.2013 - Japanese GP, Suzuka - Winner: Sebastian Vettel
  • 27.10.2013 - Indian GP, Greater Noida - Winner: Sebastian Vettel - Secured WDC
  • 03.11.2013 - Abu Dhabi GP, Abu Dhabi
  • 17.11.2013 - United States GP, Austin
  • 24.11.2013 - Brazilian GP, S?o Paulo

Thanks to Meph for the template

Link to comment
https://www.neowin.net/forum/topic/1128560-f1-world-championship-2013-thread/
Share on other sites

  • 2 weeks later...

The poll will be added once all teams are confirmed.

was just going to ask that :D

anyway: if ferrari manages to build a half-decent car from the very beginning (not such a s*itbox like last year) alonso has to be the clear favourite.

Timo Glock agrees to leave Marussia for 'commercial' reasons

German Timo Glock will not race for Marussia this year after he and the team "agreed to part company with immediate effect".

The German, 30, has raced for Marussia since their debut in 2010 as Virgin. Team boss John Booth said "commercial" considerations were behind the move.

Timo's time

"Tough economic conditions prevail and the commercial landscape is difficult for everyone," Booth added.

Glock earned a salary; Marussia need a driver who brings sponsorship.

Marussia did not say in their statement who would be replacing Glock. They have already confirmed the English novice Max Chilton in one of the seats.

Brazilians Bruno Senna, who raced for Williams last year, and novice Luis Razia have been linked to the team.

Source: BBC News

This is really turning me off F1, its not about who has the skill anymore its all about who can bring the most money to buy a seat, you get idiots like Pastor Maldonado who clearly wasn't ready for F1, though has been improving, smashing into everyone and being aggressive.

In the lower ranking teams anyway.......

Something needs to be done, like the constructors championship, normalise the payments a bit, you have to be top 10 to get any money at all, so the better teams get more money to spend on developing faster cars and the bottom ranked teams get jack ****. It should be the other way round.

Here's the testing/car launch calendar for you all.

28-Jan Lotus

31-Jan McLaren

01-Feb Ferrari

01-Feb Force India

02-Feb Sauber

03-Feb Red Bull

04-Feb Mercedes

04-Feb Toro Rosso

05-Feb Caterham

05-Feb Test 1: Jerez

19-Feb Williams

19-Feb Test 2: Barcelona

28-Feb Test 3: Jerez

15-Mar Australian Grand Prix

This is really turning me off F1, its not about who has the skill anymore its all about who can bring the most money to buy a seat, you get idiots like Pastor Maldonado who clearly wasn't ready for F1, though has been improving, smashing into everyone and being aggressive.

pay-drivers have always been a part of formula 1 especially in the lower-grid teams. have a look in the 90s, there have been much worse pay drivers.

maldonado has shown he can win races, thats at least something. also grosjean has shown he can contend for wins. if id had to throw out someone based on last year it has to be senna.

Formula 1 isn't meant to be some utopian sport where everyone gets equal cars, if you want stock car racing watch nascar or champ car. It's about the biggest and the best showcasing their engineering and driving talents. If you don't have the capital to compete that's your problem, not the problem of the FIA and of FOM. Rewarding failure just doesn't make sense.

  • Like 1

Here's the testing/car launch calendar for you all.

31-Jan McLaren

01-Feb Ferrari

01-Feb Force India

02-Feb Sauber

03-Feb Red Bull

04-Feb Mercedes

04-Feb Toro Rosso

05-Feb Caterham

05-Feb Test 1: Jerez

19-Feb Williams

19-Feb Test 2: Barcelona

28-Feb Test 3: Jerez

15-Mar Australian Grand Prix

Add the Lotus launch on January 28 to the list.

As for the team finances/pay driver situation: It reminds me of 1994/95. Only this time around there are no new teams waiting to enter F1. Or manufacturers who would want to buy an existing team. The FIA needs to act, and quickly - what good is a F1 grid with 16 drivers?

One more thing: How has the regulation regarding having enough fuel in the car changed? The FIA already send cars that don't have enough fuel to the back of the grid as Seb and Lewis found out to their cost during 2012.

One more thing: How has the regulation regarding having enough fuel in the car changed? The FIA already send cars that don't have enough fuel to the back of the grid as Seb and Lewis found out to their cost during 2012.

I think its changes by increasing the minimum amount of fuel so they have the minimum 1L plus another 1L for a sample. Any punishments will remain the same i think.

One more thing: How has the regulation regarding having enough fuel in the car changed? The FIA already send cars that don't have enough fuel to the back of the grid as Seb and Lewis found out to their cost during 2012.

they threw out the passus "higher force" out of the rules, so by now if you cant provide ennough fuel you are demoted back to the grid no matter what, you cant argue with "higher force" anymore.

however that also means that if you have indeed ennough fuel and had to stop the car for another technical reason, nothing will happen.

The FIA have also said that teams can cover the platypus nose/step to make them smoother and more appealing to the eye. That was following the controversy that 2012 cars were ugly and no longer good looking.

car looks ok, nothing too radical but it seems to be a good package. allison expects many teams to keep the stepped nose because the cover means only more weight added. however williams and mclaren have said that they will use the cover. if one team is not to use it, its probably red bull because they have some kind of air-intake in the step included.

i cant wait for mclaren and redbull to show their cars. their launches are usually the most exciting ones. :D

car looks ok, nothing too radical but it seems to be a good package. allison expects many teams to keep the stepped nose because the cover means only more weight added. however williams and mclaren have said that they will use the cover. if one team is not to use it, its probably red bull because they have some kind of air-intake in the step included.

i cant wait for mclaren and redbull to show their cars. their launches are usually the most exciting ones. :D

McLaren don't have the stepped nose to cover in the first place. Was the best looking car last season.

Can't wait for the this season...

If a car stops on track during qualifying how do they calculate the fuel need to finish the lap? Say x ml's per lap and multiply by the remainder of the track left or better still count a car on track as requiring a laps worth of fuel and the 1 litre required for testing?

Prefer the 2nd option so you don't see drivers coasting to save fuel and stopping on track. Wouldn't put it past some of the teams to try it on!

McLaren don't have the stepped nose to cover in the first place. Was the best looking car last season.

i was talking about the mp4/28 not the mp4/27

This topic is now closed to further replies.
  • Posts

    • WhatsApp is getting usernames, and you can reserve your preferred one now by Fiza Ali Sharing your phone number isn't always something you want to do, especially with people you've just met. Whether it's someone from a class, a local community group, or a sports team chat, handing over your number can feel like giving away more personal information than necessary. That's exactly the problem WhatsApp is trying to solve with its upcoming usernames feature. The company has announced that users can now reserve a unique WhatsApp username ahead of the feature's wider rollout later this year. Once usernames become available, they'll let people connect without revealing their phone numbers. It's a change that makes a lot of sense for group chats. Right now, everyone in the group can see your phone number. With usernames enabled, that won't necessarily be the case when someone contacts you for the first time. WhatsApp says it's opening username reservations early because more than three billion people use the app, meaning plenty of people are likely to want the same usernames. Reserving one now gives users a better chance of securing the name they actually want before the feature launches more broadly. If your preferred username is already taken, WhatsApp will also offer a built-in username generator to suggest available alternatives. The feature isn't only aimed at individual users. Creators, businesses, and organisations will be able to claim the same username they already use on Instagram or Facebook, making it easier to keep a consistent identity across Meta's apps. Furthermore, privacy is a big part of how WhatsApp is introducing usernames. There won't be a public directory where people can browse or search for usernames. Instead, people will need to know your exact username before they can start a conversation with you. Additionally, users can also choose to enable a username key, which adds another layer of control by requiring people to enter that key before sending a message. Once the feature rolls out, people who choose to use a username will no longer have their phone number shown when messaging a person or business for the first time. If you want to reserve a username, make sure you're running the latest version of WhatsApp, then head to Settings > Account > Username. The tech giant says usernames will roll out gradually over the coming months, and users will receive an in-app notification when the feature becomes available in their country.
    • When I think about a network, there are really two aspects, the hardware and the wiring. So here is what I would do for both. Wiring: Use Cat6A for the patch panel, outlets, and all structured cables (cables installed in walls). Run plenty of Wireless Access Point (WAP) cables, as a general rule, assume a signal can only pass through 2-3 walls and can't pass through a floor (that is conservative, but trust me on this if you want strong WiFi)  Cat6 patch cables are fine for now if you don't plan to run 10gig, those are easy to replace later if needed. Run OS2 single-mode fiber to anywhere you think you may have a server or sub-switch. (yes, single-mode for everything on a small network, don't mess with multimode unless you have entire racks of servers and that minor module cost and power savings will matter). If you really want to future proof, also run fiber to any high density WAP locations, it is likely that WiFi 8 WAPs will push the limits of 10g. Run 6-12 pairs of single-mode fiber between your MDF and the building's MDF, even if you only need 1 or 2 pairs now, those extra pairs will pay off down the road. Hardware: (its easy to say "get all the features incase you need them", so instead of futureproofing, I am going to take approach of suggesting areas worth investing in, and areas you can save money). Don't overspend thinking you need every feature on every port. You don't need 10g on every port, you don't need PoE on every port. Don't overspend on redundancy either, unless you are ready to buy two of everything, don't waste money buying two of some things and not others. Dual power supplies are worthwhile, but probably not HA or multi-path redundancy.  Get 1 "distribution layer" switch that your router/firewall will connect to as well as all your access layer switches below. This should be a 10g switch with a combination of copper and SPF ports and should be a fully managed switch. Given that you said it is a small network, I suggest also using that distribution layer switch for servers and WAPs, meaning it will need PoE. Speaking of wireless, get good professional tri-band WAPs, and either turn on the band stirring options, or limit 2.4 to an IoT only SSID. This will provide a solid WiFi capable nearly everything but the highest of bandwidth clients...you could even consider skipping wiring workstations depending on usage. Access layer switch for workstations and printers can be cheaper switches, 2.5g is a good sweet spot between price and future proofing, but even 1g is fine for most individual clients (the kind that could probably be fine on WiFi). You can consider saving a little on access layer switches by only getting 1 PoE switch for whatever needs it (remember your WAPs are connecting to the distribution switch, not here), and non-PoE for your workstations, because desk phones are falling out of favor. You can also save money here by not buying managed switches if you don't need them--but really do some soul searching there, if you go this route, then anything that isn't on your workstation VLAN would either need to be connected to the distribution switch, or its own access layer switch. Also, don't feel like you need a fancy fabric stacking switches for your access layer, that is the point of the higher-end distribution layer, to remove the need for things like that at this level. Home Hardware: I'm realizing the above assumed an office setting, if this if for your house and home lab then the above still applies, but you'll probably want everything managed and PoE, just because, but you probably also don't need multiple access layer switches. If your total port count is below 24, just skip separating distribution layer and access layer and just get one nice switch with the features you want. If you are at the point of considering a 48-port switch, I would instead get a nice high-end distribution switch for things that need it, and cheaper access layer switches with specs based on the needs of connected devices. For home use, don't worry about home running every device to the main switch, there is nothing wrong with running sub-switches for your media areas and office, those essentially become your access layer, just look for sub-switches with a 10g uplink so sharing bandwidth isn't an issue.
    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      534
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!