HN user

ahmelsayed

33 karma
Posts1
Comments16
View on HN

You certainly can do this. Though keep in mind that your functions are running on Windows, so make sure to compile your native binaries to target Windows.

It's just very inconsistent. It just happens sometimes and I either restart firefox or close and open the tab and it goes away. I can try to take a memory dump when that happens. I don't know how useful that might be for you. If I ever get something consistent I will make sure to file a bug.

Thanks for all the amazing work though! nothing beats the visual tools and network traces in Firefox.

I primarily use Firefox for browsing, but for development I usually use a mix of Firefox and Chrome. It might be just me, but it's very common when I use the JavaScript debugger in Firefox that it either freezes the site, the debugger, or Firefox itself. That causes me to give up and head to Chrome. I also wish they put a visual queue on the web page when you pause the debugger like Chrome does. Everytime the site get's unresponsive I have to click around few times, wonder what I screwed up, and then realize that the debugger was paused.

While that is absolutely true for IIS and the Shared tier in Azure Websites (although it's fully configurable if you own the IIS box[1]), Dedicated tiers (when you own the whole VM) in Azure have a feature called Always On[2] Where there is no idle Time-out on the app itself, so even if the app remained idle for days, w3wp process won't be killed. Also if the app happen to shutdown for any reason (machine restart, Azure Update, Windows Update, app crash, etc) Azure Websites will make sure to send a request to the app to start it up and warm it, then the app can use Application Initialization[3] to do any more complex warmup

[1] http://serverfault.com/a/595215/219792

[2] http://azure.microsoft.com/en-us/documentation/articles/web-...

[3] http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-...

I think he is referring to running different versions with different CLRs side-by-side. It means Platform-as-a-Service friendly. Since in PaaS you usually don't own the machine, you just run code somewhere. You don't want to be tied in with is framework X installed on the machines or not. You want to be able to pull in what ever framework you like, as you would do with node.js for example

also

- right click on the running instance in the task bar and select Visual Studio

- middle click on the already running instance in the task bar

same as with Windows 7