tal_berzniz

Yeah... it actually works. Mostly for programmers who don't need bold/italic/headers and can make those out of ASCII chars

Wouldn't it make more sense to ask the community what they want to do? Without taking time from the original maintainers

If the alternatives are better, then devs will choose those solutions and "request" will fade over time. It doesn't have Promise support, so new projects will likely not choose it.

request is very simple and straightforward library that solves a very common issue.

Deprecating it causes a lot of work for every project out there. Either using request directly or indirectly.

I have a lot of respect for the maintainer, and he can choose to do whatever he wants with this module. That's his privilege.

However, the fact that he got "bored" with this solution, doesn't mean he needs to deprecate it. He can just stop working on it, and give ownership to someone else.

If it had a security issue and he is not going to ever update it, then that would deserve the deprecation so people should be warned.

Deprecating is a weird decision as there is nothing wrong with the "request" module. It doesn't lead to bad code, bugs or security risks.

It would be better to say this is the last version, except for security upgrades. These upgrades can be done by other maintainers that are assigned to the project.

Nothing... it's an idea and a website

A lot of the important tech decision take place around a whiteboard where people communicate their ideas.

Whiteboard questions are okay. Only giving tasks is not how a real workplace work

Cool idea - Web Extensions API are very powerful.

How would you go about installing the extension in a CI/CD setup? Can it be installed on headless Chrome?

Octotree is great, only thing is you need to give access for private repos

Options indeed was always a common use case but made the function declaration less verbose. Now we can have the best of both worlds

The "hipster hacks" are things you not necessarily use but are fun things to try. Some of these are for fun (like #1) and others (like #2) are day to day life-savers.

Indeed the swap variables is a fun fact.

Amazon is amazing at creating scaleable and reliable services, but their UX and the way they announce new products is awful.

There's room for startups to wrap these services into something more usable. There are already good examples: netlify, graph.cool, dashbird and others.

One of the better comments in this thread

Imagine what these people would do with a tool like rebase going wrong

Finally someone agrees with me! Yey!

Kidding aside, git-merge is simpler because you only need to know 6 commands: co, add, commit, push, pull and merge. I believe that these will help you achieve everything you need with git.

It can be easier. We've used https://github.com/GUI/lua-resty-auto-ssl to provide SSL provisioning on the fly at my previous company for our customers` custom domains. This also means that there is no downtime at all when they change the DNS record from their old servers to the new one

Awesome service so far. The Continuous Deployment flow is awesome with deploy previews, CDN, custom routing, Automatic SSL from Let's Encrypt. The SSL can be improved to be true automatic without a provisioning step (first hit issues a cert)

I think serverless currently means " I don't have to think about servers, provisioning or scaling". It's === to function-as-a-service. S3 is the best example so far since people see it as no servers at all, just static file serving (there USA server running S3, but as a user we don't really care)

Thank you for PhantomJS! Been using it for testing, generating PDFs and screenshot.

If you want to attract the best talent and not lose the good engineers you already have, keeping up with the times is a must. ES6 is one major advancement for front-end developers and they want to be part of it

Thanks, it seems that some users opt-out of committing their email information.

We've set it up in our company with NGINX and LUA (https://github.com/GUI/lua-resty-auto-ssl) and it works great

Talking mostly about things like:

// 1. [a + b] // [a + b] is an array {[a + b]: c} // [a + b] is not an array

// 2. { x, y: x, y} // inconsistent object fields

and there are more examples. After you get to know the syntax, it can be used for good -- but some decisions are making the language more complex.

As written above, I enjoy its new features

JS ES2015. The syntax looks awful at first glance, but after heavily using it, there's much more power to this language now.

LetsEncrypt is automated, so for hosting services who wants to issue certs for customers - LetsEncrypt currently wins

Just our own employees. We can help by sharing what we've learned - as detailed in the post.

Good questions.

1. Everything must enter your main branch (master) via Pull Request 2. Everyone can review it. Sometimes more than one person is needed. 3. It's asynchronous - write comments on the code or sit together if you need to see UI / Changes. 4. Code Review should also review unit tests (which pass) 5. Merge PR

This shouldn't block your team and in a week of doing it people will adore this since it will save them at least once.

Nicely put

Totally forgot about this one. Just wanted to test an idea... I guess I should be be banned according to the guidelines.

thanks for providing the email to contact.

Hi had a decent Karma of 299 at that account. One day I noticed my posts to HN aren't bringing any traffic at all. This seemed odd so I checked and learned about hellbanning. I never asked to upvote my posts (until the final post in that account to check if I was hellbanned).

Wish my other account was brought back to life. I will continue with this one, be more strict with what I post.