leaverou

Glad you figured it out! Btw if TinyMCE makes you icky, you may like the Markdown plugin: https://plugins.mavo.io/plugin/markdown

There's an FAQ item on this! http://mavo.io/faq/#angular

Note that as is mentioned on the website, this has indeed been tested on users, and the results of the study have gone through rigorous peer review and published at a top tier academic conference on HCI. And yes, the audience is programming novices who do know HTML and CSS. For now. Since Mavo is a language, one can easily imagine an integration with a visual editor, to make it accessible to the average Joe.

Not sure where you got this from. Operators are supported as normal and are listed there too.

That cannot be updated by the non-technical people in the company.

Yup, we have! Here's the paper: http://dl.acm.org/citation.cfm?id=2984551 and here's an open version: http://people.csail.mit.edu/karger/Papers/mavo.pdf Look at the References and you'll find more :) There's a whole area of research about end-user programming, though it doesn't usually involve languages, but more GUIs.

IE 11 is a dead browser. Development stopped 3 years ago. There will never be an IE 12, it's just Edge now (which Mavo works in just fine).

Spreadsheets have function calls as well, and yet non-programmers can use them. We don't care about making a theoretically pure distinction, we care about making something that non-programmers can actually use.

It's been years but I think it was just exclamation. Like "oh, fuck!".

Nope. There were many people around, and it was clear that he didn’t know all of them. There were people he didn't know just as close as I was. He apologized only to me, nobody else.

It was absolutely NOT directed just at men. We all have internalized stereotypes and biases.

THIS. There is nothing wrong with dick jokes. The only sexist thing about them is the imbalance: We need more vulva jokes too :)

“Just don’t have a bias”. Unfortunately, it doesn’t work like that. The problem is that it’s very hard to know when biases are affecting your decisions. You cannot just decide to not have them. Agreed though that fighting bias with bias is not a solution. What is the solution then? I don’t know. :(

Apple is a steward, but they chose not to have their logo in the footer. You can see them on the list of the stewards http://webplatform.org/stewards/

Um, when did we forget how to write our own abstractions? It’s not black and white, either jQuery or vanilla JS with no helpers.

Yup, it's all here: http://www.browserscope.org/browse?category=usertest_agt1YS1...

Edited, thanks!

Yes, as long as their unprefixed equivalent is in a W3C specification.

FOUC? It's only some CSS3 that won't display until DOM load, not the whole styling. As for the performance, I'm pretty sure you're just guessing, and haven't done any testing.

The spec-compliant gradient syntax hasn't yet propagated in Safari, even though it's in the nightlies since February.

It's a browser limitation.

Yes, eventually the prefixes get dropped. In some engines sooner than others. Eric Meyer recently wrote a nice article about this, on ALA: http://www.alistapart.com/articles/prefix-or-posthack/

The slides were initially made to complement my talk at Front Trends 2010, so it wouldn't make much sense in that context.

I just didn't want to clutter it with duplicate things like <dt class="opera">Opera</dt>. I kinda agree with your point though, it was something I also wasn't very sure about.

I also agree that box-sizing is better, I have also used it in a few places. I mentioned it in my talk too, I just didn't put it in the slides. I just wanted to experiment with calc() a bit too :P

By "Full support" I meant that it fully supports the feature (without a prefix or huge deviations from the spec). It doesn't have anything to do with browser versions.

It's best if you read the rest of the information that I posted along with this, here: http://leaverou.me/2010/10/my-ft2010-slides-and-csss-my-pres...

I mention quite a lot known compatibility issues with the presentation, including the Firefox 3.6/Win problem (it works fine in my FF3.6 for OSX) along with an explanation of why it only works in latest versions. :)