Hacker Newsnew | past | comments | ask | show | jobs | submit | avanderhoorn's commentslogin

2 core, 4GB ram... can't config atm.


My biggest problem is not being able to get sharp corners. Thats not a problem with Shaper Origin per se, but more with CNC based routers (note the chess board on their homepage, it doesn't have squares with 90 deg corners). If something like Shaper Origin supported being able to do this, I'd buy it in a heartbeat.


You only cannot get sharp internal corners. External corners can be square/arbitrarily sharp. I don't think it's too big of a problem, usually you want things rounded to relieve stresses anyway, but indeed I can see situations such as aesthetics or piece compatibility this could be an issue.


Sharp internal corners are hard period. CNC milling machines have the same issue -- the usual way to to just use a smaller end mill.

You either need some type of punch or an (actual) shaper.


That's what square hole drill bits are for.


Those round the corners too I'm afraid.


@matt4077 thanks for your feedback and questions. I'll post my reply here and on the GitHub issue for coverage and for anyone else wondering at this point in time (as the answer is likely to evolve in the future).

I totally agree that having public code in a repo on github that has a proprietary license leads to headaches, hence why we haven't done that. If you take the time to have a look around the Glimpse org, all code that exists there, is under MIT/Apache2. No code associated with the Node project is yet publicly available on GitHub. Once you have looked, feel free correct me if you think something has slipped through. Given that everything is MIT/Apache2, there is no chance that someone could accidentally commit code to a repo that has a license that goes against the spirit of the community.

Regarding our use of the Open Source Code of Conduct, parts of the project, specifically the .Net components, are currently open source. Even though not all elements of the project are public, a large portion of the project is and we choose to operate under that code. For Glimpse/Home we have it mentioned there, not to confuse people, but rather to advise people the guidelines under which we are operating. If you have a chance to read through it, please feel free to reach out to me if you don't agree with what it states as it pertains to running a project.

To summarizes, the only repo under the Glimpse Org that is associated with the Node effort is Glimpse/Home and it has no code in it. All other public repos carries the MIT/Apache2 license. Glimpse/Home is our current best place for gathering feedback and is situated on Github since it is where the community is. It works given our future direction.


Glimpse v2 is using React/Flux for pretty much everything client related and all parts are open source and on github.

For those who don't know, Glimpse is an OSS diagnostics platform and we are in the process of building out v2 (including NodeJS and .NET backends) - http://getglimpse.com.

Current work on the front end can be tracked here - https://github.com/glimpse/glimpse.client/tree/version-2. Very much a work in progress but all good so far.

The system is quite large. In the end it will contain several major "sub applications" that users can switch between and each "application" has large number of components, major interactions, etc.

We are currently using the following stack:

- Views - ReactJS, - Server Comms - Superagent + Primus (SocketIO), - Build - Gulp, - Packaging components - Webpack, - Module System - CommonJS, - Message Bus/Dispatcher - Postal.js, - Testing - Jasmine, Jest, Chance, Karma, etc


Which services and whats your breakdown?


Main work project: Around $500 a month split across 2 services - Mixpanel ($350) and Azure Hosting ($150). Its a 2 man team

Side projects: Around $40 a month split across 2 services - Gtihub, Asana


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

Search: