n42

7 ms·

1.
by n42 8d ago
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/ipho
2.
by n42 8d ago
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 ph
3.
by n42 2mo ago
The combination of static safety gracefully degrading to runtime safety where not provable is interesting to me
4.
by n42 3mo ago
https://matklad.github.io/2025/08/09/zigs-lovely-syntax.html
5.
by n42 3mo ago
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
6.
by n42 3mo ago
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
7.
by n42 3mo ago
Not if choosing statically checked memory safety sacrifices for correctness where it is a local optimum
8.
by n42 4mo ago
No ___, no ____. Just _____ or using "honest" to describe an approach.
9.
by n42 5mo ago
Quality over quantity
10.
by n42 7mo ago
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
11.
by n42 7mo ago
"some of the newer ideas happening in this space are in the GNOME OS project and the KDE Linux project"
12.
by n42 9mo ago
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
13.
by n42 10mo ago
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.
14.
by n42 10mo ago
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
15.
by n42 10mo ago
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 defensiv
16.
by n42 10mo ago
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.
17.
by n42 11mo ago
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
18.
by n42 1y ago
One that I know of is https://timetree.org/
19.
by n42 1y ago
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 metaprogrammin
20.
by n42 1y ago
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
21.
by n42 1y ago
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 wh
22.
by n42 1y ago
> it's even worse that they landed on // for the syntax .. it is using \\
23.
by n42 1y ago
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 requ
24.
by n42 1y ago
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,
25.
by n42 1y ago
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
26.
by n42 1y ago
"Days Since Last VSCode Fork", when? this seems unmaintained https://dayssincelastvscodefork.com/
27.
by n42 1y ago
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 nickname
28.
by n42 1y ago
I've been trying to beat this point in and failing. If a parameter type creates "colors", you can extrapolate that to an infinite set of colors in every single language and every single standard library, and the discussion on
29.
by n42 1y ago
It's hard to parse your comment, but I think we are agreeing? I was refuting the point of the parent. you have given another example of calling an IO-taking function inside a non-IO taking function. the example I gave was initializing
30.
by n42 1y ago
I do want to say that I regretted that comment as nonconstructive after it was too late to edit it. Others in the thread are representing my argument better than I can or care to.

More ›