The post is about developers.

UTC is expressed using positive or negative offset from IAT

Isn’t that UT0?

UTC is timezone too. It has leap seconds. IAT is atomic time. It is perfect.

Worst is UTC vs IAT

Used, not improved.

1. a
2. b
3. c
4. Very long text, that is longer than one line, to demonstrate how very long text is formatted.

Very long text, that is longer than one line, to demonstrate how very long text is formatted.

The rent will never go down and the landlord will never sell.

1. Thanks for proving capitalism doesn’t work.
2. Some countries have seizures if land isn’t used for its intended purpose. But quick search says Spain doesn’t have it.

Thanks

1. They seem to hate my devices. Lots of captchas.
2. They seem to hate when people bypass their country’s censorship. Using sites behind cloudflare through tor is pain without end.

I think I haven’t seen story you mention.

THIS MESSAGE (MATERIAL) CREATED AND (OR) DISTRIBUTED WITH PURPOSE OF HATE AND (OR) ENCOURAGING HATE.

You forgot to put it.

I heavilt dislike cloudflare, but this is not valid reason to hate them.

No. Verlilogjson.

Nvidia spotted. Launching “Nvidia, fuck you!” strike

and in rust’s case sometimes even how to fix it

Then there’s C with “segmentation fault”

1. You are comparing compiler-generated errors and runtime errors
2. Rust can trigger segmentation fault and bus error too.
3. GCC’s error messages are very detailed, sometimes can contain suggested solutions.

For example if I will try to compile helloworld without including stdio.h, gcc will warn implicit declaration of function ‘printf’(by default, almost everyone make it error with -Werror=) and will suggest note: include ‘<stdio.h>’ or provide a declaration of ‘printf’. And runtime error reports are as good as programmer makes them, no matter language program was written in.

I am spoiled by core dumps(although rust technically has them too).

Also in context of kernel, it will print stack trace and (if used) will kexec into another kernel that can make core dump or continue working.

Join the dark side. We have cookies.

No framework will make FSM for you. Managing state of web ui is not as hard as managing state of game.

Using TCP for networking? Loss, retransmit, lag, you’re dead. Using UDP for networking? Loss, desync, you’re dead. Sending full game state? Congestion, loss, lag, dead. Doing sync right, but still pushing too much data? Congestion, loss, lag, dead. Also keeping on server you need not only track game state, but what game state client confirmed to receive.

Linux has better error messages. “Dazed and confused, but trying to continue”.

Hah. I get it. Good one.

ServiceWorkers?