4 ms·
That's a brilliant answer. As someone who has worked supporting a commercial compiler, it never ceases to amaze me how companies will pay 6 figures per seat fo
by aidenn0 6y ago
That's a brilliant answer.
As someone who has worked supporting a commercial compiler, it never ceases to amaze me how companies will pay 6 figures per seat for development tools, and then install them on a 5 year old machine that wasn't fit for the title "workstation" when it was brand new.
- WalterBright 6y agoTrue, that does happen, but at Zortech we discovered that the professional segment of the market was not price sensitive for just that reason - the price of the dev tools was noise compared to the cost of developer time.
- dragonwriter 6y ago> As someone who has worked supporting a commercial compiler, it never ceases to amaze me how companies will pay 6 figures per seat for development tools, and then install them on a 5 year old machine that wasn't fit for the title "workstation" when it was brand new. Well, because the dev shop buys the dev tools, but general desktop IT buys the computers, with policies around limiting number of different builds in the organization for IT convenience, and distribution policies for new machines based on internal politics (if you are in th chain of command above the head of the unit in charge of the hardware, or politically connected to someone in that position, you and your staff can get newer, better machines, whether or not you have a real business need, and even if that means denying someone else with a real business need.) Or, at least, I've seen enterprise shops like that.
- userbinator 6y agoI wish companies would force developers to use much slower machines than they are normally given, so that they will be more efficient with what they do, since chances are that the majority of your users won't be running extremely high-end hardware either. ...and I'm saying this as a developer myself.
- aidenn0 6y agoI've visited customers where we hit "build" and then wait about 15 minutes for an incremental build of a project. Every day I was there they could have bought a faster machine with the amount of money they were paying me to wait for builds to complete. They were developing embedded software, so the "dogfooding their customer's machines" was non-sensical.
- vram22 6y agoVery good point. I've thought that about Google, starting years ago. Look at the Wave fiasco / failure. That would not have happened (at least due to reasons of unusable slowness) if your suggestion had been implemented there. And there are many other examples of their products needing more machine horsepower. On the contrary, they equip their developers with high-end machines. How dumb. It should at least be a mix of low and high-end, and should be made compulsory to test the products on low-end satisfactorily before release.
- pjmlp 6y agoIt still happens, see Android development experience with Studio and build times.
- vram22 6y agoYes, seen tangentially earlier, when I consulted to a startup using Android as one of the stacks. Happy I did not have to work on it, going by what I have read about its too frequent changes. Like the JavaScript framework du jour :) https://mobile.twitter.com/vasudevram/status/1270752659402706945 https://mobile.twitter.com/vasudevram/status/127075265940270...
- WalterBright 6y agoI always used an older, slower machine, and that was one of the reasons. Still do, my main machine is about 8 years old.
- LoSboccacc 6y agoIdk, waiting on a task kick me out of the zone real fast, and as I age it takes longer for me to get into it.
- golergka 6y ago> As someone who has worked supporting a commercial compiler, it never ceases to amaze me how companies will pay 6 figures per seat for development tools, and then install them on a 5 year old machine that wasn't fit for the title "workstation" when it was brand new. Well, now you often have an overreaction to this problem, when web developers work on their Javascript frontends and Electron applications on the latest, beefiest Macbooks and blazing fast internet speeds and get completely out of touch with what their end users might be using. (This comment was written on an i9, 64gb RAM Macbook Pro provided by my employer).