Hacker Newsnew | past | comments | ask | show | jobs | submit | bryanmig's commentslogin

After using an email-based homegrown solution that I thought was sufficient, I gave RayGun.io a shot. I use it for .NET exception tracking and I am about to wire it up to a Rails app, and a very very large Backbone JS application.

It is really quite good (at least for .NET). The management UI is great and does a very nice job of grouping duplicates, similar issues, etc.

I already use some dev tools from Mindscape (their .NET ORM, LightSpeed) and their products and support are top notch in my experience.

http://raygun.io


This isnt that big a deal. They say that you can opt out of this and that it does not apply to Fios or Business customers.

I'm sure there is a huge amount of customers who will never have any clue that anything has changed since they dont play games, run servers, need VPNs, etc.

It's probably a good thing for everyone else given that it does raise even more awareness of the problem.


There are some large-ish groups of people out there for whom this will cause issues, eg. people who play console multiplayer gamers (millions of people including Halo/COD/etc players).

As someone who games on Xbox Live, a part of me would actually like to see this become more common with other carriers to force next gen consoles to move to a dedicated server model since the current "pick a host among the gamers in the lobby and hope for the best" model results in a fairly poor experience a lot of time even without pervasive CGNATing.


Unfortunately, things seem to be moving the other way, with PC FPSs (traditionally using dedicated servers) adopting the lobby model - it's why I never moved beyond CoD 4.


And so? You can still opt out?


I can also opt out of my ISP's DNS hijacking, but I don't bother to anymore. (It keeps forgetting me when I get a new address.) It's simply become the new norm.


Client side: jQuery, SASS, Backbone.js, JS written in CoffeeScript. AngularJS for our internal administration app.

Server side: ASP.NET MVC 4, Ninject IoC, LightSpeed (amazing super fast ORM from Mindscape, not free)

Infrastructure: Amazon AWS (EC2, S3, CloudFront), SendGrid for email, RabbitMQ, MySQL 5.6, MongoDB (for realtime stats)


Admittedly, I dont know anything about the law but I have a couple of questions:

1) If convicted, would that have set some precedent that could have affected others for years to come?

2) If the "Suggest of Death" papers were filed, does that mean that the courts cannot convict him of any wrong doing, thus preventing any precedent from being set?

(Though it sounds like one.. this is not a conspiracy theory.. just a legitimate question)


Common law holds an individual responsible for their actions, not their families or associates. As such, there is no-one to punish in the event of death, so there is no point in continuing the trial (and no-one to pay for a defense, hence no fair trial is possible). It's why in some areas suicide is not a crime, but attempted suicide is.


Criminal convictions don't carry any binding authority of precedent. Only if some issue of the case were to be appealed, would the ruling on that issue become precedent on courts subject to that appellate jurisdiction.

Having said that, a successful conviction could encourage other ambitious AUSAs to bring charges in situations with similar facts.


1. Generally speaking, district court criminal cases are non-precedential; i.e., they are not binding on other courts. Sometimes a district court will decide a legal issue that is adopted by a higher court and then becomes precedential. But the more I think about this case, the more it seems to be a political case, and in political cases, the rules are different. In this case, if the Internet reporting is correct, Swartz was only given the option to plead open to the indictment. That is extraordinary. Usually in a non-political case the prosecutor will agree to dismiss most of the counts in exchange for a guilty plea; would recommend a cap or prospective sentence, agree on the amount of the fine, agree not to allocute, etc. Someone wanted Swartz' head on a pike, perhaps for the PACER episode. 2. Yes. Upon the death of the defendant, the case is over. With all respect to Ms. Ortiz, Rule 48(a) of the Federal Rules of Crim. Proc. shouldn't apply in this case. That rule relates to the dismissal of charges before trial. Upon the death of the defendant, the case cannot proceed to trial as there is no longer a case or controversy; there is only one name on the side of the v. and there needs to be a name on each side. This is a simplification, and it may well be a practice in the District of Massachusetts, but it is not the correct procedure (though I may be hypertechnical here). The point is that it wasn't government benevolence that caused them to file, the case was over upon the death of the sole criminal defendant. If there was another party involved, the case can and would proceed, absent a plea.


Your questions are kind of like asking about what could happen if we could go faster than the speed of light. But in this case I don't think there's much to be gained precedent-wise one way or the other, the applicable laws have been on the books (at least in their basic form) for decades.


