lmorchard

13 ms·

91.
by lmorchard 12y ago
Most of the things you describe have nothing to do with REST. That might be part of your problem :)
92.
by lmorchard 12y ago
I take it that no one's seen JSON-RPC? http://json-rpc.org/
93.
by lmorchard 12y ago
REST doesn't add "restrictions". REST describes constraints that - if you can work within them - provide certain guarantees and benefits and capabilities. It solves a bunch of real problems. REST wasn't just pulled out
94.
by lmorchard 12y ago
You have missed the point of REST. REST is an architectural pattern for a World Wide Web global-scale system. Your API may not fit that description. Thus, REST may not be appropriate for your API. Following the REST patterns means you can t
95.
by lmorchard 12y ago
> It can be summed up as "don't use technology without understanding it, and don't blindly follow the crowd." But then again, how are you supposed to learn when a certain piece of technology should be applied, other t
96.
by lmorchard 12y ago
I'm on T-Mobile in the US, been swapping a SIM card between an Android daily driver and an FxOS dev phone for months now. Works fine.
97.
by lmorchard 13y ago
As far as I'm aware, the intent is to develop any non-standard Firefox OS API into a web standard API. Any API that starts out as non-standard on FxOS, starts that way so that it can be shaped to serve practical uses before it gets s
98.
by lmorchard 13y ago
Web as native on Firefox OS is not an argument or an illusion. Seriously, no kidding, it's the entire point for the existence of Firefox OS. There will never be access to run native binaries on a Firefox OS device. Web APIs are as cl
99.
by lmorchard 13y ago
Yeah, I would say that the problem is the "little phone" hardware moreso than the web tech. I wouldn't be surprised if a "native" (ie. Dalvik) Android app had similar issues on the same hardware.
100.
by lmorchard 13y ago
Probably the most relevant code can be found here: https://github.com/mozilla/kuma/tree/master/apps/search
101.
by lmorchard 13y ago
Rendering page content after edits is exactly what we do. Most page views are served up from a pre-built cache, either from a straight caching HTTP proxy or from a single DB column.
102.
by lmorchard 13y ago
The site started on MediaWiki. But, probably around 7 years ago, it switched over to a platform called DekiWiki, later renamed to MindTouch. This is way over-simplifying it, but: MindTouch looks like a fork of MediaWiki (PHP) that's ha
103.
by lmorchard 13y ago
That render() method is called only on page edits or forced refreshes, not on every page view.
104.
by lmorchard 13y ago
Yes, you are correct. We're trying to limit the system to one rendering per page at a time.
105.
by lmorchard 14y ago
Pinboard. 25441 bookmarks and counting, carried over from the 15000 or so I imported from delicious a few years ago. http://pinboard.in/u:deusx The thing is, though, how do you use bookmarks? I hoard everything and rely on search. I feel
106.
by lmorchard 14y ago
Even more handy would be to submit a pull request! It's open source! https://github.com/jdm/asknot
107.
by lmorchard 15y ago
Computing is hard; let's go shopping.
108.
by lmorchard 15y ago
Any ideas, in particular?
109.
by lmorchard 15y ago
Believe it or not, HTTP vs HTTPS is not the problem. As I mentioned in another thread: We're rewriting the wiki basically from scratch [1]. There are problems and growing pains. Pull requests welcome! [1] https://github.com/mozilla/kuma
110.
by lmorchard 15y ago
What would you rather we used, other than developer.mozilla.org?
111.
by lmorchard 15y ago
dochub.io pulls data from MDN. They deserve hugs. <3
112.
by lmorchard 15y ago
FWIW: I work on MDN. In short: We're in the process of basically rewriting the wiki software from scratch, right now [1]. There are a lot of growing pains. MediaWiki won't cut it. Pull requests welcome! [1] https://github.com/mozilla/kuma
113.
by lmorchard 15y ago
Most users never touch defaults. I'd bet you $100 million a year that AltaVista would stay default in the majority of Firefox installs, if it were released that way.
114.
by lmorchard 15y ago
I'm sure Adobe would love it if "Just use Flash" were part of the <video> spec, too.
115.
by lmorchard 15y ago
Oh, and by the way: Microsoft was opposed to WebSQL, too. It wasn't all Mozilla.
116.
by lmorchard 15y ago
"SQLite was the spec" was the problem. No arbitrary version of any arbitrary vendor's software should be the core of a web-wide spec, no matter whether it's open source or popular or loved by millions. The HTML5 authors & editors have a
117.
by lmorchard 15y ago
Which, you know, we hoped Yahoo! would do when I was there working on Delicious. Maybe these guys will figure it out.
118.
by lmorchard 17y ago
Of course that whole time, we on the Delicious team were watching the rise of those apps, thinking "Wouldn't it be cool if we could..." but being told "Maybe, though first you'll need to..."