Not sure what KOReader is but the fonts included in this one and the overall reading experience is solid.
1,001 karma · joined April 24, 2012
Not sure what KOReader is but the fonts included in this one and the overall reading experience is solid.
It is not the researchers' fault that some slop got posted here instead.
This is the relevant quote from the original article.
Do you have a source for this?
We need more art that pushes boundaries and remains controversial. Instead, we favor the type of artist who attracts the most attention through their personality, whether because of their looks or a manufactured edgy image, while producing mundane, lowest-common-denominator work. We must support contemporary artists who move us forward rather than remaining stuck in popularity contests or constant nostalgia.
Under the current system, it is almost inevitable that influencers use their status to promote gambling ads and NFTs, ruining the lives of their fans. We need to break this cycle of rewarding increasingly poor behavior while making it harder for independent artists to earn a living.
Has this situation changed?
I hope ChatGPT starts writing only short sentences.
Punchy one-liners.
One thought per line.
So marketers finally realize this does not work.
And stop sending me junk emails written like this.
Today people are much more reliant on real-time collaboration, polished cloud and mobile experiences. Fractionalized open source software has a harder time competing with this than file based boxed software workflows of the past.
I do not use it collaboratively. I use it to continuously ship smaller things while working on bigger pieces and I constantly move independent changes around to different “lanes” to ship frequently as parts of my work mature.
With Magit I used staging area and amended commits continuously. With GitButler I “assign” files or chunks by dragging them into lanes as I am happy with the changes, and when I have a logical unit I commit it. Having this multiple staging areas has been a great workflow improvement as well.
GitButler does this cool thing where you can work on multiple branches at the same time, applied to the same working directory. For example you can work on the css while an agent works on the admin panel on a separate branch. It would be cool to have this with a tool like FleetCode.
This is much cheaper to run on a server. For example: https://github.com/ozanmakes/scrapedown
- Remove curly braces from props and children
<MyComponent name="Joe" onClick=(() => canBeInParanthesis()) />
<div>userName</div>
<div>"Text contents"</div>
- Add punning (like how { age: age } becomes { age } in JS) const age = 40;
<MyComponent age />/
<MyComponent active=true /> // explicit boolean attributesSome other fun examples: https://gist.github.com/ozanmakes/0624e805a13d2cebedfc81ea84...
Once, a team at my old job wanted to try A/B testing for the first time. After some research, they picked a SaaS tool to make it quick. Simple, right? Just sign up and go.
Of course not. First they had to go through THE PROCUREMENT! (dun dun dun dun)
Those legends weren’t about to let us limp along on a humble pro plan. They wheeled, dealed, and months later emerged triumphant: a glorious three-year enterprise contract. SLAs! Volume discounts! The whole nine yards. The art of the deal baby!
Small snag: by the time the ink dried, the original team had moved on. New PM, new priorities. No one even generated an API key during the whole time we paid for this top-tier enterprise service.
Free versions are generous enough for daily use as well. For example for TablePlus "The free trial is limited to 2 opened tabs, 2 opened windows, 2 advanced filters (filters are not available on the free TablePlus Windows) at a time."
Recently I've been trying jujutsu[0]. As awesome as Magit is, it can't fix some warts of Git like how it does conflict management. But I hate having to do version control from CLI. Most of all, I miss doing a bunch of work, going to magit-status (or edamagit), staging lines or entire files and committing parts of my work separately (like, dependency updates in a separate commit before committing api changes).
I've tried VisualJJ[1] and GG[2] but I just can't find a nice workflow with jj coming from Magit. Splitting changes feel cumbersome. What is your commit workflow with jj coming from Magit?