https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
http://kangax.github.io/compat-table/es6/
There doesn't seem to be anything wrong with Firefox 32+'s implementation.
1,026 karma · joined December 11, 2011
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
http://kangax.github.io/compat-table/es6/
There doesn't seem to be anything wrong with Firefox 32+'s implementation.
Right now it's around 75 kB without minification and without gzip. However, this doesn't include any code for doing feature detection.
So, my somewhat educated guess would be: around 30 kB (which is comparable to jQuery).
We got this years ago. You can do per-pixel stuff via the Canvas API.
You can see the CPU/RAM/network utilization of each in Chrome's task manager. You can open it via Shift + Esc or ☰ -> More Tools -> Task Manager.
Most minifiers have a switch for that. E.g. UglifyJS2's is "-m"/"--mangle". YUI Compressor's is "--nomunge".
By the way, this stuff looks a lot nicer with AngularDart or Angular 2.x.
Once a feature works as intended, optimizations aren't premature anymore. You're then in a position where you can profile, measure, and compare.
The comments are written in a markup language (Markdown, UBB, whatever...) which is then converted to HTML.
It's transformed and not displayed as-is.
It's converted into paragraphs. Just like stuff inside asterisks is converted into emphasis.
Virtually all of the text I write is Markdown. Even this very comment is written in a subset of Markdown (and so is yours).
Markdown is a markup language for relatively simple structured documents. You can convert it to HTML, but you could as well convert it to something else.
> However that is where the use case ends. .MD is not a useful format for many other cases unless you want to prove to the programmers that you too can do tricky stuff in plain text. For the rest of us it has little value.
It's used by Reddit and some content management systems. Regular users don't have any problems with it. It's a lot easier to use than HTML and also more convenient to use than RTEs.
Markdown isn't for writing HTML. It's for writing the actual content.
I wrote about 100 articles in "raw" HTML. I surely don't miss those days. It was error prone and the tags added very distracting visual noise.
However, video, audio, input handling, and loading resources would be a lot simpler.
E.g. take a look at the input manager:
https://github.com/keendreams/keen/blob/master/id_in.c
You also wouldn't have anything like this:
https://github.com/keendreams/keen/blob/master/id_ca.c
You'd put some resources in a list and that's all the caching you'd do.
You should be able to do a game like this in less than 10k lines of Dart/TS/JS (2D Canvas, Web Audio, Gamepad API). Without using any external libraries or engines, that is. It also would be a lot easier to write, because all of the low level parts are gone.
JSC doesn't seem to have an advantage in the extremely short-running SunSpider benchmark suite.
Dart's snapshots are also something you just can't do with JavaScript, because the program structure is created imperatively with JS. You have to run quite a bit of code before you can actually run the program itself.
> Is it a meaningful amount that I should be worried?
Worried about what? Why would you care anyways? Do you also get worried if some game uses a Lua VM?
I use Dart for pretty much everything. Command line tools, web servers, and client-side scripting. It's an excellent choice for the things I do and the things I want to do.
It's a better fit than Java, C#, JavaScript, Python, or PHP. I still do use those languages occasionally, but Dart is my primary language now.
As far as the VM itself is concerned, it doesn't really matter if other browser start to support Dart natively. The VM is extremely useful for development, you can embed it in native applications, and you can use it to write web servers and other command line tools.
<script>
var CONTENT = '' +
"Why Common Markdown isn't the Solution\n" +
...
That's probably the most roundabout way to put an article on the web. You are inlining Markdown in an HTML document. Then the browser has to parse and execute 4.5 MB (!) of JavaScript and then it can finally turn that Markdown string into HTML.HTML documents are a pretty good choice for, y'know, HTML.
Well, if your goal was to increase the page weight from 10kB to 2.2Mb, you surely succeeded.
PHP Markdown, MultiMarkdown, etc also support that syntax. Stack Overflow is pretty much the exception [2].
I'm not interested in Markdown parsers which do not support tables. They are useless to me.
[1] http://www.reddit.com/about/ - "last month, reddit had 114,540,040 unique visitors"
[2] http://meta.stackexchange.com/questions/138946/can-we-add-ma...
Coming from CouchDB, support for attachments (=binary data) was the only thing I was missing.
Then the introduction needs some work.
"DocumentDB enables complex ad hoc queries using the SQL dialect"
"Azure DocumentDB offers the following key capabilities and benefits: Ad hoc queries with familiar SQL syntax"
The "Query DocumentDB" article also seems to be focused on that SQL dialect.
Generating a list of all used tags:
r.table('posts')('tags').reduce((a, b) => a.setUnion(b))
Grabbing all posts with the 'foo' tag: r.table('posts').filter((doc) => doc('tags').contains('foo'))I'm not really sure why you think that this stuff is meant for designers. Recompressing images is a frontend optimization. It's something you automate. It's a task for machines, not humans.
Secondly, it paves the way for competing implementations. Having more implementations automatically means more performance, because they compete with each other.
And finally, a language specification is also super useful to people who create tools such as IDEs, linters, or compilers/transpilers.
I already have to use some user CSS because they removed the ability to set the tab min width via `browser.tabs.tabMinWidth`, because that property wasn't "worth it" according to one developer.
Edit: Turns out Classic Theme Restorer has an option for that.
Because there is no dead code removal. All of it goes over the wire. Even the stuff you don't use.
If you use a 70kB library, you'll pay 70kB in page weight for it. Even if you only use half of it.
The Closure Compiler can remove unused code if its "advanced mode" is used. However, it requires everything to be annotated and to be written in a particular style. Very few libraries meet these requirements.
Those micro libraries and micro frameworks try to address this issue by doing only one specific thing.
[Personally, I prefer something Dart's built-in dead code removal. I really don't want to think about that stuff. Let me put 30 tween functions into one lib and simply don't ship those functions I'm not using.]