Some late-night reading on the Necronomicon?
Some late-night reading on the Necronomicon?
I am currently a software engineer at Google, where as a member of the Android platform team I build frameworks and user interfaces.
The blog here at dsandler.org is mostly historical; you can find more recent posts on Google+.
Some late-night reading on the Necronomicon?
Atari industrial design sketches.
This stuff is just awesome:
The 70s graphic-design nostalgia is wonderful, but even beyond that,
these are simply visionary. (Memo to self: It’s easy, in retrospect,
to be considered to have been visionary, if you happened to be at the right
place at the right time, with the opportunity to make those visions
real.)
(It’s also interesting that the Atari ID guys included plenty of teapots
(err, “pretty girls”) in their sketches. Gotta write an article on teapots
some time.)
Almost as interesting: major rumors about
forthcoming Palm handhelds and OS 5.
This is a true gem. From MSDN:
Visual
Studio .NET: Managed Extensions Bring .NET CLR Support to C++
Excerpt: (emphasis mine)
Where Are We?
Unfortunately, as powerful and flexible as managed C++ is, it’s not the native
language of .NET, which means that books, articles, courses, code samples,
and so on, are not going to be written in managed C++-they’re going to be
written in C#. But this should come as no surprise. C++ has never been the
native language of any popular platform. Unix and Win32 have C. The Mac
has Pascal. NeXT had Objective C (of all things). COM has Visual Basic. Only the BeOS has C++ as its
native language, and when was the last time you wrote any BeOS code?
The fact that .NET favors C# merely means that another language will be
translated into the C++ equivalent, as has been done since 1983.