Nah. I like it where I am.
Nah. I like it where I am.
from the article:
Unicode has the entire gamut of Greek letters, mathematical and technical symbols, brackets, brockets, sprockets, and weird and wonderful glyphs such as "Dentistry symbol light down and horizontal with wave" (0x23c7). Why do we still have to name variables OmegaZero when our computers now know how to render 0x03a9+0x2080 properly?
uh yeah, Go allows you to use the full unicode just fine; on identifiers and everything - people should read the spec before making sensationalist comments that waste everyones time.
Let them use BSD were no loophole is required if that's what they want.
Eh... we do. Except that it's Apache 2.0, which is just like BSD but with an anti-patent-burn clause.
And BTW, parent post is spot-on.
I think your two issues are programming mindset (code today is structured and designed differently from code in the 80's - a lot of innovation is not in programming languages but in how programming is approached.)
Work from your Pascal experience:
- Learn Delphi, this will get you into Object Oriented languages while building off your Pascal experience - this gives you a strength to fall back on.
- Using Delphi, write various GUI applications, this will move you from a procedural style of programming to todays event-driven style of programming.
- Having mastered Delphi, move to C++; the two are similar enough to allow you to translate the concepts from Delphi into roughly equivalent C++.
- Write GUI applications in C++ to see how modern platform APIs work (Qt, win32, wxWindows, dare I suggest MFC?)
- Write a server-app in a few of those; don't bother with scaling any of it, but make sure the code elegantly handles any and all error conditions.
Then you should be in the modern world.
Just grab the Algorithm category and all its subcategories - unfortunately it does not recursively descent to grab all pages by itself nor does it categorize into chapters so this will be a bit of work:-(
When done, please share and post a PDF here, or if possible (even better) share the book so it can be printed and wikipedia can get its dues!
Audi HQ is in Ingolstadt,
Mercedes HQ is in Stuttgart,
BMW HQ is in Munich,
VW HQ is in Wolfsburg,
Porsche is in Zuffenhausen (which apparently is in Stuttgart).
I think that about covers German cars.
Why do you even bother, man?
So teach him assembler as a first language, and EVERYTHING else will look simple in comparison!
I think for many of us who grew up on home computers, Assembler was our first language; and we used it to write games and demos on C64 and Amiga's. Things don't get any simpler than assembly language (few concepts and a very finite set of instructions) and it's great for getting a gradual but very deep understanding for what a computer is and how it works. We did it in 68K and it was the ideal set-up for growing into higher-level languages (as it showed you what a higher level language is trying to help you with.) The problem with learning a higher level language first is you'll be too easily intimidated by lower-level concepts (pointers, call-stacks, hardware interfaces or just the way things are laid out in memory) and avoid those things for the rest of your career - I'm sure we've all seen the type of 'professional' programmer I'm talking about.
Having said that, the amount of shit ("work") you need to wade through to get anything done these days in assembler means it's no longer an option; definitely not for a "from-scratch" type of program, and definitely not for getting quick experimental results; so it's today pointless for teaching a kid how to code as he'll get bored before anything exciting happens (unlike the Amiga days when the code to get some copper bars going would fit on your screen.)
"Gotcha, you snot-necked weenies!" -- Post Bros. Comics