| |||||||||||||
Crowding out OpenBSDCrowding out OpenBSDPosted Nov 17, 2012 22:15 UTC (Sat) by cmccabe (guest, #60281)In reply to: Crowding out OpenBSD by mikemol Parent article: Crowding out OpenBSD
Someone should create a language that you can "write once, run anywhere." Radical to the max, dude!
That was a 90s reference, for you youngsters...
(Log in to post comments)
Crowding out OpenBSD Posted Nov 19, 2012 9:03 UTC (Mon) by ortalo (subscriber, #4654) [Link]
Hmmm, strictly speaking, it seems that this should even be a reference to the 70s and... C no?
BTW, note that C is the primary unifying factor between Linux and the BSDs in fact... and the main difference with the dominant proprietary OSes.
Crowding out OpenBSD Posted Nov 20, 2012 9:05 UTC (Tue) by cmccabe (guest, #60281) [Link]
One of Java's slogans was "write once, run everywhere."
I guess the implication was that C programs always required tweaking to run on platforms other than the ones they had been written on, and Java programs would not. Of course it didn't quite turn out that way in practice-- for example, Hadoop is mostly written in Java, and the process of porting it to Windows is still ongoing.
It's hard to find a free lunch in computing. Even harder to find a type of free lunch that someone else hasn't already spent years looking for.
Crowding out OpenBSD Posted Nov 20, 2012 11:52 UTC (Tue) by Cyberax (✭ supporter ✭, #52523) [Link]
Uhm. I've been running Hadoop on Windows for _years_. The main stumbling block is setting up an SSH daemon, but even without it you can use Hadoop for certain limited tasks.
Crowding out OpenBSD Posted Nov 21, 2012 21:33 UTC (Wed) by cmccabe (guest, #60281) [Link]
Yes, there's a branch of hadoop called branch1-win that has been modified to work well on Windows. There's a JIRA tracking its progress here: https://issues.apache.org/jira/browse/HADOOP-8645.
Crowding out OpenBSD Posted Nov 20, 2012 12:11 UTC (Tue) by man_ls (subscriber, #15091) [Link] The idea was actually that a single "binary" (bytecode actually) could run, unmodified, on several platforms. Yes, "write" here is grossly misused.Given that the bytecode was in fact interpreted by the VM (and later compiled on the fly), the comparison to compiled languages was misdirected: Java had the inconvenience of having to compile and the slowness of interpreted languages, but none of the advantages. It would have been more appropriate to compare with interpreted languages such as Python or Perl, but then Java would have lost big time since VMs were only available for a handful of platforms and the competition can run, unmodified, on tens. Here by "platform" I mean a combination of OS and processor architecture. Nowadays Java is JITted and fast. But then again so is the humble javascript...
|
|||||||||||||