msmith

FWIW, I caught the tail end of the stream and the quality was fine.

I'm looking forward to being able to watch the entire recorded session when it's available. If you're at all interested in the issue, I recommend that you watch this and make up your own mind on it.

Edit:

The recorded video is at http://infodocket.com/2011/11/16/live-video-stream-sopa-stop... I used VLC to view it.

12:19PM central time - The chairman, Rep. Smith, was asking whether this bill would impact our ability to implement DNSSEC. He seemed legitimately concerned that it could weaken security on the internet.

I have no idea whether there's any basis for concern, but I'm sure we have some DNSSEC experts here on HN. Comments?

Did not recognize my unicode snowman, but it got pretty close: Ṏ Ổ ồ

How do you do the code obfuscation? rubyencoder or something homegrown?

I learned recently that you can also do this on the command-line with "git diff -b"

Ah, I see. Thanks for the pointer.

You failed to launch the project that was going to help people launch projects.

It's interesting that someone went out of their way to obfuscate the interim.html script:

    document.write('<s'+'cript language="JavaScript" src="');

I guess they were intentionally trying to evade some tool that looks for '<script'?

I'm sure it's monthly. The price tiers are the same as the full Heroku platform (http://heroku.com/pricing), which is billed monthly.

No, Java and Scala syntax are quite different. I can really only think of a few cases where they share syntax.

It's calling the fromFile method on the io.Source object. Package names are lower-case by convention, class and object names are capitalized camel-case, and methods are lower-case camel-case.

Also, 1.upto(10) can also be written as (1..10) in ruby

That's a really good explanation.

To be honest, I didn't really understand what he was trying to say, but I am certain that the first two problems he mentions are not what DI is intended to solve.

This is not at all the definition of Dependency Injection. The wikipedia article [1] does a pretty good job of describing what it really is. DI is a pattern that is intended to reduce coupling between components in a large system. It applies to any OOP language, although it is true to say that the term first gained popularity in the "enterprise" Java world.

I also think it's wrong to conflate DI with XML. One of the first major DI frameworks, Spring, did use XML for configuring and wiring-up components, but it's also quite popular to do this part purely in the code, without any external configuration files.

[1] http://en.wikipedia.org/wiki/Dependency_injection

Or maybe his paying customers would worry that they're relying on a service that's considered to be a side project.

I'm pretty excited about Account Manager, the identity management feature, that's scheduled for Firefox 5. It has the potential to make the web both more secure and simpler to use. Usually those goals are opposing.

Of course, the biggest obstacle will be getting people to add support for the feature to their site.

This is not hacker news.

I'm not sure if I'm following your point. Are you suggesting that anonymous inner classes aren't useful in a well-designed Java program? If so, I'd have to disagree.

As an example, the Java Collections API (one of the most well-designed Java APIs, imho) uses Comparators extensively. It's pretty common to define the Comparator as an anonymous inner class when you need to do a one-off sort() or max() call.

Scala just makes it easier to use this pattern. There's no need to go through the effort of wrapping the function in class if you're only going to use it once.

Nope. In the FAQ, it says "You will not be able to switch back to the old design after upgrading."

How long does it take your software to crack the other half?

The thing that bothers me the most about this is that children are subject to the same pat downs. I can't imagine the difficulty of trying to explain to a child why it's OK for a TSA officer to touch you in this way, but it's not OK for anybody else to.

Well, he'll be saving $65M in capital gains taxes by selling this year before the rate increases to 20%. No doubt that was a consideration.

126 lines of python. This is a great demonstration of how simple it is to exploit the vulnerability. Be aware, people.

I really wonder how much time the author has spent with a modern IDE like Eclipse. For Java development, it really does have all of the features on his wish list, or something equivalent.

I just replaced the 5400rpm drive in my Macbook Pro with an OCZ Vertex2 SSD. The performance improvements for many things are dramatic. I did some very unscientific before-and-after measurements..

* Cold boot (Power button to login screen): 79s HDD, 76s SSD (didn't improve much, surprisingly)

* Login (Login -> Desktop menu bars loaded): 16s HDD, 6s SSD

* Firefox start: 11s HDD, 3s SSD

* OpenOffice start: 11s HDD, 3s SSD

* Metasploit msfconsole start (i.e. loading lots of ruby code): 22s HDD, 12s real

A lot of other things are noticeably faster. Searching for things in Spotlight is almost instantaneous. Previously, there could be a few seconds delay between typing a filename and seeing it appear in the results. Running find over large directories is noticeably faster as well. Time Machine backups are way faster, since it takes much less time to determine what has changed since the last backup.

I was a little hesitant to get an SSD knowing that OSX doesn't have TRIM. We'll see how it goes. I'm hoping Apple adds support soon. If not, I might be doing a secure erase and re-install periodically.

Agreed. Technical Debt is a great metaphor for explaining these concepts to non-developers.

http://forums.construx.com/blogs/stevemcc/archive/2007/11/01...

Short-term technical debt can speed development, but like credit card debt, it quickly accrues interest. If you let your technical debt accumulate, then eventually you're spending all of your energy servicing the debt instead of improving your software.

I was just about to make the very same comment, but you've said it much better than I would have.

In my experience, these requests that initially seem unreasonable will often have a very reasonable explanation. If you take the time to understand the motive, then will often be able to find some alternate solution that satisfies both the business and the developer needs.

It sounds HP's suit is based not on a non-compete agreement, but a provision of his $35M severance package in which he agreed not to disclose trade secrets or confidential info.

That's the impression I got from the article, anyway. I suppose it wouldn't be hard to argue that he can work for Oracle without disclosing HP trade secrets.

This is the first version where conformance to RubySpec was made a high priority. It now passes over 99% of the spec. This is great news for the community because it makes it much easier for alternative ruby implementations to remain compatible.

Yes to all of your reasons, but I think you missed the biggest one:

- Many of us produce and sell software and we understand that pirating makes it harder for people like us to make a living at it.