Probably the difference is that extracting as many calories as possible from food was a guarantor of survival for the neanderthals whereas that's not so true with the level of calorie abundance we have in the western world, partly because of analogous fat refining processes we also use.

Yeah I like the sound of the functionality but I don't like the idea of it taking up menu bar space. Console utility would be good or even a gui that can be quickly launched through spotlight

> I don't like the idea of it taking up menu bar space

You know you can close it? :-)

I will 100% ADHD it left open and it will sit there making it more cluttered than it needs to be

You might like Ice: https://github.com/jordanbaird/Ice

Sadly Ice is no longer maintained, but the fork Thaw[1] is active:

https://github.com/stonerl/Thaw

No comparison with competitor models other than the previous granite version strongly implies that it does not compete well with other comparable models. At least this is the most reasonable assumption until data comes out to the contrary

Wow that's a lot of hollow words that are backed by precisely fuck all.

Yeah, honestly it feels like this came faster than I was expecting. I thought we'd see another few years of reeling in with too-good-to-be-true prices to really lock in dependency but it feels like most companies have kind of a lot of wiggle room to back out of this still

I'd say it looks pretty readable on android although I still wouldn't describe it as good. I wouldn't say I feel encouraged to squint. But possibly different antialiasing explains it.

Well they don't attract nearly as much investment in the current market, I think that might be the problem people really want to solve

The attention economics are bad more than anything else. LLM articles ask us to put more time into reading it than the LLM put into writing it. Actually committing time to production is the minimum bar which suggests something is worth our time in a world where so much is already vying for our attention.

If a truly amazing thing was released tomorrow that had massive utility you wouldn't care how long it took to create and would just use it.

I get the attention economy is messed up right now, but using it as a justification for being curmudgeonly or abandoning principles is lame.

Yeah but we're not talking about utility, we're talking about content and in this particular case content which basically just boils down to someone's slightly quirky taste in something.

I think utility is a big component of that. I think there's a reason we're discussing these types of things instead of just cat pictures and memes.

78% autistic, 16% German. My ancestry is Dutch which as someone who grew up in the UK feels about 16% German.

I think as a solo developer there's actually a good argument for increasing code density and coupling (things which in large multi developer projects are seen as spaghetti), as it can help you keep a lot of that code in mental and visual context at one time.

It loses flexibility and readability for others, but you don't usually have enough time to concern yourself with such flexibility if you're working on a project by yourself, and you're not concerned about onboarding other developers and having them understand your code. The upshot is then that as a single person "bad code" is often highly effective code, and "clean code" is expensive code that buys you a lot of stuff you don't need or want.

I say this as a boring enterprise developer who at work is highly concerned with appropriate abstractions etc. imo there's no universally good approach, what is optimal is context dependent. Although there are some core features of code like consistency and strong conventions which are fairly universally helpful, this represents a small fraction of best practices.

This is pretty anti-thetical to most good practices but the older and more experienced I get the more(13 years as a C# dev) I think copy & pasting sections of code is wayyyyyy more appropriate than extracting into a method/class/library or other forms of abstraction.

Everything starts out with good intentions when someone comes along and says “hey you could make that an abstraction” and I just clench my jaw because I’ve seen that happen so much and then that simple clean abstraction eventually ends up being a horrible 1000 line monster that barely anyone understands and no one wants to change.

I agree with everything except for it being anti-thetical to good practice. I have noticed a lot of experienced devs agree with that sentiment.

It has been a pretty common trend for the last few years of people breaking out of the “OOP style programming” and practices they were taught at university. I am not saying avoiding things like over abstraction is new, but I do think there is a newer generation of programmers who have been taught and warned about drawbacks from practices like that.

Similarly, my anecdotal experience tells me more newer game devs are aware of basic memory practices being better than overly complex OOP code. Think flat arrays and simple cache alignment over something abstract and over engineered

100% this. All the abstractions and OOP stuff make you end up with a codebase where half the code doesn’t actually DO anything in the product itself, it just connects to other code! It also becomes impossible to follow the flow of execution because it passes through dozens of files and layers of abstraction.

KISS is also good practice.