DrDeadCrash

joined 2 years ago
[–] DrDeadCrash@programming.dev 2 points 6 hours ago

Likely fewer, though...

Another American here, I think it's important to be aware that those attacks happened as a direct result of evil -empire level shit the US is responsible for in the 20th century.

[–] DrDeadCrash@programming.dev 7 points 1 week ago

That's the neat part .png

[–] DrDeadCrash@programming.dev 5 points 1 week ago (2 children)

Though the farms world need to start growing different crops...

[–] DrDeadCrash@programming.dev 2 points 2 weeks ago

Or to "teach a lesson" to everyone else.... Greed and cruelty go hand in hand.

[–] DrDeadCrash@programming.dev 1 points 2 weeks ago

They'll kill them all regardless, what shame.

[–] DrDeadCrash@programming.dev 3 points 2 weeks ago

He's the most senior Senator in the democratic party, he's as entrenched as they come.

[–] DrDeadCrash@programming.dev 2 points 3 weeks ago

These fuckers know they're the brown shirts.

[–] DrDeadCrash@programming.dev 2 points 3 weeks ago

I think the line of thinking is when you're struggling, resisting temptations that cross moral lines has a greater impact on your life. You get to make these decisions all the time and it's a lot easier to make the moral choice if you're financially secure.

[–] DrDeadCrash@programming.dev 3 points 3 weeks ago (1 children)

China won Big-time

[–] DrDeadCrash@programming.dev 11 points 3 weeks ago* (last edited 3 weeks ago)

Yes there has been a court case, Colorado didn't want to put Trump on the ballot because of the insurrection clause, it went up to the supreme Court and they said it was A-OK.

Edit, link: https://www.scotusblog.com/2024/03/supreme-court-rules-states-cannot-remove-trump-from-ballot-for-insurrection/

[–] DrDeadCrash@programming.dev 14 points 3 weeks ago (2 children)

Allowing trump to run again after inciting an insurrection?

 

I hope they fight extradition...

 

I've been using Visual Studio for almost 20 years as my primary code editor /project manager and for all that time it's been solid. If there were errors it told you and highlighted/underlined them before you tried to build no matter where the error was in the entire solution.

I am willing to accept a slight decrease that solidness in order to gain the extra flexibility provided by dotnet core over framework. However...

My experience with the recent updates to Visual Studio have culminated into a state where errors that exists are not detected, or if they are (ex. on rebuild) they are only reported, not underlined. Once I find and fix the error it remains in the list until I rebuild, if there are other errors it will remain until I find and fix each of them (which themselves will remain in the error list...) and finally rebuild.

I've adjusted options, to no avail. Sometimes restarting VS helps for a few minutes sometimes deleting the .vs folder will help for a few more...I feel like It used to be a lot nicer.

Today I'm seriously considering moving to a plain code editor and using the donet cli for build/test/publish.

Is anyone else experiencing problems like this?

17
submitted 9 months ago* (last edited 9 months ago) by DrDeadCrash@programming.dev to c/csharp@programming.dev
 

A collection of tools for dealing with nulls, failures and the generic type issues that arise in this domain.

https://github.com/Andy3432344/SafeResults

I'm the author, let me know what you think!

*Edit: updated to show GitHub link, sorry!

 

I work for a services company, and we're not getting much right now. Just wanted to ask about work availability across the board.

 

error no posts

I have an active post in vscode right now, which I made in browser, but cannot see anything when viewing the community with Connect. Any ideas?

 

Hi everyone, I'm trying to try out F# via FSI in VS Code (Windows 10)

I have Ionide for F# installed, and have used it before, but now every time I try to start it I get a message "FSI :Start resulted in an error", it goes on to helpfully report "the option has no value".

dotnet is in path, dotnet works great. FSI? nothing.

I also have the .net workload installed for visual studio 2022 (if that matters).

I started up my Linux VM (KDE Neon) fired up vs codium and tried FSI Start...same error! So no tinkering in f# for me tonight. Does anyone have an idea what's happening, across two environments? Google is no help...

view more: next ›