Viewing profile — thymanl23

The crux of the article: "The answer is simple, if not exactly satisfying: when enough of the population—possibly 60 or 80 percent of people—is resistant to COVID-19" But then in t…

Check out "The Problem with Promises in JavaScript" [0] for some gotchas with the design of js promises. [0] https://dev.to/craigmichaelmartin/the-problem-with-promises-...

Hooks are a reconception of state and effects within a declarative model. Rather than effects being tied to a component's mutable lifecycle, they are tied to the data. Rather than …

The issue I found with the raw SQL approach was receiving back flat results. I made PureORM[0] to do only and exactly that: map flat data to correctly nested business objects. It i…

Yeah, ORMs have grown to mean more than mapping relational data to objects. An example of "just" this mapping can be seen in PureORM[0]. [0]: https://github.com/craigmichaelmartin/…

The things I've found positive about ORMs are exactly that mapping of results to business objects. The things I've found "not worth it" are the query-building APIs baked into the o…

Or use a "pure orm" (mapping to plain business objects) without a query builder - thus writing native sql and receiving nicely structured objects from the results (eg https://githu…

> Fortunately, there are tools out there that solve the "mapping tables to objects" problem without trying to control all access to the database In javascript land there is PureORM…

The desire for the object mapping (to pure objects, not db-aware objects), while having an aversion to query building APIs led me to use https://github.com/craigmichaelmartin/pure-…

Hmm, yeah, but I think more than just not using a query building api, I prefer pure result objects. Even when dropping to SQL, the result objects are still database-aware objects. …

In an ORM, the returned objects from even raw SQL is still ORM objects (database-aware objects). I prefer keeping the business logic layer distinct from the data access layer, so I…

Wow, that sounds like a really neat approach!!

I've been using an ORM for years - and often still find myself frustrated trying to map the complexity and nuance of SQL to an ORM api. What is attractive to me about ORMs, though,…