home.social

#devdrive — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #devdrive, aggregated by home.social.

fetched live
  1. I'm not yet convinced that #Windows11 #DevDrive helps. I built #Ruby on Windows on a DevDrive, on the system drive, and also on a new regular partition on the same disk - results are all quite similar with DevDrive being slightly slower than the others. I was hoping for better 😥

    Only a different disk was slower (but maybe that SSD is slower)

    #Programming

  2. I'm not yet convinced that #Windows11 #DevDrive helps. I built #Ruby on Windows on a DevDrive, on the system drive, and also on a new regular partition on the same disk - results are all quite similar with DevDrive being slightly slower than the others. I was hoping for better 😥

    Only a different disk was slower (but maybe that SSD is slower)

    #Programming

  3. I'm not yet convinced that #Windows11 #DevDrive helps. I built #Ruby on Windows on a DevDrive, on the system drive, and also on a new regular partition on the same disk - results are all quite similar with DevDrive being slightly slower than the others. I was hoping for better 😥

    Only a different disk was slower (but maybe that SSD is slower)

    #Programming

  4. I'm not yet convinced that #Windows11 #DevDrive helps. I built #Ruby on Windows on a DevDrive, on the system drive, and also on a new regular partition on the same disk - results are all quite similar with DevDrive being slightly slower than the others. I was hoping for better 😥

    Only a different disk was slower (but maybe that SSD is slower)

    #Programming

  5. I'm seeing an observable behavior difference in File.Replace() between Win10 NTFS and Win11 ReFS (DevDrive):

    github.com/KirillOsenkov/Misc/

    On regular C: drive I get two renames, on DevDrive I get a delete of the original + rename. Weird.

    #dotnet #devdrive #refs #ntfs

  6. I'm seeing an observable behavior difference in File.Replace() between Win10 NTFS and Win11 ReFS (DevDrive):

    github.com/KirillOsenkov/Misc/

    On regular C: drive I get two renames, on DevDrive I get a delete of the original + rename. Weird.

    #dotnet #devdrive #refs #ntfs

  7. I'm seeing an observable behavior difference in File.Replace() between Win10 NTFS and Win11 ReFS (DevDrive):

    github.com/KirillOsenkov/Misc/

    On regular C: drive I get two renames, on DevDrive I get a delete of the original + rename. Weird.

    #dotnet #devdrive #refs #ntfs

  8. I'm seeing an observable behavior difference in File.Replace() between Win10 NTFS and Win11 ReFS (DevDrive):

    github.com/KirillOsenkov/Misc/

    On regular C: drive I get two renames, on DevDrive I get a delete of the original + rename. Weird.

    #dotnet #devdrive #refs #ntfs

  9. I'm seeing an observable behavior difference in File.Replace() between Win10 NTFS and Win11 ReFS (DevDrive):

    github.com/KirillOsenkov/Misc/

    On regular C: drive I get two renames, on DevDrive I get a delete of the original + rename. Weird.

    #dotnet #devdrive #refs #ntfs

  10. @bradwilson Have you tried creating a physical partition for #devdrive or just a virtual disk? I’ve only tried a virtual drive, and am curious if a partition would help.

  11. @bradwilson Have you tried creating a physical partition for or just a virtual disk? I’ve only tried a virtual drive, and am curious if a partition would help.

  12. @bradwilson Have you tried creating a physical partition for #devdrive or just a virtual disk? I’ve only tried a virtual drive, and am curious if a partition would help.

  13. @bradwilson Have you tried creating a physical partition for #devdrive or just a virtual disk? I’ve only tried a virtual drive, and am curious if a partition would help.

  14. @bradwilson Have you tried creating a physical partition for #devdrive or just a virtual disk? I’ve only tried a virtual drive, and am curious if a partition would help.

  15. I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.

    A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.

    So, back to raw SSD and (sigh) NTFS for now. #DevDrive #dotnet

  16. I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.

    A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.

    So, back to raw SSD and (sigh) NTFS for now. #DevDrive #dotnet

  17. I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.

    A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.

    So, back to raw SSD and (sigh) NTFS for now. #DevDrive #dotnet

  18. I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.

    A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.

    So, back to raw SSD and (sigh) NTFS for now. #DevDrive #dotnet

  19. I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.

    A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.

    So, back to raw SSD and (sigh) NTFS for now. #DevDrive #dotnet

  20. Found my first issue with using a Dev Drive, and wanting to have access to it from WSL: apparently the way Dev Drives mount in Windows is not compatible with the WSL auto-mounting.

    Why does this matter? Docker Desktop (in WSL 2 mode) can't mount a Dev Drive folder.

    Do I dump WSL 2 mode for Docker? Or do I dump Dev Drive? Tough choice, but I suspect I dump the Dev Drive.

    #DevDrive #Windows #WSL #Docker

  21. Found my first issue with using a Dev Drive, and wanting to have access to it from WSL: apparently the way Dev Drives mount in Windows is not compatible with the WSL auto-mounting.

    Why does this matter? Docker Desktop (in WSL 2 mode) can't mount a Dev Drive folder.

    Do I dump WSL 2 mode for Docker? Or do I dump Dev Drive? Tough choice, but I suspect I dump the Dev Drive.

    #DevDrive #Windows #WSL #Docker

  22. Found my first issue with using a Dev Drive, and wanting to have access to it from WSL: apparently the way Dev Drives mount in Windows is not compatible with the WSL auto-mounting.

    Why does this matter? Docker Desktop (in WSL 2 mode) can't mount a Dev Drive folder.

    Do I dump WSL 2 mode for Docker? Or do I dump Dev Drive? Tough choice, but I suspect I dump the Dev Drive.

    #DevDrive #Windows #WSL #Docker

  23. Found my first issue with using a Dev Drive, and wanting to have access to it from WSL: apparently the way Dev Drives mount in Windows is not compatible with the WSL auto-mounting.

    Why does this matter? Docker Desktop (in WSL 2 mode) can't mount a Dev Drive folder.

    Do I dump WSL 2 mode for Docker? Or do I dump Dev Drive? Tough choice, but I suspect I dump the Dev Drive.

    #DevDrive #Windows #WSL #Docker

  24. Found my first issue with using a Dev Drive, and wanting to have access to it from WSL: apparently the way Dev Drives mount in Windows is not compatible with the WSL auto-mounting.

    Why does this matter? Docker Desktop (in WSL 2 mode) can't mount a Dev Drive folder.

    Do I dump WSL 2 mode for Docker? Or do I dump Dev Drive? Tough choice, but I suspect I dump the Dev Drive.

    #DevDrive #Windows #WSL #Docker

  25. The absolute best thing I can say about #DevDrive is that I enabled it about 6 weeks ago and promptly "forgot" about it. It's just worked, no hiccups.

    It contains my source and my NuGet package cache, mounted under C:\Dev. I've been running it as a half-terabyte raw ReFS partition on a SATA SSD. It's way over-provisioned but I had the space to spare, so why not?

  26. The absolute best thing I can say about #DevDrive is that I enabled it about 6 weeks ago and promptly "forgot" about it. It's just worked, no hiccups.

    It contains my source and my NuGet package cache, mounted under C:\Dev. I've been running it as a half-terabyte raw ReFS partition on a SATA SSD. It's way over-provisioned but I had the space to spare, so why not?

  27. The absolute best thing I can say about #DevDrive is that I enabled it about 6 weeks ago and promptly "forgot" about it. It's just worked, no hiccups.

    It contains my source and my NuGet package cache, mounted under C:\Dev. I've been running it as a half-terabyte raw ReFS partition on a SATA SSD. It's way over-provisioned but I had the space to spare, so why not?

  28. The absolute best thing I can say about #DevDrive is that I enabled it about 6 weeks ago and promptly "forgot" about it. It's just worked, no hiccups.

    It contains my source and my NuGet package cache, mounted under C:\Dev. I've been running it as a half-terabyte raw ReFS partition on a SATA SSD. It's way over-provisioned but I had the space to spare, so why not?

  29. The absolute best thing I can say about #DevDrive is that I enabled it about 6 weeks ago and promptly "forgot" about it. It's just worked, no hiccups.

    It contains my source and my NuGet package cache, mounted under C:\Dev. I've been running it as a half-terabyte raw ReFS partition on a SATA SSD. It's way over-provisioned but I had the space to spare, so why not?

  30. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, @JetBrainsRider, and more

    bit.ly/3GcOPhU

  31. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, @JetBrainsRider, and more

    bit.ly/3GcOPhU

  32. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, @JetBrainsRider, and more

    bit.ly/3GcOPhU

  33. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, @JetBrainsRider, and more

    bit.ly/3GcOPhU

  34. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, @JetBrainsRider, and more

    bit.ly/3GcOPhU

  35. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, #JetBrainsRider, and more

    bit.ly/3GcOPhU

  36. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, #JetBrainsRider, and more

    bit.ly/3GcOPhU

  37. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, #JetBrainsRider, and more

    bit.ly/3GcOPhU

  38. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, #JetBrainsRider, and more

    bit.ly/3GcOPhU

  39. Blogged: Test-Driving #Windows 11 Dev Drive for .NET

    🔍 What is #DevDrive and ReFS?
    🧪 Trying it out for various scenarios
    ➡️ #dotnet, #jvm, #JetBrainsRider, and more

    bit.ly/3GcOPhU

  40. Windows 11: Dev Drive Within Storage Spaces

    Let me give you a quick walkthrough to make use of Dev Drive within Storage Spaces on Windows 11. Because Microsoft's own docs fail at it.

    flameeyes.blog/2023/11/12/wind

    #Windows #DevDrive #Windows11

  41. Windows 11: Dev Drive Within Storage Spaces

    Let me give you a quick walkthrough to make use of Dev Drive within Storage Spaces on Windows 11. Because Microsoft's own docs fail at it.

    flameeyes.blog/2023/11/12/wind

    #Windows #DevDrive #Windows11

  42. Windows 11: Dev Drive Within Storage Spaces

    Let me give you a quick walkthrough to make use of Dev Drive within Storage Spaces on Windows 11. Because Microsoft's own docs fail at it.

    flameeyes.blog/2023/11/12/wind

    #Windows #DevDrive #Windows11

  43. Windows 11: Dev Drive Within Storage Spaces

    Let me give you a quick walkthrough to make use of Dev Drive within Storage Spaces on Windows 11. Because Microsoft's own docs fail at it.

    flameeyes.blog/2023/11/12/wind

    #Windows #DevDrive #Windows11

  44. Windows 11: Dev Drive Within Storage Spaces

    Let me give you a quick walkthrough to make use of Dev Drive within Storage Spaces on Windows 11. Because Microsoft's own docs fail at it.

    flameeyes.blog/2023/11/12/wind

    #Windows #DevDrive #Windows11

  45. Guess which drive letter came to mind first for my new #DevDrive