olov

8 ms·

31.
by olov 14y ago
You're trying to make a complex issue simple. It's true that scenarios exist where you can use the redistribution-loophole to keep your modifications to a server side GPL program proprietary (Affero GPL was later designed to prevent that).
32.
by olov 15y ago
The major difference is that JSLint as well as "the good parts" focus on a subset that can be verified statically (before running the program) while restrict mode sanitizes operator semantics that must be verified dynamically (when running
33.
by olov 15y ago
I want to take this further still. Most JavaScript programmers already use a subset of the language and I believe that there is quite a broad union of those subsets that should resonate with the majority of us. Excluding certain parts of th
34.
by olov 15y ago
Yes. "LuaJIT 2.0 intellectual property disclosure and research opportunities" < http://article.gmane.org/gmane.comp.lang.lua.general/58908&#... ; is further proof to that. Rumor has it that Mike Pall is actually a collective pseudonym u
35.
by olov 15y ago
Tracing is no silver-bullet. Mike Pall is.
36.
by olov 15y ago
I found the blog comments far more interesting than the post itself.
37.
by olov 15y ago
Great article, shame it got optimized away before I had the chance to re-read it. edit: seems Blogger turned their -O knob to eleven http://status.blogger.com/
38.
by olov 15y ago
I'd also like to see macro capabilities in JS, although as others have said it's not trivial (but certainly not impossible) to add. For what its worth JSShaper [ http://jsshaper.org ] may be of interest although it doesn't provide macros pe
39.
I made JSLint restrict mode clean. Here's what I found(blog.lassus.se)
2 points by olov 15y ago|0 comments
40.
99.93% of the source was valid restrict mode. Making v8bench restrict mode clean(blog.lassus.se)
1 points by olov 16y ago|0 comments
41.
Announcing restrict mode for JavaScript(blog.lassus.se)
3 points by olov 16y ago|0 comments