pothibo

9 ms·

31.
Shopify files for IPO(shopify.com)
18 points by pothibo 11y ago|0 comments
32.
by pothibo 11y ago
Where you see failure, I see natural evolution. You don't know how/where/when your application will fail, so it's pointless to try to prevent it. People uses Node, Rails or whatever because it's easier to develop
33.
by pothibo 11y ago
Wordpress WYSIWYG (TinyMCE) is notorious for bugs - I experienced them first hand - and it's not a website, it's a software people install. Big difference. I had forgotten about Gmail, so I guess this is the exception to the rules
34.
by pothibo 11y ago
WYSIWYGs have its own set of problems and this is why most popular websites have WYSIWYG editor but do have Markdown. Some issues: - Portability - Error prone (want to close a bold style but can't unless you copy/paste text)
35.
Is this ET? Mystery of strange radio bursts from space(newscientist.com)
1 points by pothibo 12y ago|0 comments
36.
by pothibo 12y ago
By your measure, Facebook is still not a large-scale engineering organization... I think I'll stop there.
37.
by pothibo 12y ago
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 c
38.
by pothibo 12y ago
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 fi
39.
by pothibo 12y ago
> 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
40.
by pothibo 12y ago
StackEdit is very nice, it's certainly one of the best.
41.
by pothibo 12y ago
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 obv
42.
by pothibo 12y ago
You understand that you are the saleman of this post by talking about micro services, right? Unless I oversaw your sarcasm...
43.
by pothibo 12y ago
FYI, Angular, React, Backbone, Ruby on rails all started as in-house frameworks.
44.
by pothibo 12y ago
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&#x
45.
Show HN: JointJS is simple yet powerful(pothibo.com)
3 points by pothibo 12y ago|0 comments
46.
by pothibo 12y ago
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
47.
by pothibo 12y ago
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
48.
by pothibo 12y ago
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.
49.
by pothibo 12y ago
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&#x2
50.
by pothibo 12y ago
> 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. Th
51.
by pothibo 12y ago
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.
52.
Churn(pothibo.com)
4 points by pothibo 12y ago|0 comments
53.
by pothibo 12y ago
Is that DBMonster app becoming the new todo app for all JS framework to implement?
54.
by pothibo 12y ago
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
55.
Event based response in JavaScript(pothibo.com)
1 points by pothibo 12y ago|0 comments
56.
by pothibo 12y ago
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
57.
by pothibo 12y ago
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&#x2
58.
by pothibo 12y ago
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
59.
by pothibo 12y ago
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 launche
60.
by pothibo 12y ago
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

More ›