Recommended Posts

built on September 12, 2005, pretty old i'd say

586648837[/snapback]

I agree. Hardly desirable. Considering that August 30th was the build date for 5219. Not even 2 weeks later.

I like my builds more than a fortnight apart and recent :p

Edited by crimsonhead
I agree.  Hardly desirable.  Considering that August 30th was the build date for 5219.  Not even 2 weeks later.

I like my builds more than a fortnight apart and recent :p

586648851[/snapback]

Umm that's not quite how it works...

5219 was split from the main beta 2 tree weeks before the final 8/30 build that was given out at PDC. Meanwhile the beta 2 branch went forward on its own. The fixes made to 5219 are then reverse integrated into the main branch before the next IDW candidate is broken off from the main branch.

5231 has some significant changes since the PDC build. To think that it has "only 2 weeks" of difference is to misunderstand how software development works. Many of the new features that were merged into the main branch between 5219 and 5231 had been worked on in seperate private branches for a long time.

It does, however, look like some UI stuff has actually been removed from this build versus internal builds. Looks like they don't want even beta testers to see some stuff just yet.

Umm that's not quite how it works...

5219 was split from the main beta 2 tree weeks before the final 8/30 build that was given out at PDC.  Meanwhile the beta 2 branch went forward on its own.  The fixes made to 5219 are then reverse integrated into the main branch before the next IDW candidate is broken off from the main branch.

5231 has some significant changes since the PDC build.  To think that it has "only 2 weeks" of difference is to misunderstand how software development works.  Many of the new features that were merged into the main branch between 5219 and 5231 had been worked on in seperate private branches for a long time.

It does, however, look like some UI stuff has actually been removed from this build versus internal builds.  Looks like they don't want even beta testers to see some stuff just yet.

586649727[/snapback]

I meant that I like compiled builds with all the nuts and bolts about a month apart. I know everything is integrated seperately and worked on. I like it when major changes have occurred between builds. From the screenshots i've seen so far, besides WMP11 being added, I don't see much difference.

Agreed, I'm really looking forward to the audio stack.

WMP11 looks like it will be nice. Although it's clearly very early to final. The new IE7 thumbnail thing looks pretty sweet as well. Thinking I'm probably moving back to IE after moving to Firefox.

Think about if you had seen these screenshots 6 months ago. Probably would have blown your mind. Just thought about when people were talking dates. How is a build for an OS that is less then a month old considered old? ;) If September 12 is old, I don't want to think what 5.1 is. :)

Can't wait until Wednesday or Thursday for this build.

well somone earlier in the thread said nobody cares about the screen shots... so.. just change the word nobody to MOST PEOPLE... and thats the truth... once everyone knows it out and are able to get it.. they start carring... cause when there was just screen shots... i didnt have 118 people connected to me...

if anyone wanted more proof... (no names of web site or users on the page.. so.. ya..should be ok right?)

586650925[/snapback]

You erased the url and the title bar wording, but forgot to remove the taskbar entry...

If I didn't know the site already, I would be thanking you :p

Nick

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

    • No registered users viewing this page.
  • Posts

    • Hello, Were you using a product or service from one of the companies affected by the Klue data breach?  See https://klue.com/blog/an-update-on-recent-klue-security-incident for the company's public statement.  That blog post does not list affected customer. From looking around at reports, I created this list: Gong HackerOne Huntress Insurity Jamf LastPass OneTrust Recorded Future ReliaQuest Salesforce Snyk Sprout Social Tanium It is likely there are other companies affected as well. Regards, Aryeh Goretsky  
    • SpaceX reportedly plans a Starlink mobile service for U.S. consumers by Karthik Mudaliar SpaceX reportedly wants to sell mobile phone plans directly to consumers in the United States as part of a wider expansion of Starlink. According to a report from the Financial Times, SpaceX president Gwynne Shotwell discussed the plan with investors during the company’s recent IPO roadshow. The company is also said to be considering building a terrestrial mobile network to complement Starlink’s satellite coverage. The plan is quite different from how Starlink currently operates in the U.S. mobile market. SpaceX already provides satellite connectivity for T-Mobile’s T-Satellite service, but T-Mobile remains responsible for the subscription, billing, and customer support. A Starlink-branded mobile service would give SpaceX control of the customer relationship instead. It could also turn the company from a partner of traditional mobile operators into a direct competitor. T-Mobile also began testing its Starlink-powered satellite service in early 2025. The beta was initially limited to text messaging and was also available to some AT&T and Verizon customers. The service has since expanded to support limited data access through selected apps, including WhatsApp, Google Maps, AccuWeather, and AllTrails. It is designed to provide a connection in areas where normal cell towers are unavailable, rather than replace a conventional mobile network. However, if SpaceX actually has a plan to serve nationwide, it needs to do more than just satellite networks and actually support on-ground operations. It can also partner up with existing carriers and become a mobile virtual network operator (MVNO). With that said, SpaceX has already spent heavily to support its mobile ambitions. Just last year, the company agreed to acquire wireless spectrum licences from EchoStar in deals worth a combined $19.6 billion. EchoStar's spectrum includes AWS-4, H-Block, and AWS-3 frequencies that could be used for both satellite and terrestrial communications. According to a SpaceX securities filing, the Federal Communications Commission approved the transaction in May 2026, although it is not expected to close until late 2027. There's no official statement by SpaceX for now. Pricing, availability, and other details remain unknown. Source: Financial Times
    • We had no idea as kids how much time and energy it took to be an adult 😅
  • Recent Achievements

    • Week One Done
      xvvxcvv earned a badge
      Week One Done
    • One Month Later
      xvvxcvv earned a badge
      One Month Later
    • Enthusiast
      Xonos went up a rank
      Enthusiast
    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      400
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      127
    4. 4
      neufuse
      69
    5. 5
      Xenon
      66
  • Tell a friend

    Love Neowin? Tell a friend!