n42

I mean, I get it, but there's nothing unique to millennials about your role model generation dying off

I found this post on reddit

https://www.reddit.com/r/HelixEditor/comments/1wpt22a/mitos_...

  It is not an invasion of privacy

this rubbed me the wrong way.

absolutely no one but me gets to decide what is an invasion of my privacy.

iPhone 18 Pro: 2.83 inches wide

iPhone 18 Pro Max: 3.07 inches wide

iPhone Duo: 3.31 inches wide

my issue with phone sizes has never been their height, and has always been about resting in my palm.

https://www.apple.com/iphone/compare/

I am really quite disappointed this was not taken as an opportunity to make the default form factor smaller. Instead it seems like the folded mode is larger than a pro max, which is insane. I guess I'll just continue with the normal phones.

It seems they are segmenting the market on creator vs consumer between the pro and the duo, and betting the consumers want this form factor.

The combination of static safety gracefully degrading to runtime safety where not provable is interesting to me

I looked it up:

  The line separating investment and speculation, which is never bright and clear, becomes blurred still further when most market participants have recently enjoyed triumphs. Nothing sedates rationality like large doses of effortless money. After a heady experience of that kind, normally sensible people drift into behavior akin to that of Cinderella at the ball. They know that overstaying the festivities — that is, continuing to speculate in companies that have gigantic valuations relative to the cash they are likely to generate in the future — will eventually bring on pumpkins and mice. But they nevertheless hate to miss a single minute of what is one helluva party. Therefore, the giddy participants all plan to leave just seconds before midnight. There’s a problem, though: They are dancing in a room in which the clocks have no hands.

you do not sacrifice memory safety. you sacrifice a compiler ensuring that code is memory safe by it enforcing one quite opinionated approach to it: RAII and lifetime analysis.

you seem to think there is one path to memory safety. there is not. unsurprisingly, some programmers may need different tools when working with a different set of requirements.

Not if choosing statically checked memory safety sacrifices for correctness where it is a local optimum

  No ___, no ____. Just _____

or using "honest" to describe an approach.

Quality over quantity

I have no idea why I am responding to someone who flippantly uses a phrase like "dilittante mindset", but here we go

there is definitely a tendency for noobs and amateurs in any hobby or industry to obsess over expensive gear and things that don't matter (I love the term "buyhard" for it). you're out of your mind if you think the professionals in literally any industry do not discuss the specific technical tradeoffs of tools they are using among themselves.

"some of the newer ideas happening in this space are in the GNOME OS project and the KDE Linux project"

If I am remembering correctly, there was a moment where Garry was seriously considering using Squirrel instead of Lua. I think he experimented with JavaScript too.

I’m not sure it’s still the case but he modified Lua to be zero indexed and some other tweaks because they annoyed him so much, so it’s possible if you learned GMod Lua you learned Garry’s Lua.

Of course his heart has been with C# for many years now.

Don't engage with this guy, he shows up in every one of these threads to pattern match back to his heyday without considering any of the nuance of what is actually different this time.

I can see how you would have read it that way, now, but yes — I meant this article is defensive for no reason while being uninformed

As a fan and user of Zig I found the original post embarrassing, but chalked it up to the enthusiasm of a new user discovering the joy of something that clicked for them

Taking offense to that enthusiasm and generating this weirdly defensive and uninformed take is something else, though

It’s hard to see this article as being written in good faith. We’re at the point that we are responding to low quality LLM outputs with low quality LLM retorts and voting them both to the front page because of feelings.

I stopped using Rust because of this. I spent more time learning and cursing at other people’s abstractions versus thinking about what the computer is doing.

> the ones who’d use Zig if it weren’t allergic to syntactic sugar

You’re very close to understanding why some people prefer Zig. There is a correlation between language design and how things are built with it.

One that I know of is https://timetree.org/

I considered making the case for the parallels to Lisp, but it's not an easy case to make. Zig is profoundly not a Lisp. However, in my opinion it embodies a lot of the spirit of it. A singular syntax for programming and metaprogramming, built around an internally consistent mental model.

I don't really know how else to put it, but it's vaguely like a C derived spiritual cousin of Lisp with structs instead of lists.

this is a really, really good article with a lot of nuance and a deep understanding of the tradeoffs in syntax design. unfortunately, it is evoking a lot of knee-jerk reactions from the title and emotional responses to surface level syntax aesthetics.

the thing that stands out to me about Zig's syntax that makes it "lovely" (and I think matklad is getting at here), is there is both minimalism and consistency to the design, while ruthlessly prioritizing readability. and it's not the kind of surface level "aesthetically beautiful" readability that tickles the mind of an abstract thinker; it is brutalist in a way that leaves no room for surprise in an industrial application. it's really, really hard to balance syntax design like this, and Zig has done a lovely and respectable job at doing so.

Zig does not really try to appeal to window shoppers. this is one of those controversial decisions that, once you become comfortable with the language by using it, you learn to appreciate.

spoken as someone who found the syntax offensive when I first learned it.

> it's even worse that they landed on // for the syntax

.. it is using \\

to me it seems like the market is breaking into an 80/20 of B2C/B2B; the B2C use case becoming OSS models (the market shifts to devices that can support them), and the B2B market being priced appropriately for businesses that require that last 20% of absolute cutting edge performance as the cloud offering

here's a quick recording from the 20b model on my 128GB M4 Max MBP: https://asciinema.org/a/AiLDq7qPvgdAR1JuQhvZScMNr

and the 120b: https://asciinema.org/a/B0q8tBl7IcgUorZsphQbbZsMM

I am, um, floored

my very early first impression of the 20b model on ollama is that it is quite good, at least for the code I am working on; arguably good enough to drop a subscription or two

"Days Since Last VSCode Fork", when?

this seems unmaintained https://dayssincelastvscodefork.com/

why do I get so annoyed every time I read the word "slop" used like this? I have the same reaction with "enshittification". am I just getting grumpy and old?

it triggers the same eye roll as the schoolyard bully nicknames so popular in politics right now. bite sized, zero effort, fashionable take downs that suffocate any attempt at genuine discourse.

but I am probably just grumpy and old.