That RDBMS remark has nothing to do with hype. The hyped-up no-SQL paradigm says that no-SQL is good for loosely structured or unstructured data, of which there is actually quite a lot "out there", in the wild. What I see, is different, especially when it comes to the latest generation of graph databases, like neo4J and Titan: as soon as people encounter those technologies, they begin to think differently even about already highly-structured data. As a matter of fact, all data whose structure can be depicted in a relational schema can also be represented by a graph.
Add to that the growing resentment and inimicity Oracle is encountering with its extant client base, simply because of vendor lock-in. Add to that the natural cap there is on SQL Server usage numbers, due to slowly shrinking Windows ( server-side ) market penetration. Add to that the slow disappearance into gloom of mySQL.
For sure, very conservative corporate customers, like banks and insurance, will continue to rely upon RDBMSes for a long time. Same thing as for COBOL. You may not believe me, but I am willing to bet several hundreds of euro upon it: 10 years from now, Oracle will be company in trouble ( only their large cash reserve is keeping them outside of troubled waters right now; remember Blackberry ? ) and SQL Server will have dwindled to insignificance. no-SQL databases of a kind and of performance we can, right now, not even yet dream of will rule the roost.
1) JavaScript. And one of the technologies building up on it, or improving it. Google V8 seems a good candidate
2) Some new, web-oriented programming language. Try Dart.
You should know a minimum about databases. RDBMSes are going to die, so learn how to interact with one of the major no-SQL databases. Apache Cassandra is a good starting point. So are MongoDB and Couchbase / CouchDB. The most bleeding-edge ones are Titan and neo4J, both graph databases.
lies not in the so-called "global warming pause". It lies in the fact that most, if not all of the naysayers, are creationist, drill-baby-drill Americans. Sorry. I know - I am going to be modded down into oblivion. So what.
The article under the link makes a good point. So do you. Truth is, I am betting hard that next summer, when I will celebrate 20 years without interruption on the server side of the IT business ( programming & design ), I have never, never ever seen a production system relying / running on any BSD. Theo de Raadt was saved by the bell. This time.
Get a dedicated development box. Quickly. Do it now. You will be heading for serious trouble otherwise. And as another use above said: SEPARATE YOUR CONCERNS. You need at least 2 boxes, then. Really.
Yes, I drive less than, say, 10 years ago. Ten years ago I had quite a large sedan. For meetings and seeing customers, I made it gobble sometimes as much as 2000 kilometers a week. And then ? Then came Skype, Dropbox et al.. Then came the cloud. Then came radically altered habits of working together. That's all.
Exactly this. For working, I use 2 monitors. One in "traditional" orientation for overlooking running processes, in many shell windows tiled / staggered behind eachother. And one for coding and reading in portrait mode. It is quite the experience to see what portrait mode does with e.g. your perception of code. NetBeans in portrait mode absolutely rocks ! Now I am all frustrated when I look at the code of colleagues, in "traditional" orientation - especially when they show it on a laptop screen: it gives me the impression of being obliged to forcibly narrow my mindset.
Typo. I omitted half of the project description. It should read "... the entire IT landscape, software and hardware, of the city's main hospital, which is publicly funded.
Almost two years ago I bought a new laptop. My choice fell upon an Asus K53. The thing has been doing some heavy-duty work, and I love its brown, aluminium case. BUT the keyboard is a chicklet one, and is absolutely horrible. So I began looking for THE ultimate keyboard, once more. I tried the classic IBM clickety-click keyboard, clones of that one. I had an old sysadmin dig out a keyboard from 1986 which was so heavy you could actually throw it at a cow and kill the beast with its sheer weight. I used that one for some months, at home ( after I had found a DIN-to-PS/2 adapter cable, of course ). It drove my girlfriend nuts, being louder than a mechanical typewriter.
Then, one day, I walked into a shop and saw a shiny black monster. It had Cherry MX blue switches, the ones that provide tactile and hearable feedback. It weighed in at a hefty 1.385 kilograms. Once my fingers rested upon it, they seemed to be physically invited to fly through the standard text I had come to use to test keyboards, making my typing speed flirt with the 100 wpm barrier. It had five programmable macro keys, on the far left. I bought it for what I then thought was a staggering price: € 120 ( US $ 162 ).
It still sits, looming blackly, on the simple white table I use for work. It is a Razer BlackWidow, a gaming keyboard. I use it for programming, browsing, writing emails - anything. It is wonderfully solid, and will prolly last for 20 years. I am thinking of buying an extra one, as one day Razer will certainly stop producing them, and leaving it in its original boxing, just to have a spare item for this wonderful, wonderful tool.
But it took a lot of patient searching, well worth the time and frustration. Now I pity the people who, at work, get a Dell laptop or workstation with a 4 euro piece of plastic as their main productivity tool, with which their hands have to deal for hours and hours and days and days.
... tiny. Minute. About the same as for any monster project, e.g. here in Vienna the project that was retrofit the entire IT landscape, software and hardware, in one giant project. Awarded to IBM. Who majestically botched it.
Slashdot Mirror
cool.
That RDBMS remark has nothing to do with hype. The hyped-up no-SQL paradigm says that no-SQL is good for loosely structured or unstructured data, of which there is actually quite a lot "out there", in the wild. What I see, is different, especially when it comes to the latest generation of graph databases, like neo4J and Titan: as soon as people encounter those technologies, they begin to think differently even about already highly-structured data. As a matter of fact, all data whose structure can be depicted in a relational schema can also be represented by a graph.
Add to that the growing resentment and inimicity Oracle is encountering with its extant client base, simply because of vendor lock-in. Add to that the natural cap there is on SQL Server usage numbers, due to slowly shrinking Windows ( server-side ) market penetration. Add to that the slow disappearance into gloom of mySQL.
For sure, very conservative corporate customers, like banks and insurance, will continue to rely upon RDBMSes for a long time. Same thing as for COBOL. You may not believe me, but I am willing to bet several hundreds of euro upon it: 10 years from now, Oracle will be company in trouble ( only their large cash reserve is keeping them outside of troubled waters right now; remember Blackberry ? ) and SQL Server will have dwindled to insignificance. no-SQL databases of a kind and of performance we can, right now, not even yet dream of will rule the roost.
You should know a minimum about databases. RDBMSes are going to die, so learn how to interact with one of the major no-SQL databases. Apache Cassandra is a good starting point. So are MongoDB and Couchbase / CouchDB. The most bleeding-edge ones are Titan and neo4J, both graph databases.
Godspeed !
Religion is, and remains a certain sort of brain-porn for the brainless, after all.
Hey ! PSSSST ! Want a subscription real cheap ? I got some good stuff here, man ! Wanna have a go ? Yeah, you can try it for free for 10 minutes....
Fail: doesn't work when I take her from behind. She likes to bury her head in the pillows. Bug. Issue #22. See http://github.com/rabidfukker/theotherview/issues/22
That's what I meant.
That is what I need, to keep reading /. !
, in LOCRiDS ( Library Of Congress Replacement Cost in DollarS ) , of one of those to my doorstep ?
are not sweet. They are not even biter. They are tasteless.
Must be because I never get inside switches, routers or firewalls. I should have precised "production servers.
Clear enough. Thanks for the answer !
lies not in the so-called "global warming pause". It lies in the fact that most, if not all of the naysayers, are creationist, drill-baby-drill Americans. Sorry. I know - I am going to be modded down into oblivion. So what.
Granted for the first point. Second point: true, I use openSSH every day, in production. But that is quite different from an entire OS.
I am a bit astounded. Why would you want to compile that into an OS kernel ?? Please enlighten me.
There, 'nuff said.
Get a dedicated development box. Quickly. Do it now. You will be heading for serious trouble otherwise. And as another use above said: SEPARATE YOUR CONCERNS. You need at least 2 boxes, then. Really.
someone mod parent up "funny"
Yes, I drive less than, say, 10 years ago. Ten years ago I had quite a large sedan. For meetings and seeing customers, I made it gobble sometimes as much as 2000 kilometers a week. And then ? Then came Skype, Dropbox et al.. Then came the cloud. Then came radically altered habits of working together. That's all.
What a shameless plug !
Exactly this. For working, I use 2 monitors. One in "traditional" orientation for overlooking running processes, in many shell windows tiled / staggered behind eachother. And one for coding and reading in portrait mode. It is quite the experience to see what portrait mode does with e.g. your perception of code. NetBeans in portrait mode absolutely rocks ! Now I am all frustrated when I look at the code of colleagues, in "traditional" orientation - especially when they show it on a laptop screen: it gives me the impression of being obliged to forcibly narrow my mindset.
Typo. I omitted half of the project description. It should read "... the entire IT landscape, software and hardware, of the city's main hospital, which is publicly funded.
Almost two years ago I bought a new laptop. My choice fell upon an Asus K53. The thing has been doing some heavy-duty work, and I love its brown, aluminium case. BUT the keyboard is a chicklet one, and is absolutely horrible. So I began looking for THE ultimate keyboard, once more. I tried the classic IBM clickety-click keyboard, clones of that one. I had an old sysadmin dig out a keyboard from 1986 which was so heavy you could actually throw it at a cow and kill the beast with its sheer weight. I used that one for some months, at home ( after I had found a DIN-to-PS/2 adapter cable, of course ). It drove my girlfriend nuts, being louder than a mechanical typewriter.
Then, one day, I walked into a shop and saw a shiny black monster. It had Cherry MX blue switches, the ones that provide tactile and hearable feedback. It weighed in at a hefty 1.385 kilograms. Once my fingers rested upon it, they seemed to be physically invited to fly through the standard text I had come to use to test keyboards, making my typing speed flirt with the 100 wpm barrier. It had five programmable macro keys, on the far left. I bought it for what I then thought was a staggering price: € 120 ( US $ 162 ).
It still sits, looming blackly, on the simple white table I use for work. It is a Razer BlackWidow, a gaming keyboard. I use it for programming, browsing, writing emails - anything. It is wonderfully solid, and will prolly last for 20 years. I am thinking of buying an extra one, as one day Razer will certainly stop producing them, and leaving it in its original boxing, just to have a spare item for this wonderful, wonderful tool.
But it took a lot of patient searching, well worth the time and frustration. Now I pity the people who, at work, get a Dell laptop or workstation with a 4 euro piece of plastic as their main productivity tool, with which their hands have to deal for hours and hours and days and days.
... tiny. Minute. About the same as for any monster project, e.g. here in Vienna the project that was retrofit the entire IT landscape, software and hardware, in one giant project. Awarded to IBM. Who majestically botched it.
Abay-ba-da bum-bum bay-do
Fox language is Turing-complete, as everybody knows.