voidfiles

RSS?

Markdown is the new Cursive

So, my personal blog doesn't get a ton of traffic, but the one article that gets the most traffic is an article about how to monkeypatch feedparser to not strip about embedded videos.

While not hard evidence, I think it's indicative of the kind of experience a developer has when they choose to engage with syndication.

This seems like a great idea. If it can help even one developer it's worth it.

I added Kim to my ongoing set of python serialization framework benchmarks here is how it ranks.

  Library                  Many Objects    One Object
  ---------------------  --------------  ------------
  Custom                      0.0187769    0.00682402
  Strainer                    0.0603201    0.0337129
  serpy                       0.073787     0.038656
  Lollipop                    0.47821      0.231566
  Marshmallow                 1.14844      0.598486
  Django REST Framework       1.94096      1.3277
  kim                         2.28477      1.15237

Comments on how to improve the benchmark are appreciated.

source: https://voidfiles.github.io/python-serialization-benchmark/

We developed that flag after the incident I referred too.

Human misery isn't something most companies want to be associated with. For that reason, many companies don't want their ads to run next to content like that. I've personally had to quickly pull ads off a site because of that fact.

We spend far more time consuming content generated by our friends and family then we do consuming content created by media companies. I don't think he could conceive that a company like Facebook could control the means of distribution by providing something that people want more the professional media.

What problems did you run into while using RequireJS?

Webdis has more features right now. It has authentication, and it supports things like websockets. It's also written in C.

Lark is written in python and I would argue that Lark does a better job of meeting the expectations of what an API should be like supporting POSTs, and DELETEs.

It would also fit in well with an existing flask project. It has a blueprint that you can mount.

oAuth integration is planned, I am working on it right now. I also plan on making websockets work in the same manner as flask-sockets.

Content owners don't make feed readers. If they didn't want people to pre-screen content they could just get rid of their RSS feeds altogether. They haven't done that. They clearly find some value to users being able to find their content through RSS, so I don't think this is why feed readers have failed to breakout.

It's not just your tools though. They are asking you to throw away many of your ideas about web development as well. They ask you to adopt a new paradigm that doesn't fit in with the template, innerHTML style of development.

If you embrace that idea, and go with the flow, you can do some amazing things amazingly fast with angular that doesn't work so well in other frameworks.

Agreed.

Out of all the feeds that I checked CNN had the largest number of Google Reader subscribers. If you are right, I would argue that CNN market penetration is lower then 50% and thus the feed reader market would be bigger.

I'm not sure. They seem to be in the right space, but they are also aggregating big media, as much as independent publishers.

You aren't alone. There is actually a version of Markdown for writing Screenplays. When writers adopt Markdown then I am not sure who Markdown is not for.

http://octopress.org/ is essentially something written from the ground up that addresses many of the concerns in ghost, but that doesn't mean its the solution.

Because WordPress is built on PHP it has a wider array of deployment options, including many low-cost options, while maintaing a relatively easy to use sheen.

I think it makes sense to evolve WordPress to merge the benefits of something like octopress with WP.

What made sense about the Ghost write screen was that it embraced Markdown. It showed what things would look like as you wrote them. I don't think the screenshot of the new WordPress dashboard addresses that.

Hi, I wrote the blog post. I haven't been able to find any public discussion about a spec from the parties involved other then Atwood's blog post.

Maybe he is referencing the pdf: http://fletcher.github.com/peg-multimarkdown/mmd-manual.pdf

Isn't the point of the article that we do have other great guides, the failures. They are a great example of how things when wrong. Maybe by paying closer attention to the failures we can see how to fix what they did wrong and fix it.

With such a complicated system I think you are missing out on the most signifcant speed optimization technique; reducing http requests.

For reference: http://developer.yahoo.com/blogs/ydn/posts/2007/04/rule_1_ma...

It's laudable that you are paying attention to caching, but you don't compile all your files in to one file. It seems like you could pick up a lot ground here by at least concating all css into one file, and js in to one file.

Also you could load jquery from the Google AJAX API endpoint. That way the users has a higher chance of having already loaded jQuery.

Also using the same CSS/JS products across multiple pages would help.

Doesn't fit in with the bootstrap code style. Your plugin has too many semicolons.

Free food is a big idea. As a one time Yahoo, I was shocked. This shows to me that Mayer is going to be different. I am not sure if every CEO previous to her had this choice, but none of them did it. It either proves that the board has given her a lot of leeway, or all the others have been weak kneed.

Seriously, food is a big deal, someone at my orientation asked a VP why we didn't get free food. She answered by explaining that the only people who liked the free food were the employees, and that share holders didn't like the free food, and that we work for the shareholders. With that everyone clapped. I remembered at the time that free food sounded good, especially because I was about the become a Yahoo employee.

So, I hope this is like the Canary in the coal mine, but in reverse.

I use grabbox(http://grabbox.devsoft.no/) it's free does all of the things people have listed here.

Have you read this http://daltoncaldwell.com/an-audacious-proposal

I am not so sure that is the case. Kevin Kelly wrote about having 1000 true fans. I think his argument works here too.

http://www.kk.org/thetechnium/archives/2008/03/1000_true_fan...

If you think about how Twitter needs to reach 100 of millions if not billions of users to possibly become sustainable, or figure out how to squeeze more money out of the users they have. Then compare that to the App.net proposal. Especially the part about making the user the customer. Then you can see how having a small set of faithful users might be more sustainable.

Dalton wrote more about this in his post: http://daltoncaldwell.com/an-audacious-proposal

disclaimer: I work for App.net, but this post represents my own views.

It's always hard to find a market for your product. This is one way to make sure there is a market before building a product.

Neal Stephenson is a master of the diatribe. In almost all of his books he takes the time to go into detail on some arcane subject. While I may not be a master after he is done I feel like one.

When it comes to a mainstream adaptation I wonder if they will retain the diatribes. It would be really interesting to see how an audience takes to his level of engagement in a specific subject.

So, the code you post requires jQuery, I am assuming, because you don't say. Which means you would need to also include jQuery in the header. Doesn't that seem like a waste? Also if you had jQuery already you could probably writing a queuing system for almost all actions, and not just "important" ones.

You should take a queue from Flickr. I took a look at how they handled this, and I think it's one the best I have seen so far.

http://dailyjs.com/2011/11/28/flickr-async/

The method there could actually be a small amount of code, and wouldn't require that you load jQuery before queuing events.