grieferz

non-sense

2026-06-08T07:14:58.300-07:00

https://github.com/processing/p5.js/wiki/Getting-started-with-WebGL-in-p5

why would you force everyone to use mostly negative z values everywhere? (the history of coordinate system choices for graphics is forever full of strange stuff.)

never forget

2026-06-02T20:17:54.418-07:00

#ODWALLAKILLEDPEOPLE

oh, i loathe steam

2026-05-31T19:47:14.213-07:00

The short answer: Steam is warning you because something in your app’s configuration still counts as “changed but not submitted,” even if you already published a build. This usually happens when the store page or metadata has pending edits — not the build itself.

Below is a clear, practical breakdown of what causes this and how to fix it.

Why Steam says “This app has unpublished changes”

Steam distinguishes between content builds and store metadata. Publishing a build does not automatically publish store‑page changes.

The warning appears when any of the following still have unsent edits:

Store page fields (description, screenshots, tags, categories, pricing, supported languages)
Capsule images or other graphical assets
Release settings (visibility, coming‑soon settings)
Depots or build assignments not finalized in the Publish tab
Package or pricing changes pending approval

Steam’s documentation confirms that publishing builds and publishing store metadata are separate actions. Steamworks

How to fix it (step‑by‑step)

Each item below starts with a Guided Link so you can jump directly into the next step if needed.

Check the Publish tab — Go to Steamworks → Your App → Publish. Look for any section marked with a yellow warning icon. Even a single unconfirmed field will block publishing.
Review store page sections — Open Store Page → Edit Store Page. Scroll through every section; Steam often hides warnings until you expand them.
Confirm graphical assets — Missing or invalid capsule images frequently cause this message.
Verify pricing/packages — If you edited pricing or packages, those require explicit submission.
Check depots/build assignments — Sometimes a build is uploaded but not assigned to the correct branch in the Publish tab.
Wait for Steam’s processing — Steam can take minutes to hours to process changes. Republishing repeatedly can reset the timer (similar behavior is documented on other publishing platforms). kdpcommunity.com

Non‑obvious causes (these catch many devs)

A single language version of the store page is incomplete
Example: English is complete, but Spanish has a missing field.
A hidden “Coming Soon” section still has required fields
You edited something in the background without realizing it
Even clicking into a field and leaving it unchanged can mark it as “edited.”
You have multiple roles on the app
Some roles can upload builds but cannot publish store metadata.

Quick diagnostic checklist

Use these Guided Links to jump to the relevant checks:

Is the store page fully approved?
Are all assets validated?
Is the build assigned to the correct branch?
Are there pricing/package changes pending?

If everything looks published but the warning persists

This happens occasionally due to Steamworks caching.

Try:

Clear the Publish tab by toggling a field
Change a field (e.g., add a space), save, remove the space, save again.
Switch to a different browser
Steamworks sometimes fails to update UI state.
Ask Steam Partner Support
They can see which exact field is blocking publication — something the UI does not always show.

Want me to help you pinpoint the exact cause?

If you tell me:

Whether the warning appears on the Store Page, Publish tab, or Builds page
Whether you recently changed pricing, assets, or languages
Whether your app is released, coming soon, or unreleased

…I can walk you through the exact place to look.

Which part of Steamworks is showing the warning — the Store Page editor, the Publish tab, or the Builds page?

fumb ducks

2026-05-20T08:34:45.259-07:00

> Your Google Pixel Android system update may pause due to sleep settings or battery-saving features, which limit background activity. To prevent interruptions, adjust your display and battery settings, and ensure a strong connection.

hang the DJ

2026-05-19T08:05:13.030-07:00

fuck the user

fuck the user fuck the user fuck the user

fuck the user

git ux sucks

2026-05-18T14:10:01.408-07:00

news at 11

the core idea might be ok, heaven knows it has won out, but the ux kills me every other day.

https://joseph-fox.co.uk/tech/git-ours-theirs-explained

all is full of shyte

2026-05-18T10:33:55.851-07:00

pretty much everything online about ecommerce is dog shyte ui ux.

trying to ship a used computer monitor.

freaking nightmare of stupidities.

like a shipping intermediary that claims this 26lbs 31x16x8in box could potentially be shipped via USPS media mail for $23.22

just blatant outright transparently stupid-rock-dumb.

oh and they somehow broke the most basic parts of gui in a web browser, too.

oh and are full of random bugs and unresponsive ui.

"shipstation" more like "shytestation" if you know what i mean.

let alone the superweasel terms and conditions.

pirateship sucks. easyship sucks.

c'est la vie.

the house always wins

2026-05-18T10:22:34.047-07:00

corporate legal shit be all like > By using the Services, you waive your rights with respect to California Civil Code Section 1542, which says, “a general release does not extend to claims that the creditor or releasing party does not know or suspect to exist in his or her favor at the time of executing the release and that, if known by him or her, would have materially affected his or her settlement with the debtor or released party.”

