trashburger

6 ms·

31.
by trashburger 2y ago
Not quite; the interpolations are not eagerly stringified which is the potentially expensive part. In this sense it's kind of a middle ground between the two approaches.
32.
by trashburger 2y ago
Pathological case for link rot.
33.
by trashburger 2y ago
Please no. Templates being lazy is so much better than Rust's eager trait evaluation, the latter causing incredible amounts of pain beyond a certain complexity threshold.
34.
by trashburger 2y ago
https://justforfunnoreally.dev/
35.
by trashburger 2y ago
> modular architecture > single, static binary compiled for any platform Huh? Aren't these exact opposites?
36.
by trashburger 2y ago
Also too many dogs it seems, as the infinite and finite loop examples also produce "dog".
37.
by trashburger 2y ago
This is what I felt initally, too. However, you easily become used to the lack of overloading, and since the language has method syntax sugar you can easily get used to .add() over +. I'd recommend you give it another shot.
38.
by trashburger 2y ago
If I'm saving changes that were done because of a arduous debugging journey and other people are likely to have to refer back to it, yes. In fact, forget little; the smaller the change is, the bigger the text. Some of my changes have 2
39.
Tell HN: Latta.ai is spamming FOSS projects with bogus fixes
3 points by trashburger 2y ago|1 comments
40.
by trashburger 2y ago
The image, sure. Their ethos never changed.
41.
by trashburger 2y ago
Would be much slower and eat up precious context window.
42.
by trashburger 2y ago
Hmm, why not Cap'n'Proto? Also this seems to be multi-process like ROS. I wanna see something adopt the Isaac model of nodes and codelets.
43.
by trashburger 2y ago
Good for you. Now please aim 10,000 requests a second at your file server.
44.
by trashburger 2y ago
I think it's just a meme.
45.
by trashburger 2y ago
Not when you are willingly connecting to a server. The server owner didn't force you to do it.
46.
by trashburger 2y ago
Bet you're real fun at parties.
47.
by trashburger 2y ago
Not a personal website, but putting my Free Software contributions and own projects on my CV helped me get my current job.
48.
by trashburger 2y ago
Yes, always. Of course I make mistakes, but the idea is that any patch I put up for review, if it cleanly applies, should not break any user and any tests. It's much more liberating knowing that bisects actually work and each commit do
49.
by trashburger 2y ago
How is it zealous to prevent people from co-opting and diluting the meaning, like you have done here? If anything, companies are trying to misuse "open source" for their source-available code.
50.
by trashburger 2y ago
All the more reason to keep GApps completely off one's devices. Even if Google doesn't overreach, governments can and (per TFA) do.
51.
by trashburger 2y ago
I think Zig not having a way to "modify the environment map" is a good thing, personally. Global state should be avoided at all costs. If a downstream library's setting isn't exposed through a config struct, and can only
52.
by trashburger 2y ago
Is this satire? Being a scripting language and tracking dependencies are primary features of shells and Make, respectively.
53.
by trashburger 2y ago
Had Nvidia put their hubris aside for a second (tough ask, I know) and worked to make Isaac into an open source project, it would have eaten ROS' lunch. The subgraph-based approach was much better, the node/component/channel
54.
by trashburger 2y ago
At work I always try to do things that I didn't know about and dive as deeply as I can afford to. At my previous job I learned Kubernetes from nothing to the point where I had a nice GitOps based CD pipeline. At my current job, I dived
55.
by trashburger 2y ago
I completely disagree. In doing so you lose all visibility into the components and gradual evolution of the code that atomic commits provide. Same thing with squashing (which is just the worst).
56.
by trashburger 2y ago
By doing this, you break commit atomicity and make bisects hell. Please don’t do this. Commits aren’t perfect at first for sure, but they should be by the time you make them reviewable.
57.
by trashburger 2y ago
The "hustle culture" affects you if you believe it does. If you didn't "get a commit in on react or vue or whatever" until now, what was it that stopped you? Why aren't you billing that client? Will starting a
58.
by trashburger 2y ago
I mean, good for you, but some need to be reminded that it's not all about the grind.
59.
by trashburger 2y ago
https://leebriggs.co.uk/blog/2019/02/07/why-are-we-templatin... Something like Jsonnet would serve one better, I think. The only part that kinda sucks is the "package management" but that'
60.
by trashburger 2y ago
Arguably, one should call `flush()` on the file first. Resource deallocation must always succeed; otherwise a lot of invariants break. This is why Zig's close method[0] ignores errors (with the exception of `EBADF`). [0]: https:/

More ›