I was thinking...

[Red Squirrel]

Microsoft needs to bring back Clippy. But instead of having him on Office, have him in the .NET development suite.

Imagine you're just typing code and "It looks like you're declaring a pointer in a way that will lead to a NullPointerException, do you want help declaring it properly?".

Clippy saves the day!

 

[biostud]

Microsoft needs to bring back Clippy. But instead of having him on Office, have him in the .NET development suite.

Imagine you're just typing code and "It looks like you're declaring a pointer in a way that will lead to a NullPointerException, do you want help declaring it properly?".

Clippy saves the day!

Co-pilot is Clippy, but you have to pay for him to be in your office suite.

But otherwise couldn't the compiler check for it?

 

[FelixDeCat]

I remember using Office at work in the 1990s. Clippy as annoying. However I support his return now.

 

[herm0016]

its not a bad idea. he should be the face of copilot.

 

[WelshBloke]

I was thinking...​

Lies!

Just yanking your chain there mate!

 

[IronWing]

Clippy AI

 

[Stiff Clamp]

Yikes. I'd hate to de-reference a null pointer.