5 ms·
I'm happy for the person who wrote this because they've found a nice impedance match between themselves and Javascript. But I could have written almost the sam
by jgrahamc 15y ago
I'm happy for the person who wrote this because they've found a nice impedance match between themselves and Javascript. But I could have written almost the same article and substituted Google Go for Javascript (with some modifications).
The reality of much programming is that once you've got your set of tools, and a good familiarity with a language which helps you solve problems you're happy. You're happy because you're getting stuff done in a manner that you find elegant, or easy.
For example, I really like Go because it's C-like, with an OO paradigm that I'm comfortable with, lightweight 'processes', and neat communication. Also, builds and tests really, really fast. But you probably don't learn much more from me saying that other than "John likes Google Go because he's comfortable with it".
- BruceM 15y agoWell, given that I've seen 7-15 minute build times for 180,000 lines of code in a popular JVM language ... what I wouldn't give for Go-like build / test iteration times in that language. I think there's some value in your list of things that you like about Go. It gives others an idea of what they might be missing out on. (And for me with my work on Open Dylan, it gives me a nice target to aim for.)
- weavejester 15y agoOut of interest, is there any technical reason you'd want a JVM application with 180,000 lines of code?
- johncoltrane 15y agoNot the parent. But the people who signed the checks probably didn't care about those details ("We want a solution to our problem and a reassuring longterm support contract.") and the people who banked the check probably just passed the baby to whoever ended up writing/managing these 180,000 LOC.
- batista 15y agoIs there any technical reason why you would NOT? The JVM is a proven and stable platform, with nice tooling and exceptional support. It's also polyglot. And 180,000 LOC is not that much --it depends on the requirements. Perhaps you are thinking "I can do all that in 1/10 the size in language X", but chances are you are wrong. It's not about doing the same thing in the turing-complete sense, it's about doing the same thing in the real world sense. You might achieve the same functionality with less code. But can you achieve the same interoperability with other systems the company uses with that other language? Could you utilize the 20-something already existing dev team of JVM coders? Could you have the same support from the vendor? The same toolkits? The same performance characteristics? Etc etc...
- weavejester 15y agoAs a disclaimer, I wasn't intending to bait anyone. I'm genuinely interested if there are any reasons for writing a 100k+ LOC application, rather than dividing the functionality up between smaller applications and libraries. Operating systems like the Linux kernel are usually over 100k LOC, but Linus has made some compelling arguments about why you'd want a monolithic architecture in an operating system you want to be reasonably performant. But that argument doesn't appear to apply to server systems running under the JVM. Building an application out of small, interchangeable, independent components seems rather more sensible than one large monolithic architecture. My current hypothesis is that any server application over, say, 10K LOC is badly designed. I'm therefore quite interested in anyone who maintains or develops very large server systems, and if they could perhaps offer any reasoning why systems that large are the best solution. Admittedly this is a little off-topic, though :)
- JoachimSchipper 15y agoData point: nginx-1.0.14 has 124 574 lines in the src/ directory.
- ExpiredLink 15y ago> I'm genuinely interested if there are any reasons for writing a 100k+ LOC application, rather than dividing the functionality up between smaller applications and libraries. IIRC, Google has such 'large' settings (for whatever reason). All companies I've seen use the latter approach.
- RegEx 15y agoSorry for off topic, but do you have any recommended resources for learning Go? I've been curious for a while and I think I'd like to finally get my hands dirty with it.
- wollw 15y agoI've found that simply reading the documentation[1] was enough to get started. The package reference[2] was pretty easy to understand after going through it. I would also make sure you're running the current RC and using the information at http://weekly.golang.org/ http://weekly.golang.org/ as it's the most up to date and has some substantial differences compared to the stuff at http://www.golang.org/ http://www.golang.org/ [1]http://weekly.golang.org/doc/ http://weekly.golang.org/doc/ [2]http://weekly.golang.org/pkg/ http://weekly.golang.org/pkg/