wtetzner (u/wtetzner)

wtetzner commented on Go is still not good blog.habets.se/2025/07/Go... · Posted by u/ustad

grey-area · 6 days ago

There’s probably no deep reason, does it matter much?

wtetzner · 6 days ago

Having to wrap a loop body in a function that's immediately invoked seems like it would make the code harder to read. Especially for a language that prides itself on being "simple" and "straightforward".

wtetzner commented on FP8 is ~100 tflops faster when the kernel name has "cutlass" in it twitter.com/cis_female/st... · Posted by u/limoce

mcculley · 2 months ago

I was surprised to see “AAAA”. I didn’t know there were 4 As now.

“AAAA Game Studio shits out another unoptimized clunker” seems a paradoxical statement to me. I would have thought “AAAA” meant “highly resourced” game company. Does it just mean high revenue? Lots of players?

wtetzner · 2 months ago

AAA/AAAA just means "how much money was spent developing the game". High cost doesn't automatically equal high quality. In fact, it seems after a certain point to mean the opposite.

wtetzner commented on FP8 is ~100 tflops faster when the kernel name has "cutlass" in it twitter.com/cis_female/st... · Posted by u/limoce

monkpit · 2 months ago

You’re looking as a dev, but the reality is that a consumer cannot see technical debt. If the studio churns out a game, the vendor sprinkles on some optimizations, people play it and move on, then the tech debt just vaporizes into the void. It’s not real at that point.

wtetzner · 2 months ago

Just because a consumer can't see technical debt doesn't mean they aren't paying for it. Most game studios continue to re-use code, so it doesn't just "vaporize" into the void.

wtetzner commented on Bill Atkinson's psychedelic user interface patternproject.substack.c... · Posted by u/cainxinth

jekwoooooe · 2 months ago

Without rigorous science and licensed professionals it would be insanity to take these drugs. They can potentially PERMANENTLY traumatize your brain possibly even _literally_ ruining your entire life. I guess that risk is worth it for some people

wtetzner · 2 months ago

I mean, so can alcohol.

wtetzner commented on Meta-analysis of three different notions of software complexity typesanitizer.com/blog/co... · Posted by u/ingve

prospero · 2 months ago

Show me a software developer who isn’t an end user for someone else’s code.

wtetzner · 2 months ago

This feels like it missed the point.

Hickey's approach is relevant in how the software is constructed, and Tellman's is relevant to the user experience. Both approaches are useful for a single application.

wtetzner commented on Web designs are getting too complicated websmith.studio/blog/webs... · Posted by u/parkcedar

tokioyoyo · 3 months ago

Websites in 1990s and 2000s did not have UX flows that we have nowadays. Yes, most of it is extremely bloated. But some of the flows we have right now, would just not be possible with the 2000s components. There are also billions of more people browsing the web nowadays as well.

wtetzner · 3 months ago

I'm curious about which flows you mean.

wtetzner commented on Web designs are getting too complicated websmith.studio/blog/webs... · Posted by u/parkcedar

croes · 3 months ago

Bad performance makes even good design bad but good performance doesn’t make bad design good.

Looking at performance is making the second step before the first.

Performance is the means to an end, but if you fixate on performance, the means becomes the end

wtetzner · 3 months ago

> Looking at performance is making the second step before the first.

I'm not sure I agree. Bad design can ruin a fast UI, and bad performance can ruin a good UI. I'm not sure one is more important than the other, because they're necessary parts of the UX. They should be designed for together, not independently.

wtetzner commented on Deep learning gets the glory, deep fact checking gets ignored rachel.fast.ai/posts/2025... · Posted by u/chmaynard

r3trohack3r · 3 months ago

Dude. I just asked my computer to write [ad lib basic utility script] and it spit out a syntactically correct C program that does it with instructions for compiling it.

And then I asked it for [ad lib cocktail request] and got back thorough instructions.

We did that with sand. That we got from the ground. And taught it to talk. And write C programs.

Never mind what? That I had to ask twice? Or five times?

What maximum number of requests do you feel like the talking sand needs to adequately answer your question in before you are impressed by the talking sand?

wtetzner · 3 months ago

I don't think it has anything to do with being impressed or not. It's about being careful not to put too much trust in something so fallible. Because it is so amazing, people overestimate where it can be reliably used.

wtetzner commented on (On | No) Syntactic Support for Error Handling go.dev/blog/error-syntax... · Posted by u/henrikhorluck

dlisboa · 3 months ago

I understand how that seems logical in isolation but it's just not how syntax is usually read by people. It's done so as part of a reading context instead of as separate syntatical tokens. The underlying idea is not the same for the reader because the context is vastly different.

wtetzner · 3 months ago

This feels disingenuous. I have a hard time imagining a case where someone would find this confusing.

wtetzner commented on (On | No) Syntactic Support for Error Handling go.dev/blog/error-syntax... · Posted by u/henrikhorluck

arccy · 3 months ago

and this is how rust gains its reputation as an ugly to read language with inconsistent syntax: design by committee

wtetzner · 3 months ago

Ugly is subjective, but which part of the syntax is inconsistent?

u/wtetzner

KarmaCake day4999November 6, 2010View Original