zupa-hu

6 ms·

31.
by zupa-hu 2y ago
Oh wow you can also use this for contract diffing when signing in person!
32.
by zupa-hu 2y ago
Interesting. You have a bug in the name of your language. :)
33.
by zupa-hu 2y ago
Same here.
34.
by zupa-hu 2y ago
Consider updating your vocabulary because the term is often used for both. Note that rendering to the “screen” really means writing bits at a memory range, which is just one interface for displaying things. Html is another, higher level int
35.
by zupa-hu 2y ago
My partner is an orthodontist. (That’s a specialization within dentistry.) I’m a software engineer btw. The saying goes that you only need to floss the teeth you want to keep. If you think about it, a toothbrush will only clean 3 sides of a
36.
by zupa-hu 2y ago
Hey, thank you so much for Pager! It helped me a lot (in supporting my own free users on Reddit)! I was often wondering how long it will remain free. Well, forever. <3
37.
by zupa-hu 2y ago
had such a good laugh, I’m going to steal that :)
38.
by zupa-hu 2y ago
Thanks, that's great to hear!
39.
by zupa-hu 2y ago
Hi, author here. If you want to play with the language try the language docs that includes executable playgrounds: https://lang.boomla.app/types/boolean
40.
by zupa-hu 2y ago
As I understand Swift's error handling falls straight into the explicit camp. That's all good and I love it. My problem is that it seems it's not for everyone at every stage of their journey. When I teach software development
41.
by zupa-hu 2y ago
Thanks for the link!
42.
by zupa-hu 2y ago
So the error type can be left out when the compiler can infer it. If it is left out, and the compiler can't infer it, Zig will fail to compile and provide an error message pointing to the missing error type information. Thanks for the
43.
by zupa-hu 2y ago
The problem is that making function signature errors optional effectively "colors" all the functions. If I want to write a function with errors in the signature, then what if I call a function that doesn't have the error in t
44.
by zupa-hu 2y ago
(Author) Thanks for the Zig examples, great comparison! I'm puzzled how Zig can do exhaustiveness checks in the presence of interfaces (dynamic dispatch). A quick google search suggested Zig may not have them? The problem is, having dy
45.
by zupa-hu 2y ago
(Author) Thanks indeed checked exceptions have been brought to my attention in this thread, and in theory they are indeed very similar, except I understand changing the type of a checked exception causes refactoring hell, so they are painfu
46.
by zupa-hu 2y ago
(Author here) Yes, that's correct. It's an algebraic effect elevated to a dedicated language feature. The benefit is that it is simpler than having full-blown algebraic effects, both to learn and to actually use. Probably not for
47.
by zupa-hu 2y ago
> I don't think you can lump Java with the others in this comparison Fair point, I've removed Java from the examples. Apologies, I haven't used Java for ages and relied on my memories. That said, I understand they are not
48.
by zupa-hu 2y ago
It didn't exist originally, but for high level programs like a TODO app that is mostly html templates, those question marks really don't add much value. Plus every time I showed code snippets to web developers, they got hung op on
49.
by zupa-hu 2y ago
Author here, thanks for the comment, it is indeed a hard compiler error not a warning. Bad wording. It is a fair point too about new developers / seasoned developers. Maybe citizen developers is a better phrase? I've encountered m
50.
by zupa-hu 2y ago
Thanks for the long answer. Okay, it's good you have thought it through. Will be interesting to see how it evolves.
51.
by zupa-hu 2y ago
I enjoyed the thoughtful article. It's interesting that type checking happens at runtime so there is no compile time, only runtime. It seems this would make it acceptable. But I wonder if the assumption will always hold. The assumption
52.
by zupa-hu 2y ago
Do you have a better idea?
53.
by zupa-hu 2y ago
The problem is there are not 100 tools out there but literally infinite, in the sense that one could not learn them all simply because new ones are created faster. Given that, the article does have an implied filter criteria that goes unsai
54.
by zupa-hu 3y ago
Indeed.
55.
by zupa-hu 3y ago
The problem is the cost of doing this. If it gets overturned, the defendant shouldn’t be the one to bear the cost. I’d be happy with either 1) the patent owner or 2) the patent office, who didn’t do its job properly.
56.
by zupa-hu 3y ago
So to paraphrase, the problem is around context passing between threads, which makes sense. Sounds like that could be solved by a language surfacing the context at thread boundaries like the `go` statement, possibly channels. Thanks for the
57.
by zupa-hu 3y ago
> Thread-local storage is bad because it's implicit and causes bugs when used with concurrency; if you farm out some work to another goroutine, it will break. Can you elaborate on why being implicit is bad and how it causes bugs? I
58.
by zupa-hu 3y ago
Great post, love reading these. I noticed the author mentions implicit context argument passing in Odin. I looked into it, and as I understand it is for language related use only - memory management, etc. I'm looking for inspiration in
59.
by zupa-hu 3y ago
His tool, his pricing, take it or leave it. Nothing scammy in it. Build something better, undercut his price, then we can talk.
60.
by zupa-hu 3y ago
- Require two independent kill switches, one long range, one close range (say 5m). - Allow everyone to have close range kill switches, which use a universal open standard protocol that works on every robot (alas pepper spray for robots).

More ›