3 ms·
This is supposedly the Pro model. Until my video processing and compile times are instantaneous, there's always room for performance increases. Phil Schiller s
by jacquesc 10y ago
This is supposedly the Pro model. Until my video processing and compile times are instantaneous, there's always room for performance increases.
Phil Schiller specially blamed RAM battery drain for it being limited to 16GB. http://www.theverge.com/2016/10/28/13460496/apple-macbook-pro-16gb-ram-battery-life-phil-schiller http://www.theverge.com/2016/10/28/13460496/apple-macbook-pr...
- mpweiher 10y agoYour compile times not being instantaneous is not a hardware problem and will never be solved by throwing hardware at it. "Software gets slower faster than hardware gets faster" -- With's Law. I just ran some experiments with tcc: it compiled + ran 300KLOC in around 0.158 seconds. My system cc (clang+llvm) took 9.3 seconds, so roughly a factor 60 difference. And clang+llvm is considered fast by today's standards, languages such as Scala or Swift are typically at least an order of magnitude slower than that. So compile times will improve when we make it a priority.
- jacquesc 10y agoI agree. The age of hardware performance gains papering over software optimizations is definitely over. The developer world has to get used to it. People also run a lot of code that "compiles" (not strictly converting to binary). Transpiling js, packaging assets, or just running spec suite. Any small performance we can get is much appreciated and over 2-3years will add up to something significant (justifying a large cost, which I never had a problem paying the Apple premium price).