3 ms·
Another huge difference was how slow compilers were. Programming is a completely different task when you don't mind hitting compile. I remember programming as a
by gmarx 10y ago
Another huge difference was how slow compilers were. Programming is a completely different task when you don't mind hitting compile. I remember programming as a kid in the 1980s with my older brother. He would hit compile and we would wait and wait and wait and finally get an error. After a few times he would slam his fists on the keyboard in frustration.
These days I sometimes compile rather than looking up the correct syntax for something.
Fast cycles changes everything. When you don't get up for a cup of coffee during compiles you program differently, learn about your code differently and can think abiout high level design more
- jandrese 10y agoYou can always add Boost to your project if you pine for the days of slow compiles.
- gmarx 10y agoHaha- I couldn't be happier to be rid of it. I used GWT for a couple of projects. It's a good useful thing but it was like being back in the 80s (or mayber early 90s)
- NotSammyHagar 10y agoGoogle Web Toolkit was great for putting your java in your javascript. Those were the days. I didn't really know Java or JS that well but I could write stuff! We actually used it for projects at Google. Plus anything interesting in java was always not implemented in GWT.
- gmarx 10y agoWhat, is that project gone? I used it recently. I'm too lazy to learn javascript
- ghaff 10y agoAt the risk of dating myself, when I took my first (FORTRAN) programming course in college, you ran batch jobs from punch cards. Make more than a couple mistakes and you were out of CPU time. This involved begging the grad students running the facility for additional CPU time which they grudgingly gave while making it clear what they thought of freshmen who couldn't get a program right on the first try. :-) The school swapped out the IBM 360 for a VAX a year or two later.
- return0 10y agoMaybe that's what people are missing: the emotional thrill of it. How often do you find yourselves fixing a bug for days and nights? Almost every possible bug is now a few web searches away.
- rabidrat 10y agoI frequently find myself frustrated by a bug for days and nights and too often eventually have to just work around it. Only the most common bugs are searchable. The rest are clouded by layer after layer of unnecessary dependencies.