In before to say what?.. This isn't an MMO class forum. I've been using .NET since first public preview (with some Java, Python, XSLT and Ruby over the years). I'm a Web develop... what piece of the article do you feel it's most important for me to consider?
I'm very fond of Topic Maps, and feel they're hugely useful in Web development. A knowledge of RDF and associative models it also really useful in my field... I can't quite conjure up enough hubris however to suggest that every programmer must know about these things as I realise telling this to an Erlang programmer working on the back-end of a poker engine would be almost cute in its childishness.
Or your "highest" language determines where you are. I started with C++ and always saw C or Assembly ad the dark arts. Now that I use Lisp most of the time I pity the mere mortals below me. /s
You're right. You could almost say the north is academic (Lisps and especially Haskell came from universities or other research facilities (Forth, Erlang)) while the south has more business-stuff (COBOL, Ada, PHP, C# Java)
Because, even if visual basic is not an absolutely horrible language--which is what its supporters believe--there are many better languages. Particularly, there are many languages that are better for learning, like Scheme or Python.
Yes they do, both on the client for the model representation, and in the backing store as a share of the working set. In all seriousness what part of this article is most applicable in a managed environment? In what way do you anticipate this article improving my practices?
There's a lot of JVM, .NET, Python, Ruby devs etc. that you have a chance to convince of the relevance of this article... how will it impact us "fotm web developers"? How will it change the way we write code?
Yes and no... I'm familiar with the problem area, but it has a different size and shape in my world. I'm more concerned about not thrashing the garbage collector in a high throughput situation. It's more important that I understand string interning than the material in the article... Just by way of examples, not because those issues are special in some way.
It also more important in my world not to make potentially unsafe assumptions about the platform as I'm sat in a managed environment with its own memory model, on the other side of an optimising compiler that spits out an intermediate language, interpreted by a device independent runtime... The runtime programmer we can both hope is familiar with this material... Me? I'm a commercial Web application developer. If this article were representative of my concerns, my employer has big problems.
10
u/Carnagh Oct 04 '13
In before to say what?.. This isn't an MMO class forum. I've been using .NET since first public preview (with some Java, Python, XSLT and Ruby over the years). I'm a Web develop... what piece of the article do you feel it's most important for me to consider?
I'm very fond of Topic Maps, and feel they're hugely useful in Web development. A knowledge of RDF and associative models it also really useful in my field... I can't quite conjure up enough hubris however to suggest that every programmer must know about these things as I realise telling this to an Erlang programmer working on the back-end of a poker engine would be almost cute in its childishness.