Hacker News new | past | comments | ask | show | jobs | submit | j0k3r's comments login

Of course yes. Feedly to the rescue after Google Reader shut down.

I even build apps to read more: - https://f43.me to have full content in RSS feeds - https://bandito.re to have GitHub star repo’s release as feed


Where is the pricing page? Is it free?


from https://deepscan.io/getting-started/

Pricing

We are in BETA stage and do not provide paid plans yet.

But open source projects are free and one private project is for your trial experience.

If you're interested in using DeepScan for more private projects, please contact us.


Ok thanks! I was looking for a pricing page in fact :)


Registering where?


Yep!


This is what I got in my rss feed:

---------

Ionic 2 is the next generation of Ionic, the popular open-source mobile app development SDK that makes it easy to build top quality mobile apps with web technologies.

Ionic 2 is based on the new 2.x version of AngularJS, and comes with many significant performance, usability, and feature improvements.

For a quick intro to Ionic 2, see the guide (https://github.com/driftyco/ionic2/blob/master/GUIDE.md).

Building & Running

  - Run npm install.
  - In the ionic2 working directory, run gulp watch. This will transpile the Ionic project files to es5 (using the 'system' module format), bundle them, build out all the Ionic examples, and watch for future changes. In dist/js/es6/ionic you will find clean es6 Ionic files (no @Annotations), and in dist/js/es5/ionic you will find all of the Babel-transpiled es5 Ionic project files. The Ionic bundle is located at dist/js/ionic.bundle.js and the examples are located in dist/examples.
  - Go to http://localhost:8000/dist/examples/
  - Stay cool



Been there last summer, it's really an interesting place. It's crazy to see how people left everything back when they leaved. The city seems to be stuck in 90's. Nothing changed since. Stunning..


Not a single test?


Gitlab guys found a working method to fight the git conflict on the CHANGELOG file: https://about.gitlab.com/2015/02/10/gitlab-reduced-merge-con...

Sumup:

> At GitLab we solved the above problem by adding a 100 lines with just a hyphen placeholder at the top of the changelog. People can insert their entry at a random location in the changelog. There is still a chance of conflict when two merge requests change the same line but it is greatly reduced. It looks a bit strange to have these empty lines on top so we added a comment to explain their purpose..


Seems they no longer use this method. Instead they use `CHANGELOG merge=union` in a .gitattributes file at the root of the repository. That means that conflicting merges take changes from both sides of the conflict. It's what you usually want with a changelog.


+1 for lunr.

I built my own search on my blog using lunr. It's fast and works great.


Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: