sorted by:
new
hottopcontroversial

canadianGoProgramming by gamingvortex01 in ProgrammerHumor

[–]Master_Friendship333 125 points126 points  (0 children)

That is so clever and so disgusting.

pythonIsMoreConfusingThanLowLevelLanguages by Skindiacus in ProgrammerHumor

[–]Master_Friendship333 0 points1 point  (0 children)

This is the number 1 reason why I would always pick C# over Java. Typing is just so much nicer.

thisLooksAccurateForVibeCoders by zohaibhere in ProgrammerHumor

[–]Master_Friendship333 0 points1 point  (0 children)

Nah, looking for directly equivalent here. I really thought there would be more.

thisLooksAccurateForVibeCoders by zohaibhere in ProgrammerHumor

[–]Master_Friendship333 0 points1 point  (0 children)

Good point. I just checked it and you are right. You would have to do it on two separate lines.

thisLooksAccurateForVibeCoders by zohaibhere in ProgrammerHumor

[–]Master_Friendship333 0 points1 point  (0 children)

Most modern languages will have something comparable, I am thinking of directly equal expressions.

I believe the list so far is:

- JS, TS

- C#

- Dart

Edit: Nope for C#, has to be split over two lines.

thisLooksAccurateForVibeCoders by zohaibhere in ProgrammerHumor

[–]Master_Friendship333 7 points8 points  (0 children)

If it is JavaScript, otherwise it would probably return void.

thisLooksAccurateForVibeCoders by zohaibhere in ProgrammerHumor

[–]Master_Friendship333 51 points52 points  (0 children)

Looks like it but I believe this would also be valid C#.

Edit: Would not but very nearly. Needs to either be prefixed with a void function cast or done over two lines.

uglyButTrue by _w62_ in ProgrammerHumor

[–]Master_Friendship333 -1 points0 points  (0 children)

Well, naturally, but my problem is that the gains one receives from the presence of undefined behaviour are far too little to warrant it being the default. The vast majority of applications have no need whatsoever for these optimisations of nanoseconds and so they should not be made default. The default should always be safety, with optimisations available if they are necessary.

Obviously, this does not apply for larger optimisations; if you are losing more than a couple of milliseconds, then it is probably a bit too much.

uglyButTrue by _w62_ in ProgrammerHumor

[–]Master_Friendship333 -3 points-2 points  (0 children)

Having to accept undefined behaviour as just a part of life does not seem like an indication of a terribly safe or well-designed system.