The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Yesterday I had to fight Hammerlocked!
(Eden-6 main mission boss fight)
What an epic fight and epic bugger!
First you bring down his humongous armour and health down (takes a while, was running out of rifle ammo)...
And then he was almost down...
And then he turned into raging warden, regenerating his full health!
What the heck?!
And then he was almost down....
And then he did it again, turning into a super raging warden, and regenerating his full health!
And then he was almost down....
And then he did it again! Turning into mega raging warden, regenerating his full health!
And then he was almost down.... please for good...
But nope, he does it again, turned into an ultimate warden! regenerating his full health!
Alright, ultimate, gunning him down...
And then he does it yet again, turning into godly warden, regenerating his full health!
And then, should be good, right?
Yeah! The warden is finally dead!
Special thanks to my trusty old Torque (rocket) gun, 140 damage a shot! 700 ammos!
The Atari 2600 is considered archaeological material now. This was an very interesting read. They supposedly found a never before documented algorithm inside the dissassembled ROM. They tracked down the engineering team and this is what was said:
The basic maze generating routine had been partially written by a stoner who had left. I contacted him to try and understand what the maze generating algorithm did. He told me it came upon him when he was drunk and whacked out of his brain, he coded it up in assembly overnight before he passed out, but now could not for the life of him remember how the algorithm worked.
I took a look (The algorithm is at the bottom of the paper) and it looks very similar to a simple Moore[^] or von Neumann[^] neighborhood.
As someone who (still) works with WinForms, I was interested to read:
The Windows Forms designer is still in preview, and available as a separate download. It will be added to Visual Studio as part of a later release. The designer currently includes support for the most commonly used controls and low-level functionality. We’ll keep improving the designer with monthly updates. We don’t recommend porting your Windows Forms applications to .NET Core just yet, particularly if you rely on the designer. Please do experiment with the designer preview, and give us feedback.
You can also create and build desktop applications from the command line using the .NET CLI.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
I haven't found anything easier or more straightforward when I want a quick Windows program that just does something without me having to learn 6 new weirdly-named frameworks and 7 new ways of doing old familiar things.
- I would love to change the world, but they won’t give me the source code.
The caveat is that WinForms, even in .NET Core, is still Windows only.
The "only" benefits you get is a performance improvement and you can run applications without the need of having the .NET Framework installed on the client Windows computer (which is pretty sweet).
If you want to make use of Core packages, like Microsoft.EntityFrameworkCore, Microsoft.Extensions.Configuration(.*) or Microsoft.Extensions.DependencyInjection you can just keep your current .NET Framework application as all of those are built on .NET Standard and will run in .NET Framework as well.
I just inherited a WinForms application, but it'll be a while before I port it to .NET Core.