Gajus Kuizinas
medium.com/@gajus · Personal blog · on HN since 2016
Gajus Kuizinas is a JavaScript and Node.js developer who writes about PostgreSQL, parsing, React, and CSS-in-JS.
What HN saysHN commenters link his posts on Earley parsing, scaling PostgreSQL, and CSS-in-JS, and he joins discussions on ORMs and his Slonik library.
16HN people shared it
5linked it in comments
43stories submitted
541story points
6 years agolast shared
2016people per year2026
Most-shared posts
- 1Parsing absolutely anything in JavaScript using Earley algorithm3 people · 14 points · first shared 2017 · discussion on HN
- 2Using SQL query builder is an anti-pattern3 people · 3 points · first shared 2019 · discussion on HN
- 3Lessons learned scaling a PostgreSQL database to 1.2bn records/month2 people · 262 points · first shared 2019 · 73 comments on HN
- 4Processing large volumes of data safely and fast using Node.js and PostgreSQL2 people · 12 points · first shared 2019 · discussion on HN
- 5Do not protect your website from scraping (part 1, technology barriers)2 people · 6 points · first shared 2018 · 2 comments on HN
- 6The biggest UX mistake in e-commerce: discount code input on the checkout page2 people · 4 points · first shared 2017 · discussion on HN
- 7Stop using CSS in JavaScript for web development2 people · 3 points · first shared 2017 · 1 comments on HN
- 8Using React v16 to create self-destructing components2 people · 2 points · first shared 2017 · 1 comments on HN
- 9Pre-loading: cache When cache is slower than one query2 people · 2 points · first shared 2019 · 1 comments on HN
- 10A Kubernetes/GKE mistake that cost me thousands of dollars1 people · 155 points · first shared 2019 · 111 comments on HN
- 11Stack Overflow is leaking user emails (unsafe use of MD5 hashes)1 people · 15 points · first shared 2020 · discussion on HN
- 12Reducing CSS bundle size 70% (short class names and scope isolation)1 people · 9 points · first shared 2017 · 2 comments on HN
- 13Distributing a self-replicating malicious code using NPM1 people · 8 points · first shared 2017 · 1 comments on HN
- 14Distributing a self-replicating malicious code using NPM1 people · 5 points · first shared 2017 · discussion on HN
- 15The wheels of open-source (we’ve got many of them)1 people · 4 points · first shared 2017 · 1 comments on HN
What HN people wrote when they linked it
kasbah · 2018-08-11
Hey folks, I created this to augment the Octopart API while working on bill of materials tools for https://kitspace.org.
Working with Nearley was a fun experience and I recommend the blog post that got me started with it to anyone who is interested in writing a parser in JS: https://medium.com/@gajus/parsing-absolutely-anything-in-javascript-us…
We have started porting it to Antlr to make it language agnostic though we are still open to looking at other options as well. Does anyone have any good experience or some ideas for alternative approaches?
hn_throwaway_99 · 2021-04-20
We are not using an ORM. I am a pretty strong advocate against ORMs, but that is a topic for a different discussion. We have a set of DAO components that access the DB using Slonik, https://github.com/gajus/slonik (overview explaining the rationale for this library is at https://medium.com/@gajus/bf410349856c ).
Our app doesn't have a huge need for caching, but we use a mix of in-server-memory caching ( https://github.com/isaacs/node-lru-cache ) and Redis when we need a global cache.
Gigacore · 2018-01-04
Haha! I saw this coming. There's still a lot of developers who don't like the idea of css-in-js. It is a bigger topic to debate on. I have personally tried styled-components and I like the way it works.
https://medium.com/@gajus/stop-using-css-in-javascript-for-web-develop…
https://css-tricks.com/the-debate-around-do-we-even-need-css-anymore/
acemarke · 2017-11-28
Several people had already noted [0] that you could implement equivalent behavior by using a component that simply returns its own children:
const Fragment = ({children}) => children;
// later
return <Fragment><Component1 /><Component2 /></Fragment>;
Nice to see this added as both a built-in component type and a useful syntax extension. (Now if they'd just modify JSX syntax so that we can pass props by matching local variable names similar to how ES6 object literals work, like `<SomeComponent a b c />`, rather than having that become a defaulted-true boolean, I'd be happy :) )
[0] https://medium.com/@gajus/using-react-v16-to-create-self-destructing-c…
gajus · 2017-07-29
Its my weekend project. I have written an accompanying post explaining how I got the data. https://medium.com/@gajus/filming-sites-of-the-imdb-top-1000-movies-f8…