I have the commit bit to the repo backing my blog. You do not. I f you have some serious suggestions, feel free to submit a pull request.
I'll review your PR and decide whether it matches the tone and style of my blog. If it doesn't , regardless of what you see as its merits, it will be rejected.
That state of affairs is not acceptable to most people, and fortunately, there is an alternative route forward: Instead of trying to lecture me about what to write in my own blog, and instead of lecturing me about what I should consider important to mention, and why, YOU CAN WRITE YOUR OWN BLOG POST REFUTING MY POST.
I am not being sarcastic. Great things have transpired in history when two or more people engage in a conversation via essays.
Words are so vague. I don't even know what "hard locked the dev tools" even means!
But if you write your own essay, with your own code illustrating your own ideas. Ah! That clarifies things for me and for everyone else reading.
It has never been easier to publish words. Avail yourself of this opportunity.
---
As for bugs and chaos all over the javascript world...
I have been publishing essays on the Internet for fourteen years. Most have been of a highly impractical nature: I save my practical thoughts for my work, and I scratch my "boy this is interesting" itch in my writing.
In all that time, I haven't broken the Internet. No hordes of people rushed out to implement macros in Ruby when I released Ruby.Rewrite.Ruby.
The JavaScript world was not taken over by decorators when I released Method Combinators. My book has an entire chapter on implementing traits in JavaScript. Where are all the traits?
(tumbleweeds)
I write to provoke thought. I think most people grasp that. You should have a little more faith in people.
Some people find these things interesting, even provocative. They may wonder if such a thing makes sense. But few people rush to implement an idea just because of one essay on Hacker News. Typically, they need to see a preponderance of momentum.
An essay from me. A library from someone else. A major framework baking it in. Only then will people bet their projects on it.
Until then, it's nothing more than one person, me, saying "Here's something interesting," and a bunch of other people saying, "indeed," over their coffee breaks.
Then we all go back to work and the world carries on just fine.
Honestly, with the exception of your statement that my trampolines will cause an out-of-memory error, you are not wrong about performance and the fact that practical applications for greenspunning your own trampolines are rare to the point of statistical non-existance.
I sense that everyone agrees with you, they just don't worry that hordes of Eternal September JavaScript n00bs will start swapping iteration for anonymous recursion powered by recursive combinators.
I have the commit bit to the repo backing my blog. You do not. I f you have some serious suggestions, feel free to submit a pull request.
I'll review your PR and decide whether it matches the tone and style of my blog. If it doesn't , regardless of what you see as its merits, it will be rejected.
That state of affairs is not acceptable to most people, and fortunately, there is an alternative route forward: Instead of trying to lecture me about what to write in my own blog, and instead of lecturing me about what I should consider important to mention, and why, YOU CAN WRITE YOUR OWN BLOG POST REFUTING MY POST.
I am not being sarcastic. Great things have transpired in history when two or more people engage in a conversation via essays.
Words are so vague. I don't even know what "hard locked the dev tools" even means!
But if you write your own essay, with your own code illustrating your own ideas. Ah! That clarifies things for me and for everyone else reading.
It has never been easier to publish words. Avail yourself of this opportunity.
---
As for bugs and chaos all over the javascript world...
I have been publishing essays on the Internet for fourteen years. Most have been of a highly impractical nature: I save my practical thoughts for my work, and I scratch my "boy this is interesting" itch in my writing.
In all that time, I haven't broken the Internet. No hordes of people rushed out to implement macros in Ruby when I released Ruby.Rewrite.Ruby.
The JavaScript world was not taken over by decorators when I released Method Combinators. My book has an entire chapter on implementing traits in JavaScript. Where are all the traits?
(tumbleweeds)
I write to provoke thought. I think most people grasp that. You should have a little more faith in people.
Some people find these things interesting, even provocative. They may wonder if such a thing makes sense. But few people rush to implement an idea just because of one essay on Hacker News. Typically, they need to see a preponderance of momentum.
An essay from me. A library from someone else. A major framework baking it in. Only then will people bet their projects on it.
Until then, it's nothing more than one person, me, saying "Here's something interesting," and a bunch of other people saying, "indeed," over their coffee breaks.
Then we all go back to work and the world carries on just fine.
Honestly, with the exception of your statement that my trampolines will cause an out-of-memory error, you are not wrong about performance and the fact that practical applications for greenspunning your own trampolines are rare to the point of statistical non-existance.
I sense that everyone agrees with you, they just don't worry that hordes of Eternal September JavaScript n00bs will start swapping iteration for anonymous recursion powered by recursive combinators.