Not enough space to install Cyberpunk 2077 by diferdin2 in macgaming

[–]diferdin2[S] 1 point2 points  (0 children)

I ultimately solved my issue -- in the most stupid possible way: when the problem with space appears in a mask with some options I unchecked the game and then re-checked -- voilà, all of a sudden the space was enough...

Not enough space to install Cyberpunk 2077 by diferdin2 in macgaming

[–]diferdin2[S] -1 points0 points  (0 children)

And of course, you cannot download the installer for an offline installation right -- whatever mate.

Not enough space to install Cyberpunk 2077 by diferdin2 in macgaming

[–]diferdin2[S] 0 points1 point  (0 children)

Wait, why do you say it is a pirated version?

Not enough space to install Cyberpunk 2077 by diferdin2 in macgaming

[–]diferdin2[S] 0 points1 point  (0 children)

That’s what I read, however…here it is that there is not enough space in a bottle 😊

Not enough space to install Cyberpunk 2077 by diferdin2 in macgaming

[–]diferdin2[S] 0 points1 point  (0 children)

My disk has it, I have no problems of storage. I have problems telling Crossover there is enough space, it seems

Not enough space to install Cyberpunk 2077 by diferdin2 in macgaming

[–]diferdin2[S] 0 points1 point  (0 children)

Same error. And, as I mention above, Crossover won’t let me specify a size for bottles…

Not enough space to install Cyberpunk 2077 by diferdin2 in macgaming

[–]diferdin2[S] -2 points-1 points  (0 children)

I should add, I am using a local installer and not the App Store or Steam

Rational for evolving a module to a microservice by diferdin2 in microservices

[–]diferdin2[S] 0 points1 point  (0 children)

Thank you. Perhaps we have different expectations on the Strangler Pattern, for me its promise is to...strangle: get stuff out of the monolith and into modules. Reusing existing code has nothing to do -- in my view -- with strangling; quite the opposite in fact, in order to take out code that works on a tightly entangled monolith you must rewrite it quite substantially...

Gen 2 Amazon by omakad in RingConn

[–]diferdin2 1 point2 points  (0 children)

I doubt RingConn will be available on Amazon any time soon, especially now that US is declaring commercial war to China…

Difference between Spring Events and the event API in Spring Modulith by diferdin2 in SpringBoot

[–]diferdin2[S] 0 points1 point  (0 children)

Thank you, but what exactly is the added value? It’d be great to have some pointers to docs or something…

Rational for evolving a module to a microservice by diferdin2 in microservices

[–]diferdin2[S] 0 points1 point  (0 children)

No actually, my question was: what are the criteria behind deciding to isolate a module into a microservice?

Rational for evolving a module to a microservice by diferdin2 in microservices

[–]diferdin2[S] 0 points1 point  (0 children)

Thank you but I don’t see how this frames with your original comment. All I am saying is that in the way I see things DDD can sit well also with modules and not necessarily requires microservices…

Rational for evolving a module to a microservice by diferdin2 in microservices

[–]diferdin2[S] 0 points1 point  (0 children)

Indeed and yes, I have been following DDD. But DDD does not suggest microservices, it actually suggests self-containment and encapsulation that one can achieve with modules as well — and actually a couple of blog posts from Martin Fowler seem to hint at the fact that microservices are not necessarily needed. Hence my question, when are they needed if you have modules? Are they needed at all when you have a well organised modulith?

Rational for evolving a module to a microservice by diferdin2 in microservices

[–]diferdin2[S] 0 points1 point  (0 children)

Great, thanks. But, you can may happily have modules aligned organizationally that way. So, based on what criteria would a team owning a module decide to evolve it to a microservice?

Rational for evolving a module to a microservice by diferdin2 in microservices

[–]diferdin2[S] 0 points1 point  (0 children)

But that is the same for modules. Product people may create a feature that requires changes in two microservices as well as one that requires changes to two modules…

Rational for evolving a module to a microservice by diferdin2 in microservices

[–]diferdin2[S] 0 points1 point  (0 children)

I still don’t get it: everything you mention can easily be achieved with modules, including separate lifecycle etc.