morrvs

8 ms·

31.
by morrvs 6y ago
Many thanks :) like the concept of your site, I will take a look some time
32.
by morrvs 6y ago
Glad you liked it and could follow through!
33.
by morrvs 6y ago
Thanks, although I wouldn't claim it to be "proof" :) and yeah, the choice of ES5 vs. ES6 seems to be a major weakness of the study as others here have said as well. In any case I believe switching the current product to ES6
34.
by morrvs 6y ago
Completely agree. In hindsight the choice of ES5 is questionable and in the study I actually conclude that another ES6-based experiment is desirable. Also, as others here have noted, you could start with ES6, see if it works for enough of y
35.
by morrvs 6y ago
Sorry :D nothing wrong with server-rendered HTML and forms for many use cases. Unfortunately, by the limits of connectivity, if you want to build something that is interactive, data-driven, and responsive at the same time you will always b
36.
by morrvs 6y ago
Performant drag & drop + FLIP animations were not trivial to implement (naive approaches like re-render fully on each mousemove fail spectacularly). I needed to see FPS on a couple different devices so I added the counter. Also, since I
37.
by morrvs 6y ago
Totally agree. I should update the study to express praise for the original TeuxDeux, it's conceptually the best to-do app out there in my opinion.
38.
by morrvs 6y ago
Thank you very much, looking forward to your feedback! And yes, this is exactly what I wanted to achieve :)
39.
by morrvs 6y ago
It does start from scratch but it (re-)invents a whole lot of general-purpose code, in effect making up a framework/library, which was an explicit non-goal for the case study (because there are good ones already).
40.
by morrvs 6y ago
Would you mind creating an issue with some details (browser and version, maybe how to reproduce)? Thanks :)!
41.
by morrvs 6y ago
Sorry, I didn't mean to make a difference between frameworks and libraries in this case; both would violate the method/goal of the case study which was finding vanilla patterns that are not dependant on general-purpose code.
42.
by morrvs 6y ago
Thank you very much! This is quite exactly what I'm trying to achieve. Very happy that you like it :)
43.
by morrvs 6y ago
Original author here - thanks! Yes, ES5 is a huge pain. However, I believe 5% of users (see other comment) are not a joke for many apps. There's always the question of minimum critical APIs required: If you build a 3D or webcam app you
44.
by morrvs 6y ago
:D just to be clear, the rules were made just for the case study. I'd never recommend following these rules in a professional project. They are part of the method of the case study, not its outcome; the outcome is a couple of (hopefull
45.
by morrvs 6y ago
Thanks for reading - original author here. For the precise quote you mentioned I came up with somewhat format rules which prevented building a framework (code-wise) for this case study. The "caveat" you mention is just an explanat
46.
by morrvs 6y ago
Original author here. During the study, I explicitly forbid myself from writing general-purpose helpers which would make up a framework. Would you mind elaborating what in your view makes up the "custom framework"? Thanks!
47.
A case study on viable techniques for vanilla web development(github.com)
2 points by morrvs 6y ago|0 comments
48.
How to replace Webpack with (almost) only TypeScript(medium.com)
1 points by morrvs 6y ago|1 comments
49.
Show HN: A tiny, static AMD API implementation(github.com)
2 points by morrvs 6y ago|0 comments