Link to Original Source
COBOL is a hipster programmer's dream!
I remember when Perl was the workhouse behind all custom web server development. One of the few times I had "fun" writing code. Such a cryptic looking language that made perfect sense the moments you are writing it and completely alien days later.
Multi-process is the scalable architecture of choice. You get the same advantage of utilizing all available cores within a given hardware context as well as the ability to expand across multiple hardware contexts. Hardware still gets limited eventually by memory, cores, network throughput, disk, etc. Multi-process allows you to utilize more pieces of hardware to scale up your system.
Multi-threading unnecessarily complicates the ability to develop, debug and maintain a program and is still limited within the hardware context it's running. If you want real, scalable performance that isn't bottlenecked by cores, memory or other hardware context limitations, design for multi-process architectures.
How many Bio-chemists or Doctors do you know that are college drop-outs?
The whole "drop out" is a farce rationalization by people looking for an easy way to financial wealth. Almost always you have technologists, business or artistic type people used as "successful" examples of the whole "college doesn't matter" supporters which makes sense because the actual skill and resources used to be successful in those kinds of ventures can be learned outside of college with resources readily available for those interested in those particularly career paths. Bandwidth, paints, computing hardware, brushes, ideas are all readily available at the individual's fingertips; all that's needed is vision, passion, persistence and hard work.
You can't and won't learn bio-chemistry or how to do surgical procedures at home as is true with many ventures. And the reality is most people won't have the fortune of great ideas, capital and luck timing to realize an amazing idea that turns them into independently wealthy, successful "drop out" examples.
Yes, there are examples of people who have become wildly successful while being a college drop-out in certain fields. What will still be required for even those rare examples is hard work, focus, persistence in the face of adversity and fortuitousness timing which most "drop out" enthusiasts are most likely looking to avoid and skip to the "successful" part.
Linux is free yet still hardly registers as a blip on the Desktop radar. It's only been recently with the standardization of Android as the smartphone platform of choice has Linux finally gained significance to the general consumer outside of the server room and enthusiast crowd.
Widespread adoption requires standardization.
I imagine something wireless that doesn't require a physical connection. I personally love my remote/keyless entry and start and want to extend that convenience to the interface with my smartphone to my in-dash output. I don't want to have to manually plug anything in or fetch a cable. Just simply the presence is enough to activate.
Fair point. A voice activated UI system would complement this nicely for this particularly situation.
I view it as something akin to HTML which is versatile and flexible without being company/brand specific. In this case, there are many different parties involved. Making it "free" like Linux just causes fragmentation and won't create the adoptive critical mass to make it useful for the general population.
That was my original thought, but, that can just as easily become obsolete in the future when it's some other computing device we haven't imagined.
The point I'm really pushing for is to create a useable interface with devices, known and known, that has a chance to resist obsolescence.
Car companies and tablet/computer/smartphone companies should work on a standardized touchscreen API. Car companies then install a general purpose touchscreen that is activated and controlled by whatever tablet or smartphone device the user currently has in her possession.
Uvlad Brolaf?! lol j/k
There's definitely things I'd like to go back and do better on every project I've been on (UO, TR, SWG, DDO, LoTRO, LoL).
Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them?