morrvs

5 ms·

1.
Designing Together(morrisbrodersen.de)
2 points by morrvs 1y ago|0 comments
2.
by morrvs 2y ago
There is https://github.com/kofrasa/mingo for in-memory objects
3.
by morrvs 2y ago
> main.ts file contains multiple small functions It's purely demo code. I personally subscribe to the "modules should be deep" school of thought (Ousterhout). > tests test the same thing twice: once with a unit test, an
4.
by morrvs 2y ago
I also use Vite professionally on a daily basis. FWIW Vite would indeed handle the responsibilities of sass, typescript (partly), s4d, terser, cbst, vendoring (but not eslint, stylelint, prettier, playwright, c8, exdom). It's certainly
5.
by morrvs 2y ago
Fantastic comment, I'll take these to the drawing board... thank you so much for taking the time!
6.
by morrvs 2y ago
I like to look at it as a spectrum from "truly vanilla" to "same old bloated". I've previously looked at the dogmatic vanilla approach here [0] and wanted to try something else this time, on a different location on
7.
by morrvs 2y ago
In all honesty, I've never got to properly look into Vue, but it has been mentioned multiple times in the comments. Time to study it I guess :) The "src/js" directory was initially called "src/scripts" but
8.
by morrvs 2y ago
Did not know this one, will study for sure. Thanks!
9.
by morrvs 2y ago
Not sure who said it but I was aiming for the "Simple Ain't Easy" trope here ;) I agree that the JS build scene can be churning a lot as well (e.g. ESLint's recent config changes), that's why I tried to make everyth
10.
by morrvs 2y ago
Now that's a cool accident... thanks for sharing :)
11.
by morrvs 2y ago
I was pondering if "vanilla" should be part of the name as well. In the end I felt I got sufficiently close to the vanilla flavor you describe, and the name conveys the "as little as possible" approach. Hope it's no
12.
by morrvs 2y ago
Original author here, thanks for the comment! I also think that backend would be an interesting subject to try and reduce, if only to not constantly wade through 100s of Dependabot pull requests... It's a very different scenario where
13.
by morrvs 2y ago
I find "web platform poorly designed, therefore frameworks with 100s of dependencies" a bit too easy, especially when the user experience suffers in the end. I also believe that not every complexity needs to be solved with code. I
14.
by morrvs 2y ago
Original author here. No, you don't need all of it; everything is optional (as stated in the article). It's just a boilerplate with some tools and conventions, so "using it" has little implications, I think. Other than t
15.
by morrvs 3y ago
Thanks for this, gives my intuition some words to back it up! I find especially compelling how the author separates concrete problems like reconciliation (hard to argue against) from the abstract principle of "everything should be a co
16.
by morrvs 3y ago
Original author here, thanks for sharing! The case study has been discussed back in 2020 [1] but there have been quite a few updates (ES2020, local dev, testing, etc.) since then. Happy to chat! [1] https://news.ycombinator.com&#
17.
Show HN: MongoMQ2, message/event queuing with MongoDB only(github.com)
1 points by morrvs 3y ago|0 comments
18.
by morrvs 3y ago
> The point is requirements change, features are added, and when an abstraction becomes wrong, tear it out. I like this phrasing a lot, thanks for this! I'm still wondering if there's also potential in avoiding the wrong abst
19.
Show HN: E7 Estimation Framework(morris.github.io)
2 points by morrvs 4y ago|0 comments
20.
by morrvs 4y ago
Did some research on this a while ago and I‘d wager that 5x in LOC & growth is a bit off: https://github.com/morris/vanilla-todo - probably it’s more around 1.5x (which can still be problematic). Would be interesti
21.
by morrvs 6y ago
Not sure about the interruption handling, maybe I need to do more research there. But totally agree with the last parts - currently, typical SPA implementations are often misguided and create more problems than they solve (if any) compared
22.
by morrvs 6y ago
I've heard the Assembly vs. C analogy a couple times now, and find it hard to apply: Assembly languages come in many flavors whereas C is a single, standard abstraction over these. DOM is a single, standard API whereas frameworks/
23.
by morrvs 6y ago
True, we should respect all the resources of a device, at best. Also true for desktop (Slack's memory usage comes to mind). A major result of the study is greatly reduced bandwidth (and consequently, shorter parse time) compared to the
24.
by morrvs 6y ago
For what it's worth, the study was not targeting SPAs specifically. The patterns I found can very well be used to add some minimal behaviour to some HTML generated completely on the server side. I'm by no means advocating SPAs or
25.
by morrvs 6y ago
Thanks to everyone who took the time to read it, and thank you all so much for all the feedback! I'm quite overwhelmed by the response :) looking to address as much of the feedback as possible by the end of the week. A major weakness s
26.
by morrvs 6y ago
It does not have to be. However, animations greatly contribute to UX, and are an interesting cross-cutting concern to implement (with any tech). Remember that 44K is unminified, unoptimized, with considerable duplication, and includes HTM
27.
by morrvs 6y ago
I'm not an expert but I'm certain we aren't even close to providing this level of connectivity. Throttled data, sucky hotel wi-fi, underground tunnels, bad service in rural areas of e.g. Germany etc. are real, unfortunately.
28.
by morrvs 6y ago
You bring up an interesting point. I intentionally used "may" in that statement as using .innerHTML can be both effective and performant enough (and a lot simpler). A couple possible problems off the top of my head: 1. CSS transit
29.
by morrvs 6y ago
No, I'd consider them a standard and a candidate for implementing the case study. When I started the study I was thrown off by this: https://caniuse.com/?search=components - and very huge polyfills. In hindsight I&#x27
30.
by morrvs 6y ago
I've tried but I (surprisingly) found the string array to be the most readable way to do it without helpers. It's also easily replaced by ES6 templates when upgrading.

More ›