is this an all or nothing kind of thing? Sure, if I wanted pure OOP, I'd look at Smalltalk. But what I'm looking for is a language built on OOP principals, even if not fully object oriented (ie. possesses non-object primitives), with a large set of libraries. Java and C++ are close enough to that that I can live with them not being pure object oriented languages.
Because coding in Perl is like having a root canal. Perl may run on more platforms than Java, but I hate programming in Perl. And Python brings nothing to the table that Java doesn't already have, so why should I bother?
And what "complexity" is that? You're not going to write device drivers in Java, that's for sure, but modern Java is pretty capable whether it's desktop apps or, where it's used more often, in enterprise solutions, which is why the big guys like IBM use it.
And what's wrong with abstracting the architecture. One of C's original intentions was portability, and a lot of that was done by porting over libc to as many platforms as possible so all the system calls of the operating system in question were, well, abstracted. Java's just further down that road.
And OOP has been with us for over thirty years, and while not suitable for every problem, is still a pretty rock solid way to solve a lot of problems. That's why people went out and developed c++ and Objective C, and why most of the other modern iterations of earlier pre-OOP languages have had OOP extensions for a couple of decades now.
Largely my experience now. There are certainly a few incompatibility issues that creep up, after all Java is over 20 years old now, so that's quite a few iterations of both the language and the JVM. But when I consider the complexity of porting C code from, say, Linux to Windows, or in many cases from Linux to BSD or some other *nix flavor, the odd quirk I run up against when popping a JAR file on to a new platform, I'd say Java is as close as anything gets to true cross-platform portability. No one has put more effort into making obscuring the underlying architecture than the JVM teams, and I still get a thrill when I fire up a Java app I've written on Windows on my Linux test machine and it, well, just works. No recompiles, no wild makefiles and compiler redirectives.
C is an awesome language, and truly one of the great inventions of the computer age, but it is fundamentally a different tool than Java, with very different intentions. For me, Java means I'm not locked into any architecture, and not having to fight my way out of the box that the architecture represents. It's not for every task, but for the bulk of problems thrown at me, it does the job very well. Not perfectly, but very well.
Most of the Java code out there isn't GUI code, and yes, high portability is one of the major reasons. And honestly, I have compiled code written 15 years ago that still runs on newer JVMs
Just because you're a paranoid idiot doesn't translate into some grand scam in science. That chip on your shoulder is of your own creation, so grow up, man-child, and accept the universe doesn't give a flying fuck about your feelings about the radiation absorption and re-emission properties of carbon dioxide.
While it's possible there is life on Titan, it seems improbable; considering the extremely low temperatures. Titan has some of the conditions for life, but a lot of available free energy isn't one of them.
Exactly. If Southern California is anything like Seattle or Vancouver, those ranchers being sold for hundreds of thousands of dollars over the asking price aren't being bought by people who intend to live in them, they're being bought by people who intend to build some form of multi-family dwellings; ie. condominiums, townhouses and the like.
In some cases it's also foreign buyers looking to park their money in what they view as a secure and stable market. The Chinese are big purchasers for this reason on the West Coast, and I know in Britain you have wealthy Russians and other Eastern Europeans burying their assets in property.
Whatever the case, these sorts of sales are not by normal buyers, and the West Coast from British Columbia down to California is having a very peculiar kind of real estate boom. Every attempt to tamper with it up here in British Columbia has had only a modest short-term effect, and though rising interest rates may dampen it a bit, I'm not sure considering the kinds of buyers we're seeing that it will have that serious effect. It's a damned weird thing happening.
I have a feeling that in a hundred years, the Arabian Peninsula will be covered in solar collectors, and they'll still be an energy superpower.
The fact is that everyone knows oil is doomed. At this point, the oil barons are more interested in eking out another couple of decades of profits before fossil fuels are put to bed for good. Watching the faux skeptics around here is like watching a meeting of flat Earthers, half of them knowing what they're saying is idiotic, but just unable to give up their pointless contrarianism.
I don't know when you started coding in BASIC, but I started about 1982, on a couple of dialects of MS-BASIC (one for the Radioshack Color Computer and the other the variants on the Vic-20 and Commodore 64). Developing larger applications was an unpleasant experience. With limited variable lengths, meaning often undescriptive variable names, limited memory meaning you were limited in the number of comments you could insert, developing larger applications was quite an ordeal.
If you're talking about the structured variants that began to appear in the late 1980s, well, that was an entirely different experience. You had something akin to modern IDEs, far fewer limitations on variables, structured (and later OOP) elements. I'd call languages like QuickBASIC to basically be hybrids between BASIC and Pascal, with clear inspiration taken from the TurboPascal environment. Once you get to VisualBasic 5 and 6, these are basically weakly-typed Pascal environments with BASIC-like syntax, so yes, developing large applications in those structured and object-oriented dialects with a full suite of development tools was a lot different experience than banging out BASIC programs in the 1970s and 1980s with, at best, primitive editing tools. I'm not saying it couldn't be done, and it certainly was, because on many of these microcomputers it was either BASIC or assembly. I do recall some C and Pascal environments for some of these 8 bit machines, but they weren't all that common and tended to cost $$$ as compared to the language burned into the ROMs on your computer.
The other problem with traditional BASIC is that was in a lot of ways a highly stylized and simplified form of COBOL, so it inherited some pretty bad concepts, so a lot of us folks that cut our teeth on the older pre-structured versions of BASIC learned some bad habits (in particular the infamous GOTO), and I remember taking my first Pascal course having to get used to a rather different and far more rigorous paradigm, but for me that transition left me for a permanent distaste for weakly typed languages. I know they have their advantages, and certainly make some problems a lot easier to solve, but I fell in love with Pascal's elegance and structure, and it's the way I program even now.
We're talking about a guy who invented and named his own law; the Iron Rule of Bureaucracy. Whether you agree with his analysis, there's a level of conceit in naming your own law. Pournelle thought himself a very important man, and took every opportunity to remind people of the influence (as modest as it actually was) that he possessed at one time. He also had an uncomfortable habit of name dropping other SF authors, particularly the great ones, though I can't imagine that the likes of Asimov would ever have been that impressed with him.
I enjoyed his writing, and was able to wade past some of the obvious ideological slants he inserted, but he was at best in the second tier of SF authors, a good writer but not a great one.
Slashdot Mirror
First of all, I doubt it's even a million. Second of all racism is hardly merely a "political opinion".
We'll see how you feel when you Flynn and Manafort start singing.
Since when does Edge matter at all? All the statistics I've seen suggest users view Edge as their Chrome download application.
Debt makes the world go around, and has for thousands of years.
Missed your latest cognitive therapy session, i see.
I have an eight core notebook with an SSD drive and 8gb of RAM, and eclipse comes up very quickly. Very sorry you have such a badly configured system.
So really, the better solution is to actually run Linux on VMWare, VirtualBox, Hyper-V, and so on.
Got it, avoid another MS integration clusterfuck.
There have been plenty of insecure frameworks built in all the major languages, and thus far has anyone proven that Struts was the source of the hack?
is this an all or nothing kind of thing? Sure, if I wanted pure OOP, I'd look at Smalltalk. But what I'm looking for is a language built on OOP principals, even if not fully object oriented (ie. possesses non-object primitives), with a large set of libraries. Java and C++ are close enough to that that I can live with them not being pure object oriented languages.
I'm picking a tool set, not a religion.
Because coding in Perl is like having a root canal. Perl may run on more platforms than Java, but I hate programming in Perl. And Python brings nothing to the table that Java doesn't already have, so why should I bother?
And what "complexity" is that? You're not going to write device drivers in Java, that's for sure, but modern Java is pretty capable whether it's desktop apps or, where it's used more often, in enterprise solutions, which is why the big guys like IBM use it.
And what's wrong with abstracting the architecture. One of C's original intentions was portability, and a lot of that was done by porting over libc to as many platforms as possible so all the system calls of the operating system in question were, well, abstracted. Java's just further down that road.
And OOP has been with us for over thirty years, and while not suitable for every problem, is still a pretty rock solid way to solve a lot of problems. That's why people went out and developed c++ and Objective C, and why most of the other modern iterations of earlier pre-OOP languages have had OOP extensions for a couple of decades now.
Largely my experience now. There are certainly a few incompatibility issues that creep up, after all Java is over 20 years old now, so that's quite a few iterations of both the language and the JVM. But when I consider the complexity of porting C code from, say, Linux to Windows, or in many cases from Linux to BSD or some other *nix flavor, the odd quirk I run up against when popping a JAR file on to a new platform, I'd say Java is as close as anything gets to true cross-platform portability. No one has put more effort into making obscuring the underlying architecture than the JVM teams, and I still get a thrill when I fire up a Java app I've written on Windows on my Linux test machine and it, well, just works. No recompiles, no wild makefiles and compiler redirectives.
C is an awesome language, and truly one of the great inventions of the computer age, but it is fundamentally a different tool than Java, with very different intentions. For me, Java means I'm not locked into any architecture, and not having to fight my way out of the box that the architecture represents. It's not for every task, but for the bulk of problems thrown at me, it does the job very well. Not perfectly, but very well.
Most of the Java code out there isn't GUI code, and yes, high portability is one of the major reasons. And honestly, I have compiled code written 15 years ago that still runs on newer JVMs
Just because you're a paranoid idiot doesn't translate into some grand scam in science. That chip on your shoulder is of your own creation, so grow up, man-child, and accept the universe doesn't give a flying fuck about your feelings about the radiation absorption and re-emission properties of carbon dioxide.
Indeed. Cassini is another great triumph of space exploration, and shows we can build some pretty damned hardy and long-lasting probes.
While it's possible there is life on Titan, it seems improbable; considering the extremely low temperatures. Titan has some of the conditions for life, but a lot of available free energy isn't one of them.
Would you actually want their lips on your testicles?
I think I'd rather get it done by ten dollar prostitute with cold sores, she'd be cleaner.
https://www.ncbi.nlm.nih.gov/p...
It's not our fault you're retarded.
For pleasure, I'm reading Raymond Chandler's Philip Marlowe novels. Every once in a while I get an itch for old noir novels that I need to scratch.
Exactly. If Southern California is anything like Seattle or Vancouver, those ranchers being sold for hundreds of thousands of dollars over the asking price aren't being bought by people who intend to live in them, they're being bought by people who intend to build some form of multi-family dwellings; ie. condominiums, townhouses and the like.
In some cases it's also foreign buyers looking to park their money in what they view as a secure and stable market. The Chinese are big purchasers for this reason on the West Coast, and I know in Britain you have wealthy Russians and other Eastern Europeans burying their assets in property.
Whatever the case, these sorts of sales are not by normal buyers, and the West Coast from British Columbia down to California is having a very peculiar kind of real estate boom. Every attempt to tamper with it up here in British Columbia has had only a modest short-term effect, and though rising interest rates may dampen it a bit, I'm not sure considering the kinds of buyers we're seeing that it will have that serious effect. It's a damned weird thing happening.
Money talks, and considering California is the sixth largest economy in the world, that's a very loud voice.
I have a feeling that in a hundred years, the Arabian Peninsula will be covered in solar collectors, and they'll still be an energy superpower.
The fact is that everyone knows oil is doomed. At this point, the oil barons are more interested in eking out another couple of decades of profits before fossil fuels are put to bed for good. Watching the faux skeptics around here is like watching a meeting of flat Earthers, half of them knowing what they're saying is idiotic, but just unable to give up their pointless contrarianism.
I don't know when you started coding in BASIC, but I started about 1982, on a couple of dialects of MS-BASIC (one for the Radioshack Color Computer and the other the variants on the Vic-20 and Commodore 64). Developing larger applications was an unpleasant experience. With limited variable lengths, meaning often undescriptive variable names, limited memory meaning you were limited in the number of comments you could insert, developing larger applications was quite an ordeal.
If you're talking about the structured variants that began to appear in the late 1980s, well, that was an entirely different experience. You had something akin to modern IDEs, far fewer limitations on variables, structured (and later OOP) elements. I'd call languages like QuickBASIC to basically be hybrids between BASIC and Pascal, with clear inspiration taken from the TurboPascal environment. Once you get to VisualBasic 5 and 6, these are basically weakly-typed Pascal environments with BASIC-like syntax, so yes, developing large applications in those structured and object-oriented dialects with a full suite of development tools was a lot different experience than banging out BASIC programs in the 1970s and 1980s with, at best, primitive editing tools. I'm not saying it couldn't be done, and it certainly was, because on many of these microcomputers it was either BASIC or assembly. I do recall some C and Pascal environments for some of these 8 bit machines, but they weren't all that common and tended to cost $$$ as compared to the language burned into the ROMs on your computer.
The other problem with traditional BASIC is that was in a lot of ways a highly stylized and simplified form of COBOL, so it inherited some pretty bad concepts, so a lot of us folks that cut our teeth on the older pre-structured versions of BASIC learned some bad habits (in particular the infamous GOTO), and I remember taking my first Pascal course having to get used to a rather different and far more rigorous paradigm, but for me that transition left me for a permanent distaste for weakly typed languages. I know they have their advantages, and certainly make some problems a lot easier to solve, but I fell in love with Pascal's elegance and structure, and it's the way I program even now.
We're talking about a guy who invented and named his own law; the Iron Rule of Bureaucracy. Whether you agree with his analysis, there's a level of conceit in naming your own law. Pournelle thought himself a very important man, and took every opportunity to remind people of the influence (as modest as it actually was) that he possessed at one time. He also had an uncomfortable habit of name dropping other SF authors, particularly the great ones, though I can't imagine that the likes of Asimov would ever have been that impressed with him.
I enjoyed his writing, and was able to wade past some of the obvious ideological slants he inserted, but he was at best in the second tier of SF authors, a good writer but not a great one.