StudioLE

@StudioLE@programming.dev

• ⁨Comment⁩ on ⁨Cities Skylines II is an absolutely beautiful game⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  This is the catch 22 of PC gaming. On the one hand you’ve got people complaining that the latest games that require high end hardware to run, and simultaneously at the other end of the spectrum people are complaining that supporting low end hardware is dragging a game down?!

  Hence why targeting a single console generation makes far more sense to me?

• ⁨Comment⁩ on ⁨Cities Skylines II is an absolutely beautiful game⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Full price? I’ve had over a week of gameplay for just a £1 Game Pass trial. Usually I tire of games after just 3 days or 30 hours or so for me and I’m sure many other casual gamers it’s great value.

• ⁨Comment⁩ on ⁨Cities Skylines II is an absolutely beautiful game⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Enscape provide photorealistic VR rendering for architectural software ( enscape3d.com/…/architectural-virtual-reality/) so with some conversion of the geometry from unity the only missing link is interactivity.

• ⁨Comment⁩ on ⁨Cities Skylines II is an absolutely beautiful game⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’ve never understood 4k. Surely it’s better to play high settings on a QHD screen than medium on 4k?

• ⁨Comment⁩ on ⁨Cities Skylines II is an absolutely beautiful game⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  This was why I favoured console gaming over PC. Having a standardised hardware always meant you don’t have the heart ache of a game not performing well. With the introduction of the Steam Deck hopefully that will become the new baseline for future games.

• ⁨Comment⁩ on ⁨Cities Skylines II is an absolutely beautiful game⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’d actual prefer they avoided going for photo realism, it always tends to fall short. The art style they’ve developed works really well - realistic detail and form but with a plastic sheen and strongly saturated colours.

• Cities Skylines II is an absolutely beautiful gamevimeo.com ↗
  Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ to ⁨games@lemmy.world⁩ | ⁨34⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Sycamore Gap tree at Hadrian's Wall 'felled overnight'⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  This really is a great loss. It was a true, natural icon of Northumberland. The landmark I pointed out to people most often.

  I do hope funding can be secured to fill the void left behind.

• ⁨Comment⁩ on ⁨Why shouldn’t firearm manufacturers be held accountable for the use of their weapons in crimes?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Arms manufacturers would probably argue that guns are intended to be deterrent. And they shouldn’t be held liable that the cops keep executing unarmed suspects with them.

• ⁨Comment⁩ on ⁨Google Chrome pushes ahead with targeted ads based on your browser history⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Chrome’s UI was light years ahead of the competition. I’d be tempted to say they had an impact on the design of all desktop applications.

• ⁨Comment⁩ on ⁨American XL bulldogs kill 22 sheep⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  And then farmer gets stiffed with increased insurance premiums. I really hope that’s not how it works.

  Hopefully the farmer can directly sue the owner for actual and emotional damages with Farm insurance covering the legal costs.

• ⁨Comment⁩ on ⁨More than half of UK children do not read in their spare time, survey reveals⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  The obsession with Shakespeare puts a lot of students off literature

• ⁨Comment⁩ on ⁨Lidl recalls Paw Patrol snacks after website on packaging displayed porn⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  How many people are actually returning this product though? Nobody is going to any effort to return a product that costs so little. And everything I’ve read about this recall makes it pretty clear the v reasoning so I can’t see anyone opting not to just consume it - which more than likely they already did immediately on purchase.

• ⁨Comment⁩ on ⁨What helps people get comfortable on the command line?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  -p –patch

  Interactively choose hunks of patch between the index and the work tree and add them to the index. This gives the user a chance to review the difference before adding modified contents to the index.

  This effectively runs add --interactive, but bypasses the initial command menu and directly jumps to the patch subcommand. See “Interactive mode” for details.

  The documentation is entirely meaningless? What does it do?

• ⁨Comment⁩ on ⁨What helps people get comfortable on the command line?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  You’ve never used a graphical git client?!

  I’m comfortable on the command line but a decent git UI is a way better experience.

  git diff is so basic using a GUI makes it far easier to compare changes.

  Same for merge conflicts. I’m not sure you can even resolve them on the CLI?

  Any form of rebase: I think I used the CLI to do an interactive rebase a few times in the early days but I’d never do so without a GUI now.

  Managing branches: perhaps I’m a little too ott but I keep a lot of branches preserved locally, a GUI provides a decent tree structure for them whereas I assume on the command line I’d just get a long list.

  Managing stashes: unless you just want to apply latest stash (which admittedly is almost always the case) then I’d much rather check what I’m applying through a GUI first.

  There are some things I still use the CLI for though:

  git remote add git remote set-url because I’m just too lazy to figure out how to do that in a GUI. It’s usually hidden away somewhere.

  git push --force because every GUI makes it such an effort. C’mon! I know what I’m doing - it’s /probably/ not going to mess things up…

• ⁨Comment⁩ on ⁨Dell fined $6.5M after admitting it made overpriced monitors look discounted⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  That’s assuming they were only using the tactics during those exact dates, but I imagine that’s just the period the prosecutors could prove.

• ⁨Comment⁩ on ⁨Movies vs life⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’ve been playing around with Grafana alot lately so my screens do look closer to the second. Except not such a disordered jumble so it doesn’t have any where near the same wow factor

• ⁨Comment⁩ on ⁨Trying to get release and testing in sync⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  It sounds like your process isn’t working because you’re treating Tuesday’s deadline as just a feature freeze rather than a full freeze.

  If you want to go ahead with the full freeze then if it fails QA the feature should simply be rejected. Revert the change make the fixes and wait for the next Tuesday deadline to resubmit it.

  If you’re keen to continue the feature freeze then you need to move forward the freeze deadline and agree very specific timings with QA. For example: Feature freeze at 9 am Tuesday morning - so devs must submit all features before end of the day Monday. QA have all Tuesday to review for a deadline 9 am Wednesday.

  That gives the dev at a minimum some time on Wednesday to address any issues, but more likely QA can come back quicker so they’ll have some time on Tuesday as well.

  Dev must submit fixes before a 2 pm deadline on Wednesday. QA do a second review and have all feedback by 9 am Thursday at which point it’s simple commit/revert.

• ⁨Comment⁩ on ⁨is it just me or GitHub is turning into some sort of LinkedIn⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  It sounds like your issue is with capitalism rather than GitHub. The same logic is true of many corporations.

• ⁨Comment⁩ on ⁨is it just me or GitHub is turning into some sort of LinkedIn⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Has GitHub actually done anything negative? Your comments really just sound like fear mongering, I can’t see any actual issues.

  What is the bloat you’re referring to? The UI is clean and simple. Navigating and searching code is intuitive. The issue tracker is basic but reliable. Releases are clear. GitHub Actions are complex but featureful and incredibly useful. GitHub Packages are basic but useful. GitHub Copilot is damn impressive.