<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for sintaks</title><link>http://disqus.com/by/sintaks/</link><description></description><atom:link href="http://disqus.com/sintaks/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 08 Dec 2012 16:56:56 -0000</lastBuildDate><item><title>Re: http://blog.neevita.net/archives/12664</title><link>http://blog.neevita.net/archives/12664#comment-732100544</link><description>&lt;p&gt;*wave*&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sat, 08 Dec 2012 16:56:56 -0000</pubDate></item><item><title>Re: Announcement: Pricing and value</title><link>http://staging.lemonstandapp.com/blog/post/pricing_and_value/#comment-108810911</link><description>&lt;p&gt;Does that mean there's no way for a dev to "practice" without paying for a full license?&lt;/p&gt;&lt;p&gt;I rather like Expression Engine's model of giving the core away. I think in your case it makes sense to charge for the core, but not allowing devs access for the purpose of learning without overcoming the hurdle of paid licensing limits your developer community. This introduces the chicken/egg problem - why should devs pay for a license if they don't know if they can recoup the cost? And why will customers go with your solution over something which already has a broad developer base?&lt;/p&gt;&lt;p&gt;Even MS started giving awar their Express products to foster developer adoption. Seems like a similar approach could work here.&lt;/p&gt;&lt;p&gt;Don't mean to be harsh. I just want this to succeed... but I don't see myself putting forth money just yet.&lt;/p&gt;&lt;p&gt;You mention support being the difference between commercial and open source efforts.  I think you can get great support both ways. The "free" in open source also means "freedom", and "free market" - that is, you create a market for professionals to offer competitive support and services.&lt;/p&gt;&lt;p&gt;All the same, I wish you good luck, and look forward to seeing how far this model takes you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Wed, 08 Dec 2010 16:42:38 -0000</pubDate></item><item><title>Re: Announcement: Pricing and value</title><link>http://lemonstandapp.com/blog/post/pricing_and_value/#comment-108778520</link><description>&lt;p&gt;Does that mean there's no way for a dev to "practice" without paying for a full license?&lt;/p&gt;&lt;p&gt;I rather like Expression Engine's model of giving the core away. I think in your case it makes sense to charge for the core, but not allowing devs access for the purpose of learning without overcoming the hurdle of paid licensing limits your developer community. This introduces the chicken/egg problem - why should devs pay for a license if they don't know if they can recoup the cost? And why will customers go with your solution over something which already has a broad developer base?&lt;/p&gt;&lt;p&gt;Even MS started giving awar their Express products to foster developer adoption. Seems like a similar approach could work here.&lt;/p&gt;&lt;p&gt;Don't mean to be harsh. I just want this to succeed... but I don't see myself putting forth money just yet.&lt;/p&gt;&lt;p&gt;You mention support being the difference between commercial and open source efforts.  I think you can get great support both ways. The "free" in open source also means "freedom", and "free market" - that is, you create a market for professionals to offer competitive support and services.&lt;/p&gt;&lt;p&gt;All the same, I wish you good luck, and look forward to seeing how far this model takes you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Wed, 08 Dec 2010 14:55:12 -0000</pubDate></item><item><title>Re: heypanda: The Coolest JavaScript Trick I've EVAR Used</title><link>http://heypanda.com/posts/77-The-Coolest-JavaScript-Trick-I-ve-EVAR-Used#comment-34943342</link><description>&lt;p&gt;Indeed! In some ways, I wish Ruby (at least, pre 1.9) did the same thing. For instance:&lt;/p&gt;&lt;p&gt;var a = "a";&lt;br&gt;(function(a){&lt;br&gt; console.log(a);&lt;br&gt;})("b");&lt;br&gt;console.log(a);&lt;/p&gt;&lt;p&gt;This logs "b" then "a". Even though the parameter has the same name as the variable in the outside scope, it's only temporarily overshadowed. In Ruby, the very act of using an existing variable as a lambda parameter overwrites it:&lt;/p&gt;&lt;p&gt;a = "a"&lt;br&gt;lambda{|a| puts a}.call("b")&lt;br&gt;puts a&lt;/p&gt;&lt;p&gt;This outputs "b" and "b" - very frustrating.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Wed, 17 Feb 2010 16:59:47 -0000</pubDate></item><item><title>Re: My typical day running a startup</title><link>http://blog.styleguidance.com/post/332896939#comment-29699734</link><description>&lt;p&gt;I would suggest moving that one-hour block of work (from 10-11p) to the edge of another block of working, or getting rid of it completely. Having it dwarfed in the middle like that is a total drag, since by the time you get "in the zone", the hour is almost up.&lt;/p&gt;&lt;p&gt;Everyone's different, but that's what works for me. I often find that when I "work" for 16 hours, often I'm still only *working* for 8, if that. Better to just get it all done with one shot, and enjoy the feeling of freedom I have from being done for the day.  Those 5-60 minute breaks kill my context, and it takes me longer to rev back up again.&lt;/p&gt;&lt;p&gt;Speaking of which... back to work...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Wed, 13 Jan 2010 19:46:32 -0000</pubDate></item><item><title>Re: Hands on with MSI&amp;#8217;s dual touchscreen netbook prototype</title><link>https://liliputing.com/2010/01/hands-on-with-msis-dual-touchscreen-netbook-prototype.html#comment-29321091</link><description>&lt;p&gt;It's foolish to think that they standard keyboard layout is the direction we should be going with devices like this. It's a relic from a forgotten past, with keys laid out so it would *slow the typist down* to prevent a typewriter's hammers from jamming.&lt;/p&gt;&lt;p&gt;New tech, new input/output devices. It's the only way we'll make significant advances in the field of mobile computing. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sun, 10 Jan 2010 23:56:30 -0000</pubDate></item><item><title>Re: HipChat Is Yammer For The Masses</title><link>http://techcrunch.com/2009/12/14/hipchat-group-chat/#comment-71155179</link><description>&lt;p&gt;I would say this is *much* more like Campfire for business than it is Yammer for the masses. You draw the similarity to Campfire almost in passing, when in fact the formatting/styling for the chat transcript is almost a direct rip from 37signal's version. The fact that this runs on the desktop and Campfire "is web-based" is almost incidental, considering HipChat transcripts are stored on the web (like Campfire), searched on the web (like Campfire), and the app itself is Flex+AIR (meaning  it's "built for the web, and then packed for the desktop").&lt;/p&gt;&lt;p&gt;You can force the parallel between HipChat and Yammer if you want, but it feels just that: forced.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Tue, 15 Dec 2009 03:28:12 -0000</pubDate></item><item><title>Re: mirRoR Blog: Now Hiring: Rock$tar$ Only!</title><link>http://mirrorplacement.com/blog/now-hiring-rocktar-only?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+MirrorPlacement+%28mirRoR+placement%29#comment-24735017</link><description>&lt;p&gt;Awesome. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Thu, 03 Dec 2009 19:54:34 -0000</pubDate></item><item><title>Re: The+End+Of+The%26nbsp%3BCrunchPad</title><link>http://techcrunch.com/2009/11/30/crunchpad-end/#comment-71673968</link><description>&lt;p&gt;Whiskey. Tango. Foxtrot.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Mon, 30 Nov 2009 22:49:08 -0000</pubDate></item><item><title>Re: heypanda: More and More, I'm Liking Flex on Rails</title><link>http://heypanda.com/posts/55-More-and-More-I-m-Liking-Flex-on-Rails#comment-21203401</link><description>&lt;p&gt;In this vid, none (I don't think). I'm not using the RubyAMF stuff here - just straight RESTful controllers serving up XML, which is parsed using e4x. So... I just set up the Flex project within the Rails project, and set the build output path to /public/bin, and I'm g2g.&lt;/p&gt;&lt;p&gt;Mind you, this was a year ago. Hm. I should probably add the year to the "posted at" time. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Wed, 28 Oct 2009 15:17:50 -0000</pubDate></item><item><title>Re: Announcement: Pricing and value</title><link>http://blog.lemonstand.com/announcement-pricing-and-value/#comment-109986408</link><description>&lt;p&gt;Does that mean there's no way for a dev to "practice" without paying for a full license?&lt;/p&gt;&lt;p&gt;I rather like Expression Engine's model of giving the core away. I think in your case it makes sense to charge for the core, but not allowing devs access for the purpose of learning without overcoming the hurdle of paid licensing limits your developer community. This introduces the chicken/egg problem - why should devs pay for a license if they don't know if they can recoup the cost? And why will customers go with your solution over something which already has a broad developer base?&lt;/p&gt;&lt;p&gt;Even MS started giving awar their Express products to foster developer adoption. Seems like a similar approach could work here.&lt;/p&gt;&lt;p&gt;Don't mean to be harsh. I just want this to succeed... but I don't see myself putting forth money just yet.&lt;/p&gt;&lt;p&gt;You mention support being the difference between commercial and open source efforts.  I think you can get great support both ways. The "free" in open source also means "freedom", and "free market" - that is, you create a market for professionals to offer competitive support and services.&lt;/p&gt;&lt;p&gt;All the same, I wish you good luck, and look forward to seeing how far this model takes you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Fri, 11 Sep 2009 06:21:52 -0000</pubDate></item><item><title>Re: Announcement: Pricing and value</title><link>http://staging.lemonstandapp.com/blog/post/pricing_and_value/#comment-108816240</link><description>&lt;p&gt;Does that mean there's no way for a dev to "practice" without paying for a full license?&lt;/p&gt;&lt;p&gt;I rather like Expression Engine's model of giving the core away. I think in your case it makes sense to charge for the core, but not allowing devs access for the purpose of learning without overcoming the hurdle of paid licensing limits your developer community. This introduces the chicken/egg problem - why should devs pay for a license if they don't know if they can recoup the cost? And why will customers go with your solution over something which already has a broad developer base?&lt;/p&gt;&lt;p&gt;Even MS started giving awar their Express products to foster developer adoption. Seems like a similar approach could work here.&lt;/p&gt;&lt;p&gt;Don't mean to be harsh. I just want this to succeed... but I don't see myself putting forth money just yet.&lt;/p&gt;&lt;p&gt;You mention support being the difference between commercial and open source efforts.  I think you can get great support both ways. The "free" in open source also means "freedom", and "free market" - that is, you create a market for professionals to offer competitive support and services.&lt;/p&gt;&lt;p&gt;All the same, I wish you good luck, and look forward to seeing how far this model takes you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Fri, 11 Sep 2009 06:21:52 -0000</pubDate></item><item><title>Re: Disabling Paperclip asset timestamp keeps you from committing genocide</title><link>http://www.mrkris.com/2009/09/08/disabling-paperclip-asset-timestamp-keeps-you-from-committing-genocide/#comment-16229123</link><description>&lt;p&gt;Good stuff, mate. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Wed, 09 Sep 2009 03:01:39 -0000</pubDate></item><item><title>Re: heypanda: Deploying CodeIgniter Projects to Dreamhost Using Capistrano</title><link>http://heypanda.com/posts/6-Deploying-CodeIgniter-Projects-to-Dreamhost-Using-Capistrano#comment-15551815</link><description>&lt;p&gt;Do you have subversion installed on your remote box? This line here seems to be issue:&lt;/p&gt;&lt;p&gt;C:/Ruby/lib/ruby/gems/1.8/gems/capistrano-2.5.8/lib/capistrano/recipes/deploy.rb&lt;br&gt;:97:in ``': No such file or directory - svn info http://labs.*******.com/autotra&lt;/p&gt;&lt;p&gt;Capistrano uses svn to pull down the latest version in version control (by default), so it needs to be installed both on your desktop machine and your server.&lt;/p&gt;&lt;p&gt;I actually recommend using git instead of svn now, only because git makes branching so easy. Then you just create a deployment branch (I use deploy/live), set it to :branch in your recipe, and you're good to go.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Fri, 28 Aug 2009 20:46:13 -0000</pubDate></item><item><title>Re: It%26%23039%3Bs+On%3A+Bing+Jingle+Guy+Proves+He+Sucks%26nbsp%3BLess</title><link>http://techcrunch.com/2009/08/06/its-on-bing-jingle-guy-proves-he-sucks-less/#comment-71498806</link><description>&lt;p&gt;Don't you mean *bing* it on?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Thu, 06 Aug 2009 18:21:06 -0000</pubDate></item><item><title>Re: heypanda: Too Many Twitter Friends? Kill Stale Accounts.</title><link>http://heypanda.com/posts/72-Too-Many-Twitter-Friends-Kill-Stale-Accounts-#comment-13876841</link><description>&lt;p&gt;Since my comments disappeared when I switched from FB to DISQUS, I guess I'll reiterate: this version doesn't do pagination. See me for the fix.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Tue, 04 Aug 2009 09:11:53 -0000</pubDate></item><item><title>Re: heypanda: The Facebook Comments Are GONE?!</title><link>http://heypanda.com/posts/75-The-Facebook-Comments-Are-GONE-#comment-13808691</link><description>&lt;p&gt;This thing needs to stop tweeting as me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sun, 02 Aug 2009 09:52:43 -0000</pubDate></item><item><title>Re: heypanda: What is Extendy, and Why Did We Build It?</title><link>http://heypanda.com/posts/74-What-is-Extendy-and-Why-Did-We-Build-It-#comment-13808682</link><description>&lt;p&gt;Woo! More beta users! Hooray!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sun, 02 Aug 2009 09:52:04 -0000</pubDate></item><item><title>Re: heypanda: I Just Made a Reddit Plugin for Extendy</title><link>http://heypanda.com/posts/76-I-Just-Made-a-Reddit-Plugin-for-Extendy#comment-13808563</link><description>&lt;p&gt;There's just no stopping the madness.&lt;/p&gt;&lt;p&gt;Pfft.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sun, 02 Aug 2009 09:44:49 -0000</pubDate></item><item><title>Re: heypanda: The Facebook Comments Are GONE?!</title><link>http://heypanda.com/posts/75-The-Facebook-Comments-Are-GONE-#comment-13793514</link><description>&lt;p&gt;If we weren't on opposite sides of the country, I'd slap you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sat, 01 Aug 2009 19:44:12 -0000</pubDate></item><item><title>Re: heypanda: The Facebook Comments Are GONE?!</title><link>http://heypanda.com/posts/75-The-Facebook-Comments-Are-GONE-#comment-13774856</link><description>&lt;p&gt;Hmm... this comment system also loads much snappier than FB's. Disqus, I think I'm in love.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sat, 01 Aug 2009 02:47:03 -0000</pubDate></item><item><title>Re: heypanda: What is Extendy, and Why Did We Build It?</title><link>http://heypanda.com/posts/74-What-is-Extendy-and-Why-Did-We-Build-It-#comment-13476075</link><description>&lt;p&gt;There. No more Facebook comments. Yay!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Tue, 28 Jul 2009 14:54:15 -0000</pubDate></item><item><title>Re: Vote on the scent for reddit soap, determine the smell of thousands of redditors</title><link>http://blog.reddit.com/2009/07/remember-family-soap-business-you.html#comment-12064029</link><description>&lt;p&gt;Coconut. Nom nom nom.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Fri, 03 Jul 2009 03:01:38 -0000</pubDate></item><item><title>Re: bitquabit - The One in Which I Call Out Hacker News</title><link>http://blog.bitquabit.com/2009/07/01/one-which-i-call-out-hacker-news/#comment-12022732</link><description>&lt;p&gt;I really appreciate this article. Not only should overly arrogant and/or misinformed/idealistic developers read this, but project managers, too.&lt;/p&gt;&lt;p&gt;Too frequently, a client or PM drop the phrase "small feature" or "little fix" or "minor request". That's because they only see the feature/fix/request where it sits on the page, not how it interops with the system on the whole. Yes, it's just an X, but it also has to invalidate caches, replicate quickly, and take Y into account, which we don't have control of! *sigh*&lt;/p&gt;&lt;p&gt;The point is, people tend to see software as parts. They often fail to see the interaction between those parts, or parts which remain hidden to the user (considerations made to easy deployment, to easy upgrading, to handle bad nodes, etc). I could whip up the crappiest version of StackOverflow together in 3 days, but it wouldn't be a StackOverflow clone, because SO is more than the sum of its visible parts.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Thu, 02 Jul 2009 01:58:32 -0000</pubDate></item><item><title>Re: It&amp;#039;s Heeerrre: &amp;#039;Pay With Facebook&amp;#039; Is In The Wild</title><link>http://techcrunch.com/2009/05/29/its-heeerrre-pay-with-facebook-is-in-the-wild/#comment-71444034</link><description>&lt;p&gt;If you poke around in the FB Connect code that gets loaded with, say, Facebook Comments, you'll see the Payment library is being loaded onto third-party sites. A clear indicator that this will bust out of the realm of FB's site soon.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mase</dc:creator><pubDate>Sat, 30 May 2009 22:37:35 -0000</pubDate></item></channel></rss>