3 ms·
>It's harder to remove bottlenecks from mature applications than it is to plan ahead for the target platform and common use cases. I disagree. It's easier to r
by vortico 8y ago
>It's harder to remove bottlenecks from mature applications than it is to plan ahead for the target platform and common use cases.
I disagree. It's easier to release first and change what you need later, since there might only be 1-10 sections of code that need to be changed. Python is extremely fast to write, maybe 3x faster than C. This means you can get seed funding and sales faster, and if the idea is good enough to get a decent salary, you can just hire out optimization for a v2 release. It also allows your application to appear to get better over time, which makes long-term customers happy.
- agentultra 8y agoFor a typical SV B2C web application, sure, but we're talking about developing applications for a low-power device. Knowing your target platform and your end goals can aid in planning. Planning your architecture ahead of time can save you from having to optimize later... and often optimizing later is harder than simply doing the easy, right thing first.
- vortico 8y ago"Low power" or "slow CPU" has nothing to do with it. When you have a bottleneck (GTK, X11/Wayland, video drivers) that is 100x more significant than the binding language (Python), switching languages will only buy you 1% speedup at best. I'm not saying to go forth unplanned. I'm saying that using C over Python in this case is a waste of time.