HNHacker News
TopNewBestAskShowJobs

johnzabroski

148 karma · joined November 18, 2008

Founder @ Simmaculate - bespoke software start-up, Christian, Hockey fan
submissionscomments
johnzabroski··on Oracle on why you shouldn't use NOSQL (PDF)
I left out the part where most of our fetch operations operate on just one primary key. The data structure is very stable and the need for different kinds of analysis has disappeared after several years of refining what the product does and should be. It's an analysis app that sets market prices to hypothetical values and simulates that alternate reality. It provides very fine-grained maximum likelihood explanations for why revenue would drop or rise.
johnzabroski··on Oracle on why you shouldn't use NOSQL (PDF)
There is some good information in this article if your ignore the Oracle marketing message. It is basically a synopsis of the past 3 years of NoSQL discussion.

What it doesn't mention is that everyone who picks NoSQL generally acknowledges these downsides. So it doesn't do a good job explaining why people still pick NoSQL.

TCO is probably the biggest factor I would have in picking NoSQL. As a (Microsoft) SQL Server customer, we (developers) all hate the cost of scaling SQL Server for each customer. Each customer needs their own resource governance. This means either separate servers or a virtual machine, both tied to a SAN. Virtualization MSSQL licensing costs are large without much material benefit due to odd licensing strategies that negate most if not all financial benefit to virtualization for small IT shops like us. By comparison, the better we understand why customers use our product and the more engineering decisions we can make (get away with?) then the cheaper technologies we will be able to use (NoSQL, etc.).

johnzabroski··on Oracle on why you shouldn't use NOSQL (PDF)
Why not store the data points in a Stable Bloom Filter and use the filter to automatically tell you the frequency of mouse movements? Could this work well? What does the data for mouse movements look like?

I am curious if your hypothetical question is a reality. :)

johnzabroski··on Design patterns aren't
I can look at code and say, "ah, Alan Perlis, you were right when I read your advice when I was 11 years old, but did not understand your wisdom [1]":

10. Get into a rut early: Do the same process the same way. Accumulate idioms. Standardize. The only difference(!) between Shakespeare and you was the size of his idiom list - not the size of his vocabulary.

[1] http://www.cs.yale.edu/quotes.html

johnzabroski··on Microsoft refuses to endorse WebGL, labels it ‘harmful’
That blog is trolling. The blog author copied and pasted the material from the blog we are currently discussing, and replaced WebGL with Silverlight.

Silverlight is more secure than WPF, too, by the way, and has to be. For example, in WPF there is a very insecure static method that allows you to steal a bitmap of the entire screen! This was one of the first things taken out of Silverlight.

If you want to know more about Silverlight security, ask Nick Kramer who maintains the Silverlight security best practices document for Microsoft.

johnzabroski··on I'm the guy who bought 259684 Bitcoins for under $3000 yesterday
Very good synopsis by Kevin.

However, he has two technical mistakes in his post from a security perspective:

1) We don't know the attack vector. For example: If Mt Gox has a SQL injection vulnerability, then a sophisticated attacker will not waste their time doing a rainbow attack on a random user. Instead, if the account balance is not encrypted and the key kept secret, then the attacker simply needs to do a SQL injection attack that returns the account with the largest balance:

select top 1 t1.account_id, t1.balance from Account t1 order by t1.balance desc

Instantly, the attacker knows the largest balance. This automatically reduces the attack space. This is a standard trick attackers use to bypass even needing to guess a password.

2) Compounding this issue, it seems Kevin is right, the attacked account had a naive password susceptible to a rainbow attack. According to rumors, this attack was a pooled account that mediated all the assets traded on the exchange. This implies that MtGox used a password susceptible to a rainbow attack to secure the master account. To answer Kevin's question, what user would amass $8M in bitcoins and use a bad password? The system administrators. 0xDEADBEEF.

Postscript: I have never traded or owned bitcoins, or even signed up for an exchange. I just find the security breach fascinating!

johnzabroski··on Everybody thinks SQL joins are slow-is it because MySQL doesn't have hash joins?
I just read up on this and it appears you are right, my issues are fixed in more recent versions of PostgreSQL. Apologies.
johnzabroski··on Everybody thinks SQL joins are slow-is it because MySQL doesn't have hash joins?
Aggregates that have to do full table scans are notoriously slow in Postgres due to how multi-version concurrency control is implemented.

