Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mattdesl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
56 ms
·
691.
▲
by
mattdesl
12y ago
I'd be curious to see how a medium to large project (500+ files) works with this approach? I'm guessing it would take a while to load the page since the browser has to request each script? The tool looks pretty good. I think the m
692.
▲
by
mattdesl
12y ago
You still need to maintain build scripts for production, though. p.s. For prototyping like in the vid, you can use tools like beefy or wzrd to avoid setting up any browserify build step. :)
693.
▲
by
mattdesl
12y ago
A more common scenario is non-editable 3D text for UI, HUD, infographics, etc. The core glyph layout, word wrapping and rendering is all the same, just without interaction.
694.
▲
by
mattdesl
12y ago
I would be curious to see what kind of tool could do this. It sounds like "tree shaking" (like dead code removal) which may be possible in the far future with ES6 imports. I imagine it would further add to build times. Not sure ho
695.
▲
by
mattdesl
12y ago
There are a lot of reasons to break modules into really tiny pieces, even if they are only a dozen lines or less. Some benefits: - a terse and frozen API (like "domready" and "xtend") does not end up with the scope creep
696.
▲
by
mattdesl
12y ago
A better approach is to re-use arrays instead of creating intermediate ones, which is what gl-matrix[1] advocates. Each tween might still need its own matrix instance for start and end points, but at least these are not created per tick. A
697.
▲
by
mattdesl
12y ago
I don't think it's reason to turn somebody down, but it can be fairly annoying using a library that doesn't follow standard naming conventions. If your code brings together four different libraries and they all use drasticall
698.
▲
by
mattdesl
12y ago
Competition is healthy. :) https://www.npmjs.com/package/tweenr Besides, different authors will tackle the problem a little differently.
699.
▲
by
mattdesl
12y ago
JS animations are inherently very fast, most likely because you're running a modern browser. :) The code is basically just computing a 4x4 matrix for each card per frame built up from some tweened position/rotation/etc. Then
700.
▲
by
mattdesl
12y ago
Nice library. The current implementation leads to a lot of garbage since you are allocating several typed arrays per tick for each tween. Also looks like gimbal lock and Euler interpolation could be a problem for some 3D rotations. I guess
701.
▲
by
mattdesl
12y ago
An awful lot of top down 2D tile based games.
702.
▲
by
mattdesl
12y ago
Yup, education could definitely improve. Something else I would really like to see added to curriculums is a focus on npm and modularity. Even just the basics like semver, common unit testing practices, etc.
703.
▲
by
mattdesl
12y ago
Great post! I'm also really curious about the future of Dev Tools and hope to see it applied to other uses. I think there is a range of tools we could be building on top of or around Chromium/DevTools/etc to provide real-time
704.
▲
by
mattdesl
12y ago
Well, there is a reason: consistency. ;) I hate seeing "==" in code because it's rarely clear whether the programmer intends it to coerce or just didn't bother with the third keystroke. So "===" is just enforce
705.
▲
by
mattdesl
12y ago
Re-posting what I said in r/javascript. I'm digging the modularity. My only complaint would be that some of those modules do not really need to be "turf" specific. For example, "turf-is-clockwise" would be more
706.
▲
by
mattdesl
12y ago
Tools like atom-shell and thrust[1] may not integrate into the OS as smoothly as Qt/etc but they do show a lot of promise for web tooling. e.g. shader authoring tools, motion/animation editors, WebAudio API editors, etc. Summed up
707.
▲
Motion Graphics for the Web
(mattdesl.svbtle.com)
2 points
by
mattdesl
12y ago
|
0 comments
708.
▲
Show HN: Impressionist Style Post Processing in WebGL
(mattdesl.github.io)
4 points
by
mattdesl
12y ago
|
0 comments
709.
▲
by
mattdesl
12y ago
Curious why the Mario demo is running at ~24FPS, and jumps to 45FPS when the keyboard is active. Is it throttling frames on purpose? Why can't it hit 60FPS for such a simple demo? It doesn't inspire much confidence for a language
710.
▲
by
mattdesl
12y ago
It would be cool to combine this with the Requirebin.com backend so the GLSL code could use glslify, and the GL code could use stackgl (or some other family of modules) rather than just an in-house GL abstraction.
711.
▲
Various Front End / Creative JavaScript Modules
(gist.github.com)
2 points
by
mattdesl
12y ago
|
0 comments
712.
▲
Show HN: JavaScript 2D/3D Verlet physics module
(npmjs.org)
8 points
by
mattdesl
12y ago
|
0 comments
713.
▲
by
mattdesl
12y ago
Yeah, and you also have to use Google's ugly name spacing and global scope pollution instead of modern (sane) module approaches like CommonJS. Following an old-school technique just because you might see it in some legacy code doesn&
714.
▲
by
mattdesl
12y ago
Performance isn't really a big concern unless you're creating several hundreds of thousands of new objects per second. And I would question why you need to do that in the first place...
715.
▲
by
mattdesl
12y ago
Name your factory "createFoo", problem solved. :)
716.
▲
by
mattdesl
12y ago
The issue has very little to do with forgetting "new" and more to do with hiding implementation details and improving module composability.
717.
▲
by
mattdesl
12y ago
Works fine with npm "inherits" module. Not that you should be using instanceof anyways...
718.
▲
by
mattdesl
12y ago
I wouldn't say constructors are the problem -- the problem is with the "new" keyword. I tend to use constructors like this: https://github.com/mattdesl/module-best-practices/blob/maste... W
719.
▲
JavaScript modules: best practices
(github.com)
2 points
by
mattdesl
12y ago
|
0 comments
720.
▲
by
mattdesl
12y ago
This looks great. I've also been exploring path rendering and timeline playback in the browser, see here: http://mattdesl.github.io/path-illustrator/demo/advanced.htm... (path rendering) https://gi
More ›