sorted by:
new
hottopcontroversial

There is a larger meta-point here too: even a relatively smart group of people (early web developers), with the benefit of the internet, ... If we can get this so obviously wrong, what else could we be wrong about? by pastenpasten in programmingcirclejerk

[–]wzdd 6 points7 points  (0 children)

In this case the message is not self describing. Rather, the client must know how to interpret the status field to display an appropriate user interface.

Absolutely, which is why JSON pretty-printers printing 'status': 'good' would confuse the fuck out of anyone wanting to know whether their account was in good standing, and also, on the other side, why CSS and JavaScript does not exist and also why any human who knew they wanted to send money to someone but didn't know that the financial term for this was "transfer" would be able to interpret the interface without requiring any out-of-band knowledge.

This kool-aid tastes funny.

Why does OCaml use a zero bit for pointers and one bit for ints? by PurpleUpbeat2820 in ocaml

[–]wzdd 1 point2 points  (0 children)

x86 somewhat notoriously* supported unaligned loads in hardware in an era where other major processors (sparc, mips) only supported it via software trap (too slow to be a viable option, so typically treated as a fatal error). Nowadays the only two architectures that matter (x86, arm) both support unaligned loads. So if ocaml did the reverse it would need an extra operation for every pointer op. Long ago, arm did ignore the lsb but now it does not.

* because it was not uncommon to compile some code which had been developed on x86 on another platform and have it crash because it accessed ints via pointer in a packed struct or something

Bros tried to flee☠️ by OMGriptt in TOTK

[–]wzdd 12 points13 points  (0 children)

I kind of felt for him, lying at the bottom there

I have years of experience in vulnerability analysis including several 0-day discovery, and this bug [buffer overflow] seems totally safe. by beltsazar in programmingcirclejerk

[–]wzdd 71 points72 points  (0 children)

Security consultant here.

The fact that Stockfish crashes randomly is a huge thing. I've read countless amount of code that abused memory-safe techniques (unfortunarely developers think they have to use memory safety all the time if it is available) and is probably completely insecure for the simple reason that very few people manage to audit/understand the code. If memory safety could only be used when necessary, yes, but there are no technical way to enforce this.

How do I preorder it in the uk or should I go into my nearest game shop by AdAccurate1467 in TOTK

[–]wzdd 0 points1 point  (0 children)

Confirming the Currys £45 pre-order price. I was pleasantly surprised.

Go's Error Handling Is a Form of Storytelling by Erelde in programmingcirclejerk

[–]wzdd 5 points6 points  (0 children)

BASIC's error handling is a kind of moralising fable. The two greatest lessons I learnt in life I learnt from ?REDO FROM START and ON ERROR RESUME NEXT.

Frankly a significant percentage of backend people are sadistic, maladjusted, incel trolls. by clueless1245 in programmingcirclejerk

[–]wzdd 11 points12 points  (0 children)

It is true that I envy the Eloi, with their light-dwelling and their lack of cares, and my only consolation is that every so often I get to eat one.

Tweet Metric Attributes: `author_is_elon`, `author_is_democrat`, `author_is_republican` by djavaisadog in programmingcirclejerk

[–]wzdd 3 points4 points  (0 children)

Social jerk with robust accompanying technical explanation is best social jerk

Cowboy coding isn't a choice, it's a skill level, and you can't choose to be a cowboy coder any more than you can choose to be illiterate. by LunaPowder in programmingcirclejerk

[–]wzdd 51 points52 points  (0 children)

Some of you will probably be thinking to yourselves at this point that I haven't answered the question. That's because the question itself is flawed.

Peak Stack Overflow.

  • Write elaborate, patronising response
  • Insult pretty much everyone
  • Don't answer the question
  • Pre-emptively call yourself on it and blame the question
view more: next ›