mort96

5 ms·

91.
by mort96 2mo ago
It's categorically uninteresting until and unless that happens. Weird to release 1.0 without it. What are they waiting for?
92.
by mort96 2mo ago
How do you estimate the improved customer retention and improved future customer acquisition of something as nebulous as, "this does very little on its own but is a tiny part of making Microsoft software feel more robust in general&quo
93.
by mort96 2mo ago
No, but "this action consumes a potentially exhaustible resource and could therefore fail" is normally part of programming language semantics
94.
by mort96 2mo ago
The specification allows implementations to have limits on maximum call stack depth and all sorts of other things. It's absolutely semantically meaningful in C to allocate a new stack frame.
95.
by mort96 2mo ago
Of course. I wasn't talking about empty loops. But also, I wouldn't rely on a compiler to remove empty 'while (true)' loops.
96.
by mort96 2mo ago
If it's not encoded in the language's specification, it's not a feature of the language but just an optimization. You can't rely on optimizations for correctness.
97.
by mort96 2mo ago
That's not a type system thing... Whether a call gets TCO'd isn't represented in the type system if it's just an annotation on a return statement.
98.
by mort96 2mo ago
If the semantics of 'while (true)' was "will crash the program after an implementation-defined but often fairly low number of iterations", I would stop using 'while (true)'.
99.
by mort96 2mo ago
Mastodon works like email. Users have their data hosted on instances and most big instances can communicate with most other big instances, and all instances blacklist a bunch of other instances for spam or political reasons. Just like e-mai
100.
by mort96 2mo ago
I don't see the connection. The article is full of talk of servers: app servers, view servers, database servers, event log servers, ...
101.
by mort96 2mo ago
It wasn't actually meant to be a slight against designers, the choice to have a big background image is sometimes perfectly fine. You're a bad developer if you argue against it because it'll use some small amount of extra mem
102.
by mort96 2mo ago
Are you disagreeing just to disagree? My numbers are obviously not going to fit every app in every situation, but I think they illustrate a perfectly realistic use case For the text rendering thing, I think we're talking past each othe
103.
by mort96 2mo ago
Which, if you'll do the math, is more than a few kB
104.
by mort96 2mo ago
What do you mean by "windows doesn't share both"? Windows doesn't get a say, Intel iGPU systems literally don't have video memory
105.
by mort96 2mo ago
* I never said all software handles the swapchain itself. The front and back buffers are obviously not usually allocated in user code. But they're allocated nonetheless and contributing to memory usage. * Not every app is fullscreen, b
106.
by mort96 2mo ago
Because a big picture looks pretty sometimes? Not sure what you think "having an SVG renderer in memory" means exactly, typically the way an SVG renderer works is that you give it a huge chunk of memory and ask it to draw pixel da
107.
by mort96 2mo ago
That, plus markup, be it something XML/HTML-like or something Markdown-like.
108.
by mort96 2mo ago
Honestly if the image is of the current weather it kinda does. I don't mind e.g Apple's weather app design at all
109.
by mort96 2mo ago
Windows 98 wasn't composited, which makes a huge difference. And to be clear, there's a ton of unnecessary bloat today as well. It's just that even a lean and mean highly hand optimized native app is gonna be way bigger today
110.
by mort96 2mo ago
Yet they're the ones who get promoted because their KPIs are the best.
111.
by mort96 2mo ago
WAY lower resolution screens so pixel and frame buffers were a tiny fraction of the size, non-composited graphical environments which meant there was one fewer frame buffer per window, and a visual style which typically emphasized large pic
112.
by mort96 2mo ago
On disk yeah, sure. But you're gonna render them into a pixel buffer which lives in memory.
113.
by mort96 2mo ago
Pictures and frame buffers. If you're running fullscreen at 4k, you're probably gonna take two roughly 3840x2160x3 byte frame buffers for the window. Your designers want a background image which moves as you scroll in some paralla
114.
by mort96 2mo ago
Microsoft absolutely doesn't need it, but I'm guessing the weather app team (or the core filler apps team or whatever team is responsible for it) needs it to juice a metric to make some middle manager happy. And it makes the middl
115.
by mort96 2mo ago
Not reading standard attributes sounds like a bug in the screen reader software.
116.
by mort96 2mo ago
<button title="whatever">?
117.
by mort96 2mo ago
I haven't seen one in a kitchen in decades, other than extremely old ones. The touch control design is absolutely everywhere. At least here in Norway, where ~all stovetops are electric.
118.
by mort96 2mo ago
I hate it but I think the reason might be regulations? I have family who recently had to replace their stove setup, they used to have a combined oven + stovetop thing where dials on the front of the oven controlled the stovetop. They wanted
119.
by mort96 2mo ago
Exactly. The tooltip should be part of one line, not spread across 4 lines and 2 attributes.
120.
by mort96 2mo ago
No, having 7 lines for a simple button with hover text is horrible

More ›