You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
(For the record, I don’t place myself in the top tier re understanding of speed or anything else. I am somewhere in the middle of that gradient between the 99.9% and the People Who Really Know.)
We see all this bad rhetoric claiming “system X is only 2x slower than native code therefore it’s fast”... but one must ignore rationalizations and look at the actual output, which is several orders of magnitude inefficient. Few people are willing to put 2 and 2 together here.
The most common objection to these points is "we write slow software because it lets us make things faster and more easily". I agree this is the common belief, but it's wrong. If development is so much easier, why is productivity approaching 0 over time?
Replies seem to be rat-holing on the old well-understood concept that software is slow. Yeah, we know, I have said that many times (and said to ignore that this time). What I am highlighting here is a deeper issue: programmers don't really know what computers are any more.
Speed is one dimension of understanding that's lacking; the picture of speed in programmers' heads is 2-4 orders of magnitude too slow. It's easy to see and understand this, which is why I brought it up. But it's not the only dimension of missing understanding.
To make the speed point again, for an attempt at clarity: Programmers have a picture of their computer, in their minds, that they use to figure out what to do. For 99.9%+, that picture is inaccurate: the imagined computer is 100x-1000x slower than the real computer.
This will result in software that's too slow, obviously. But it also affects what one thinks is possible, what one dares to imagine to do. That is the more important part. Humans are very example-based, and if our examples are wrong, where they lead us will be wrong too.
what change would you make though, assuming you're running a data intensive site, where speed is a concern? I don't disagree, just curious. I've been thinking a lot about this recently.
The whole web needs to be removed and replaced. There’s no small change.
So, what you're poking at here is programmers being OK with crappy performance because they have no idea of how fast things could be? Well, yeah, it's a thing. It could be because 99% of us work with databases and various ways of interacting with them. Lag is expected.
No, I am saying something more basic than that. Most programmers do not really understand what their computers are.
So, everyone should be programming in assembly?
Let's just start with "not Electron" and work from there.
I made a toy programming language that I only expected to be ~100x slower than things like C or rust and it was actually ~5000x slower actually testing speed directly is important
this article captures some of what i feel about writing slow software: it's a sign of poor craftsmanship, which speaks poorly for the program overallhttps://craigmod.com/essays/fast_software/ …
With all the efforts being put towards AI I have to wonder why it hasn't been steered towards optimizing code rather than prodding social networks.
In my experience, to belabor the metaphor, few people have actually seen 2 and 2, so they have nothing to put together. We don't often see examples of stuff that's truly fast, or truly small.
Maybe the problem are the tools we use to craft this software? You have examples like electron that allows to cheaply craft new products with the cost of really bad performance.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
