|
Well I can't speak for CP, but....
Stack Overflow - You'll make the mods/admins mad
Quora - You'll get a strike on your account
Facebook - You'll get a 24 hour posting ban
In all 3 cases, try to use lmgtfy, and the ban you receive will be cited as "Not being courteous or kind to others, and using language intended to inflict harm."
I keep racking up bans, then I hit the limit and have to be very careful for 3/6 months or whatever, otherwise my account will get closed down, it is crazy how easily those 3 are triggered these days.
|
|
|
|
|
On my GFX project at github I got my first issue request that wasn't a bug - from someone that wants to use my library commercially! They've evaluated the other graphics libraries, and are leaning toward my offering.
That's super cool. It's the first serious use of my library by someone aside from me that I'm aware of.
Real programmers use butterflies
|
|
|
|
|
the butterflies are flapping really hard today.
Also, congrats
To err is human to really elephant it up you need a computer
|
|
|
|
|
Congrats, always nice to see someone using your work for good and not evil. 
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Congrats - butterflies are the theme for the CCC this week ( as long as you are a monarch )
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
That is so cool! 
Make sure you get a percentage of the cut and don't forget about us when you're a billionaire 
|
|
|
|
|
I released it MIT. If they want support I'll charge them. 
Real programmers use butterflies
|
|
|
|
|
I remember you agonizing over licenses a while back. I am glad you found the right one.
Don’t forget to display your HoneyWitch logo as part of the driver initialization with your website of course! Kind of like all of the production companies do for movies.😊
|
|
|
|
|
My favorite kind of license 
|
|
|
|
|
Provide support for crawler (11)
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
CATER-PILLAR
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Quote: Ah, breaker one-nine, this here's the Rubber Duck
You gotta copy on me, Pig Pen, c'mon?
Ah, yeah, 10-4, Pig Pen, fer shure, fer shure
By golly, it's clean clear to Flag Town, c'mon
Yeah, that's a big 10-4 there, Pig Pen
Yeah, we definitely got the front door, good buddy
Mercy sakes alive, looks like we got us a theme week!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
YAUT
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
La oruga muy hambrienta
The very hungry caterpillar
That book always made me hungry!
|
|
|
|
|
It's screaming about a bunch of warnings that didn't crop up in .Net Framework. CS8600, 8601, 8602, and 8618. I see no benefit when the objects it's screaming about can in fact be null without hurting anything. In fact, my code is written to handle it gracefully.
Nanny state bullsh|t...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
I realize that (and I've done it), but having to do it now when it's been good for 20 years is annoying.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Open the .csproj file and change "the" line to read:
<Nullable>disable</Nullable>
And yes, bloody annoying.
|
|
|
|
|
No need to edit, that Nullable switch is available under Properties/Build/General
Luc Pattyn [My Articles]
The Windows 11 "taskbar" is disgusting. It should be at the left of the screen, with real icons, with text, progress, etc. They downgraded my developer PC to a bloody iPhone.
|
|
|
|
|
#realJSOP wrote: Nanny state bullsh|t...
Yup. The state dictates that, offcourse.
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
|
Let me see.
I can enable null check - clearly advertising intent outside my method - make it very clear where I can ignore null check and get the compiler to tell me where I need it. Reference types and value types both able to advertise clearly if they are nullable or not.
Or I can disable nullable check and accept more null reference exceptions - often not telling you enough to easily tell what was null when all you have is a log file from a production server. When calling a method always having to wonder "hmm, can this return null or not" - and either forget to handle null in one or another edge case, or clutter the code with null handling code that will never execute. And have value types that can communicate if they can be null or not, while my reference types can't.
And in case you say "never happens to me". Well, congratulation for working on such a simple code base.
It is not exactly a hard choice for new code. I can't think of a single reason to disable it besides "I am not used to it".
For old code it is of course a question if it is worth the investment which will vary from project to project.
It is unfortunately not as good as it should be due to the requirement to link to libraries developed before null checks, but at least it is an attempt to fix one of the most serious design mistakes in the .NET type system.
Can we please get more "nanny state" to let the compiler deal with this trivial crap so I can concentrate on the domain.
|
|
|
|
|
Just to add to my own argument....
Why should:
int i = null;
be an error and you have to write
int? i = null;
while
object obj = null;
is supposed to be OK?
And yes, I understand the technical and historical reasons for this. And they are exactly that: technical and historical. The compiler can finally move us beyond this.
|
|
|
|
|
I disagree with this sentiment. I think that the way a variable is declared is very important to allow the compiler to check for misuse. Any misuse found would indicate that the programmer means something other than what he wrote.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
