Skip Navigation

Mountaineer

@ Mountaineer @aussie.zone

Posts
9
Comments
11
Joined
3 yr. ago

  • Linux 7.1: Kicinski Called It ‘LLM-pocalypse.’ Then Deleted 138,000 Lines

    Jump

  • This is great.The unused code is (now) no longer an attack surface.If Kicinski is wrong, someone needs to take ownership of the module and it gets re-added.Win-Win.

  • Minutes before Trump's announcement, $800 million in trades made on oil prices

    Jump

  • It's one thing for someone inside to profit off their insider knowledge.It's a whole 'nother level of evil to make announcements and decisions based on the profits you can make.

  • CachyOS Is Now the Most Popular Desktop Distro on ProtonDB

    Jump

  • I've been running Cachy for a few months - it just works.

    I picked it because it appeared to be easy to install Arch (which I've run before, btw) with sane defaults.But that's exactly what Endeavour is from what I just read.I don't know if the purported optimisations provide any real world benefit, but the major reason I went Cachy is it being the flavour of the month.For the time being, it's where a lot of focus is for new development in the gaming space.

  • S&Box went open-source and the comments are very calm

    Jump

  • These are pretty calm messages to an Australian and Garry is British, so culture checks out.

    // What the fuck// Fuck dynamic compiling.// what the fuck is this shit// What the fuck, why isnt this a method

    Should this by the by commentary be there?Not really.But as a programmer, I understand each and every time I see something like:

    // Urgh this is so dirty, Invalidate() and Refresh() do nothing.tButt.AutoSize = false;tButt.Width = maxWidth;tButt.Height = maxHeight;tButt.AutoSize = true;

  • Selfhosted @lemmy.world
    Mountaineer @aussie.zone

    Jellyfin 10.11.1 minor

    github.com /jellyfin/jellyfin/releases/tag/v10.11.1
  • Opensource @programming.dev
    Mountaineer @aussie.zone

    Jellyfin 10.11.1 minor

    github.com /jellyfin/jellyfin/releases/tag/v10.11.1

  • Jellyfin 10.11.0 Released

    Jump
  • Opensource @programming.dev
    Mountaineer @aussie.zone

    Jellyfin 10.11.0 Released

    github.com /jellyfin/jellyfin/releases/tag/v10.11.0
  • Selfhosted @lemmy.world
    Mountaineer @aussie.zone

    Jellyfin 10.11.0 Released

    github.com /jellyfin/jellyfin/releases/tag/v10.11.0

  • Jellyfin 10.11.0 RC9

    Jump

  • I think the feel from the Devs is that there isn't enough new functionality to justify the major version bump, this primarily being a reimplementation of existing features.

    BUT, I agree with you, it should definitely be V11 under the semantic versioning scheme.Whilst there is a migration path here, the database changes under the hood alone are likely to break backwards compatibility with all plugins (with in-house plugins being upgraded in sync).Such breakage is kind of the defining characteristic of a MAJOR version.

  • Selfhosted @lemmy.world
    Mountaineer @aussie.zone

    Jellyfin 10.11.0 RC9

    github.com /jellyfin/jellyfin/releases/tag/v10.11.0-rc9
  • Jellyfin: The Free Software Media System @lemmy.ml
    Mountaineer @aussie.zone

    Jellyfin 10.11.0 RC6

    github.com /jellyfin/jellyfin/releases/tag/v10.11.0-rc6
  • Jellyfin: The Free Software Media System @lemmy.ml
    Mountaineer @aussie.zone

    New Jellyfin Server/Web release: 10.10.7

    forum.jellyfin.org /t-new-jellyfin-server-web-release-10-10-7
  • Jellyfin: The Free Software Media System @lemmy.ml
    Mountaineer @aussie.zone

    New Jellyfin Server/Web release: 10.10.6

    forum.jellyfin.org /t-new-jellyfin-server-web-release-10-10-6
  • Jellyfin: The Free Software Media System @lemmy.ml
    Mountaineer @aussie.zone

    Jellyfin Server/Web release: 10.10.4

    forum.jellyfin.org /t-new-jellyfin-server-web-release-10-10-4

  • Sometimes, it's backwards

    Jump

  • Sounds like you’re stuck in a worst practices mindset.

    Worst/Pragmatic.If I get a timeline for a feature request, then everything can be scheduled, tested, whitelisted, delivered at a reasonable time.That's the rarer event - normally it's more like "the scale head has died and a technician is on the way to replace it" and whilst I modify the program in question to handle this new input, hundreds of staff are standing around and delivery quotas won't be met.Is my position arrogant? This is the job.

    Sign your damn releases and have the whitelisting done by cert.

    I'll see if this is possible at the site in question, thank you.

  • Sometimes, it's backwards

    Jump

  • It IS bespoke internal development, not for deployment outside of the facility.The computers running the software exist only to run this software and have no business talking to the internet at all.IT is provided by an external third party vendor who operate on an inflexible "best practices dogma".

  • Sometimes, it's backwards

    Jump

  • In a rapidly churning startup phase, where new releases can and do come out constantly to meet production requirements, this one size fits all mentality is impractical.

    If you refuse to whitelist the deployment directory, you will be taking 2am calls to whitelist the emergency releases.

    No it can't wait until Monday at 9am, no there will not be a staged roll out and multiple rounds of testing.

    I am more than willing to have a chat; you, me and the CEO.

  • Bussin no cap fr fr

    Jump

  • Us oldies being able to parse it, just means that it is now out of date. ;-)

    Crinj fr fr.