Hacker News new | past | comments | ask | show | jobs | submit | nurettin's comments login

> So what are they in this case?

You wouldn't want to go public with donations to churches (it would be ideological) or orphanages (that would just be bragging).


> Pivoting from "for all mankind" to "all for myself"

Isn't the former already a red flag?


No it’s good to try to build tech that helps people. Doesn’t mean such declarations need to be taken at face value, but being baseline-cynical is generally unwarranted, undesirable, and uninteresting.

The baseline stance for tech startups is wanting to solve a problem in the world and profiting from the value that provides. And thankfully, most of the time, those motives don't conflict. Even a mundane business like my local grocery store solves the problem of a curating a selection of food producers, buying in bulk to ensure a sustained sustained supply at a reasonable price and make it available to me close to my home. That is a tremendous value! And for that they make their markup. They aren't necessarily solving other social problems like food scarcity or maximizing nutrition or whatever, and instead focus on what their customers want to buy, those that can pay for it. But there still is a meeting in the middle of value being created.

I know a certain Nigerian prince who would wholeheartedly agree with such broadly encompassing statements.

Cynicism doesn't necessarily protect you from getting scammed, but it does absolutely prevent you from accessing any upside there is to be had in the world :)

The upside being people flocking from MLM to DeFi to LLMs like headless chickens while I watch in amusement?

The only downside for me is having been involved in all these projects and knowing enough to innovate. At least I do try to warn people before we proceed.


Interesting, I wonder if this means that they got paid.

> It's also hard to tell them not to use AI because the code does work. I would say even most of the times the code does work.

> But it's just written in the worst possible manner and maintaining it long term is going to be so much harder if instead they had just handwritten the code.

Just charge more for LLM generated crappy code due to above reasons?


> As the author notes: the typing system is very pleasant. And the standard library is great!

The author complained about the standard library, specifically the Dir module using inconsistent types and the implementation details of Temp files potentially leading to security flaws, leading me to think there are more warts he didn't cover.


Temp file issue is debunked here: https://news.ycombinator.com/item?id=41684848

Dir module works fine, though maybe the docs could be improved. https://crystal-lang.org/api/1.13.3/Dir.html . The stdlib code is also highly readable: https://github.com/crystal-lang/crystal/blob/d14d04562/src/d... shows that #each_child just calls #read and yields it to the block, so I don't think this is really a wart :)


I think the Dir issue wasn't that documentation was inadequate or stdlib code was hard to read, but he expected paths, and received strings instead.

As I remember, when you step slowly from the middle of a tile, you always end up on the edge of that tile. And if there is a chasm and you try to step once again, you almost trip and regain balance. If there is no chasm, you step to the middle of the next tile.

IIRC, you can adjust your position quite precisely by crouching, which has a side effect of making you move forward a tiny little bit. Yes, stepping towards a chasm will make you stop at the edge, but that does not alter the fact that your position is definitely not clipped to fixed steps, as the article erroneously claims.

https://www.renpy.org/

This does pretty much what you have described. It supports scenes, image maps for point and click, dialogues and is low code.


I would gladly switch to a valkey redis compatibility layer if it supports xstreams.

That is... probable, if you bought a newish m2 to replace your 5-6 year old macbook pro which is now just lying around. Or maybe you and your spouse can share cpu hours.

No, you need two of the newest M3 Macbook Pros with maxed RAM, which in practice some people might have, but it is not gettable by using old hardware.

And not having tried it, I’m guessing it will probably run at 1-2 tokens per second or less since the 70b model on one of these runs at 3-4, and now we are distributing the process over the network, which is best case maybe 40-80Gb/s

It is possible, and that’s about the most you can say about it.


It is the name of a feature in Nix. This is as obfuscated as calling a rock a rock.


Strange thing to say but you do you.

I tried to dabble in Nix several times and the term never stuck.

I suppose for you it's impossible to accept that the term is just bad and unintuitive. And other comments here say the same.


I mean it has variable names, configurations, documentation, a file extension and lots of code and a history behind it, so the strange thing to me is trying to suggest a replacement phrase as if you don't know what it is, acting like it's some high-brow language used in a blog to look smart, complaining about how this makes it less accessible (paraphrasing a little), then rolling back saying you dabbled in Nix and acting like you know what it is.

But then, you do you.


The part you seem to deliberately miss is that what is obvious to people deeply invested in Nix is not obvious to anyone else.

I for one can't trace the train of thought that is going from "intermediate build artifact" and somehow arrives at "derivation".

I found out just enough about Nix to reject it. My take is still informed, I simply didn't buy its pitch.


I geniunely thought you knew nothing about derivations and were criticizing the blogger for writing the term in their blog, not the term standard to Nix itself. Which is just as weird to me as complaining about std::string, well why call it a string? it is obviously text!


> Which is just as weird to me as complaining about std::string, well why call it a string? it is obviously text!

It's really not, though. String is a common technical term used in programming languages for many decades. If a new language decided to call them "textrons", _that_ would be weird. And this is the exact thing Nix did with "derivations", "flakes", etc. There is no precedent for these terms in other software, so they're unfamiliar even to its core audience.

It would be different if Nix invented an entirely new branch of technology that didn't have any known precedent. But for a reproducible build system that uses a declarative language? C'mon.


No need to resort to obvious straw man arguments, you can just accept some people dislike the dev UX of Nix and move on, which is basically what me and others have been trying to say in this entire sub-thread, some much more detailed than me.

No idea why you keep digging at this, the takeaway was clear at least three comments ago.


FYI "here's what I genuinely thought" is not a straw man. Now I am genuinely sorry for ever responding to you. Say hello to others for me.

The straw man was your std::string example. It was nowhere near the same as you claimed.

Say hi to the others in your club of "I'm gonna pretend I didn't get it for no reason whatsoever" for me.


It was an example, you thought it was a bad example, and the rest were just inane accusations.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: