bartq

I own MacBook 12 inch with 2nd gen of this keyboard from 2017 and actually like it more than on MacBook Pros that I got from a company I worked for. It seems to be a bit different, like click is smaller and is quieter. In MacBook 12 it matches whole laptop philosophy of being the thinest and lightest and even has smaller trackpad that you doesn't accidentally touch while typing.

You can also play with Vanillin: http://metaes.org/playground.html#6-For%20statement%20-%20ba...

Paste this and run:

  <script>
    const rows = 100,
      cols = 10,
      table = Array.from({ length: rows }).map((_, i) => Array.from({ length: cols }).map((_, j) => ({ i, j })));
    console.log(table);
    setInterval(function() {
      let cell = table[Math.floor(Math.random() * rows)][Math.floor(Math.random() * cols)];
      cell.i = Math.floor(Math.random() * 100);
      cell.j = Math.floor(Math.random() * 100);
    }, 1);
  </script>

  <table>
    <tr for="let row of table">
      <td for="let cell of row" bind>cell.i + ":" + cell.j</td>
      <td></td>
    </tr>
  </table>

It only updates DOM element textContent on each change.

Ageism definitely exists when company feels someone is too old to join them. There's obviously easy solution to this problem: join companies where people are similar age to yours or older. Because younger people are probably just not able to handle you or appreciate your life experience and are looking for people similar to them. What if you're extremely old and your equals are dead? You should've retired by that time or have alternative revenue streams than salary. If you've failed to have other income streams than salary that's your fault. You've limited your (professional) life to technical excellence which is obviously only one of the aspects of career and life general. I think people should at some point take wider responsibility of what they're doing and become not necessarily managers, but maybe tech leaders, authors, trainers etc. There is one more aspect to that: person may have a mental condition, like asperger's or something like that. Then he probably cannot build his career in a way described above and he needs to seek alternative ways of progression.

May be relevant: https://docs.google.com/presentation/d/1MD-CgzODFWzdpnYXr8bE....

what are worst parts of vue for you?

They advocate one graph, because it's too hard to merge graphs in parent-child (many-to-one, many-to-many) relationships (recursively) in a flexible way. This is purely because of technical limitation of GraphQL IMO.

Good point, will add that part.

Yes, but it may be worth effort. See for example this editor: http://evanw.github.io/sky/ and paste there even tens of thousands long text. It will work super smooth, like Sublime Text does. If only browsers provided low level APIs for text, font calculations and accessbility (what they already support internally), those kind of editors would make a lot of sense.

Probably you're using dense screen (with pixelratio > 1), like Apple's retina. You can support it in HTML canvas, but author didn't.

Yes.

Optimization and statistical algorithms known as "AI" are far far far away from surpassing humans. Philosophically, it will never happen, we can create intelligence at best equal to human being's, but creating that kind of "AI" would be equal to creation of life which is beyond scope of technology.

AI is as dangerous as we decide it can be, for example we can create gun with camera and shoot to people based on their looks. Law and common sense should not allow that, that's criminal activity.

I think AI should grow, and take over boring and repetitive tasks. This will free up many people form dull jobs and new jobs on top of that will be created, i.e. jobs to tune and organize AI units of computations and talk to other people about results.

they won't abuse because of GDPR. And people are already smarter, the same tricks from the past won't repeat. Browser vendors will be able to easily block too heavy WASM programs, for example which run too long. Or new laws will enforce that. [edit]: Or even very heavy WASM apps will require to be signed by certificate provider, otherwise user will be warned about risks. Just like HTTP vs HTTPS.

From blogpost: this flipped laptop screen standing next to bigger monitor looks very interesting. If it's close enough to mess up using your fingers, that potentially could be very interesting setup for work. But software seems to be a limiting factor; I'm not aware of apps on screen (a) that would react to changes happening on other screen (b) or even other app window.

I liked the idea of Flutter since I saw it for the first time probably long time ago. Dart as a language choice was throwing me back though, but in general this language is very similar to ES6 and makes OO easier. For example it doesn't require to use `this` in methods. I wish it was TypeScript instead, because it has more mature tooling and community support.

I'm still hesitant to put my hand on it for side project until it's more popular. Chicken and egg problem I guess.

they probably discovered it because were working towards being GDPR compliant.

No, Google just sinks in people into project which is going to be doomed anyway - otherwise the same people could build businesses of higher chance of success and endanger Google's position. It's destroying competition by paying people salaries. Not sure if Google does it purposely or it's uncontrolled fatal mechanism.

Because technology shouldn't surpass real human interaction. Wanna world from Matrix movie?

Object.assign({},obj)

I think we're don't do that because it's too dangerous and user would have too much privileges. I'm referring to something like AWS Lambda, but handled by your library on your web server. Say you can run JS snippet only for 10ms and the only global non-standards variables are those that contain data that can be queried. Or even pass them through function params, look:

ctx => ctx.users.filter(u=>u.name.contains('Janusz')).slice(0,10);

And that will return 10 firsts users as JSON.

I think it's only an upgrade for shitty REST-like protocol for APIs. The next after GraphQL will be something like executing your own code in sandboxed environment on the server, with strong constrains etc. Anyhow, I don't like centralized approaches. Easier access to Github data will encourage to create apps based on a global variable which is the Github. I'd rather want them to release installable libraries that communicate with other parts of the system. Sort of.

hey. meh, general rule: listen to your gut and follow it. It's that simple ;)

finally someone did haskell examples in decent modern blog UI instead of old fashioned dark depressing terminal-like colors ;)