vvoyer

At Algolia, we use simple requests (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#Simpl...) in our JSON API. So that there's no OPTIONS requests being done in the most important scenarios (GET, POST).

This is a very neat trick because you can definitely ask an API for JSON via accept header (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ac...) while being compliant with simple requests by using query strings and/or multipart/form for routes option.

Careful though because typeahead.js is not maintained at all even if not said clearly on the GitHub repo

Hi vonseel, sorry to hear that. I work at Algolia and can directly impact how this search works. Do you have any particular, specific issue or feedback for us to make it better? Thanks!

I had a look at your latest viewer project, but I missed the high level problem this is solving. i.e. what is the real world use case you had that made you invent this library.

Reading "This allows you to go back in time and render values you'll calculate later into your templates." did not help me understand the use case.

By providing the real world use case, you'll have people that can relate their own use cases. Thanks!

Please Bloomsbury or JK Rowling, send this person a hardback copy

That's completely fine, doing open-source is not a mandatory experience for your own career. Also you can do open-source contributions at work, when it's related to work or just if your company thinks that on the long term it's good and that the benefits are great.

> The article is more geared toward those who think they don't fit into the open-source community.

Exactly what I wanted to outline in the article. Too often I thought that open-source people where inside the NBA of developers, that's not true at all. It's just people that have code visible by everyone. It's just code.

I did not mention it in the article, but it's also completely fine to abandon your own project if you state so and wait for anyone willing to maintain it.

There's no shame in ignoring feedback in open-source if that's a struggle on your side, health before open-source :)

Hey hi author here, the title is misleading (or click bait, yes). Inside the article there's a nuance though between shopping for things to fix (first time contributions) and solving your own problem by offering solutions to the community.

The obvious way is for sure to solve problems you already have, but if really you don't have any idea where to start and you still want to be in a community then it also exists and they are welcoming you.

About the "open-source career" usage, it's about engaging with different communities than your regular job but that's how I phrase it.

Thanks for the feedback still.

True, and open-source projects can also have "Edit this page" links on every pages that directly goes to the edit mode of the file, example: https://community.algolia.com/react-instantsearch/guide/

We got many first time contributions with that.

We see grit as in "You want to write about company engineering culture? Draft it, review it, share it and publish it". Not as in "work crazy hours until you burn out".

It is true that grit can be taken the way you said. And it's also true that Algolia being a great company to work for we get excited about work and sometime want to deliver outside 9 to 5.

Still we do ensure via regular one on one how people behave/work and we adjust/advise them when we see that they frequently work too much/burn out.

Finding the sweet spot of work life balance is hard. We want people to feel passionate about what they do instead of looking at the clock waiting to finish work.

Hey hi! I am the author of this article and happy to discuss work-life balance since this is a very important topic for me.

Could you point out the parts that made you think that work-life balance was unbalanced at Algolia?

I am 33 years old, married, with a kid and my schedule is mostly oriented towards enjoying time with my family: - I walk my kid to school (8:30am) - I arrive at work between 9am and 10am - I leave work at 5:40pm max - In holidays I have no twitter, no work emails, no GitHub

Not everyone share this balance but we insist a lot on this.

Thanks for reading.

Obligatory blog post: https://blog.algolia.com/secure-tool-for-one-time-self-destr...

Or from https://yarnpkg.com/en/packages?q=http&p=1?

Thanks, also did not quite understood what exactly was headless_shell: how to run it, pro/cons, when to use it versus chrome headless.

Can you detail what is the embedded viewer and how/when you access it? Thanks.

Almost one year old but there was a talk on headless chrome at the Blink conference (BlinkOn 6):

Video: https://youtu.be/GivjumRiZ8c

Slides: https://docs.google.com/presentation/d/1gqK9F4lGAY3TZudAtdcx...

More links: Headless Chrome architecture: https://docs.google.com/document/d/11zIkKkLBocofGgoTeeyibB2T...

Mailing list: https://groups.google.com/a/chromium.org/forum/#!forum/headl...

All of those links are on https://chromium.googlesource.com/chromium/src.git/+/master/...

Works for me when using https://github.com/cyrus-and/chrome-remote-interface

What the best strategy that worked for you on high volumes, multiple tabs or multiple docker instances? I am wondering if multiple tabs is as efficient as multiple windows/instances.

Thanks.

Also checkout https://github.com/cyrus-and/chrome-remote-interface for an easy way to fully control those headless instances

Yes: https://github.com/cyrus-and/chrome-remote-interface/wiki/Tr...

But ultimately selenium and webdriver.io will do a better job at this

Yes: https://chromedevtools.github.io/debugger-protocol-viewer/to...

Did not find easily any live example, should be required for any "UI" library. And should be displayed on the frontpage

Hi! Algolia employee here, thanks for the mention, did you encounter any issue using our widget based libraries or where you only willing to use the raw JavaScript client?

Thanks!

PHP and MySQL by example: you build an IMDB like website in a very progressive and beginner manner.

https://www.amazon.com/PHP-MySQL-Example-Ellie-Quigley/dp/01...

Author here, ask me anything on how this is built.

We replicate via pouchdb the npm registry to an Algolia index then we build the frontend on top of it.

The index is kept up to date live via CouchDB changes.

https://github.com/algolia/npm-search

https://community.algolia.com/instantsearch.js/

We would love to get some feedback on the API we went with and the choices we made. Have a look at the guide: https://community.algolia.com/instantsearch.js/react/guide/

Example: https://esnextb.in/?gist=e9a74d9f7d8afa838c8362e209e0c229

Hi, what we do is use a React build in development mode and then compile with preact.

This is safe at least for us because it allows us to keep all the good React development environement while providing a build that is a lot lighter.

There are a lot of edge cases to handle when creating a library like that and I cannot see them dealt with in this library.

More than three years ago I created in-viewport and have perfected it since. https://github.com/vvo/in-viewport it's used on fortune 500 websites along with my lazyloader (https://github.com/vvo/lazyload).

https://github.com/camwiegert/in-view/issues/7