pothibo

By your measure, Facebook is still not a large-scale engineering organization... I think I'll stop there.

That's a great approach. By restricting yourself to one new thing, you can evaluate it in isolation.

Then, when you make your decision about that new thing, you'll know why you like/dislike it. Your decision won't be clouded by arbitrary things like libraries inter-dependencies.

I don't understand how Fetch API is an improvement over XMLHTTPRequest. To me, this looks like a syntax update but I don't see it being better or worse than the previous installment.

Now that I think about it, I couldn't find any API related to download/upload progress events with the Fetch API. If that's the case, it means it's an actual regression to XMLHTTPRequest.

> Everyone’s into it because the responsiveness is so much better than loading a full page - 10-50ms with a clean API load vs. 300-1500ms for a full HTML page load.

Maybe if you start with an argument to support your claim, you want to have actual numbers. And those real numbers would tell a different story.

StackEdit is very nice, it's certainly one of the best.

Looks good! I've also worked on a markdown editor since january but it's web-based and while it's hooked on my blogging engine, I'm planning to make it available as a standalone library down the road. It might not be obvious, but the markdown on top is the actual editor. You can test ride it.

http://ecrire.io/

More the merrier!

(Small disclaimer: I have never tested it on IE...)

You understand that you are the saleman of this post by talking about micro services, right?

Unless I oversaw your sarcasm...

FYI, Angular, React, Backbone, Ruby on rails all started as in-house frameworks.

There is something very weird with the collapse of the oil prices. It doesn't make sense. I know mainstream media have talked about offer/demand being the reason for this crash but it doesn't make sense.

It says China didn't grow as much as expected, etc. Well if that'd be a simple offer/demand, the price would have not collapsed so rapidly. Oil is not like housing where bubbles comes and go. It's usually pretty steady unless something happens (9/11, 1982, etc).

Also, price seems to be recovering now which indicate, to me, that it's not an offer/demand issue. The oil collapsing and recovering in a ~6 months period is just plain weird.

If I had to bet, I'd say it's due to ISIS and their access to oil and selling it at a quarter of the ongoing prices. I read a story about that a few months back how they had access to major oil field and were selling it insanely cheap on the black market to finance their operations.

Those are all wild ideas. But things are just weird, I'm telling you.

I wasn't advocating for badly written code to run on a whole datacenter. I was just pointing the alternative with the assumption that the code was somewhat healthy and adding one new instance to cover the sub-optimization wasn't a big deal.

Of course, if you have 10k users and it runs on 3 machines, you got a problem which no amount of boxes can solve.

Nothing's wrong with spinning up more AWS boxes. If it costs 300$ annually to solve a problem that would cost 5k$ in development to fix, I believe it's a wise choice.

Yeah, down the line you will eventually have to do optimization, but you will prioritize.

Good to know it's moving towards a more open environment. Also good to know that my memory wasn't playing tricks on me. Thank you for the update.

Because the documentation for the hardware is not open source. You need to sign very strict papers to be able to look at the hardware documentation which means few selected people have access to it which means not much support, etc. Can't remember why I know this but it was something related to my linux open source back in the days.

> What has finally been made clear is that it's okay to have difficult to code APIs, if the end result just works.

So true and yet, we have all those crazy JavaScript frameworks trying to abstract everything away from developers. There's a lesson in there.

I couldn't refrain myself for posting something I just wrote http://pothibo.com/2015/3/churn

I think JavaScript people might need to read it.

Is that DBMonster app becoming the new todo app for all JS framework to implement?

Maybe he just pitched his article to a few places and venturebeat decided to run with it?

Sometimes, article like this are written by the author, and the blog takes the article, edit it a little and publish it. I'm not saying it's what happened but it's certainly a possibility

This is awesome in so many ways because it captured the imagination of the people using it. They just saw that switch and actually tried to figure out why it wasn't magic.

Obviously it wasn't, but the way this is written really shows how dumbfound they were because they couldn't explain it.

The fact that you acknowledge the opportunistic part of my comment proves my point. Yes, when you love something so damn much, you don't go out there and tell people how to build the same thing in a better way, using their name.

It's hilarious that I'm being downvoted for being exactly right.

It's nothing like you describe. They go to great length to say how they love Magic to turn around and tell the world how to do build a better clone.

Did they write about the routing? No. They advertised their product piggybacking on a frontpage story.

Look, if the same thing would happen but Magic would be an established company, I'd say it's brilliant, but it's not. And it matters.

I really don't like this opportunistic BS. These guys yesterday struggled with their launch and you took that opportunity to tell the world how to build a better clone?

Cheap shot & I hope someone did the same when you guys launched and I hope it made you struggle.

Shame on me for not knowing about <figure>. I actually looked for such an element a week ago when I had some issue with <picture>.

This is exactly what I need when rendering pictures in the markdown's auto-upload image in https://github.com/pothibo/ecrire

Thank you!

Not using external service for font anymore because it's blocking. That means your time to first render is directly impacted by the time your user download fonts from a third party.

And have you ever landed on a site fully rendered but can't see the text? High chances that it's a third party font that can't be downloaded for whatever reason.

So basically you make a claim that french is easier to rhyme than english, then I ask you if you have any evidence and you retorqued with a condescending answer adding a link to a book you took 5 second to google and that you didn't read.

You didn't read it because I just read it and while the first sentence would make it appear to back your point, it doesn't. First because he doesn't compare french to english but merely explain how the main accent is put on the suffix of words and that, in turn, makes it easy in french to build rhyme.

And if you continue to the next page, he explains how french rhyme are not on the same level as their english counterpart "because most English rhymes involve the root rather than the inflectional ending or suffix [...]"

Bottom line, you are wrong, and you try to pass as knowledgeable. You are a fraud.

How is french easier to rhyme than english? Do you have empirical evidence?

Since I'm a french canadian who is lucky enough to speak the two languages, I find it difficult to believe.

Remember that rap (rhyme and poetry) was popularized by poor english speaking people.

http://prismjs.com/ is an alternative that supports line numbers.

I often see native, iOS app being sluggish and I don't blame it on Objective-C or Swift. I blame it on the application. I don't understand how it's different when it comes to web apps.

I thought it was someone from Slack talking about their infrastructure (or similar).

Instead, it's some abstract theory. I believe everyone can dream of any architecture.

This kind of comment just show ignorance. The kernel has been around for a few decades while semver has been around for what, 3 years now?

Maybe it will adopt semver at some stage. I doubt it because the API is way too complex and broad to be covered in simple x.x.x notation, think of driver updates on vendors.

Love the SaneScript idea, that could be very big.