5,557 karma · joined September 1, 2010
I tried an informal experiment with this among my facebook friends. I asked them what podcasts they love. Then I put together an aggregator for those podcasts. It's been a great resource for me, but I don't think any of my friends use it.
I guess the answer is this -- if it's going to happen users have to want it and so far they haven't.
An API is an API. Google is part of the W3C, probably a very important part of it.
I used to be a W3C member, and remember how this worked. The big companies drove the process. They met privately and hashed things out between themselves. Then it was "debated" but somehow the decision that was arrived at was always the ones they wanted to make.
It's a way of making it look like an open process when it really isn't.
In any case, the problem for a developer is the same no matter who is doing the deprecating. You just built on something that's going away. You have some users. Not enough to matter to the big companies. You're burned. So now next time will you just go ahead and implement the API they want you to. Not unless you're an idiot! ;-)
Speaking as an idiot of this kind myself. I've been burned many times by this process.
So maybe you don't really want to do APIs at all??
Deprecate them before you start! :-)
I was just writing about this re Dropbox. People always say about the idea I want to see them do "That's a third party opportunity." Well, I would never bet on a mission-critical feature that depended on the continuing support of an API by a platform vendor. What happens to the users when the API breaks? I might not have a lot of users from their point of view, but from my point of view, my community will die if they break the API.
https://en.wiktionary.org/wiki/if_it_ain%27t_broke,_don%27t_...
This site is perfectly readable in all browsers and it's really hard to imagine the day when the browsers stop understanding <center> and <table>, so it's probably good for perpetuity.
http://scripting.com/2015/10/05/congatsToJack.html
Dave
Think of RSS as an advertisement for the stuff on your news site or blog. If you don't publish RSS, how will people find your stuff? By visiting the home page of your site and looking for stuff they haven't seen before? Sure, some people will do that. But people who read your site systematically, people who you would think of as members of your community, can benefit from more automatic notification. That's what RSS is for. All kinds of networks have developed around RSS. If you don't provide a feed, your site can't participate in those networks.
Also, how do you think links make it to Twitter and Facebook? Very often they were posted by people who follow your site's feed. So while most people aren't aware they're getting their links from feeds, they are.
I'm not aware of how the plumbing works in NYC, but I live there, and depend on it. Water flows in and out. Treated on both sides. RSS is the plumbing for news. It's best when it just works without you having to even be aware of it.
Here's an example. Sometimes I get so interested in a subject I put together a river site dedicated to news in that area. Earlier this week I did one for Major League Baseball.
The vast majority of the sites I went looking for feeds on had them, and they worked with my aggregator. I didn't need to contact anyone. And now they have a new source of flow, that didn't cost them anything, since they were already supporting RSS.
So you don't need to draw down your principal to pay your living costs.
Let's say you spend $100K per year, and you can earn 10 percent per year, then you need $1 million.
But you don't even need that much, because there's no reason to die with $1 million in the bank.
So it's probably some kind of calculus problem, an integral or a derivative, or something.
And maybe you can do better than 10 percent! ;-)
I put so much value in achieving all the goals my family set for me. I figured everyone would love me when I was a success. So I checked off everything on the list, and I mean everything. Nothing changed. Of course. I know that now, but I wish someone had told me before.
Live for yourself, do what you want to do. When other people tell you what to do, not only don't they know, but it won't please them when you do.
People use the chase for success in various forms as a way of avoiding self-knowledge. In some ways the worst thing that will ever happen to you is if you make the big bucks. Then you won't have an excuse for not knowing yourself. So what do the super-motivated people do then? They pick another milestone to shoot for before they'll start living.
Start now. Don't wait for anything to happen. You are alive in every way that's meaningful, now.
http://scripting.com/stories/2007/12/22/macsAreEvenMoreExpen...
https://www.google.com/search?q=site%3Ascripting.com+google+...
As for how it "reads" to you -- that has more to do with you than me. ;-)
In some cases the messages they've deleted have been important real emails. Not spam.
Also you're being a little dramatic in characterizing my comments. You might want to temper that, esp when you're accusing someone else of doing what you are yourself doing. ;-)
Nine times out of ten I end up at either Stack Exchange or W3Schools.
When coerced to a number, it's the number of milliseconds since January 1, 1970.
If you wanted to know the number of seconds since January 1, 1970, you could divide by 1000. Since JavaScript will do the coercion for you automatically you can pretty much treat a date object as if it were a number.
This is basically a utility routine that I use for debugging messages to say how long an operation took.
Here's an example of its use:
https://github.com/scripting/myWordEditor/blob/master/script...
It's especially nice because JavaScript automatically does real arithmetic on the division, so you get fractions of seconds displayed in the console.
I use this routine a lot. Helps me spot performance problems. Nice to have, not a crucial routine.
Hope this helps! ;-)
As should the net-based political press.
Never mind what "most people" care about -- this is news.
But in the code itself, this isn't a consideration.
Not left edges. Even in non-monospace fonts, every blank is the same with, same with every tab.