thejameskyle

11 ms·

61.
by thejameskyle 11y ago
No stupid questions.. I keep getting similar feedback. I'll do a better job of explaining it. To answer your question, it's taking a lisp-style syntax and turning it into a C-style syntax (specifically JavaScript- the output AST i
62.
by thejameskyle 11y ago
Hi I wrote the compiler, the reasons for JavaScript are: - It was for my conference talk for a JavaScript audience. - JavaScript is the language I use for 99% of my work. - JavaScript has a much larger audience. - I'm a maintainer of a
63.
by thejameskyle 11y ago
I added a separate file without any code comments as well. https://github.com/thejameskyle/the-super-tiny-compiler/blob...
64.
by thejameskyle 11y ago
Author here, you could look at the test.js file in the repo. I want to make an interactive tutorial for this in the future that should hopefully be even more helpful
65.
by thejameskyle 11y ago
Author here. I actually walked through all of this code line by line in a conference talk using another thing I built: https://github.com/thejameskyle/spectacle-code-slide I ripped these code comments from my presenter
66.
by thejameskyle 11y ago
Author here, I tried doing something like you said but it ends up being far more code. I prioritized keeping it understandable over doing something cool or complex.
67.
by thejameskyle 11y ago
We did have those warnings in the docs. I wrote those warning. No one paid any attention to them. I hate to say it, but you really don't know what you are talking about.
68.
by thejameskyle 11y ago
You should, TypeScript is great and you'll get what you want out of it.
69.
by thejameskyle 11y ago
It's extremely dangerous, we're talking about tens of thousands of developers who have chosen to depend on Babel for their livelihood, we can't just keep breaking things on them. We don't want Babel's configuration
70.
by thejameskyle 11y ago
Making it "work out of the box" is something we had before, and we watched as proposals changed and we blew through 5 major releases in like 6 months getting more and more complicated as we went. On top of that it was only going t
71.
by thejameskyle 11y ago
It's not that the users should be protected from themselves, but that they should be protected from instability. Proposals are constantly changing, and keeping a monolithic Babel on track with them without breaking things for users all
72.
Spectacle CodeSlide: Present code with style(thejameskyle.com)
5 points by thejameskyle 11y ago|0 comments
73.
by thejameskyle 11y ago
+1
74.
by thejameskyle 11y ago
People are split between: - GitLab - Phabricator - GitHub + Phabricator Maniphest (or alternative)
75.
by thejameskyle 11y ago
Some of the responses here are kinda obnoxious. I helped kickstart the original letter and I'm very happy about this response. GitHub more than anything has been a blackbox, and this was a very notable first step towards opening up. It
76.
by thejameskyle 11y ago
I'm one of the co-authors of the Dear GitHub letter. This is the type of response I want so badly from GitHub (but wasn't expecting). GitLab still has a ways to go in terms of performance/reliability and polishing their produ
77.
Babel Plugin Handbook(github.com)
4 points by thejameskyle 11y ago|0 comments
78.
by thejameskyle 11y ago
I'm done responding to you since you've chosen to be a dick throughout this thread rather than have a productive conversation. If literally anyone else wants to chat, feel free to ping me on other channels.
79.
by thejameskyle 11y ago
You must really enjoy going through threads to say the same negative thing over and over. This is exactly why I can't stand Hacker News.
80.
by thejameskyle 11y ago
Well modular and re-usable internals is exactly what we mean by "platform"
81.
by thejameskyle 11y ago
You're cool, thanks for the productive input.
82.
by thejameskyle 11y ago
There's a pretty lengthy discussion about it here https://github.com/babel/babel/issues/2168 I may do a followup blog post about it.
83.
by thejameskyle 11y ago
Babel already had to build all of the things to do this, we're just exposing them to the world. I can only see this improving things as people start using what was Babel internals directly and reporting issues on them as they are disco
84.
by thejameskyle 11y ago
That's concerning, this is what I'm seeing on my system: babel 5: 0.47s user 0.06s system 101% cpu 0.519 total babel 6: 0.47s user 0.06s system 102% cpu 0.508 total Want to hop in our Slack channel? http://
85.
by thejameskyle 11y ago
Meh, that's becoming less and less true. We're definitely never going to do that again.
86.
by thejameskyle 11y ago
The positives outweigh the 37 extra keystrokes you have to make to do the exact same thing as before.
87.
by thejameskyle 11y ago
Stop thinking about Babel as an ES* to ES5 transpiler. That's just one of the things Babel can do. http://babeljs.io/blog/2015/02/15/not-born-to-die/
88.
by thejameskyle 11y ago
Keep reading the blog post, we introduced presets for this very reason. It not hard to setup at all.
89.
by thejameskyle 11y ago
Likely a separate tool using Babel modules. Flow is more likely at this point. TypeScript syntax might be in the future too. There hasn't been a whole lot of desire for it yet.
90.
by thejameskyle 11y ago
Using various Babel modules? Likely. Using Babel plugins? No, it wouldn't be a good way of building a tool like that. Take a look at Rollup.

More ›