NYC - Full time - iOS and Android developers

FieldLens

We are hiring both an in-house Android developer and iOS developer for FieldLens, a venture-backed startup in the heart of Manhattan’s Flatiron district. You'll be responsible developing new features and iterating and maintaining our existing application.

Our Android application currently specified for API Level 8 (Android 2.2) and up.

Our iOS application is being built for iPhone using iOS 5, uses Core Data for local storage. After launching on iPhone we will target iPad as a universal application.

FieldLens is a technology startup focused on bringing a beautifully designed enterprise solution to the construction industry. Our application is a fully-networked solution with robust back-end services driving functionality across any platform. Designed mobile-first around the actual needs of the construction professional, our mobile applications work completely offline. It’s time for the awesomeness of apps to change a big old broken industry. Join us and make it happen!

We’ve got a great team and work in an awesome shared workspace in the thick of the NYC startup scene. Over the past several months we’ve been building Version 1.0 and are headed into beta soon. Recently seed funded, its now time to build out the team. No annoying management meetings, no dress code, and there is a beer bottle (with the FieldLens logo) on our dev team’s desk. We work our butts off but also know how to have fun.

We'd like you to have the following skills: - Experience with SQLite databases, JSON and RESTful web services (Spring framework) preferred - Seriously good OOP skills - Solid Java or Objective-C

Sound interesting? Shoot an email over to matt at fieldlens.com


True and untrue.

I use MongoDB for my startup (yabblr.com) and have quite a relationship data stored in my entities.

For example, my user entites have an array of commentId's stored inside of them.

Whenever I fetch 1 or 1000 users from the database, a framework that i designed will look at the entire list of users and build a single list of commentIds based on that list.

Then I do one more lookup on the database to find all comments in my new list of comments.

Then a final pass over the users looks up the commentId associations and inserts the actual comment object into the user object.

Finally the list is passed back to the consumer. Its 2 database calls. It does require that there are 2 iterations over the first call (one to gather up comment Ids and one to associate comments with users) but since its being done in the application layer, its much easier to scale.


The point is that when your table has 4 rows in it, it doesn't matter if you do a full table scan. Wait until you deploy your app and that table now has 4,000,000 rows in it.. then you have a problem.

In MongoDB (and maybe others too) there exists an option to fail when doing a table scan so that you know immediately while developing that there exists a potential for things to go awry at some later point. You can fix that now by either re-thinking your data structure, re-thinking your query, or adding appropriate indexes.

MySQL's slow query log is good for reactive development instead of proactive development.

I think its an indispensable feature.


Errr... With a typical RDBMS, doing a full table scan depends on the current stats (e.g., number of rows, are the stats current, state of the index, possibility to use an index, presence of cached data, previous query performance etc.). It does not depend only on the query and the data structure, so it is near impossible at development time to be certain that a table scan will occur during production. In fact, a table scan might occur today and not tomorrow for the same query, but with different data.

Many developers have been burned by trying to optimize their queries and indexes too early. The query planner, although sometimes unpredictable, is generally better than developers at predicting the performance of a particular execution plan. Table scans are also preferable in certain situations.

Relying on the fact that RDBMS have sophisticated query planner (as opposed to MongoDB) is not a sign of "reactive development". It just means that you should test your queries (and your indexes) with close-to-production data, and, as the data grows and evolves, continue to test, because the best execution plan might change.


Slower query using indexes is better than randomly using table scans depending on statistics, ...

At least for interactive apps, NoSQL wins.


There are cases where a full table scan is faster than an index scan, and there are cases where the index scan is faster. There are even cases where the only option is a full table scan!

I still don't see what a setting that gives errors when a particular access method has been chosen would be good for.

You don't care about the plan, you care about how fast the query runs.

You'll always have to do reactive development when trying to get good performance. There is only so much simulating and testing you can do and real data volume and distribution changes all the time.


I've used Bugzilla, Mantis and Jira.

Jira, while not free, is the best of those three for sure. They have a nice $10 for 10 user license that is quite affordable and besides the 10 user limit, has no functional limitations.

I've read good things about FogBugz but have not used it myself.


The ability to pick and choose the components that make up my workstation - laptop, monitor, etc. I hate being given a laptop that I dont like upon joining. Or worse, being given a laptop used by the guy before me.


Proof that hipsters are taking over the world.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: