HNHacker News
TopNewBestAskShowJobs

foobarbazoo

186 karma · joined November 12, 2010

submissionscomments
foobarbazoo··on The FBI stole an Instapaper server in an unrelated raid
Even better, they can use that information to build or enhance profiles WITHOUT getting any kind of judicial approval or oversight. Yay, Patriot Act (not).
foobarbazoo··on Announcing SproutCore 2.0 Developer Preview
"acknowledging that the SproutCore approach from the past four years needs to be ditched in favor of a brand-new codebase"

This is just flat out incorrect. SC 2 is a more moduler SC 1.x runtime, not an entirely new codebase. Similarly, SC 1.x apps will be able to run almost unchanged on SC 2 once their UI frameworks are updated for the changes in the SC 2 runtime.

The only "change" is that instead of making Web-app style opt-in, and Desktop-style the default, Web-app style is now the default and Desktop-style is opt-in. That change could have easily been made on the SC 1.x runtime as well, but it makes the most sense to do it on the modular, tighter SC 2 runtime for obvious reasons.

foobarbazoo··on Dr. Stallman responded to my open letter
You say that like it's a bad thing. Stallman is who he is. His time has passed. Oh well, move on. Life is to short to spend it giving advice to someone who clearly couldn't give a damn.
foobarbazoo··on Bitbucket: Free unlimited user source code hosting for university students
This is an ad, in the guise of a news link. WTF?
foobarbazoo··on HTML5 Is An Oncoming Train, Native App Development An Oncoming Rocket Ship
HTML is the UI, and it's hardly "non-standard". If anything, HTML is the most widely used interface style in the world.

I do agree that HTML 5 apps should not be trying to emulate native desktop or mobile apps. Instead, they should be what they really are: native browser apps.

foobarbazoo··on Today, Web Development Sucks
SproutCore loves the DOM. You're thinking of Cappuccino.
foobarbazoo··on Today, Web Development Sucks
This is how SproutCore validation logic is used on the server, BTW.

It's easy to use SproutCore's (very) powerful model layer on both the client and the server.

foobarbazoo··on CloudEdit: A Backbone.js Tutorial with Rails
In most cases, it will dramatically increase the load on your server, especially if you use a ReST API like the author suggests.

UPDATE: To clarify, in the specific situation the author describes (exactly one model class, no relationships, basically the simplest "schema" one could create), the load will go down slightly. For real, interactive single-page apps (the kind backbone.js is targeting), the load will go up because apps requests data often, way faster than your current app which is limited by page refresh time.

foobarbazoo··on CloudEdit: A Backbone.js Tutorial with Rails
I'd be willing to do the identical tutorial for SproutCore, if the author will allow his page to be copied and edited.

(I didn't see a license anywhere allowing that.)

foobarbazoo··on How to Disagree
> The truly intellectually honest way to disagree: Take the idea in question, and give it some genuine love.

Or just ignore them; this is what successful people do. It's not sexy, but life is far too short to spend it "giving love" to other people's ideas.

(I'm violating my own statement by writing this; what can I say? I like to explain things.)

foobarbazoo··on Programming is Easy, Software Development is Hard
There is a very easy way to explain programming (in assembler, no less) by analogy to how children do basic mathematics -- addition and subtraction.

That's because mathematicians do use algorithms, and concepts like "position" (indexing to us programmers), though they don't have names for them. If you explain programming using the concrete things every educated person knows, it is much easier to teach.

foobarbazoo··on ACM considered harmful
If someone publishes via ACM, IEEE, or one of the other places papers go to die, it just ensures that their work will be unread, unused, and more or less ignored.

Which is sad, because the individuals publish there in order to move up through the academic ranks. By moving forward in their careers, they are also marginalizing their own work.

The incentives are perverse, and it will be a very happy day when all CS content is freely available online, as it should be.

foobarbazoo··on HTML is the new HTML5
Where by "open", Hixie means "highly controlled by myself and my vision for the web."

I wish Hixie would retire and get some new blood in there. He's done good work, but it's time to move on.

foobarbazoo··on The polynomial algorithm for 3-SAT problem (or P=NP)
Time to fire up Coq and really prove it.
foobarbazoo··on Speculative History & Future of H.264 & WebM
My god that sucked.
foobarbazoo··on IPad 2 Likely to Have 2048x1536 Screen Resolution
2048x1536 resolution has a name: 2K (from the digital film world). iPads are already widely used on movie sets; this would more than cement that trend. Hope it's true!!!
foobarbazoo··on Google's dropping H.264 from Chrome a step backward for openness
Let's see, international ITU/ISO standard designed by video professionals (not web search people) vs. WebM de facto "standard" controlled by Google.

I think I know which one the world is behind and which one Google is behind. I vote: world.

foobarbazoo··on SproutCore Book Project Proposal
It's 1-3 developers per chapter. Last I heard, 50 developers had already signed up to write.
foobarbazoo··on SproutCore Book Project Proposal
Yes, Addison-Wesley is, as are O'Reilly and Prag Prog. The problem is not the publisher, it's the writing! That's what the proposal is designed to solve...
foobarbazoo··on Apple will not allow Verizon to preload software on iPhone
They can't be removed because there is no way to get them back. (They are not available in the App Store.)

Yes, this could (and should) be fixed. And someday, perhaps, it will be. For now, it's just not a serious problem, outside of Hacker News.

Having three different IM clients on a phone pre-installed and unremovable? Yeah, that's the kind of shit Apple doesn't do.

foobarbazoo··on The sproutcore 60-60 days for 60 devs to train for 60 hours to write one book
Totally agree, but apparently the Kickstarter people turned them down.

From the article: "I had originally hoped to do a Kickstarter project, but I have since been informed that we do not fit the profile of project they are trying to promote at this time."

foobarbazoo··on Build apps not businesses.
I love that this guy, and people who think like him, are my competition.
foobarbazoo··on Emotional Rescue
Apple barely got above 10% market share with the Mac since 1984. Even that high was done using tactics that left the company "beleaguered", and at any rate, Steve Jobs wasn't at the helm when that happened.

It's really not valid to compare Apple now to Apple pre-Steve Jobs.

foobarbazoo··on The State of Things.app Sync, Part 1
Two years and all I got was this stupid blog post.
foobarbazoo··on Cash Cow Disease: The Cognitive Decline of Microsoft and Google
In cases like that, the wealth effect would have to consider the entire value stream, not just an individual transaction.

If the company with products you describe, over many years, lost money consistently and it was not due to just "giving away" product at lower than the market would pay but was truly because the market would not pay the company's cost of production for the goods and services offered, then in that case, the company will have destroyed global wealth.

Happens all the time.

foobarbazoo··on Cash Cow Disease: The Cognitive Decline of Microsoft and Google
That explains a lot then. Thanks for the info.
foobarbazoo··on Cash Cow Disease: The Cognitive Decline of Microsoft and Google
Thanks for sharing. You got a lot of things right.

What you didn't get right was my example. I'm not talking about a situation where Microsoft is pricing a $100 product at $80. That does not result in wealth destruction, as you explained in detail. (It does result in less $$$ in Microsoft's bank account, though.)

My example was specifically about an Xbox that people were only willing to pay $80 for, and that Microsoft spent $100 to create. (Obviously, $100/$80 are illustrative, not actual figures.)

I will continue to assert that spending $100 to create a product that no one else values at more than $80 does, in fact, destroy global wealth. And that that is a Bad Thing, not "wise". You're free to continue to tell people the opposite.

foobarbazoo··on Cash Cow Disease: The Cognitive Decline of Microsoft and Google
Anyone know why I'm not getting more downvotes? Lots of people have upvoted replies to my comment that disagree with me, and I'm assuming they also downvoted my comment.

Is the downvoting on some kind of logarithmic scale? I've lost something like 27 karma points, so clearly something is happening. Any ideas?

UDPATE: I suppose it could be that people can't read it anymore, and so the downvotes have stopped. Hard to say. My karma has started creeping back up though.

foobarbazoo··on Cash Cow Disease: The Cognitive Decline of Microsoft and Google
Without getting into it too deeply, money is not wealth. It is a wealth transfer mechanism.

When wealth is converted into $100 for trade with someone (e.g. Microsoft, by buying Windows and Office products) and Microsoft takes that $100 and converts it into something that can only be traded for $80, it has destroyed wealth, even though the original $100 of money is still around (it paid for materials and labor after all). The "world" still has the $100 that Microsoft used to have, but instead of having $100 worth of wealth to trade it for, Microsoft has stupidly destroyed wealth and now there is only $80 of wealth to trade for.

So yes, the money is the same, but the wealth actually did decrease, by $20. Someone, somewhere is stuck with $20 and nothing to buy after the Xbox is sold for $80, thanks to Microsoft. Global wealth was destroyed; the amount of $100 bills stayed the same.

foobarbazoo··on Cash Cow Disease: The Cognitive Decline of Microsoft and Google
"the simple fact is, when you have a cash cow, you got extremely lucky"

And here we have yet another comment purporting to argue against the article, and inadvertently proving it's main thesis.

Google should give the profits back to shareholders instead of trying to duplicate or continue what you yourself agree was success that was "extremely lucky".

The author isn't expecting lightning to strike twice at Google, and thinks they should put the money back in the marketplace where it can be spent wisely.

← PreviousPage 2 of 3Next →