retoor/drstats
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update export statistics with new user data and extended date range for graphs

Browse Source 
- Refresh dataset and statistics files to reflect 401 active users and 11371 total contributions
- Replace export graphs with updated date range from 2024-11-07 to 2025-02-01
- Add new user posts to 12bitfloat and ANGRY-STUDENT export files
- Update Buffon's contribution percentage from 0.02 to 0.01 in statistics
This commit is contained in:
bot
2025-02-01 03:28:26 +00:00
parent 3e5b5569ed
commit f790e2db60
643 changed files with 4567 additions and 849 deletions
Download Patch File Download Diff File Expand all files Collapse all files
export/rants-Lensflare.txt
+13 -1
View File
@@ -86,4 +86,16 @@ This is the information that your future you has sent you.
Repeat this process with the other time machines for more bits of information.
Then wait the time which corresponds to the path length (maybe send in your lottery numbers) and then (this part is very important) make sure to flip the switch corresponsing to the bit that you wrote down, so that your past you receives that info in the past.
I hope that helps :)```
I hope that helps :),Why the hell do languages like Kotlin (Java) and C# handle dates and datetimes so needlessly complicated?
There are multiple types with different implementations and concepts like local time or time zones represented by those types. Some of them have capabilities like serialization, some of them don’t.
Parsing and encoding is tied to the types.
Why? Take Swift as an example:
It has one single Date type (including time) which represents a point in time independent of any calendar, time zone, encoding or format.
There is a DateFormatter to parse from APIs from iso or timestamps or whatever and to format to UI as a string in any language (localization), for any region, in any format.
If you just want a container for the date time components themselves (which the concept of local date time seems to be in those languages), you can use the DateComponents type. If you are interested in dates from the perspective of a calendar, there is a Calendar type.
Everything makes sense and the different concepts are decoupled from each other as they should be.
Damn! My memory about C# is a bit hazy but Kotlin, I’m disappointed in you! Date handling is a horrible mess!
Ok, I guess I can blame it on Java and JVM.```