Pay as you go is really going to make a difference

Arine arine123445128843 at
Thu Jan 16 19:38:21 UTC 2020

On Monday, 13 January 2020 at 18:22:19 UTC, H. S. Teoh wrote:
> On Mon, Jan 13, 2020 at 05:40:08PM +0000, Arine via 
> Digitalmars-d wrote:
>> On Monday, 13 January 2020 at 11:54:19 UTC, user5678 wrote:
>> > ( and other stuff too.
>> He's comparing two different technologies. If you want low 
>> input lag, get a TN panel gaming monitor with a high refresh 
>> rate. The thing is those cost $$$. All the while most of the 
>> devices he's testing are laptops. I'd love to a see a CRT 
>> display in a laptop. Read between the lines, that the author 
>> doesn't know what their doing.
> You're totally missing the point.  The point is to take a step 
> back at the current state of things and evaluate just how much 
> it (doesn't) make sense:

It does make sense. Software back then wasn't complicated, it 
didn't have to be. Developer time has remained constant. Software 
companies failed because they were trying to shoot for 
perfection. You can't create a perfect piece of software. You 
have to use the limited developer time you have to and allocate 
that time effectively. Not trying to reduce file size cause some 
UX designed that doesn't know what he's doing or talking about 
rants about it on his blog.

> 4) Technologically speaking, today we have enough processing 
> power to run AAA games that process hundreds of thousands of 
> objects per frame running at 60 fps.  We're talking about 
> things like *real-time raytracing* here, something completely 
> unimaginable in the 70's.
> Yes, all of this can be explained, and if you lose sight of the 
> forest for the trees, every step in the history of how this 
> came about can be logically explained. But when you step back 
> and look at the forest as a whole, the whole situation looks 
> completely ridiculous.  The necessary tech is all there to make 
> things FAR more efficient. The development methodologies are 
> all there, and we have orders of magnitude more manpower than 
> in the 70's.  What a word processor has to compute is peanuts 
> compared to an AAA game with real-time raytracing running at 60 
> fps.

Raytracing is just a marketing buzzword, it's exist for decades 
in games and it's been used in realtime for almost as long. 
That's the problem when you have people like you that don't 
understand what they are talking about, throwing things like. Oh 
we can do "raytracing" in real time then comparing that as if it 
means something because we can do that. GPUs have been doing 
operations like that for a long time, doing a lot simple tasks 
thousands at a time in parallel. But there's still a reason you 
can't run an operating system using a GPU. It's fundamentally 

> 5) Yet a browser app of today, built with said modern 
> technology with modern processing power, still runs just as 
> horribly slowly as a word processor from the 70's running on 
> ancient ultra-slow hardware, with just as horrible a lag 
> between input keystrokes.
> Yet here we are, stuck with a completely insane web design 
> philosophy building horribly slow and unreliable apps that are 
> barely a step above an ancient word processor from the 70's.

I use VS Code and Discord (both made using electron btw) all the 
time, there's no lag. It's probably more responsive than most 
bloated IDEs that weren't built using electron. Bad programs are 
going to be bad.

More information about the Digitalmars-d mailing list