gingerBill

9 ms·

31.
by gingerBill 8mo ago
First, tell me languages which have named value declarations which don't fit into that category. I'd love for my hypothesis to be proven wrong. Second, how are they wrong? You haven't proved any point as you were extremely va
32.
by gingerBill 8mo ago
In the follow up article, I wrote something like this in the conclusion: > Designing a language is more than just getting the syntax right, and denotation semantics are a lot more important in most ways, but that does not mean syntax doe
33.
by gingerBill 8mo ago
I was trying to be EXTREMELY clear I am talking specifically about DECLARATION syntax only and how for the most part, the concrete syntax for the DECLARTAION syntax is not that important in many languages. However concrete syntax matters a
34.
by gingerBill 8mo ago
I tried my best to be very clear within this article that I am talking about two specific things: DECLARATION SYNTAX and SEMICOLONS. This does not extend to anything else. In fact I got so frustrated with people like yourself who are wrong
35.
by gingerBill 8mo ago
Hello again. That's not my position in the slightest. The point of the article is to express how people will shallowly and naïvely judge something. It might be naïve conception of "aesthetics" but it's not even a good on
36.
by gingerBill 8mo ago
> I never got why compilers don't have pluggable syntaxes. Because then you've created dialects and produced the Curse of Common Lisp all over again. Syntax matters a heck of a lot, and you want consistency and coherency across
37.
by gingerBill 8mo ago
Yes it does. You can even type `;` anywhere too, go an try it. Because of how good the rules are for Python's needs, most people never know that semicolons even exist in Python.
38.
by gingerBill 8mo ago
Did you even read the article, even the heading of that section? You know there is a huge majority that do not want semicolons whatsoever, so saying people should just suck it up is actually a determent to the adoption of the language becau
39.
by gingerBill 8mo ago
That sidestepping only introduces significant whitespace, which may not be what people want in the first place. It can be quite common to align call expressions by the parentheses if they span multiple lines for clarity, and you preventing
40.
by gingerBill 8mo ago
The article does no such thing and just focused on declaration syntaxes and semicolons. I can class literally any language into the three categories for declaring variables. * Haskells are name-focused languages. * Smalltalk is a name-focus
41.
by gingerBill 8mo ago
Those syntax examples are literally just general examples, not the only way you have to write them. But to categorize the ones you wrote: * Clojure is qualifier-focused * Prolog is name-focused * Forth is qualifier-focused (`:` is the quali
42.
by gingerBill 8mo ago
I literally had to write an extra article because of the number of people who thought I was saying syntax doesn't matter. It matters a hell of a lot: https://www.gingerbill.org/article/2026/02/21/doe
43.
Choosing a Language Based on Its Syntax?(gingerbill.org)
1 points by gingerBill 8mo ago|0 comments
44.
The Only Two Markup Languages(gingerbill.org)
7 points by gingerBill 9mo ago|1 comments
45.
by gingerBill 9mo ago
In the first case in a language with type inference, I'd argue it would probably be written a bit different. And probably something like the following two cases: x := &bar if is_foo { x = &foo } // or
46.
by gingerBill 9mo ago
The thing that is at odds with Rust is the second part of the article: the difference in mindsets. Rust by default doesn't really encourage the group-element mindset and people have to work against the language in order to do it. And w
47.
by gingerBill 9mo ago
To make `Maybe(T)` feel like a multiple return, you just need to do `.?` so `maybe_foo.? or_return` would just the same. But as you say, it is more common to do the multiple return value thing in Odin and not need `Maybe` for a return value
48.
by gingerBill 9mo ago
The first paragraph from the article: > *TL;DR* null pointer dereferences are empirically the easiest class of invalid memory addresses to catch at runtime, and are the least common kind of invalid memory addresses that happen in memory
49.
Was It a Billion Dollar Mistake?(gingerbill.org)
10 points by gingerBill 9mo ago|9 comments
50.
by gingerBill 9mo ago
Unfortunately I don't think you've understand what I was I trying to say. Rust was designed from day-0 around explicit individual-value based initialization. Odin from day-0 was not designed around this (explicitly). This ever so
51.
by gingerBill 9mo ago
Here's my reply to him so I don't have to repeat it all: https://news.ycombinator.com/item?id=46457272 But in short, my hypothesis is because the Odin compiler bundles many graphics-related packages but does not b
52.
by gingerBill 9mo ago
Thank you for the comment and trying out Odin, but there are a few things in your comment which seem a bit off to me. Odin is trying to be C alternative, not a Go without GC. Odin does share a lot of similarities to Go, even including it&#x
53.
by gingerBill 9mo ago
Here's what I said in another reply: https://news.ycombinator.com/item?id=46454185 But to answer your general points here: Odin is a different language with a different way of doing things compared to others, so their
54.
by gingerBill 9mo ago
Odin's type system is just different to many other languages, and trying to compare it to others doesn't always work out very well. `Maybe` does exist in Odin. So if you want a `nil` string either use `Maybe(string)` or `cstring`
55.
by gingerBill 9mo ago
n.b. Sorry for the long reply, this is actually a really complex and complicated topic in terms of language design, trade-offs, and empirics. It's a trade-off in design which is not immediately obvious. If you want to make pointers not
56.
by gingerBill 9mo ago
Directly from the FAQ: https://odin-lang.org/docs/faq/#is-odin-just-a-language-for-... > Is Odin “just” a language for game development? # > No. It is a common misconception that Odin is “just” for game deve
57.
by gingerBill 9mo ago
I think the notion that "null" is a billion dollar mistake is well overblown. NULL/nil is just one of many invalid memory addresses, and in practice most of invalid memory address are not NULL. This is related to the drunkard
58.
by gingerBill 10mo ago
The code example is more to show the scoped copy-on-write behaviour of `context` more than how it is used in practice. I agree it might be a bit confusing and thus needs to be made clearer that is what the code example is meant to show. How
59.
by gingerBill 10mo ago
There is sadly a habit which is not bound to any "community", and I've seen a lot of cases where people will just rant a lot about something they don't understand when that rant could have been easily prevented by either
60.
by gingerBill 10mo ago
I am the author of the article. If you have any questions, please feel free to ask :)

More ›