61–70 of 99 posts
You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of developers. Luckily the 'L' + 'A' + 'P' cannot be bought. LAPP stack anyone?
Earlier quoted context omitted.
I am using the LNNMMMMP stack at the moment... Linux, nginx, node.js, memcached, MySQL, Mono, MongoDB and PHP. Am I normal?
Even for a twitter recommendation engine, that's just a lot of moving parts. I hope your development is driven by accurate profiling and benchmarks. It's much better to have a dirty, but very surgical fix in a specific bottle-neck, than to have your application "scaled" with too many layers of individually "optimized" components, that bog each other to a crawl when combined.
Mono for long-running and complex backend processes.
nginx, PHP, MySQL, memcache - for presentation - quick!
node.js provides an event bus between PHP and Mono
MongoDB is taking over from storing large blobs of JSON in MySQL.
You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of developers. Luckily the 'L' + 'A' + 'P' cannot be bought. LAPP stack anyone?
Remove M for MySQL in LAMP and make it M for MongoDB
Earlier quoted context omitted.
The idea was that their network protocol was an original copyrighted work, and that any clean-room implementation of it would be a derived work. That does indeed sound crazy, but they also had piles of cash to throw at lawyers to go after anyone who challenged them, and (maybe as a result of that) nobody ever made e.g. a clean-room BSD or LGPL licensed version of the mysql library. So it never made it to court AFAIK.
That's incorrect, just check libdrizzle.
I believe MySQL/Sun used to make a lot of money dual licensing the GPL client library. No longer!
You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of developers. Luckily the 'L' + 'A' + 'P' cannot be bought. LAPP stack anyone?
I take it the extra P is for PostgreSQL? As far as I could ever tell, the only advantage MySQL ever had over PostgreSQL 10 years ago is that it ran on Windows, and Postgres did not, back then. Oh, and by skipping ACID features, MySQL was faster. So, back in the day, that drove me to conclude that all the MySQL fans were crazy, and I decided to use Postgres at home, since Windows != server, and having done quite enoug…
I bet the whole community will support the new sql.
Earlier quoted context omitted.
Even for a twitter recommendation engine, that's just a lot of moving parts. I hope your development is driven by accurate profiling and benchmarks. It's much better to have a dirty, but very surgical fix in a specific bottle-neck, than to have your application "scaled" with too many layers of individually "optimized" components, that bog each other to a crawl when combined.
There are a lot of moving parts, but these are separate sub-systems with well defined boundaries of interaction. Each sub-system is implemented using technologies selected for specific characteristics. Mono for long-running and complex backend processes. nginx, PHP, MySQL, memcache - for presentation - quick! node.js provides an event bus between PHP and Mono MongoDB is taking over from storing large blobs of JSON in…
I was on the opposite side of things, when I did we last. I had language integrated into the web server, and I wrote my own caching primitives. All optimization went into the request handler, and optimizing a single function is easier than debugging a whole stack.
A decent solution, but it had no massive inputs, so I slept better at night knowing it wasn't being tested.
Earlier quoted context omitted.
The idea was that their network protocol was an original copyrighted work, and that any clean-room implementation of it would be a derived work. That does indeed sound crazy, but they also had piles of cash to throw at lawyers to go after anyone who challenged them, and (maybe as a result of that) nobody ever made e.g. a clean-room BSD or LGPL licensed version of the mysql library. So it never made it to court AFAIK.
A nice fiction. The reality is that copyright covers verbatim copying. If you read a book and write a review, the term "derived work" makes English sense, but not legal sense. Similarly, if you read the MySQL code looking for magic words to say to the server to get it to give you data, saying those words is not copyright infringement. It's "learning", not "copying". If anyone used MySQL, I would write a BSD-licensed…
What would happen, if the protocol would require sending a picture of a picture of Mickey Mouse with each request (or some copy-righted novel)?
Earlier quoted context omitted.
I think the reason you are being downvoted is that you are comparing PostgreSQL with the commercial version of MySQL. A better comparison would be between EnterpriseDB and the commercial version of MySQL.
Afaik, the free version of MySQL doesn't let you do a live transaction-safe database dump of InnoDB tables. A pretty basic feature I thought, which is included in the free version of PostgreSQL.
mysqldump --single-transaction
This option sends a START TRANSACTION SQL statement to the server before dumping data. It is useful only with transactional tables such as InnoDB, because then it dumps the consistent state of the database at the time when BEGIN was issued without blocking any applications.
Earlier quoted context omitted.
A nice fiction. The reality is that copyright covers verbatim copying. If you read a book and write a review, the term "derived work" makes English sense, but not legal sense. Similarly, if you read the MySQL code looking for magic words to say to the server to get it to give you data, saying those words is not copyright infringement. It's "learning", not "copying". If anyone used MySQL, I would write a BSD-licensed…
> Similarly, if you read the MySQL code looking for magic words to say to the server to get it to give you data, saying those words is not copyright infringement. It's "learning", not "copying". What would happen, if the protocol would require sending a picture of a picture of Mickey Mouse with each request (or some copy-righted novel)?