Any time you comment out a WHERE clause on a big table while performing an aggregate report, Postgres chokes.

johnzabroski··on Everybody thinks SQL joins are slow-is it because MySQL doesn't have hash joins?
What do your libraries do to fake a bitmap index? When you say libraries, what layer of the stack are you referring to? Data access layer (e.g., via an ORM)?
johnzabroski··on F*: A Verifying ML Compiler for Distributed Programming
Stick to criticizing the paper.

Then you can write a blog rant about how painful it is to refer to "the second-order (polymorphic) lambda-calculus with bounded quantification" as F-sub or F<sub><=</sub>

johnzabroski··on F*: A Verifying ML Compiler for Distributed Programming
Microsoft has some minimal degree of support for F# on Mono. It is not the core focus for the F# team, but they do get to spend some time on it currently. Give it a shot.
johnzabroski··on Microsoft refuses to endorse WebGL, labels it ‘harmful’
That is extremely informative. How did you find it?
johnzabroski··on Microsoft refuses to endorse WebGL, labels it ‘harmful’
It is a completely separate house / separate bed issue.

You do not have permission to call Direct3D directly. You can't even do cool hacks like you can in WPF, stealing the Direct3D video feed and writing it to a movie file. Everything is abstracted away by (underpowered) APIs.

All Secunia advisories on .NET Framework / Silverlight are presently patched, and the total number is relatively small compared to other technologies like web browsers and Flash. I don't really know enough about WebGL to compare, though.

johnzabroski··on ORM is an anti-pattern
Commercial DBMSes have way better customer support than open source DBMSes. Not only do they better understand the performance characteristics of their clients, but they have dedicated teams whose job it is to isolate corner cases where the DBMS is not optimized for a particular environment.

My statement -- there is not a whole lot you can do to tune your queries -- is about rewriting the queries themselves, such as join hints, etc. Changing RAID configurations, organizing the data physically on disk differently, etc. have no bearing on the quality of SQL an ORM generates. So what does? Well, 20 years ago many DBMSes required you to compile stored procedures in order for the cost-based optimizer to cache anything. Today, not only does SQL Server 2008 R2 support fine grained plan caching and allow you to adjust the size of that cache, but you can remove from the cache any plan you dislike. You can also force a poorly performing query to use a specific plan cache. This is one of the ideas behind the LINQ Re-Motion project for .NET.

I am really arguing about where to put work effort into, and really NOT disagreeing with you. We are talking past each other.

I personally believe, as I wrote in the author's blog comments, that an ORM based on an algebraic model would likely be better than the big and irregular ORM APIs we have today.

johnzabroski··on ORM is an anti-pattern
In high quality RDBMSes like Oracle and SQL Server, there is not a whole lot you can do to tune your queries and the majority of your bottleneck is likely to be in how you are using your data. If you have inefficiencies, you either have a poorly designed schema or out of date statistics/indices.

The story is slightly different for open source RDBMSes which have inferior cost-based optimizers and multi-version concurrency control implementations that fail on a wider range of corner cases like:

select count(*) from Billing_And_Accounts_Receivable.Transaction

which is slow in PostgreSQL for reasons I'd rather not take the time to teach about here.

johnzabroski··on ORM is an anti-pattern
Good observation. Anyone writing a blog article on ORM should probably read the c2 wiki entry with the huge feature comparison chart of ORMs first.
johnzabroski··on ORM is an anti-pattern
Linq 2 SQL has ambiguous relationship path decision function when deciding how to map the Linq expression tree model to the SQL DBMS's model.

Compile-time type checking is very illusory with heterogeneous execution, not only for this reason but also because it is a distributed application and the schema can change.

johnzabroski··on How Offline Web Apps Should Work
A good early example of handling partial failure is the Zimbra mail & calendar app, the original "AJAX" app on the Internet, before Gmail/Google Calendar even. The Zimbra WebGUI supported an explicit "serverless" mode, which allowed for saving things like outgoing e-mail to a local repository and then, when network availability is detected, re-synchronize with the server and transparently transition to "server" mode.
johnzabroski··on How Offline Web Apps Should Work
> It's similar to the problem with RPC; you should not and can not simply sweep the difference between local and network communication under the rug. It works small and is incredibly painful in the large. Unfortunately, I can not seem to find a pithy explanation of why this is true. (Perhaps I should write one.)