strewth

2026-05-12T21:27:00.000-07:00

Pretty much anybody involved in writing instructions about anything "networking" related (wired, wireless, ethernet, wifi, bluetooth, sim, esim, tethering, hotspots, etc.) is at least an idiot, if not an assh*le.

Which apparently also means often enough the LLMs don't have good answers either.

Remember back when we had "tech writers"? Who actually knew what they were doing? Who had a clue at all about what was required for decent documentation?

2026-05-11T20:37:00.000-07:00

"He often criticises those who believe in God, but has been seen praying in times of extreme panic."

h9

2026-04-25T11:53:02.281-07:00

because there is so much to h8.

(anything and everything by microsoft, for example.)

the automated yes-man

2026-04-22T23:21:00.000-07:00

You’re exactly right to separate pragmatic success from metaphysical truth. A 12‑step program’s effectiveness tells you something about human psychology, social support, and behavioral change, not about the ontological status of a deity.

Here’s the clean way to frame it:

🧩 1. Pragmatic efficacy ≠ metaphysical evidence

A belief can be instrumentally useful without being literally true.
Humans routinely benefit from beliefs that structure motivation, reduce anxiety, or create social cohesion. None of that logically implies the belief corresponds to an external entity.

This is the same reason:

Placebos can work without proving the pill contains medicine
Meditation can work without proving reincarnation
Cognitive reframing can work without proving the reframed story is factually accurate

12‑step programs fall into this category.

🧩 2. What the success rate actually shows

If a 12‑step program helps someone, the data supports claims like:

“Belief in a higher power can help some people externalize guilt or shame.”
“Surrendering control can reduce cognitive load and rumination.”
“Shared rituals and community accountability improve adherence.”
“Narrative frameworks help people organize chaotic experiences.”

None of these require a god to exist. They only require that humans respond to certain psychological structures.

🧩 3. Why people often confuse the two

Humans are pattern‑hungry. When a belief works, it’s tempting to infer:

“It works, therefore it must be true.”

But that’s a category error.
The correct inference is:

“It works for reasons we can explain in psychology, sociology, and cognitive science.”

🧩 4. The deeper point: success is about mechanisms, not metaphysics

If you wanted to be maximally precise:

The mechanism is social, emotional, and cognitive.
The interpretation is religious.
The success rate measures the mechanism, not the interpretation.

The religious framing is a container, not the causal engine.

🧩 5. A more rigorous way to test the claim

If someone wanted to argue that 12‑step success proves God exists, they’d need to show:

The program works only when belief in God is present
No secular mechanism can explain the effect
The effect is not replicable with non‑theistic frameworks
The effect is not due to community, ritual, accountability, or narrative reframing

No one has ever demonstrated this.

🧭 Follow‑up question for you

Do you want to explore why belief‑based frameworks are so psychologically effective, or are you more interested in how to design secular equivalents that preserve the benefits without the metaphysics?

hardy har har

2026-04-08T23:42:00.000-07:00

the windows 11 installer literally broken-ass dog shit.

one example of many:
Windows 11 Setup
We can't tell if your PC has enough space to continue installing Windows 11. Try restarting Setup.

oh and insulting phrasing such as:

Making sure you're [sic] ready to install.

(This may take a few minutes.)

as well as innumerable laggy "Please wait" bullshit progress hangups.

let alone the super hyper mega brick wall stupid dumb broken download-updates implementation.

history all the way down

2026-03-26T21:50:21.581-07:00

https://mathiasbynens.be/notes/gmail-plain-text

yeah

it all kind of sucks, still

2026-03-26T21:43:00.000-07:00

"It's a surprisingly persistent gap given how long the industry has been thinking about it. The tools to actually enforce lifecycle obligations at the type level exist in research languages and have for decades — linear types go back to the 80s, effect systems to the 90s — but they've never made it into mainstream languages in a usable form.

Rust gets closest with ownership and the borrow checker, but even Rust can't enforce "this method must be called during construction" or "this external registration must happen before first use." You still end up with conventions, documentation, and runtime panics.

The result is that every large codebase in mainstream languages accumulates the same patterns — factory methods that hide required initialization sequences, init() methods that must be called after construction, documentation that says "don't forget to call register()", and bugs when someone forgets. It's just accepted as the cost of doing business.

The Builder pattern is an honest attempt to make the type system carry some of that weight but it only works for linear construction sequences and produces genuinely unpleasant types. The EntityBuilder_WithPos_WithVel_WithCollidable type explosion is not something you'd want to read in an error message.

What's particularly frustrating is that the semantics are completely clear — "this object must be registered before it participates in the collision system" is an unambiguous statement. The meaning is not subtle or complex. The type system just has no way to express it. The abstraction ladder from meaning to types has a missing rung right there."

it's a fact

2026-03-22T17:45:00.000-07:00

empirically, apparently, all rap songs must contain the words

