HNHacker News
TopNewBestAskShowJobs

tentonova

95 karma · joined December 30, 2009

submissionscomments
tentonova··on Myths about code comments
Nine times out of ten, I ignore comments unless I'm stumped. In fact, I'm tempted to make emacs hide all comments unless I explicitly expand them.

Given that Jason Baker just got out of school and is espousing a bold "I'm too smart for X" opinion (where X is, in this case, code comments), I'm not too inclined to pay much heed.

Only write comments that aid in understanding. I tend to comment a lot, but that's because I like someone to be able to approach my code and immediately understand the purpose of a particular code block. It's faster to read the comments than to both trace and digest the code, no matter how understandable it is.

After over a decade writing software, I much prefer over-commented code to under-commented code. No, comments aren't free, but the alternative is worse. Too few comments make your code unapproachable to others -- and eventually, yourself.

tentonova··on TSA Withdraws Subpoenas Against Bloggers
This is an excellent (Regent Law School) lecture that elucidates exactly why you should NEVER speak to the police: http://video.google.com/videoplay?docid=-4097602514885833865...
tentonova··on XML Sucks
Even with a binary format, you'd be sending data out of band in XMPP. XMPP is designed for interchanging _small_ bits of data.

Having implemented both XMPP clients and servers, I don't particularly see your point. Exchanging small binary message packets would not be an issue.

How would binary stanzas be any different than other message-based multiplexing binary protocols?.

Also, the complexity of out-of-band protocols in XMPP has nothing at all to do with XML.

The fact that you have to go OOB at all introduces significant complexity.

tentonova··on XML Sucks
There are obviously much fast formats for that type of thing, but they have their own drawbacks which are significant. Protocol Buffers are crazy fast but aren't self describing or human readable.

Why does that matter? The fact that they aren't self-describing more or less requires that you use a published message definition, which solves one of the major problems of XML schemas -- nobody actually uses them, and many that do use them incorrectly.

XML is great for what it is, and it has its drawbacks, but as a universal transport it is pretty rad.

Having wasted far too much of my life on parsing XML documents, I simply can not agree.

XML as a universal transport just sucks compared to the modern alternatives.

tentonova··on XML Sucks
XML proponents always trot out "we're just not there yet" or "the basic idea is good, we just need some small fixes", or "parsers just need improvement -- use a better parser library", or any other number of excuses as to why XML doesn't actually suck, it's just a victim of poor implementations or to-be-fixed design inadequacies.

Meanwhile, Protobuf and Thrift work today. They're fast, they're size efficient, and unlike XML, they're simple.

It's time to stop making excuses for XML. It's an inexcusable ball of poorly designed unjustifiable complexity created by architecture astronauts run amok.

I'm disappointed at the upvotes on a whole page of platitudes on why XML isn't a bad format, it's just misunderstood.

tentonova··on XML Sucks
"XML is very bad at handling binary data." That is mostly false.

No, it is not. Encode a reasonably sized JPEG (say, 500k-1MB) in an XML document. Try measuring how quickly you can parse that XML document on a lower-end device.

Now try encoding a batch of thumbnails (say, 30k each) in an XML document. Now try seeing how fast you can parse 500 of them on a lower-end device.

There is no obviously winner (widely adopted) standard for binary format XML although there will be some day.

"Some day" doesn't do us any good today.

tentonova··on XML Sucks
The primary issues with ASN.1 seem to be that the availability libraries are poor and the documentation is both hard to find, and difficult to follow.
tentonova··on XML Sucks
The use of text is the right thing;

Why? It's genuinely inefficient. This is not academic, as easily illustrated by serializing even a megabyte of binary data in a text-encoded document. Base64+GZIP is not a solution.

... if you really care about performance at a level that naively compressed text formats can't provide ...

Why are we optimizing a transfer serialization for your own readability and not the devices we're actually targeting?

I've wasted days trying to get barely acceptable XML parsing performance on the iPhone, and similar lower-end ARM devices are becoming much more prevalent these days.

... you frankly need to be defining your own wire protocols anyway.

Protocols like XMPP dictate the use of XML. There wouldn't be nearly as many performance issues if they'd used something akin to Thrift, Protobuf, or even the woefully misunderstood ASN.1 DER.

Since XMPP uses XML, they've had to define complex out-of-band protocols for transfering file data, instead of simply sending the data in-line as simple binary XMPP messages.

I could not more strongly disagree with your position. Protocol implementations should use well-defined, efficient binary serialization mechanisms (such as Protobuf or Thrift) wherever possible to maximize performance, and minimize both serialization overhead and implementation complexity.