I would be willing to help you write it if you'd like. I understand network disruption, partial failure, and weak/episodic connectivity very well, including scenarios where nodes in a network are required to remain radio-silent for long periods of time. Command-and-control military-style systems are much more general than the Web.

Related, automatic code distribution is a sort of Holy Grail in programming language design. It is difficult for many reasons. Even data is a huge problem. For example, if the toolbar buttons on Google Docs suddenly die (like they did for our marketing rep a few weeks ago), then the application can become extremely hard to use. Web applications don't handle this well today, and a cache doesn't really address this well, either, because it could be that the new resource invalidates an older cache. In other words, it is a version control and configuration management problem.

johnzabroski··on How Offline Web Apps Should Work
I agree, but am not sure for the exact reasons you state.

Put simply, offline applications need to support partial failure. The author of this article seems to want to write web apps without having to have much concern for partial failure. That is my own summary and take-away. If you agree, then we are on the same page.

Not dealing with partial failure means succombing to Fallacies of Distributed Computing - period. I wouldn't even trust the browser to do atomic swaps of cache', anyway, and I wouldn't even want to think about what that code would look like, or what the spec for the author's ideal would look like.

Bottom line: The author is defining words like "brittle" from one perspective only. What he wants is probably better provided by a library on top of caching. Moreover, I shriek at the idea of an application having to know its "size". That exposes the representation of the resource.

johnzabroski··on Blunt and necessary review of programming language books.
EDIT: Duh! His email is at the bottom of the article. Oof.

How can I get in touch with Andrew Binstock? (The author of this wonderful article.)

johnzabroski··on It's the Latency, Stupid
This is very true, but the flipside is that the patterns of messages over the network matter, too. Improperly designed communication protocols result in propagation delay, which is different from latency. Many real-world applications indirectly suffer from propagation delay, and many of the largest sites have tricks for minimizing delay, and some large companies even want older protocols abandoned due to their inefficient communication.

The reason LANs generally haven't cared about propagation delay is that they are not using networks already operating near the ultimate bottleneck: the speed of light. Some college campuses I know of have less bandwidth than an iPhone. But for Internet-scale computing, propagation delay is evident.

johnzabroski··on Why IEEE Fellow Radia Perlman hates technology
Yes, that is it. Obviously my rendition of the paraphrasing is not as well said as her actual quote, but you get the idea.
johnzabroski··on Why IEEE Fellow Radia Perlman hates technology
Her book on networking is the most frank and direct and easy to understand book I've ever read. She cuts straight to the chase, including saying stuff like, (paraphrased) "and after a few rounds of committee meetings, you get a complete incomprehensible mess, but these are the root issues they are talking about and the mess derives from two different views on committees on how to view networks..."
johnzabroski··on A better way to teach math
This was the single most amazing reply to a HN story I've ever seen. Then I read your bio. Go figure :)

Wish I could've upvoted this 100,000,000 times.

johnzabroski··on HTML + CSS3 is Turing complete
Neat! I posted it to Lambda the Ultimate front page. Been awhile since a cool/wacky hacker project got a front page item. Used to happen all the time 5 years ago.
johnzabroski··on Accounting for Computer Scientists
OK, that sounds pretty amazing, but is it as good as it sounds? For example, Leon Sterling wrote a 400 page book that included a crappy unrealistic example of how to write a Tamagotchi program. http://www.amazon.com/dp/0262013118 Funny, considering Luca Cardelli's paper about biologist's fixing tamagotchi's.
johnzabroski··on Accounting for Computer Scientists
I have to say, I hated the blog post, but being pointed out this plus that Reckon code somebody else posted, has made it worth reading and criticizing.
johnzabroski··on Accounting for Computer Scientists
I had really great accounting professors, who explained WHY things were done.

As with anything else, assume a normal distribution of teaching talent, and hope you end up being taught by somebody on the right side of the curve.

johnzabroski··on On the Engineering of SaaS
I didn't catch that fish scales joke until you pointed it out. Very nice.
← PreviousPage 2 of 4Next →