PostgreSQL allow turning any programming language into a query language, AFAIK. BTW, this may be off-topic, but I'm pretty sure I'll get the most DBMS geek eyes on this article, so here it goes - would it be possible/feasible to integrate the compiler system and cache with the VCS within the database? My idea is about getting the flexibility of Portage/pkgsrc systems without the hassle of compiling the whole thing, start to finish. I'm pretty sure most compile time options can be recalculated quickly, and reflected in the database as binary diffs, or maybe just a link time option.
http://www.microxwin.com/ seems interesting, no if some good soul would clone under the Apache license the proprietary kernel module, we'd be all set for a new high-performance gaming platform.:)
Quit pushing OS X as a successful consumer UNIX. It's success is almost exclusively because Apple is pushing it with their own hardware. If the licensed NT's POWER port from M$, and threw a new skin/UI on top, it would still sell like hotbread.
You just reinvented X11, congrats. Now throw in WeirdX and XMLVM with the javascript backend, embed emacs, and you will have solved Xzibit's computing needs.
Tell me, what would you prefer for a mission critical server. Now tell me, do you give a flying fuck about certification, or do you want a good quality OS? Possibly POSIX compliant? With some simple and useful basic utilities? Nothing overly complicated? That's UNIX. Not a fuckton of paperwork like others claim.
It is usually understood GNU/Linux, under Linux distribution. Like Yoda, speak I. This weed, it is good. So, per GNU/Linux standards, ChromeOS ain't a distro. It is a new OS, which happens to use the Linux kernel, but nothing more. Sorry.
He said gasoline. As in, fuel appropriate for an Otto cycle motor. For the same compression, the Otto is better, but requires much higher quality fuel. When dealing with synthetic fuel sources, you can set up the fuel produced to be of much higher quality than could be conceived of otherwise. Ethanol is practically racing fuel, for instance. And it could be useful, just not with current methods. We need GM crops with cellulose degrading enzymes stored in vacuoles. Crush, ferment, distill, and you've got a fuckton of fuel. Technique could be reused with algae. Also, I'd say we really need a variable combustion chamber volume engine. Throttling kills efficiency.
No, the moral is that drugs should be legalized. I'm serious. Almost every time someone has problems with the police, it's about drugs - i.e. a victimless crime. If it wasn't for brain dead laws, we'd have 1/10 of today's police force, and be twice as efficient. Sorry for the OT rant.
As background, I work for IBM/Rational, participated in the design and construction of RTC from its inception, and among other activities, have been leading the teams building the "Connectors" between RTC and ClearCase/ClearQuest. Back in 1995, I joined Atria to work on ClearCase.
So why did we created a new product?.
Over the years we've observed that for large software projects, what mattered even more than point tool functionality was how well the different tools were integrated. More recently, as companies started focusing on agile development where single individuals perform multiple roles concurrently, the same became true for smaller software projects. So we put increasing amounts of efforts into integrating our tools.
But we concluded that without a tool integration platform, there's only so far we could go (and in particular, the integrations were tool version sensitive, requiring upgrading the tools together, which is not something users wanted to do). And even with a tool integration platform which improved the level of integration of all the tools, we also concluded that the only way to get optimal integration is to also build the products specifically for that tool integration platform.
In addition, a requirement for ClearCase and ClearQuest has always been that they handle all SCM (software configuration management) and CM (change management) problems that our customers have encountered over the years, work on all hardware and OS platforms, and remain compatible with all previous versions we've released. But that breadth of coverage comes at a cost... both in performance and in ability to do all the new cool things that we and others have thought of.
So a few years ago, we started Team Concert, both to build the platform that we were going to use to improve the integration between all of our tools, as well as to build new instances of those tools that were designed to take optimal advantage of that new platform.
And while we were building those new integrated tools, we were also free to focus those new tools on the most common problems and the most common platforms, since we had ClearCase and ClearQuest to back the new tools up with breadth of problem and platform coverage. The "Connectors" then plug ClearCase and ClearQuest into that platform, and into those new tools, so that a customer can use the new tools when appropriate, and use ClearCase and ClearQuest whenever they weren't.
And the integration between all these tools were enhanced by the Jazz integration architecture (i.e. it was no longer an either/or... a customer uses whatever tools best solve their problems). And while all this is going on, we continue to invest heavily in enhancing ClearCase and ClearQuest (we have significantly more people working on ClearCase and ClearQuest than we do on Team Concert).
At any rate, that was the idea (:-). For some more perspectives on this question from some other folks, you can also listen to the webcast: http://www.rational-ug.org/webcastDetail?wid=74.
Slashdot Mirror
Inter-IDE integration?
PostgreSQL allow turning any programming language into a query language, AFAIK. BTW, this may be off-topic, but I'm pretty sure I'll get the most DBMS geek eyes on this article, so here it goes - would it be possible/feasible to integrate the compiler system and cache with the VCS within the database? My idea is about getting the flexibility of Portage/pkgsrc systems without the hassle of compiling the whole thing, start to finish. I'm pretty sure most compile time options can be recalculated quickly, and reflected in the database as binary diffs, or maybe just a link time option.
Did you respond to pot? It's a very heavy duty painkiller, IIRC.
No, God no. Screw C. Please. Learn Ada, for Pete's sake. I'm sick of buffer overflows.
...a TomTom with just the Verilog source code...
FTFY.
Better idea, make them not crash. Sign up with C programmers anonymous or something.
http://www.microxwin.com/ seems interesting, no if some good soul would clone under the Apache license the proprietary kernel module, we'd be all set for a new high-performance gaming platform. :)
The tracing JIT or whatever used in Chrome is kinda tied to x86, IIRC. A Javascript frontend for LLVM is gonna be easier than porting it, methinks.
Mainstreaming of program specializers is going to rock the world, methinks...
Quit pushing OS X as a successful consumer UNIX. It's success is almost exclusively because Apple is pushing it with their own hardware. If the licensed NT's POWER port from M$, and threw a new skin/UI on top, it would still sell like hotbread.
You just reinvented X11, congrats. Now throw in WeirdX and XMLVM with the javascript backend, embed emacs, and you will have solved Xzibit's computing needs.
Throw this in and the jokes write themselves.
You don't read TFWebsite often, do you? That project has been dead since 2004.
Tell me, what would you prefer for a mission critical server. Now tell me, do you give a flying fuck about certification, or do you want a good quality OS? Possibly POSIX compliant? With some simple and useful basic utilities? Nothing overly complicated? That's UNIX. Not a fuckton of paperwork like others claim.
It is usually understood GNU/Linux, under Linux distribution. Like Yoda, speak I. This weed, it is good. So, per GNU/Linux standards, ChromeOS ain't a distro. It is a new OS, which happens to use the Linux kernel, but nothing more. Sorry.
Let me introduce you to something.
Goes well with a Tesla Electric roadster, as well.
My mother is okaying me smoking weed, as long as eat more. Tell me about it...
I think your sig is strangely appropriate.
Seriously? Why?
He said gasoline. As in, fuel appropriate for an Otto cycle motor. For the same compression, the Otto is better, but requires much higher quality fuel. When dealing with synthetic fuel sources, you can set up the fuel produced to be of much higher quality than could be conceived of otherwise. Ethanol is practically racing fuel, for instance. And it could be useful, just not with current methods. We need GM crops with cellulose degrading enzymes stored in vacuoles. Crush, ferment, distill, and you've got a fuckton of fuel. Technique could be reused with algae. Also, I'd say we really need a variable combustion chamber volume engine. Throttling kills efficiency.
Not to mention that it (C-64) was envisioned as a open-platform console that comes pre-modded than as a general purpose computer.
No, the moral is that drugs should be legalized. I'm serious. Almost every time someone has problems with the police, it's about drugs - i.e. a victimless crime. If it wasn't for brain dead laws, we'd have 1/10 of today's police force, and be twice as efficient. Sorry for the OT rant.
Upstream merges, meet recoiledsnake. recoiledsnake, meet upstream merges.
As background, I work for IBM/Rational, participated in the design and construction of RTC from its inception, and among other activities, have been leading the teams building the "Connectors" between RTC and ClearCase/ClearQuest. Back in 1995, I joined Atria to work on ClearCase.
... both in performance and in ability to do all the new cool things that we and others have thought of.
... a customer uses whatever tools best solve their problems). And while all this is going on, we continue to invest heavily in enhancing ClearCase and ClearQuest (we have significantly more people working on ClearCase and ClearQuest than we do on Team Concert).
So why did we created a new product?.
Over the years we've observed that for large software projects, what mattered even more than point tool functionality was how well the different tools were integrated. More recently, as companies started focusing on agile development where single individuals perform multiple roles concurrently, the same became true for smaller software projects. So we put increasing amounts of efforts into integrating our tools.
But we concluded that without a tool integration platform, there's only so far we could go (and in particular, the integrations were tool version sensitive, requiring upgrading the tools together, which is not something users wanted to do). And even with a tool integration platform which improved the level of integration of all the tools, we also concluded that the only way to get optimal integration is to also build the products specifically for that tool integration platform.
In addition, a requirement for ClearCase and ClearQuest has always been that they handle all SCM (software configuration management) and CM (change management) problems that our customers have encountered over the years, work on all hardware and OS platforms, and remain compatible with all previous versions we've released. But that breadth of coverage comes at a cost
So a few years ago, we started Team Concert, both to build the platform that we were going to use to improve the integration between all of our tools, as well as to build new instances of those tools that were designed to take optimal advantage of that new platform.
And while we were building those new integrated tools, we were also free to focus those new tools on the most common problems and the most common platforms, since we had ClearCase and ClearQuest to back the new tools up with breadth of problem and platform coverage. The "Connectors" then plug ClearCase and ClearQuest into that platform, and into those new tools, so that a customer can use the new tools when appropriate, and use ClearCase and ClearQuest whenever they weren't.
And the integration between all these tools were enhanced by the Jazz integration architecture (i.e. it was no longer an either/or
At any rate, that was the idea (:-). For some more perspectives on this question from some other folks, you can also listen to the webcast:
http://www.rational-ug.org/webcastDetail?wid=74.
Much more readable that way.