tentonova··on A Twitter app for Mac OS 6 through OS 9
Historic note -- prior to System 7.1, all Mac OS versions were freely redistributed and provided for a nominal fee from Apple.

We would get our copy from the local university bookstore for the cost of the media.

tentonova··on Doctorow, How to Destroy the Book
You don't "own" your instance of Basecamp, you just rent it. And there's nothing wrong with that.

Some might disagree.

Personally I find SaaS to be a general business imposition with significant long-term costs in terms of lock-in, operational expenditure, and an inherently poor negotiating position with the vendor.

I dislike required service contracts or yearly per-head licensing fees for the same reason.

With more openly licensed software, a key differentiator is that we can choose to continue to use a previous version of the software, whereas if we cease paying for a service, we must migrate all operations, data, and training.

tentonova··on 2000-2009: Microsoft's Decade of Shattered Dreams
It is amazing to me that an organization that is Microsoft's size can decide and execute on anything at all.

Cutting five layers of management, which is already few for an organization that's Microsoft's size, is really a recipe for chaos.

I'd say Microsoft's barely navigable size might have a lot to do with those 5+ layers of middle management.

tentonova··on Ask HN: What startups here are focusing on developing on top of .NET?
In terms of physical servers, we're actually 50-50 Windows / Linux. Starting on Windows did not blind us to Kannel, Rails, PostGIS, Apache, Samba, Erlang, etc. We use tons of open source software where it makes sense.

What do you use for desktops, e-mail, corporate servers, etc?

My goal was elucidate the hefty cost of Windows lock-in and Window's demonstrably strong tendency to pervade your organization in terms of political, staffing, and technological investment.

If it's considered the best tool for the job and these recognized costs are acceptable, then there's no reason to not use it -- but history should also provide some insight into how Microsoft behaves with organizations that become reliant on their technology.

Microsoft isn't being magnanimous with Bizspark -- they're trying to ensure that more startups are locked into their technology stack early, when the perceived immediate advantages may seem most attractive.

tentonova··on The Scientific Scandal of Antismoking
We live in a representative democracy.

If the costs were not externalized, market and political forces would dictate changes in both personal choices and infrastructure investment.

I don't see the rational for abdicating responsibility for the choices in where we both live and work, as disclaiming responsibility for the externalities incurred by these choices ensures that a more optimum "sociopolitical geography" will not be reached.

tentonova··on Ask HN: What startups here are focusing on developing on top of .NET?
I took some code recently and ran it on Mono and only encountered one issue, which was a Mono bug that has now been fixed. MonoDevelop isn't a drop-in replacement for VisualStudio which is a good thing since VS is bloated and MonoDevelop isn't.

Confirming neither is a drop-in replacement, which isn't to say that Mono isn't useful or valuable, but simply that it is necessarily 2nd-tier in a Windows-focused development environment.

Given that you've spend 3 years developing C# in VMware on a Mac, I'd ask why you're not using native Mono/MonoDevelop entirely?

I have been writing .NET code exclusively in VMware for 5 years now, 2 years on Windows and 3 years on a Mac. The performance impact is there but it isn't a deal-breaker (especially if you have a fast HDD and enough memory (6GB)).

What do you see as the significant advantage of .NET that has warranted using non-native tools with an admitted performance impact exclusively for 3 years?

This sounds like individual developer inertia, not a high-level business decision.

tentonova··on Ask HN: What startups here are focusing on developing on top of .NET?
If the cost is too high to bear, then you don't have a luxury of choice.
tentonova··on Ask HN: What startups here are focusing on developing on top of .NET?
There's nothing wrong with Mono, but neither Mono or MonoDevelop are drop-in replacements for C# and VisualStudio.

VMware is not an adequate solution for day-to-day development. There's a performance impact, significant memory overhead, and running Windows inside Linux/Mac OS X is not any more accommodating to users familiar with a UNIX environment than simply running Windows natively.

tentonova··on Ask HN: What startups here are focusing on developing on top of .NET?
The opportunity cost associated with learning and becoming reasonably competent in a different development stack can be non-trivial, especially if you had 5 to 10 years of experience with a different stack or set of technologies. I've yet to encounter a new framework/API/stack/language which I've been able to move to in only a few weeks and be 80%+ as productive as what I already knew, as there's often lots of useful minutiae, subtleties and new concepts you need to acclimatize over time.

If all you know is Microsoft, then that's all you can do, and the organization's technical direction will almost certainly model that initial decision.

