> The query language is deliberately less expressive than jq's. jsongrep is a search tool, not a transformation tool-- it finds values but doesn't compute new ones. There are no filters, no arithmetic, no string interpolation.
Mind me asking what sorts of TB json files you work with? Seems excessively immense.
Command-line Tools can be 235x Faster than your Hadoop Cluster (2014)
Conclusion: Hopefully this has illustrated some points about using and abusing tools like Hadoop for data processing tasks that can better be accomplished on a single machine with simple shell commands and tools.
JQ is very convenient, even if your files are more than 100GB.
I often need to extract one field from huge JSON line files, I just pipe jq to it to get results. It's slower, but implementing proper data processing will take more time.
The study is nearly 30 years old... How does this carry any relevance to today?
Moreover, it doesn't pass the sniff test. It's entirely possible that rich men are lonely too, but I have to figure that groups like incels etc are overrepresented by poorer men.
I was just lamenting the other day about the size of video.js, which is used in my legacy web app, and looking for a way to improve that. Very keen to explore how we could migrate to v10!
My first thought is "good riddance". Not only were the benchmarks surely gamed by many frameworks, but it was my impression that the benchmarks didn't even really reflect any real world application - which have plenty of i/o and compute. Moreover, ain't nobody receiving 1000 (let alone 100k) rps.
I quickly came to realize this when I came across similar projects 8 years ago. Moreover, the vast majority of the info is just irrelevant/useless clutter in such contexts. Worse, it's largely in English, so not useful to people elsewhere.
You're mistaken. I'm an absolute version control slob. JJ allows me to continue like that yet also collaborate with others. It tracks literally everything so I can not only split, squash, and rebase things to wherever they need to be, but can also rollback/restore/recover anything from either the repo-wide oplog or revision-specific evolog
You really ought to dive in deeper. jjui makes it all vastly simpler
> Open source culture celebrates intensity. It celebrates the all-night hack session, the prolific contributor, the person who maintains fifty projects and keynotes ten conferences a year. What it doesn't celebrate, what it actively looks away from, is what that intensity does to people who are wired differently. And a lot of us are wired differently. That's why we're here in the first place.
I gratefully use and meagerly contribute to open source regularly, and I marvel at a few particularly prolific mainteners. But at no point have I ever celebrated "intensity".
I defintiely see what OP describes, but is that "Open Source", or just some subset of people who happen to work/participate in open source? Likewise, surely this same mindset is even more prevalent in closed-source - especially in startups, hustle culture etc...
So, to the extent that a lifestyle and perspective as the article describes is unhealthy, I don't think it really has anything to do with open source and is really just one of many common manifestations of someone who is ill-prepared for life.
I'm glad the author has now found perspective, balance and a healthier, seemingly more fulfilling, life. I hope they continue to thrive, and that this article helps people - open source or not - to recalibrate and ultimately find the same.
Face would be an absolutely awful name. Though, interestingly, that's what people in (at least some) Latin American countries (inexplicably) call Facebook.
Why would Face be an awful name? To me it feels similar to “Apple”, which might also sound like a stupid name for a computer company if it wasn’t established already.
> The query language is deliberately less expressive than jq's. jsongrep is a search tool, not a transformation tool-- it finds values but doesn't compute new ones. There are no filters, no arithmetic, no string interpolation.
Mind me asking what sorts of TB json files you work with? Seems excessively immense.
reply