I’m sure folks would be interested even in a blog post comparing just this process with different Anthropic models if that’s something you do and need a content idea. :)

In other words, just because more code can be produced quickly does not mean that it is cheap.

edit: I’m maybe hearing your point is that LLMs may change that POV but I think that is TBD.

Comments URL: https://news.ycombinator.com/item?id=43936072

Points: 5

# Comments: 0

In hindsight, the biggest issue I ran into switching keyboards was that I was too ambitious playing around with the key configuration. The configurability is a big draw but I took for granted that I had already built up years of natural tendency for certain things - which thumb I use for space, preferences for Ctrl/Alt/Command/Option, for Shift, etc.

The default for these keyboards probably don't 100% align with what you're used to, so you should directly map what you're doing currently over to the keymap of the keyboard and then you can fiddle with making it yours over time.

I will say that if you're not already a touch typer, then a split keyboard is not going to help and it will be more difficult to get used to.

edit: also, if anything, going columnar helped me actually consistently hit number keys!

Comments URL: https://news.ycombinator.com/item?id=41100226

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=40604030

Points: 30

# Comments: 9

Some major downsides to review after merge:

- cost of context switching (author has moved on to something else new, which now remains paused to "go back", so there's no agility benefit to just merging if it works)

- increases risk of unnecessary conflicts (how do you address someone merging something, you have feedback, then someone else merges after on top? A PR helps resolve code that's done vs could be improved because it forces a communication moment between the authors)

- tooling (a PR or diff is well supported. How are you discussing feedback when everyone can just merge on top without review? I am assuming there's no point to a PR if everyone can just merge)

- decreases shared learning and understanding (I might think the code follows our standards but there still may be feedback from my team that could help improve. Why put that in the main branch before such feedback? It seems like it would be hard to keep track.)

I can't imagine my team performing well under those circumstances and I think we have a very healthy code review / quality culture. If I'm not giving or receiving feedback - that sounds more like code slinging than thinking and humility, even for the most experienced architects I've worked with welcome feedback, so it's not a matter of trust.

That said, I find Fabriq to be more inline with what I (no affiliation) think about an app to help cultivate relationships: https://ourfabriq.com/fabriq

Comments URL: https://news.ycombinator.com/item?id=35473267

Points: 1

# Comments: 0

What's the value prop for a studio to run something on Linux vs Mac / Windows?

This is interesting to me to hear as the trope for Linux is that it's not used for audio/video work (and couldn't find much online about real world professional usage without pulling up reviews of best video editor / etc sort of results).

Also, congratulations on the release - rewrites are a huge undertaking.

That sounds convenient but leaves me wondering what particularly about that quality of life improvement changes how you view Windows.

Comments URL: https://news.ycombinator.com/item?id=33979100

Points: 24

# Comments: 1

I think the main question I see is - do multiple stores benefit the user?

I'm not sure of that answer but I think we can agree that multiple stores do NOT help the default app store, which in turn could be beneficial to the consumer (multiple stores that have to compete on pricing w/ deals, self publishers offering a cheaper price directly, etc. - think more like grocery stores selling the same stuff vs farmers market vs direct from farm).

I'm no economist but I think we could also agree that having at least a few options is generally A Good Thing.

edit: regardless, even in a world with multiple stores the point re: attack surface is a good one and one of your other comments regarding what users actually value like safety is an important one, which as a business are the things you need to weigh on to make a profit

You can connect whatever "collection of apps" source you desire but you're correct that you do get the "F-Droid List" out of the box.

It may feel odd to show no apps when initially using F-Droid but, in theory, one improvement may be to have the user explicitly choose a source list and maybe the "F-Droid List" is first in the list among others.

Going in that direction would also help expose that particular feature as I wasn't even aware that you could add / change sources for F-Droid, which sounds like if easy enough to add may be an easier avenue to self publish apps than the major app stores.

> This means F-Droid gives you selected apps by default without bans or censorship. When you install the F-Droid app, it automatically connects to the collection on f-droid.org that is maintained by this community. F-Droid also makes it easy for anyone to publish their own repository, with their own curation rules.

i.e., yes, you do get the "F-Droid List" by default, but you are welcome to connect to a different list or publish your own "list" of apps that has its own curation rules.

Imagine if you could view Apple or Google's app store with an "awesome app" list curated by a list of experts you follow without all the junk of suggested apps or ads. That would go in the direction of "meta-curation" akin to what /u/hinkley is referring to in a another comment [1].

[1]: https://news.ycombinator.com/item?id=33776244

Based on your profile, I presume you're talking about https://notado.app/?

Uncaught TypeError: GLctx is undefined

--

Firefox 105 on Linux 64-bit (ElementaryOS)