tyleregeto

Opinions vary, but I've never found Apple software to be particularly good. Their hardware is almost always exceptional.

I'd go further and say I am constantly frustrated by how difficult their software can make basic tasks. I often find many of their UX patterns unintuitive, or even feel user hostile at times. Small example, I really want to view passwords as I type them in. I constantly miss type passwords on touch screens. User error maybe, but frustrating experience.

XCode is my least favourite IDE that I use regularily.

The Feb 2nd episode of the "The Bridge with Peter Mansbridge" podcast may be of interest to you, its title is "Should Canada Include Nuclear Weapons In Its Defence Strategy?", and offers a perspective on the subject.

Congrats, so much more than I achieved at that age. Keep going!

I would say not very often, but yes, very recently even. I've been researching new backpacking gear this summer, looking on sites that are known to me, so I've been seeing lots of ads for that type of stuff naturally.

One store kept popping up that I was not familiar with. So I clicked eventually, and did some online searching about the company to make sure they are legit.

Turns out they are a local independent store. I've made two purchases from them since, and price compared against them for other purchases. Their ads are more likely to catch my eye in the future now.

I don't use one either. I actually think ads are a good system for supporting content, and I do want to support the creators of the content I consume.

I also have a low threshold for obnoxious sites, and will just bail and not return if I get annoyed.

Being owned by Meta (or Facebook at the time) was a selling feature for me when settling on it. The main reason being that they use it heavily internally, and have a vested interest in its success as a result. They've built it to meet their needs, dogfood features internally, and feel the same pain as everyone else when it comes to breaking changes and backwards compatibility.

This gave me a lot of confidence in React compared to other frameworks at the time I was evaluating it. It turned out to be a great choice now 8+ years later, and I feel the same way today.

When I loaded up the link, before viewing the comments in here, the very first thing I did was look for "Rebecca purple", and I was happy to find it. Not really a comment on your remarks, but thought I would share it.

I'm influenced by the having a daughter born around this time, and Rebecca's story sticks with me.

JS has BigInt support, a quick Google tells me this is supported by wasm. I'm not sure if they are doing that here or not.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Part way through this radio program, they have a conversation with one of the team members. Very interesting stuff. https://www.cbc.ca/radio/asithappens/as-it-happens-the-frida...

I mostly agree, this is always my thought about this stuff. As you say, it is so far in the future that a new government will be in power, and can freely reverse these decisions. Or we'll just end up there anyways because that's the trajectory we are already on.

Something more immediate would have a bigger impact, probably a tax, but taxes don't often work in politician's favour. We have rebate incentives for electric cars, but that only really only helps to swallow the price difference. We can't rely on peoples morals only unfortunately.

DRY is great guideline. KISS is another one. I find that it is not uncommon for the two of them to butt heads a little, and it can be tricky to find the correct balance. In general, I am finding that I favour repetition over abstraction more and more.

Interesting article about this, one of Canada's biggest flour suppliers has not run out of flour, but rather bags to put it in. https://www.cbc.ca/news/business/robin-hood-flour-baking-yel...

Ccdwd

Mapbox is pretty expensive for small commercial apps, $499 flat rate + usage costs. If your commercial usage is on the smaller side, the new Google Maps pricing looks really good.

I was a Mapzen customer, their pricing model was great, very sorry to see it go.

There was three parts with 4 episodes each, for a total of 12 episodes. All very good. Sounds like you may have missed the next two, definitely worth watching.

Netflix plays fine in Chrome (maybe Firefox too) using HTML5, it was opt-in at one point not sure about now. I watch in Linux all the time, no Silverlight there.

For what its worth, I've been using the dev channel for a long time and have never had any issues. It's very stable. I'd recommend it.

Great, thanks for that info!

I thought there was a proposal in the works for adding checksums on script tags. Something like:

<script src='...' checksum='2fd4e1c67a2d28fced849ee1bb76e7391b93eb12' />

Which would allow the browser to use cached copies of files even if from different domains. Not sure where I saw that.

On the other hand, Polygon has been knocking it out of the park lately. Examples:

http://www.polygon.com/2015/4/6/8285529/looking-glass-histor...

http://www.polygon.com/features/2015/5/21/8627231/the-first-...

The day-to-day Polygon "news" doesn't interest me much, but their "features" have been excellent.

I think it is a bit of an exaggeration, but not entirely inaccurate. I am currently working on a large application UI re-write, we've moved to React, and JQuery was included from day one. The entire application uses JQuery exactly once as of today. (We're leveraging $.ajax) React solves a lot of the same issues JQuery does. We didn't purposely try avoiding JQuery, we just haven't needed it so far. That's a major change.

Sort of off topic, but one thing I really enjoy about the Go project is how open development and intent is. In addition to this, the Go team has shared plans (and invited discussion) for many things, some examples:

Internal changes: https://docs.google.com/document/d/1e8kOo3r51b2BWtTs_1uADIA5...

Linker overhaul: https://docs.google.com/document/d/1xN-g6qjjWflecSP08LNgh2uF...

Garbage collector changes: https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLo...

Code: The Hidden Language of Computer Hardware and Software http://www.amazon.ca/gp/aw/d/B008PGKDOO This is one of the most enjoyable reads I have had in a long time, definitely recommended.

Introduction to Information Retrieval http://nlp.stanford.edu/IR-book/ This is a free digital book, very good so far.

In your account settings, try turning on the HTML5 Player. Its opt-in.

I've stumbled across this before, its a very good read. Highly recommended! There are some great videos on YouTube about the subject, left over from that era. I really like this one: https://www.youtube.com/watch?v=oaVwzYN6BP4 (produced in 1969)

Its interesting how little programming has changed since these days. The way we program has changed significantly, put what we produce is almost identical. Each punch card represents a single instruction, equivalent to a line of code in our modern text editors.

I wrote a small punch card toy in JavaScript not too long ago to get a feel for what programming with punch cards may have been like. That's here if your curious: http://tyleregeto.com/article/punch-card-emulator

I don't get that argument. Sass manages to avoid $ conflicts while using it for both variables and mixins. Its nice clean, consistent syntax. I don't see why we need different syntax for the two. Eg:

  $myColor: #fff;

  a {
    color: $myColor;
  }

  @mixin border-radius($radius) {
    -webkit-border-radius: $radius;
    -moz-border-radius: $radius;
    -ms-border-radius: $radius;
    border-radius: $radius;
  }

  .box { @include border-radius(10px); }

This hardly even talks about the templating package in Go, which is really good. They have found a nice balance between ease of use and functionality.

It reads a lot like mustache, but has the power of a language that allows you to mix markup and code. Its worth checking out in more detail.

I can relate to this. Anyone who has ever had to take a family members car away from them as they get older can as well. When someone has driven most of their life, losing the ability to drive can be a very difficult. To them its losing their independence. Self driving technology is very much about enablement.

Yes, that's is a very interesting point. I would think that, long term, the only manual control a self driving car really needs is a "kill switch." How long will it be after self-driving tech goes mainstream until people simply don't know who to drive?

I can see my kids now, "I remember when I was a kid, my mom/dad actually had to control the automobile. Archaic!"

Not too long ago my friend's son asked me why my phone was attached to the wall. He had only ever known cordless phones. I image cars will go a similar route.

A body (or bodies) involved in a fatal accident are perfect test subjects.