Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Wyzer Programming Language

github.com

Post reply on HN
Print view View original

71–80 of 116 posts

Re: Show HN: Wyzer Programming Language

#71

Post by bramadityaw »

v0id_isgood wrote: post #26
steeleduncan wrote: post #21

const MAX: u32 = 100; // Compile-time constant let x: u32 = 10; // Cannot be changed If x cannot be changed, how does it differ (meaningfully) from a compile time constant in a safe language, ie in a case of no raw pointers

const can be used in places that need a compile-time-known value (like a fixed array size). let can't, even if it obviously holds a fixed number.

isn't there a way to infer that from context? like if the variable is declared with the Comptime role. Some guy said that the const keyword was a mistake C made that is then blindly followed by its successors.

Re: Show HN: Wyzer Programming Language

#73

Post by bramadityaw »

khat wrote: post #44

Simplicity in the tag line but uses Result . Should've followed Zig's direction for error handling. With that out of the way looks like a fun little language.

Zig's way is "simple" but not elegant, specifically since it hard codes how error handling is done. Algebraic data types are more elegant, since it can be used not just for error handling, but also other kinds of data modeling.

Re: Show HN: Wyzer Programming Language

#74

Post by Jabbles »

v0id_isgood wrote: post #45
jerf wrote: post #36

I love the ambition and the fact that this is not just another "state of the art in 2015" language like I see so often. It's trying to do something genuinely different. The field of "taking stuff out of academia and making it work" is a rich and underharvested one. However, your light is hidden under a basket, to use an old metaphor. I'm having to go digging to find the genuinely new things going on. I suggest recali…

This is hands down some of the most constructive feedback we’ve received. You hit the nail on the head. We definitely fell into the author’s trap of structuring docs "bottom-up" (Prerequisites -> Basic Syntax -> Advanced Concepts) rather than leading with our actual core innovation: choreography. We are restructuring the main README/docs front page right now to lead immediately with a concrete example of choreographi…

I think it's quite rude to reply to a well thought out comment with AI slop

Re: Show HN: Wyzer Programming Language

#76

Post by allknowingfrog »

pron wrote: post #37

> Go, Java, C#, and Python use garbage collectors. This makes them easier to use but slower and less predictable. It does not. The term "garbage collectors" covers a whole spectrum of algorithms, some might slow you down (though not for the reason you may think) while others were invented to speed up memory management beyond that of C++, in exchange for other tradeoffs. Python's (mostly) refcounting GC is actually cl…

The quoted text says "slower". It does not claim that GC makes those languages slow overall.

Are you arguing that GC is not inherently slower than other memory management strategies (e.g. the Rust approach)? Or just that the cost is not worth optimizing away?

Re: Show HN: Wyzer Programming Language

#77

Post by jwolfe »

tpoacher wrote: post #75

"Choreographic programming"? Are we just straight up inventing buzzwords now? Hey guess what, I'm more into symphonic opus programming, none of that backyard dance-club programming for me thanks. /s [no hate, just laffs]

That is apparently the existing academic term. It's got a Wikipedia page. But yes, all buzzwords were invented.

Re: Show HN: Wyzer Programming Language

#78

Post by irq-1 »

v0id_isgood wrote: post #45
jerf wrote: post #36

I love the ambition and the fact that this is not just another "state of the art in 2015" language like I see so often. It's trying to do something genuinely different. The field of "taking stuff out of academia and making it work" is a rich and underharvested one. However, your light is hidden under a basket, to use an old metaphor. I'm having to go digging to find the genuinely new things going on. I suggest recali…

This is hands down some of the most constructive feedback we’ve received. You hit the nail on the head. We definitely fell into the author’s trap of structuring docs "bottom-up" (Prerequisites -> Basic Syntax -> Advanced Concepts) rather than leading with our actual core innovation: choreography. We are restructuring the main README/docs front page right now to lead immediately with a concrete example of choreographi…

> linear/affine types and a perceus reference counting

You should put these up front also.

Re: Show HN: Wyzer Programming Language

#79

Post by tpoacher »

jwolfe wrote: post #77
tpoacher wrote: post #75

"Choreographic programming"? Are we just straight up inventing buzzwords now? Hey guess what, I'm more into symphonic opus programming, none of that backyard dance-club programming for me thanks. /s [no hate, just laffs]

That is apparently the existing academic term. It's got a Wikipedia page. But yes, all buzzwords were invented.

This confirms to me it was indeed originally intended as a buzzword then. :D

Nothing like establishing a new buzzword in a field to get them citations rolling.

Post reply on HN