friism

18 ms·

151.
Upgrade to NuGet 1.8 to speed up builds(blog.appharbor.com)
2 points by friism 14y ago|0 comments
152.
Use GitHub for Windows to deploy to AppHarbor(blog.appharbor.com)
3 points by friism 14y ago|0 comments
153.
Silicon Valley Is Stuck In An Uncanny Valley Of Density(forbes.com)
53 points by friism 14y ago|55 comments
154.
The truth about venture capital(infoproc.blogspot.com)
2 points by friism 14y ago|0 comments
155.
Microsoft announces new programming language(thenextlanguage.net)
10 points by friism 14y ago|0 comments
156.
AppHarbor goes Command Line(blog.appharbor.com)
4 points by friism 14y ago|0 comments
157.
by friism 14y ago
Thanks!, and don't forget to let us know if there's anything you think we could do better.
158.
Automatic migrations made easy with .NET Entity Framework(blog.appharbor.com)
27 points by friism 14y ago|6 comments
159.
by friism 15y ago
We haven't made any direct comparisons, but AppHarbor web workers are very fast and can handle upwards of 200 reqeusts/second for cached responses of moderate size. For non-ASP.NET workloads, we offer background workers: http://blog.apphar
160.
by friism 15y ago
AppHarbor makes hosting projects of any size much easier than Azure, check it out: https://appharbor.com/
161.
by friism 15y ago
Have you considered hosting on AppHarbor. Deployment as easy and fast, we can scale and we have a great hosted RavenDB add-on: https://appharbor.com/addons/ravenhq
162.
by friism 15y ago
Have you considered AppHarbor as a faster-turnaround alternative to Azure? https://appharbor.com/
163.
by friism 15y ago
Running .NET is even simpler if you just use AppHarbor, no need to configure, update and maintain servers at all.
164.
by friism 15y ago
Have you considered running your apps on AppHarbor? That way, you wouldn't have to worry about servers at all. We also have many of the services you use as add-ons: https://appharbor.com/addons
165.
by friism 15y ago
Have you considered running on AppHarbor instead of raw EC2? Nancy works great on our platform.
166.
AppHarbor (YC W11) adds New Relic performance monitoring(blog.appharbor.com)
6 points by friism 15y ago|1 comments
167.
CoffeeScript or Straight Up Javascript? It’s Decision Time(wekeroad.com)
6 points by friism 15y ago|0 comments
168.
by friism 15y ago
Yeah, me too - powerful stuff.
169.
AppHarbor (.NET PaaS) API now in Beta(blog.appharbor.com)
4 points by friism 15y ago|0 comments
170.
by friism 15y ago
We sent out a newsletter for the same reason (including an announcement to people who had unsubscribed). Did you not get yours? We'll do another newsletter with background workers soon.
171.
by friism 15y ago
That scheme will continue to work, but for the sake of your users, you might want consider whether having them wait for the pdf-generation while their request is being served is optimal.
172.
AppHarbor launches background workers(blog.appharbor.com)
29 points by friism 15y ago|8 comments
173.
by friism 15y ago
I think the Facebook profit per user (from the IPO prospectus) is only ~1$ and it seems likely that the potential users generated using your suggestion will be below average in terms of revenue generation.
174.
AppHarbor adds RavenDB support(blog.appharbor.com)
26 points by friism 15y ago|4 comments
175.
by friism 15y ago
That's great feedback, we'll try to a better job. In the meantime, check out the "How AppHarbor Works" page for additional details: https://appharbor.com/page/how-it-works
176.
by friism 15y ago
Here's the node.js chat application running on AppHarbor: http://nodejschat.apphb.com/
177.
AppHarbor lets users blackout hosted apps for SOPA protest(blog.appharbor.com)
10 points by friism 15y ago|0 comments
178.
How much of an iPhone is made by Samsung?(economist.com)
56 points by friism 15y ago|23 comments
179.
Iron Foundy: Cloud Foundry for .NET(blog.tier3.com)
6 points by friism 15y ago|1 comments
180.
A computerised pathologist that can outperform its human counterparts(economist.com)
6 points by friism 15y ago|1 comments

More ›