There are exactly three variations of the % symbol:

% percent, 100
‰ per mille, 1000
‱ permyriad, 10000
and per cent mille, 100000, doesn’t have a symbol anymore, just an abbreviation: pcm

We can’t even go into the other direction and reduce the number.
per deca, 10, could be % without the second circle, like °/ but it doesn’t exist as one character.

OK, so Chatgpt is ditching the EM dashes. Sad, because that's how we easily could recognize the idiots. Also it's not new at all to let Chatgpt drop the EM dashes as been stated in article. I have a very detailed analysis about my writing and it copies it perfectly. So, they're selling us a placebo. Idiots. Also, for high quality information they relied on 1900's books? All the shit that came after that is a bullshit indeed. Not surprised...

https://perplexity.ai/page/...

Hi y'all! I got question, for my engine map format (the map editor will be blender/blockbench) should I just use a GLTF that contains every node and extras for light and custom properties or code a blender plugin that exports a TOML like:
# === MAP ===
name = "E1M1"
description = "At Doom's gate"

# --- Objets ---
[[objects]]
path = "assets/models/tree01.obj"
position = [10.5, 0.0, -3.2]
rotation = [0.0, 90.0, 0.0] # pitch, yaw, roll in degrees
scale = [1.0, 1.0, 1.0]

[[objects]]
path = "assets/models/coin_gold.obj"
position = [5.0, 1.0, 2.5]
rotation = [0.0, 0.0, 0.0]
scale = [1.0, 1.0, 1.0]

[[objects]]
path = "assets/models/rock_large.obj"
position = [-2.3, 0.0, 4.8]
rotation = [0.0, 0.0, 0.0]
scale = [1.0, 1.0, 1.0]

# --- Static lights ---
[[lights]]
type = "point" # "point", "directional", "spot"
position = [0.0, 5.0, 0.0] # spot or point
direction = [0.0, -1.0, 0.0] # spot or directional
color = [1.0, 0.9, 0.7] # RGB, 0.0 to 1.0
intensity = 1.0
radius = 10.0 # influence radius
angle = 45.0 # angle for spot

[[lights]]
type = "directional"
direction = [1.0, -1.0, 0.0]
color = [0.8, 0.8, 1.0]
intensity = 0.6

# --- Spawn points (user-added triggers) ---
[[spawn_points]]
name = "PlayerStart"
position = [0.0, 0.0, 5.0]
rotation = [0.0, 0.0, 0.0]

[[spawn_points]]
name = "EnemySpawn01"
position = [15.0, 0.0, -3.0]
rotation = [0.0, 180.0, 0.0]

Week: 114 (Year 3)

How was the weekend?

Question: What is something most people misunderstand about you?

last Weekend : https://devrant.com/rants/19381611

With mentions being broken and retoor creating an RSS feed for mentions, I made a small python script that reads retoor's feed and filters out only mentions of you and sends them as desktop notifications:
https://github.com/yuriKhordal/...

It's technically cross platform, but I've only tested this on linux with KDE, so no idea how or if it works on windows, and the tools around the script (install script, systemd service, run script, and the instructions on github) are currently linux only. Sorry Windows people, hadn't had the time to test this on windows and I've already spent more time on it than I originally allocated for it (accidentally sat 16 hours straight programming yesterday until mornimg and then "collapsed" into bed :P), I'll try to get to it somewhen this week. But it's still possible to run the "manual way" as `python dr-mentions.py` from CMD.

Bug reports are welcome, and round of Applause for retoor and every one of you that is keeping this dying platform alive <3

necessity the mother of invention

or boredom?

Offset pagination is one of the biggest collective failures in software engineering.

Who wakes up one morning yearning to visit page 7218 of 100000 in the dataset?

No one, right? Because that’s not how it’s supposed to work. That’s what the search feature is for. Not that developers don’t fuck it up too, but that’s the not the point of this rant.

The truth is, most developers are lazy and don’t want to properly handle stuff. It’s even made worse by ORMs, where some dumb ass will use Django to make a shitty API without a care in the world about the underlying database.
Then after a few months of ever increasing data, they start experiencing very slow queries and response times.

Gee, I wonder what it could be! Could it be that the DB is having to go through hundreds of rows just to return the 100001st row? 

Designers also defaulting to Page 1 of 2322222 UI like the NPCs they are, is a big problem.

Pagination UI, if not done right, is a performance nightmare masquerading as a feature, solving a user problem that doesn't exist.

Fuck whoever came up with this bullshit.

I’ve had 3 side gigs where my task was to speed up the system and it always ended up being an issue with pagination. Once worked on a project where the dashboard toook 8 minutes. Yes, you read that right. 8 minutes to load. The company had accepted it as normal until a new manager joined and said, fuck that. Brough me onboard to unfuck the mess. No issue with Django devs, but bro, learn how to deal with databases properly for fuck's sake.

Before you came at me with, “well, what if I want to give users the ability to jump between pages”. Bro, that’s what search is for! If search is not allowing users to access the exact data they want, then it’s broken.
Pages are not deterministic anyway, because page 4 today won’t have the same data tomorrow.

I just fucking hate badly implementation pagination. Fucks up my day.