News for hackers. Stuff that matters.
Re:I Bought Apple Silicon by ATsch on Friday December 18, 2020 @05:29PM (#25472866)
Given it's Jonathan Blow, I feel compelled to say yes.

More seriously, while program overheads have undoubtedly gotten higher, that's always been in exchange for something else, even if non-technical, like a better developer experience and platform support. Nobody writes slow programs on purpose, but people are very willing to trade it off for things that are more important in the grand scheme of things. Low level programmers love to smugly pretend that those tradeoffs do not exist but they do.

Re:I Bought Apple Silicon by zamfi on Friday December 18, 2020 @05:46PM (#25473014)
> Nobody writes slow programs on purpose, but people are very willing to trade it off for things that are more important in the grand scheme of things

Wait, of course they write slow programs on purpose, because "premature optimization is the root of all evil," right? A developer might use Electron because it's "fast enough" and halves your development time, and "fast enough" is always a perceptual metric, and not a technical one.

Faster hardware means even less optimization is needed before something is shippable -- great for developers! -- and a recipe for software continuing to feel just as slow as before, because we only optimize until it's "fast enough".

And despite the M1, or any of the advances of the last decade, the perceptual line that is "fast enough" hasn't changed.

EDIT: Yes of course Knuth was talking about optimizing noncritical paths, but the sprit he’s espousing lives on in system design: use electron, or something else that makes your product more maintainable and easier to understand (because you didn’t build your own bespoke cross-platform app scaffold, and electron is well-documented, etc.), until you’re sure you can’t anymore. Well, the bar for “can’t” is raised every time there’s more cpu to support rapid, maintainable, “nonoptimal” development, and here we are.

Re:I Bought Apple Silicon by doggosphere on Friday December 18, 2020 @06:00PM (#25473143)
> Wait, of course they write slow programs on purpose, because "premature optimization is the root of all evil," right? A developer might use Electron because it's "fast enough" and halves your development time, and "fast enough" is always a perceptual metric, and not a technical one.

That's not writing a slow program on purpose; that's accepting a tradeoff of speed for deliverability. Writing a slow program on purpose means intentionally adding code to make it slower with no other consequence.

"Fast enough" can be measured in ms latency for UX purposes. Ex: Websites test and benchmark themselves on load time because they know sales/pageviews decrease after too long.

Re:I Bought Apple Silicon by zamfi on Friday December 18, 2020 @07:49PM (#25473914)
> accepting a tradeoff of speed for deliverability

So...making a purposeful decision that results in your program being slower...is not “writing slow programs on purpose”? They’re definitely not slow by accident.

No one but artists (this is not a dig at artists, in fact I love them and teach them to program at an art school) would take “writing slow programs on purpose” to mean “adding useless code to slow things down”.

It’s all about making decisions that prioritize the perceived latency at the expense of anything else.

Re:I Bought Apple Silicon by cwyers on Friday December 18, 2020 @08:52PM (#25474259)
There is a difference between deciding "we don't need to be fast" and deciding "we need to be slow."
Re:I Bought Apple Silicon by Turing_Machine on Friday December 18, 2020 @10:53PM (#25474855)
Code that makes your software able to run on a completely different platform with minimal further development cost isn't "useless". Quite the contrary.

And you're not adding it "to slow things down". You're adding it to make it possible to run at all on the other platform.

Re:I Bought Apple Silicon by zamfi on Saturday December 19, 2020 @02:14AM (#25475750)
I guess I wasn’t clear — this is my point! You’re adding it because it has huge benefits, and one cost is it slows things down. You are still making an explicitly decision to use something that makes your app slower, no?
Re:I Bought Apple Silicon by baumandm on Friday December 18, 2020 @07:19PM (#25473717)
There's a significant difference in meaning between "write slow programs on purpose" and "write programs that are fast enough but not faster."
Re:I Bought Apple Silicon by dragonwriter on Friday December 18, 2020 @05:53PM (#25473077)
> Wait, of course they write slow programs on purpose, because "premature optimization is the root of all evil," right?

No, the first is not the meaning of the second.

Re:I Bought Apple Silicon by adrusi on Friday December 18, 2020 @06:05PM (#25473188)
Warnings against premature optimization suggest a two-pass strategy, where in the first pass you avoid trading increased performance for increased labor, and then in the second pass you do whatever is needed to make the performance good enough.

The faster the underlying platform, the less work is required to get to "good enough" performance, so this strategy absolutely leads to software not getting faster as hardware gets faster, and the only way for an end-user to get their software to run fast is to have faster hardware than is typical for the target market for that software.

I don't think it's much of a stretch to call a development paradigm that causes software to never get faster even as hardware improves "writing slow programs on purpose."

Re:I Bought Apple Silicon by dragonwriter on Friday December 18, 2020 @06:53PM (#25473561)
> Warnings against premature optimization suggest a two-pass strategy, where in the first pass you avoid trading increased performance for increased labor, and then in the second pass you do whatever is needed to make the performance good enough.

No. The argument against premature optimization is not about labor vs. performance tradeoffs (but about correctness and maintainability vs. performance tradeoffs), nor is it about the entire code base, but about non-critical elements.

Quoth Knuth: “Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%.”

Thinking about and designing for broad performance concerns even though it adds to initial implementation time is not against the adage; it’s when you are compromising clarity and ability to reason about the code to shave off microseconds on a path without a clear reason to believe that its going to be hit often enough that those microseconds matter in the big picture that you are engaging in premature optimization of the type targeted by the expression.

EDIT:

> I don’t think it’s much of a stretch to call a development paradigm that causes software to never get faster even as hardware improves “writing slow programs on purpose.”

If that is its explicit intent, sure; if it is a side effect, no. In any case, blaming such a paradigm on the adage against premature optimization is misplaced.

Re:I Bought Apple Silicon by adrusi on Saturday December 19, 2020 @12:23AM (#25475304)
You're right, I guess it's the cargo cult interpretation of "premature optimization is the root of all evil" that's the issue.
Re:I Bought Apple Silicon by zamfi on Saturday December 19, 2020 @02:16AM (#25475758)
That the adage was intended to address a narrower case does not invalidate your argument, friend!

People should, and do, make tradeoffs for maintainability over speed — and this is still choosing to make your app slow — whether Knuth meant it or not.

Re:I Bought Apple Silicon by zamfi on Friday December 18, 2020 @07:44PM (#25473876)
> No. The argument against premature optimization is not about labor vs. performance tradeoffs (but about correctness and maintainability vs. performance tradeoffs), nor is it about the entire code base, but about non-critical elements.

If true, I envy your ability to produce correct, maintainable code without labor!

Re:I Bought Apple Silicon by erik_seaberg on Friday December 18, 2020 @06:15PM (#25473289)
Part of the reason for writing the slow version is that you need to profile it to find out where the problems actually are, because intuition is not a very good guide. Some of the worst bottlenecks seem tiny but happen so frequently they add up, while a lot of things that sounded slow don’t actually matter.
Re:I Bought Apple Silicon by carlmr on Saturday December 19, 2020 @04:07AM (#25476226)
That's also the thing with premature. I would agree with you that premature is before you know what's slow. But if you have a CI Profiling run showing a few hotspots it's not premature anymore. Still people quote this adage.

Further there are things you should know are usually performance issues, that I would expect you to avoid entirely, except with good reason. Using O(N²) or worse algorithms on big collections when there are much faster alternatives in the standard library of your language for example. I don't think these good habits are premature optimization.

Re:I Bought Apple Silicon by jimnotgym on Friday December 18, 2020 @07:07PM (#25473646)
We are looking at Electron as a potential way to write once for all platforms, not least to be able to run on Mojave, Catalina and Big Sur without a breaking change every 12 months. The software is in the 'run once every few months' category, so for me the optimisation required is not anything to do with speed or memory usage, and more about not getting nailed by Apple's latest change of direction.
Re:I Bought Apple Silicon by matthewmacleod on Saturday December 19, 2020 @06:36AM (#25476786)
That’s nonsense though. Native Mac apps built years ago continue to work completely fine on the latest OS releases.
Re:I Bought Apple Silicon by Apocryphon on Friday December 18, 2020 @05:52PM (#25473069)
One wonders if VC-funded startups or "move fast and break things" firms like Facebook or Uber (as opposed to say '90s Microsoft or Sun or IBM or Bell Labs) becoming the vanguard advancing the cutting edge of some categories of software has created perverse incentives that reward this behavior. A cultural shift in Silicon Valley software development.
Re:I Bought Apple Silicon by ATsch on Friday December 18, 2020 @06:00PM (#25473152)
People used to talk about Java in the same way people talk about electron now so I feel like that's a definite no.
Re:I Bought Apple Silicon by nalekberov on Friday December 18, 2020 @07:04PM (#25473621)
Programs written in Java runs on top JVM. On the other hand programs written for Electron comes bundled with Chromium. And we all know how it manages memory.
Re:I Bought Apple Silicon by mapgrep on Friday December 18, 2020 @09:04PM (#25474323)
The JVM is fast today after 25 years of optimization and some serious improvements in the underlying processors (even with the Moore’s law failure of maybe half that period).

It was not fast at all when the Java hype was peaking in the late 90s. I knew a dotcom era startup that replaced a bunch of Perl with Java and my friends complained it had fewer features and was much slower.

Re:I Bought Apple Silicon by nalekberov on Saturday December 19, 2020 @07:12AM (#25476938)
Java's selling point was portability, and did it very well, it was faster than programs written in interpreted languages, well it was and still is slightly slower than programs written in C and likes.

Programs written on Electron rely solely on web technologies, I always avoid these programs, one simple chat application eats up to half a GB of memory, no I am not going to increase my machine's memory in order to run those programs.

Re:I Bought Apple Silicon by Apocryphon on Friday December 18, 2020 @11:58PM (#25475182)
One wonders how fast Electron will be in 25 years, if it lasts that long.
Re:I Bought Apple Silicon by sudosysgen on Friday December 18, 2020 @08:10PM (#25474021)
The relative penalty for using Java over C is so much smaller than Electron over Java or Electron over C
Re:I Bought Apple Silicon by Turing_Machine on Friday December 18, 2020 @10:51PM (#25474844)
For cases on the edge, the penalty for not using Electron is that you don't get to use the software at all, because the developer doesn't have the personnel or budget to port it to multiple platforms.

Real software that does a job you need it to do is much better than hypothetical software that will do the same job faster.

Re:I Bought Apple Silicon by sudosysgen on Saturday December 19, 2020 @02:04PM (#25480134)
That's not really true. There's very few software that wouldn't exist if it weren't for Electron.

You don't need to port Electron tier-software. This was a solved issue long ago. Code it in Java, Python etc... Or Use Rust/C/C++ and a cross platform toolkit.

Re:I Bought Apple Silicon by groby_b on Saturday December 19, 2020 @01:57PM (#25480057)
Given that people whine if an app costs 99 cents, and that a lot of people proudly copy commercial software without paying... Maybe it's not just developers at fault here.

There are plenty of devs who'd be happy to ship extremely high quality, small & fast code. It's just that very few people want to pay for it.

Re:I Bought Apple Silicon by zeroc8 on Monday December 21, 2020 @03:53AM (#25493233)
One of the problems is, that Microsoft failed to provide a decent native framework for their platform. WinRT/C++ now kind of fits the bill, but MS still doesn't seem to push it in any way. I've recently switched to the Mac and I'm learning Swift/SwiftUI/Metal right now. Apple has its act together, writing native platforms using those technologies is a dream come true.
Re:I Bought Apple Silicon by 0xCMP on Friday December 18, 2020 @06:33PM (#25473440)
> Given it's Jonathan Blow, I feel compelled to say yes.

This is also how I felt watching the video, but on the other hand I have a really hard time finding serious faults with his point.

HN keeps things light. My personal website is super light. But the product I work on? What's a few MB gzipped down to less than a MB? 100ms? 300ms? Who can tell the difference[0].

[0]: I can, but certainly not the people who the feature matters to much of the time.

Re:I Bought Apple Silicon by hadsed on Friday December 18, 2020 @07:55PM (#25473952)
And even if you could, you're getting more value by getting that thing sooner. Or an even better argument: in the end, maybe it took just enough resources at the quality you got to even be born in the current market.

Yeah most things are frivolous... you can survive without a better camera in your phone for another year. But that ham-fisted implicit cultural aspect is what also brings people medical devices 5-10 years sooner than it could have. We all know these gains compound over time. So maybe it's ok if our programs are a little slow. We buy the truly mission critical technology faster with that frivolity.

But I'll also say, I still get mad at my phone and throw it pretty often. Just the way it is.

Re:I Bought Apple Silicon by sudosysgen on Friday December 18, 2020 @08:13PM (#25474044)
It's not an either or. Cutting edge technology has always been a bit slow and rough around the edges. That's not an excuse for your chatroom client to use 450MB of RAM.
Re:I Bought Apple Silicon by ChrisMarshallNY on Friday December 18, 2020 @05:31PM (#25472892)
> Nobody writes slow programs on purpose

No, but we are in a place where most development projects are really "stitching" dependencies together, and those dependencies can get heavy.

On the other hand, this may help apps written in things like Ionic to speed up like crazy, because WebKit is now insanely fast.

Re:I Bought Apple Silicon by ATsch on Friday December 18, 2020 @05:55PM (#25473090)
> we are in a place where most development projects are really "stitching" dependencies together

Is there anything wrong with that, though? If there's any common thread in the history of computing, it's that progress happens when things become abstracted enough to allow for another layer of building blocks. That's not to say that those layers don't have a cost, or we don't need to learn how to do them well, but gluing together components is really all software development has ever been.

Re:I Bought Apple Silicon by ChrisMarshallNY on Friday December 18, 2020 @08:20PM (#25474094)
It's both good and bad; depending on how much care is taken in selecting dependencies.

It's hard to use a lot of dependencies, regardless of their quality, without introducing bloat. Lots of redundancies.

For example, each dependency may have its own messaging or thread management system, or its own memory management system.

Or it may include other dependencies that have their own "special sauce."

For myself, I use lots of little packages; mostly written by Yours Troolie, and only occasionally use third-party dependencies.

Each of my packages is usually crafted towards a certain discrete function, and has its own project lifecycle. I think that's a good thing about using dependencies. I believe that modules with encapsulated lifecycles are a good way to ensure quality (or not, if I "choose poorly," as the Knight Templar said in the Indiana Jones movie).

Re:I Bought Apple Silicon by geodel on Friday December 18, 2020 @08:50PM (#25474250)
> Nobody writes slow programs on purpose,

Well problem is developers are not writing fast programs on purpose. That they did not write slow on purpose but it nevertheless turned out to be slow is real problem to me as a user.

Re:I Bought Apple Silicon by flohofwoe on Saturday December 19, 2020 @09:25AM (#25477570)
> Nobody writes slow programs on purpose

True, but nobody writes fast programs on purpose either, only "fast enough" programs. The optimization work stops as soon as it "feels" fast enough and, this "feels fast enough" has been the same over the last few decades no matter how fast the underlying hardware is. Any advance in hardware will ineviatably be eaten by software within a year or two. That's why running old software on new hardware feels so increadibly fast.

I also disgree that we got better developer- or user-experience out of the "deal". Most commercially developed applications have a "peak version", but still continue to be stuffed with new features that nobody asked for. E.g. name one feature that was added to Microsoft Word, Outlook or Excel in the last two versions which really added to the "user experience".

Re:I Bought Apple Silicon by sigotirandolas on Saturday December 19, 2020 @05:29PM (#25481868)
Not just old software, but with a lot of open source software you usually have a spectrum of choice between more basic, lightweight software and more elaborate, heavyweight software. Think LXDE vs XFCE vs KDE vs Gnome as desktop environments, or nano vs Sublime vs Code/Atom vs IntelliJ as text editors, for example.

However, when it comes some software areas prone to capture, there's not only no choice, but rather a multitude of incompatible-by-design options. Due to WFH, I need to have four different bloated chat/videoconference software on all the time which all offers the same features to me. When I want to watch a live stream, I need to open YouTube or Twitch or Facebook Live which all offer the same basic functionality but no one is interested in standardizing their interface so I can just point my familiar video player to it (at least without it breaking all the time due to cat-and-mouse fights between the platform and open source developers).

I'm not generally in favour of regulation, but mandating some basic degree of interoperability so platform and software can compete separately seems like the only option.

Re:I Bought Apple Silicon by eivarv on Friday December 18, 2020 @06:15PM (#25473283)

    More seriously, while program overheads have undoubtedly gotten higher, that's always been in exchange for something else, even if non-technical, like a better developer experience and platform support.
Software architecture usually entails trade-offs in many directions, between NFRs, etc. – but it feels to me like the intepretation of the performance-scale (as well as developer experience, really) is warped by two things:

- Many devs aren't familiar with the real breadth of possibilities and discount some approaches without understanding them (using "developer experience", "platform support", and "too low level" as excuses), thereby skewing towards familiarity and preference. As most devs are familiar with web tech, this tends to win out. Other legitimate issues might not be even be understood (HCI, attack surface, accessibility, etc.)

- The performance hit might not be significant enough to notice on a dev-grade machine (e.g. M1-processor, 32GB of RAM, etc.) and/or in isolation, but will become noticable when regular users run several apps built using the same heavy stack.

The latter is particularly apparent if you try to run multiple Electron-apps simultaneously on a low-to-medium specced laptop – which I find pretty egregious as a user, as multitasking computer systems has been a thing for a while now.

My interpretation is that many people (or companies) will usually write software that's no more performant than what they can get away with – which can be summed up, if cynically, as "users won't see any major performance gain or increase in capability in their day-to-day usage because of shitty software."

Re:I Bought Apple Silicon by zarkov99 on Friday December 18, 2020 @07:23PM (#25473739)
The thing is the tradeoff makes more sense for the developer, who gets his job done quicker, than to the customer who pays for the sloppy bloat every time he uses the software.
Re:I Bought Apple Silicon by curyous on Friday December 18, 2020 @07:01PM (#25473605)
Slow code is usually written due to ignorance rather than choice. Lots of people only know OOP, which is slow and unoptimisable by default.