With the algorithm revealed, it'd be possible to "predict" the future domains for a year or so forward in an automated fashion. Then you monitor the registrars for registration requests for those domains, and you have a fairly decent idea when the next wave is going to hit, and it might even provide a lead to the domain owner. Or you could "just" have those domains blocked from registration, for example.
I don't think you understand what 'enterprise' means. One
thing it means for sure is 'conservative'. With all
these version 5 new features just released, any
*sensible* enterprise will wait to see how they work in
the real world. At *somebody elses* real world. Enterprises
are not going to volunteer to be beta sites.
And _still_ no hierarchical playlists. Damn! Do people really use playlists so seldomly? I save pretty much any playlist I ever created and with iTunes that gets messy in a hurry.
Except that at the R&D where I work, WIFI is banned because of the security risks. I also see no reason to use wifi at home except for the laptop; wires are more secure and faster.
You might want to give Ingres r3 a spin. It doesn't have the fancy postgresql object-relational features, but it performs well under both Linux and Windows.
SQL Server is not getting hurt by PostgreSQL or MySQL. For places where MySQL would be a threat, MSDE would be there to cover the need. MySQL is _no_ match against MSDE unless you need what would in essence be a high-performance read-only database for the simplest of queries.
PostgreSQL would be a lot better, but it's been out for what, 2 months on the Windows platform? Only a nutcase would go into serious production based on that. Then there's the issue of availability of training. Tinkering along until you hopefully right is very expensive for a bussiness.
Standard disclaimer, like OSS as much as the next slashdotter, yada yada, but Free is not necesarily gratis.
I've heard from people inside CA that Sun is getting complaints from its Oracle-using customers; with the upcoming multi-core systems, and Oracles' per-whatever-claims-to-be-a-cpu licensing, support costs for Oracle are going to go through the roof for these clients for no real benefit (or even choice once multicore becomes the only option).
So Sun is appearantly eyeing Ingres, being the closest competition to Oracle on features and performance, to be bundled with Solaris by default. SapDB was appearantly not up to snuff on stuff like parallel queries and table partitioning, pretty crucial if you're going up against Oracle.
CA is even in talks with SAP about Ingres being bundled with SAP... says enough about how capable SapDB must be.
Visual Studio is a good IDE; things like intellisense make me immensely more productive. But intellisense is not available only in VS; Eclipse has it too, for example.
And AFAIC, the advantage of VS is offset by the problems we see debugging programs (IIS-hosted com components, specifically); since everything is tied in to everything else, it's *damn* hard to compartimentalize the problem and turn off irrelevant stuff to home in on the problem. From my perspective, developing for Linux is a lot easier.
It's either Open Source, or it's Proprietary But Gratis For Non-Commercial Use. Make up your mind. The fact that you may or may not ship the source with the product does not make it open source.
In my opinion, I think that webapps are the way to go with a project like this. I say this because we currently have an old legacy application that uses Borland C++ Builder, and it is very difficult to manage the all of the versions being used by staff members. As we've moved the functionality over to a web portal, we've been able to spend less time distributing executables and more time developing features.
A webapp has the strength that all you need is a web browser to view the content. When you update the webapp, all clients are updated instantly, without having to push something out to them, or making them download something. This saves a lot of stress and headache.
Which is nice for you. I haven't seen a single point in your message that relates to the need for the user, who is, after all, paying for this. The first order is to go see what the actual user needs, and if I were the customer, webapps would be straight out. Webapps are decent for infrequent use; they suck if you need rich functionality and need to interact with the software all the time.
Ingres was originally intended to compete with the likes of Oracle and MS SQL Server, but never had the power or client base
Ingres predates both Oracle and SQL Server by a wide margin. You're right about the client base, but I've found that Ingres R3 is a decent match for SQL Server. Can't say about Oracle.
It's not a GPL license, just a chance to peek at the source and maybe help out.
Bullshit. It's not GPL but it's a OSI-certified FOSS license, and it's Free to use in both FOSS and proprietary software.
If GDS runs as LocalSystem, it will find and display stuff of all users even if the system properly locked down and users would normally be unable to see each others documents.
They're going to attract more developers because
they're going to make sure there'll be decent
documentation and a top-notch IDE. XUL got there years before XAML
and it's documentation is still worse than XAMLs.
I have the Lizard book (which contains glaring errors BTW) and most of xulplanet et al in bound form,
and developing/debugging even simple applications
is horrendously frustrating.
In this case it might seem "small" to you. But if you have been unlucky enough to see a loved one at the receiving end of GBH, or even end up dead, damn right I want to see the guilty party suffer. I'd have taken a baseball bat to every bone in his body and would have happily left him a cripple for life if the law provided for it or would have turned an eye long enough.
If you think that's rather small, I really, really hope you don't have to find out in person how "small" you feel if this happens to you and someone else decides for you that 10 years in prison evens out the crime.
This doesn't help me at all when Postgresql refuses to install on my Windows 2000 server machine. There's a large difference between "1st release, appears to work on the desktop of the PostgreSQL devs" and "ready for production". Maybe Sybase can claim to be the "very attractive alternative to Microsoft SQL Server" because they have a (positive) history on Windows.
commercially usable low end database which is positioned against MS SQL-Server, MySQL, MaxDB, Ingres and PostgreSQL
Why, specifically, would you not want to use Ingres or for example Firebird, which both satisfy the 'commercially usable' and 'low end' criteria (although each databases proponents will probably protest the 'low end' bit. Is there something a low-end project would need that is not covered by these databases?
If you want a database that offers what Sybase does, but without those silly restrictions ("5GB ought to be enough for everyone" indeed), you might as well look at Ingres. Open Source but available with full support from CA should you want it.
Slashdot Mirror
With the algorithm revealed, it'd be possible to "predict" the future domains for a year or so forward in an automated fashion. Then you monitor the registrars for registration requests for those domains, and you have a fairly decent idea when the next wave is going to hit, and it might even provide a lead to the domain owner. Or you could "just" have those domains blocked from registration, for example.
http://opensrcd.ca.com/opensource/OpenDLM/Advantag e%20Ingres%20r3%20ClusterConfiguration.pdf
I don't think you understand what 'enterprise' means. One thing it means for sure is 'conservative'. With all these version 5 new features just released, any *sensible* enterprise will wait to see how they work in the real world. At *somebody elses* real world. Enterprises are not going to volunteer to be beta sites.
Dude, anyone leaving for Google is making the right decision.
And _still_ no hierarchical playlists. Damn! Do people really use playlists so seldomly? I save pretty much any playlist I ever created and with iTunes that gets messy in a hurry.
I dunno... restore from backup? You _are_ making backups, right?
Except that at the R&D where I work, WIFI is banned because of the security risks. I also see no reason to use wifi at home except for the laptop; wires are more secure and faster.
You might want to give Ingres r3 a spin. It doesn't have the fancy postgresql object-relational features, but it performs well under both Linux and Windows.
SQL Server is not getting hurt by PostgreSQL or MySQL. For places where MySQL would be a threat, MSDE would be there to cover the need. MySQL is _no_ match against MSDE unless you need what would in essence be a high-performance read-only database for the simplest of queries.
PostgreSQL would be a lot better, but it's been out for what, 2 months on the Windows platform? Only a nutcase would go into serious production based on that. Then there's the issue of availability of training. Tinkering along until you hopefully right is very expensive for a bussiness.
Standard disclaimer, like OSS as much as the next slashdotter, yada yada, but Free is not necesarily gratis.
It's called an ATA box, and you can simply buy one from a number of manufacturers.
WMA can be lossless. I don't know if the WMA-enabled players will play those files, though.
I've heard from people inside CA that Sun is getting complaints from
its Oracle-using customers; with the upcoming multi-core systems, and
Oracles' per-whatever-claims-to-be-a-cpu licensing, support costs for
Oracle are going to go through the roof for these clients for no real
benefit (or even choice once multicore becomes the only option).
So Sun is appearantly eyeing Ingres, being the closest competition to
Oracle on features and performance, to be bundled with Solaris by
default. SapDB was appearantly not up to snuff on stuff like parallel
queries and table partitioning, pretty crucial if you're going up
against Oracle.
CA is even in talks with SAP about Ingres being bundled with SAP...
says enough about how capable SapDB must be.
Visual Studio is a good IDE; things like intellisense make me immensely more productive. But intellisense is not available only in VS; Eclipse has it too, for example. And AFAIC, the advantage of VS is offset by the problems we see debugging programs (IIS-hosted com components, specifically); since everything is tied in to everything else, it's *damn* hard to compartimentalize the problem and turn off irrelevant stuff to home in on the problem. From my perspective, developing for Linux is a lot easier.
An adequate replacement for MySQL on Windows has been available for some time now: Ingres.
You're probably referring to XAML, and the XML part only covers GUI specification.
albeit in a somewhat limited form. It's called XSLT, and it's a HORROR to program in. Un-fucking-readable. XML is an INTERCHANGE format, people.
It's either Open Source, or it's Proprietary But Gratis
For Non-Commercial Use. Make up your mind. The fact that you may or may
not ship the source with the product does not make it open source.
A webapp has the strength that all you need is a web browser to view the content. When you update the webapp, all clients are updated instantly, without having to push something out to them, or making them download something. This saves a lot of stress and headache.
Which is nice for you. I haven't seen a single point in your message that relates to the need for the user, who is, after all, paying for this. The first order is to go see what the actual user needs, and if I were the customer, webapps would be straight out. Webapps are decent for infrequent use; they suck if you need rich functionality and need to interact with the software all the time.
If GDS runs as LocalSystem, it will find and display stuff of all users even if the system properly locked down and users would normally be unable to see each others documents.
They're going to attract more developers because they're going to make sure there'll be decent documentation and a top-notch IDE. XUL got there years before XAML and it's documentation is still worse than XAMLs. I have the Lizard book (which contains glaring errors BTW) and most of xulplanet et al in bound form, and developing/debugging even simple applications is horrendously frustrating.
If you think that's rather small, I really, really hope you don't have to find out in person how "small" you feel if this happens to you and someone else decides for you that 10 years in prison evens out the crime.
This doesn't help me at all when Postgresql refuses to install on my Windows 2000 server machine. There's a large difference between "1st release, appears to work on the desktop of the PostgreSQL devs" and "ready for production". Maybe Sybase can claim to be the "very attractive alternative to Microsoft SQL Server" because they have a (positive) history on Windows.
Why, specifically, would you not want to use Ingres or for example Firebird, which both satisfy the 'commercially usable' and 'low end' criteria (although each databases proponents will probably protest the 'low end' bit. Is there something a low-end project would need that is not covered by these databases?
If you want a database that offers what Sybase does, but without those silly restrictions ("5GB ought to be enough for everyone" indeed), you might as well look at Ingres. Open Source but available with full support from CA should you want it.