mdtusz

Montreal is an extremely easy city to live in. Very inexpensive rent, good nightlife/events and arts/culture scene, and a pretty good transit system.

The Quebecois will disagree with me on this, but I don't think you even need to speak French if you're working in tech - you might just have a smaller friend circle of Anglos.

Taxes however are crazy high and salaries are low compared to cities like Vancouver or Toronto.

Small plug - we (AON3D) are looking for c++, python, and js developers right now. Find our careers page and send us an email if you're interested in 3d printing and industrial machines.

Best of luck. I've found azure far more difficult to manage even simple things with than on AWS. Even spinning up a single simple development server feels far more complicated.

The whole reason for experimenting with this was to be able to create traces on 3d printed parts - the test runs were just on rectangular coupons for ease of testing and because he printed what looks like hundreds of them.

Montreal winters are far worse than Ottawa, if only due to the laissez faire attitude taken towards infrastructure and maintenance of the city and buildings - not just government, but landlords as well.

Any chance there's a write-up or docs on this somewhere?

I'm working on a product that has a similar case - we luckily have the benefit of the hardware having a display and input so that clients need to effectively pair themselves (i.e. you need to physically click an authorized button on the hardware) before they can have full access. We figure that if someone/something has access to the hardware, you're already boned.

"Einstein's Telescope" however, is fairly dry and a bit out of date now as well.

The resin.io team has made something like this called resin-wifi-connect[1]. It doesn't appear to be as simple as it could be, but it's prior art if you plan to make something more generalized.

[1] https://github.com/resin-io/resin-wifi-connect

Is this so bad? It seems to me that using <i> for icons has become pretty standard across many sites and you shouldn't be using the <i> tag for italics anyways - there's <em> for that now.

A fun little demonstration to do when teaching sailing to kids is to fill a baking dish around half full with chocolate pudding and level it, then drag spoons through at a slight angle to simulate a sail. It's far from scientific and isn't really working on quite the same principle, but if your pudding is the right consistency, it does a decent job of showing the pressure gradients. Best of all, you've got a bunch of chocolate pudding to eat after.

Carbon and kevlar tapes are used in sails to minimize their stretch along their stressed areas and allow for optimized sail shape. I don't think anyone selling or making sails tries to convince of any other reason.

This is not quite correct.

Even while sailing downwind, the sails are still providing "lift" (if we are calling it that here). There are opposing forces for sailing - the Center of Effort (CE) and Center of Lateral Resistance (CLR). These two need to be balanced in order for the boat to sail a proper course - of course if you are just letting the wind push you directly downwind, you could remove your keel/daggerboard, but in practice, you will want to sail on an angle to the wind - on a reach or by the lee depending on the type of boat - so as to create flow over the sails and have a greater pressure gradient than if you just let the wind push directly against the sail.

The hull of the sailboat contributes to the CLR, so it is common in dinghy racing to pull your centerboard/daggerboard up partially so as to balance these forces and minimize drag. If you watch Olympic laser sailing, you'll see while sailing downwind, they will heel the boats to windward with their daggerboards about halfway up so as to move the CE closer to being above the CLR, allowing for less rudder drag to counteract the forces and steer straight.

Every time there's anything on HN or Reddit about sailing, there's a _ton_ of misinformation and blanket statements that might apply to some types of boats, but are far from general rules. I'm happy to answer any other questions too!

Can you share this repo? I really like that idea.

Once notebooks have been created, they are just json files that get rendered to html so there's no haskell or python code running. If you're allowing other people to upload notebooks though, you'll want to sandbox them inside an iframe to prevent xss attacks - at work we do this, but allow some channels of communication using the postmessage API.

Looks nice, but I'm getting two audio tracks playing at the same time (Chrome on Windows and watching Horrible Bosses 2).

Another (not yet mentioned here) tool is Mjolnir. It requires some lua scripting but seems to be really flexible.

I stick with bettertouchtool combined with some keyboard shortcuts though.

I've never seen Cycle before, but this looks somewhat similar to Mithril (http://lhorie.github.io/mithril/index.html), which is based on a semi-FRP virtual-dom approach.

The thing that I prefer about Mithril though is that at the end of the day, your code looks like regular, vanilla js and is extremely readable. It's a pretty much invisible framework that you can use however you see the best fit - it just takes care of rendering and updating without any magic, and provides you with some helpful tools for managing models.

My immediate grip with Cycle is the api - it just looks messy and more complex than it needs to be.

I'm new to mongo still, but isn't it pretty rare to ever need to make a query like the one in the example with mongo?

My understanding is that the (one of the) whole point(s) of using mongo is that you can organize your data in a nested way so as to minimize the joins needed and just make simple queries, then only use the data you need.