• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle



  • Alphabetically by bands:

    The Agonist:

    • Prisoners
    • Orphans

    Alestorm:

    • Seventh Rum of the Seventh Rum
    • Sunset On The Golden Age
    • No Grave But The Sea

    Arch Enemy:

    • Deceivers
    • War Eternal
    • Rise of the Tyrant

    As I Lay Dying:

    • Shaped By Fire

    Avatar:

    • Dance Devil Dance
    • Hunter Gatherer
    • Hail the Apocalypse

    Godsmack:

    • The Oracle
    • Faceless

    Parasite Inc:

    • Dead And Alive
    • Cyan Night Dreams

    System Of A Down:

    • Steal This Album!
    • Mezmerize





  • Fellow .NET dev here, switched to Linux for side-gigs recently.

    In general, the experience is a lot better than Windows / WSL. Some general remarks on the setup (relevant mostly for Debian-based distros, so YMMV):

    • Rider / VSCode suggestion is spot on; go with the former if you have cash to spare and you’re fine with snaps, otherwise - DevKit can do DevKit things (with the only problem here being lack of .dcproj support in VSCode; can be ignored with proper integration test setup).
    • Containerization of DBMS: by all means, go for it if you have the resources to spare.
    • Possible gotchas:
      • If you’re going to use MS apt feed for .NET runtime / SDK, set up apt preferences to point to their feed for dotnet packages. Otherwise, you’re in for a bad time when running updates.
      • Docker: personally, I recommend Rancher Desktop for this purpose, as Docker Desktop on Windows left a bad taste in my mouth. If you’re fine with the latter, it’s up to your own preferences then.
      • Test containers: if you do use it with anything else than standard, bare-bones Docker setup, you’ll need a custom config; stumbled upon that the first time I tried running integration tests.