yoava

Have never tried it myself - but as a user of both DPP (canon digital photo professional) and Photoshop, I have found that the cabin software has an advantage with quality - something about understanding the camera better. How does darktable match up to DPP and Photoshop?

Your question is valid, assuming you trust the query planner to make the right decision. However, the query planner in most databases is not perfect and can miss.

We have tried a few different alternatives, including the join, and found that this sub-query option actually works better.

A sub query forces the database to execute the first query on routes using the index, then use the result for the second query on sites. It leave nothing for the interpretation of the optimizer which may decide to so some silly thing like full scan on the sites table before performing the join.

Big thumb up!!!

True. Memcached is a great tool and great for this use case. But when you get read latency of ~0.3 mSec from MySQL, why add another hop and another engine to the mix?

But schemaless does not help migrating the data from structure A to structure B.

Consider, that in this case, the json text field is schemaless. How is that different from other schemaless databases?

If anything, you should state that if you wanna avoid alters, use CQRS, not just shcemaless

Which NoSQL are you referring too? Most are not that easy to implement (saying that while managing a few PBs of data in production with a few such tools)

The question then is what is NoSQL. Does mongoDB a NoSQL engine? can you scale it to 10s of TBs? Can you really scale out MongoDB? I can ask the same for Redis and a whole line of other NoSQL engines that are not really scale out solutions.

(yee, you can shard both Mongo and Redis, as well as MySQL and get to 10s of TBs).

What are the benefits of Cassandra or Redis that I am missing, for this use case? We have the latency figures as good as Cassandra can get and we get a reliable engine to store data (something that Redis is not - read Aphir post about Redis)

The main advantage of MySQL that we keep is the rock solid platform with all the know-how to operate and manage.

Well, it used to be databases that do not do SQL.

But now, that Cassandra has SQL like query language, hadoop has SQL like hive and other NoSQLs implement semi-SQL interfaces, I believe a good definition is a database that is not one of

1. ACID

2. Strongly typed table schema.

When we started with this use case, at 2008, PostgreSQL did not look so good. Today, to be honest, I'd probably try it for new projects, except for the vast experience with MySQL that we have at Wix

Having read the post, I wonder about debugging of typescript, especially in the browser environment. Source maps work to some degree, but do those scale for a large project? What is the experience of debugging a large application built using TypeScript compared to plain Javascript?

There is a lot of good advice here, but let me add my 2 cents

1. good wifi - a lot of hackathons are not prepared for the number of devices connected when 100 people arrive...

2. set a clear schedule. My favorite is Fri night - intro session, people present ideas, team building Sat morning - starting to work 10am workshops at 11am end of coding Sun at 12pm presentations Sun 1-3pm Judgement - 4pm

3. team building is a critical part in the event. I normally have a few people from the organizing team helping people find who to work with. We have tried using colored stickers for different expertise - developers, designers, ideas, FEDs, etc. Most hackathons do not have sufficient designers.

4. Food - keep in mind that Pizza is great for males. But women may like lighter food. Given you have an over-night event, you need to take care of that. Same goes for beer - have a wine option

5. As many organizers as possible in the event. People have questions and need help all the time. The more people you have to help the better.

I was sure socket.io is a service you use... for some reason...

But you are right - it is exactly the same, only that socket.io looks more solid.

looks super cool.

However, I have to ask - why did you do it? What was the use case that made you create this lib?

I wonder about the rainy day cases of this - what if a connection is lost for a minute? will the recovery deliver all the missing messages? will it restore consistency once the connection is restored?

Also, Jet is based on installing a single router server. What about scaling that server? HA? If you install two such servers, do they communicate? Or does each create it's own communication domain?

Socket IO is a service, this is something you install on your server

It is a great tool, and I have used it. I have also used Emma.

Both use instrumentation at loading time, which is great (because it is transparent). However, both recommend to run tests twice because of the instrumentation. In both cases, the Maven plugin runs tests twice - once for testing, and once for coverage - which is a total waist of time.

I was thinking on using the debug interface to track coverage without instrumentation, those without the risk of modifying the tests.

One of the things I was always wondering about is if we can use the JDWP protocol to do code coverage in testing. I imaging a debugger that instead of stopping at breakpoints, just tracks what code is running and what branches are covered, and outputs a coverage report.

Today all (I think) code coverage tools use code instrumentation, potentially changing test results (as we run a modified version of the code we test). The impact of this is that most coverage tools suggest running tests twice - once without coverage tracking (the actual tests) and again with coverage, a practice that slows down builds.

Using the debugger interface for tracking code coverage means we are running unchanged code in tests, those not requiring a second run of tests just for coverage.

In addition, using the debugger interface, we can look at variable values and estimate coverage based on different states of variables in a statement.

Thanks for the pointer, I was looking for a sane explanation of the Amazon security and signature algorithm.

I have to disagree with the other comments here regarding the client library. I think that given the precedence of Amazon API, given that people understand how to sign APIs like amazon, this method will be accepted even without a client library.

Being a Java / Scala dev, I prefer that an API provider allow me to select the HTTP client libraries to use and prevent from forcing me to use a specific library & version via SDK transitive dependencies.

Agree,

He should have at least a link to the Ember project page and some intro as to what it is.

Maybe he should have a episode 0 video which explains why should someone use ember instead of just jQuery or Backbone?

And even our old Windows shell...

The one thing they did not mention was the battery weight and size. The biggest barrier for electric cars and other battery uses is the ratio of energy to weight and size.

Today, this ratio enables about 70-100 miles travel for an electric car with a similar weight and size as a gasoline car.

will be interesting to follow this initiative.