thymanl23

8 ms·

1.
The machine learning Example you've been looking for(dev.to)
3 points by thymanl23 6y ago|0 comments
2.
by thymanl23 6y ago
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 the next paragraph nonchalantly says "though w
3.
Show HN: A 12 line library for writing readable code with `await`(github.com)
6 points by thymanl23 7y ago|1 comments
4.
by thymanl23 7y ago
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-...
5.
by thymanl23 7y ago
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 state being tied to a mutable instance, it is declarati
6.
React made the DOM declarative; Hooks make React declarative(dev.to)
3 points by thymanl23 7y ago|1 comments
7.
by thymanl23 7y ago
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 is called "pure-orm" both because it is _purely_ an
8.
Marketplaces, Platforms, and Services(medium.com)
2 points by thymanl23 7y ago|0 comments
9.
React made updating the DOM declarative; Hooks made components declarative(dev.to)
1 points by thymanl23 7y ago|0 comments
10.
by thymanl23 7y ago
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/pure-orm
11.
by thymanl23 7y ago
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 objects. These principles can be seen in
12.
Show HN: A better way to `await` in JavaScript(github.com)
2 points by thymanl23 7y ago|0 comments
13.
A better way to `await` in JavaScript(dev.to)
1 points by thymanl23 7y ago|0 comments
14.
A better way to `await` in JavaScript(dev.to)
4 points by thymanl23 7y ago|1 comments
15.
Three Problems with Promises in JavaScript(dev.to)
1 points by thymanl23 7y ago|0 comments
16.
Show HN: A Pure ORM for Node(github.com)
2 points by thymanl23 7y ago|0 comments
17.
by thymanl23 7y ago
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://github.com/craigmichaelmartin/pure
18.
by thymanl23 7y ago
> 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 which seeks this balance ( https://g
19.
by thymanl23 7y ago
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-orm - where native, unobstructed SQL i
20.
by thymanl23 7y ago
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. I prefer distinct layers between the business domain layer a
21.
by thymanl23 7y ago
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 prefer for the return objects to be pure business objects.
22.
by thymanl23 7y ago
Wow, that sounds like a really neat approach!!
23.
Ask HN: Is it reasonable to choose direct SQL over an ORM
7 points by thymanl23 7y ago|9 comments