funnily that is/was one of the Lemmy creators: Nutomic :)

Plot twist

UTC is expressed using positive or negative offset from IAT

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

Worst is UTC vs IAT

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

If all data is stored as patches, then no shallow cloning

Darcs looks meh. Can’t say anything about Pijul.

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 ‘’ 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?

For example, you can do offline PWA with SPA since a page load doesn’t need a call to the server for rendering it.

Client still needs to call the server. How offline PWAs work then? They emulate server in ServiceWorkers.

It also saves processing time/bandwidth by offloading the server from the burden of rendering the page.

1. Let’s call it page generation to not confuse with actual rendering.
2. It not always saves bandwidth and processing time, but static resources can allow to hide CDN latency on initial load. Although it is not property of SPAs, just separation of static and dynamyc part and generating dynamic part after static page already shows something.
3. It will still result in more requests, but may trasfer less data per request. May.

Once the page has loaded, the web app only needs data, not markup nor style.

Static web page after loading will not request more styles. SPAs imply client-side dynamic page, and they may request more data INCLUDING styles. Also client still need to load styles on page load.

And last is that it is great since it only requires a browser without needing to write native apps in myriad of languages.

Write for QT.

And when you are deploying it for 24/7 use, down times can be costly. Deploying to cloud early and then slowly building towards on-premise after the team gets bigger is a viable route IMHO

I guess so. Not everything can be offline-oriented.

In many pages application url already bears part of state.