However, if you have the luxury of choice -- and I think most people do -- I'd advise against it. The short and long-term costs of Microsoft lock-in are decidedly "non-trivial". The considerable investment in staff, licenses, and technologies make it very difficult to migrate to a non-Microsoft stack in the future.

The converse also applies. Granted, a competent engineer can learn anything, however you're initially inclined to pass on them because of the associated ramp-up time.

In my experience, you're entirely locking out engineers who use Linux and Mac OS X when you move to a Microsoft stack, but you're not necessarily locking out Windows engineers when you use a cross-platform stack.

tentonova··on Ask HN: What startups here are focusing on developing on top of .NET?
Unless the tools/languages are tremendously better than what is available for free/cheaper, I don't particularly understand the value in:

- Risking Microsoft's ire by breaking the licenses

- Locking yourself in to long-term Microsoft licensing

This was a pattern I saw in many, many startups in the 90s -- organizations that relied first on UNIX systems for their servers (often times Solaris, Linux, and in the early-to-mid 90s, IRIX), would eventually adopt Microsoft products for some component of their infrastructure -- usually Exchange, based on heavy political pushes from the growing number of business users.

This always to the same effect -- the Microsoft products spread due to lock-in network effects until it began to near 100% MS on the desktop, e-mail, and corporate servers. Production servers generally remained UNIX due to the costs involved. The IT organization shifted to MS, costs went up as the staffing necessarily increased to support administering Windows systems, expensive political maneuvering arose between engineering and business as they both fought to move to systems that they thought better aligned with business priorities.

At the end of the day, everyone wound up locked to MS with heavily entrenched political interests in keeping the status quo (and the job security that went with it).

Having seen the fall-out from migrations to MS products in corporate IT, I can't imagine voluntarily implementing MS as the primary production and developer system at a startup. You're locking yourself out of alternative solutions, you're signing up for significantly increased capital and operational expenditures, and perhaps most importantly, you're excluding an entire class of software engineers that primarily work on UNIX-based (including Mac OS X and Linux) systems.

tentonova··on PCC builds OpenBSD kernel (4.6 -current)
Not that LOC necessarily says anything on code complexity or design, but here's sloccount on gcc42:

  ansic:       869244 (70.89%)
  ada:         150280 (12.26%)
  cpp:         114629 (9.35%)
  f90:          34164 (2.79%)
  sh:           18588 (1.52%)
  objc:         13047 (1.06%)
  exp:           8821 (0.72%)
  fortran:       7139 (0.58%)
  asm:           4422 (0.36%)
  ml:            2485 (0.20%)
  perl:          1080 (0.09%)
  awk:            842 (0.07%)
  lex:            589 (0.05%)
  yacc:           587 (0.05%)
  pascal:         105 (0.01%)
  haskell:         98 (0.01%)
  lisp:            59 (0.00%)
tentonova··on PE Fund for Litigation
Is this a reasonable vehicle for entities that simply would not otherwise have the funds to engage in legitimate litigation against an well-funded adversary?

That said, there seems to be an inherent unfairness in a system where the opponent with the largest coffers wins, and your only reasonable option as a litigant is to find an equally capable financer to invest in your redress of grievances.

tentonova··on The Scientific Scandal of Antismoking
That's fine, but doesn't solve point 2, and doesn't take into account the "social" costs of car-dedicated community infrastructure.

Of course, these costs are really not "social" at all, as easily observed by reviewing the impact on surrounding neighborhood small businesses and property values in areas where inner-city freeways were erected in the 50s-70s, and then torn down again in the 90s or 00s. If you're interested in the pure social costs, there's always the increase of crime, in-cohesive communities, etc.

Cars aren't going anywhere, but that doesn't mean we should always optimize for them above all other concerns, though I agree that we should use more efficient (and less polluting) vehicles.

This is a bit off-topic on a discussion regarding second hand smoke -- my apologies.

tentonova··on The Scientific Scandal of Antismoking
Yes, people should drive cars that don't produce such a large amount of noxious fumes, they should drive less -- cars are the number one accidental killer at 40k deaths/year in the US.

Both of these things would naturally occur if drivers were not free externalize the significant costs of their personal choices.

tentonova··on PCC builds OpenBSD kernel (4.6 -current)
Compiler licensing is not enough to supersede the BSDs' pragmatism. We've been using GCC for years.

If you've had to maintain GCC for your platform -- or worse yet, tried to add even small improvements -- you'd understand why momentum is building to replace it.

Not that switching to GPLv3 helped GCC any. That's one reason among many that Apple stopped GCC development and put their weight behind LLVM.

← PreviousPage 2 of 2