vidugavia

5 ms·

1.
by vidugavia 3mo ago
I think what Hanami had to bring to the table is already on the table for years - slice architecture, repository pattern, true view layer, explicit dependency management and perhaps one that it recent - first class operations support. This
2.
by vidugavia 11mo ago
The phrase has been weaponized in the past many times. Some figures in the community are almost as far from "nice" as possible, but you're not allowed to call that out, because "it's not nice".
3.
by vidugavia 1y ago
He is employee of Shopify, which is a side in all this. I would take these conspiracy theories with a grain of salt at least.
4.
by vidugavia 2y ago
99% coverage does not mean you have good tests. Yes, I have experienced that good tests, combined with a good understanding which parts are critical and which are not, create a great comfort about introducing changes, whether it's Frid
5.
by vidugavia 6y ago
Is the lack of incremental compilation aproblem with dub or with D compiler in general?
6.
by vidugavia 6y ago
12k is not a large number of records though
7.
by vidugavia 6y ago
What should they have chosen then? I think there wasn't much to choose from back then: either C or Lisp (or maybe Erlang).
8.
by vidugavia 6y ago
In my books the difference lies in how the HTML is generated. In case of static sites you generate it only when you rebuild the site after changes. In dynamic sites you build it dynamically on each request. Sure, you can cache the hell out
9.
by vidugavia 6y ago
RSS, pagination, categories, tagging, responsive images, ToCs - all these things work just perfectly in static sites.
10.
Luneta – an interactive filter that can be easily composed within any script(github.com)
2 points by vidugavia 6y ago|0 comments
11.
by vidugavia 6y ago
Not JavaScript or Go, that's do sure...
12.
by vidugavia 6y ago
Ruby is super backwards-compatible with new versions. Even to much. The core team almost made religion from it. So I don't really understand what the problem is - aside from using not maintained library. It will work, unless it was wri
13.
by vidugavia 6y ago
Ok, that is good to know. However from my mere-user perspective it does not look so good. With Hanami 1.3 release it was announced that Hanami 1.x line won't get anything past bugfixes and security fixes, so it basically won't be
14.
by vidugavia 6y ago
How is it "around the corner"? While having been enthusiastic about Hanami since Lotus times, I cannot help the feeling that it's more or less completely stalled at the moment. Sure, the non-functional alpha of Hanami 2.0 has
15.
by vidugavia 6y ago
Cool. I fell in love with Janet during last advent of code, so I'll definitely give it a try
16.
by vidugavia 6y ago
It still kills tools like Twine in browser though: https://www.reddit.com/r/twinegames/comments/fp1ro2/ios_user...
17.
by vidugavia 7y ago
Chapbook looks nice, but even after first glance I see a lot of things potentially missing, such as possibility to redirect to "death passage" from each passage if health drops below zero. Maybe it will be developed in that direct
18.
by vidugavia 7y ago
> Only basic features are provided: branching and image support So, if I understand correctly, there is no way to have side-effects (such as health loss) in GSE?
19.
by vidugavia 7y ago
Of course https://ranger.github.io/