solnic

5 ms·

1.
by solnic 4y ago
Yes the view layer will be introduced in 2.1. We have hanami-view ready but we need to build hanami-assets and hanami-helpers + add integration code to the main hanami gem.
2.
by solnic 4y ago
Hanami is not a micro-framework, it is composed of multiple gems though, so if you remove them all you're left with a core of the framework that doesn't do anything except providing an API for plugging in components, configuring t
3.
by solnic 4y ago
Haha no it's just an example of a custom directory that you can place under app dir We're still thinking about an abstraction for operation-like objects (I actually started experimenting with this a couple of months ago) but I do
4.
by solnic 4y ago
You missed the context of this example - it's just there to show that IF you don't want to use constructor DI, you can put things in lib and they won't become part of the automatic DI system
5.
by solnic 4y ago
You're right in principle but not in this case. Zeitwerk is not a regular dependency, it's stable and the risk it will change in an incompatible way is very minimal (reminder - it's used by Rails too). When it comes to dry-rb
6.
by solnic 4y ago
What you're describing should've been reported as a bug because we do use metaprogramming for DSLs but the "runtime" objects are actually designed to have very minimalistic public API. I can assure you we do not put clea
7.
by solnic 4y ago
Hanami 2.0 doesn’t have any interactors
8.
Hanami 2.0: Better, Faster, Stronger(hanamirb.org)
6 points by solnic 4y ago|0 comments
9.
by solnic 5y ago
> Your articles are very negative. Basically everything involving Rails is bad and wrong by them. That's what i mean. I provide critique that some (probably many) Ruby developers don't like and disagree with but my intention is
10.
by solnic 5y ago
FYI I changed the title to "Rails and its Ruby dialect". Thanks for all the comments. https://solnic.codes/2022/02/02/rails-and-its-ruby-dialect/
11.
by solnic 5y ago
welp :( I'm very sorry about this. I didn't manage to pay for my old domain because I was recovering after an accident (true story, not making any silly excuses). I was aware that it's about to expire but wasn't in a g
12.
by solnic 5y ago
Ah thanks man, I'm very happy to know this. ROM 6.0 is going to be a major improvement Stay tuned!
13.
by solnic 5y ago
What makes you think I have negative agendas? My "agenda" is quite positive, I want a Ruby ecosystem where we play by the same rules and Rails is no longer a special snowflake. This way we can evolve faster.
14.
GitHub Sponsorship and Thoughts on Open Source Work(solnic.codes)
2 points by solnic 7y ago|0 comments
15.
by solnic 9y ago
s/Ruby/Rails/g in the article and it makes more sense. You can write pretty good Ruby code, which avoids side-effects, monkey-patches and is easy to test. All you need to do is abandon Rails. There are many modern Ruby projec
16.
by solnic 10y ago
> Is your time with rails "up" in the sense that you no longer have a substantial day to day use for it It means that I'm no longer interested in supporting Rails in my gems and I accept the fact it may hurt adoption of th
17.
by solnic 10y ago
Hey Sam, great to see you commenting on this :) I started contributing to DM when Dan was already in charge but I was a DM user when you were still working on it. Anyhow, you made really good points here. I've worked on ORMs for a coup
18.
by solnic 10y ago
That's not true, although there's a lot I took from FP. Like avoiding mutable state, and functional composition for data transformations. This doesn't change the fact my code is OO - I use objects, composition, decoration, de
19.
by solnic 10y ago
I dare to disagree. My point about DM being killed by Merb/Rails merge was about what happened back in 2008 with its consequences through all the years. I'm talking about DM1 specifically, if Merb survived and DM could grow with i
20.
by solnic 10y ago
`include` is also inheritance, multiple inheritance. I try to avoid inheritance and prefer composition. It is very simple in ruby and very powerful.
21.
by solnic 10y ago
yeah it's because I was contributing to many dm-* projects and handling a couple of last releases.
22.
by solnic 10y ago
Yes, I was on the core team between 2010-20#{hard-to-tell}. DataMapper was created by Sam Smoot and quickly taken over by Dan Kubb who did a crazy amount of work, practically rewriting it and introducing all the crucial features, and then m
23.
by solnic 10y ago
Thank you my friend, I just fixed it <3
24.
by solnic 10y ago
Sorry about that, you can use Reader View in FF which works fine. Crazy part - it's not JS, I tried disabling it and it's still sluggish.
25.
by solnic 10y ago
The point I made is that this is all happening in your ORM layer, in ActiveRecord these concerns are not separated. Recent addition of Attributes API at least isolated coercion logic, but it's still part of the ORM, which for me is a m
26.
by solnic 11y ago
It's not feasible to have validations centralized. You don't validate objects, you validate data that your system received from somewhere. How it's done depends on the type of this external system, the format and sometimes th
27.
by solnic 11y ago
I stopped using statefull objects that make decisions based on their state, in general, validations aside. I don't "delete objects", I make changes in the database instead. When it's a complex operation that requires mak
28.
by solnic 11y ago
I should mention that dry-data will replace virtus in reform, as it's a) faster b) simpler c) more flexible :)
29.
by solnic 11y ago
This is exactly what I'm trying to solve with both dry-validation and dry-data. I wouldn't agree with the low probability of logic errors in AR validations though. I think a DSL with lots of options is a recipe for logic errors. T
30.
by solnic 11y ago
You'd get these runtime exceptions anyway, but they would be obscure and often hard to debug. Once you define core objects in your system that you construct from external sources (like a database) you establish a contract that the sour

More ›