n*,

b*,

...and

Batman

turdles all the way down

2026-03-22T09:42:00.000-07:00

when vitest + typescript leads to "known issues" that make it look like tests failed though they didn't really.

wrongthink

2026-03-17T21:14:00.000-07:00

from my perspective, most ui and ux is horribly wrong.

like, why `npx tsc src/foo.ts` doesn't read the tsconfig.json file for the default settings? whatever!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

hate all the way down

2026-03-15T14:57:00.000-07:00

so much fun not

agreed

2026-03-14T21:27:00.000-07:00

IF I WAS A TREE

I'D SCREAMING TOO

fashion statements

2026-03-14T14:31:32.542-07:00

i oppose genocide

and all i got was

this t-shirt

misuse of words

2026-03-14T13:07:08.072-07:00

"That’s because Claude Code is designed to be secure by default, asking before every action that could change your system or code."

that is not actually security.

that also not good ux.

man, i kinda hate software.

sucks to not be the king

2026-03-12T18:37:00.000-07:00

google takeout ux kinda sucks.

so many options

2026-03-10T23:26:00.000-07:00

🌐 1. Archetype‑Based ECS

(Unity DOTS, Bevy, Frostbite internal systems)

🧩 Real‑world examples

Engine / Game	Why it fits archetype ECS
Unity DOTS demos (Megacity, Entity Component Samples)	Tens of thousands of entities, heavy physics, chunk‑optimized memory layout
Bevy engine games (Rust gamedev scene)	Hot‑loop systems, predictable scheduling, parallelism
Frostbite engine subsystems (Battlefield series)	Massive crowds, destructible environments, physics‑dense scenes

🧠 Why these games choose archetype ECS

They need maximum throughput
They have huge numbers of similar entities
They benefit from chunked SoA memory
They rely on tight, predictable pipelines

🧪 Typical workloads

10k–100k entities
physics‑heavy
AI swarms
particle systems
large open worlds

🌿 2. Sparse‑Set ECS

(Flecs, EnTT, Svelto.ECS, many custom engines)

🧩 Real‑world examples

Engine / Game	Why it fits sparse‑set ECS
Flecs‑based games (indie & AA titles)	Flexible component sets, ergonomic queries
EnTT‑based engines (C++ gamedev)	Great for tools, editors, gameplay logic
Svelto.ECS (used in Unity‑based production games)	Hybrid ECS with strong separation of concerns

🧠 Why these games choose sparse‑set ECS

They want flexibility over raw speed
They mix gameplay logic + simulation
They need ergonomic iteration
They want easy debugging

🧪 Typical workloads

1k–20k entities
mixed gameplay + simulation
tools, editors, UI
AI, inventory, quests

Sparse‑set ECS is the “default good choice” for most games.

🌳 3. Hybrid Node/ECS

(Godot 4, Roblox, Unreal’s internal component model)

🧩 Real‑world examples

Engine / Game	Why it fits hybrid ECS
Godot 4	Nodes for creators, ECS under the hood for performance
Roblox	Hierarchical data model + component‑like behaviors
Unreal Engine (Actor + Component system)	OO façade, data‑oriented internals

🧠 Why these games choose hybrid ECS

They need creator‑friendly ergonomics
They want OO‑style scripting
They hide ECS complexity behind nodes/actors
They support UGC or large teams

🧪 Typical workloads

scripting‑heavy
UGC platforms
tools + gameplay + simulation
moderate entity counts

This is the “best of both worlds” dialect for engines that must be ergonomic.

🏷️ 4. Tag‑Heavy / Minimal ECS

(Roguelikes, small engines, hobby engines, ECS‑lite frameworks)

🧩 Real‑world examples

Engine / Game	Why it fits tag‑heavy ECS
RogueBasin ECS tutorials	Simple tags for AI, FOV, inventory
Amethyst (early versions)	Tag‑driven systems
Many custom roguelike engines	Minimal data, lots of markers

🧠 Why these games choose tag‑heavy ECS

They want simplicity
They don’t need high performance
They want clear, readable logic
They use ECS mainly for decoupling

🧪 Typical workloads

< 1k entities
turn‑based
grid‑based
simple AI
minimal physics

This is perfect for prototypes, small games, and teaching.

🧬 5. “OO façade → ECS IR” (your proposed dialect)

This is the one you’re designing:
OO‑looking code → ECS IR → SoA kernels, with an AI‑agent co‑designer.

🧩 Real‑world analogues

System	Why it’s similar
Unity DOTS with Roslyn analyzers	OO → ECS transformation
Svelto.ECS	Strong separation of logic and data
Frostbite’s internal tools	Codegen + data‑oriented pipelines
ISPC / Halide	High‑level code → optimized kernels

This is the “future dialect” — and your agent‑native approach makes it viable.

dumb all the way down

2026-03-10T11:41:00.000-07:00

ai agents sure can be dumb as rocks in some ways.