Replies: 3 comments
-
|
This should probably have been a Discussion instead of an issue. :) |
Beta Was this translation helpful? Give feedback.
-
|
I don't agree with that I'm a go dev myself, I use it every day, my job is literally writing Go code and what attracted me to lisette is that the syntax is more rust-like than it is go-like I love the fact that I can use Go libraries with a syntax that has nothing to do with Go |
Beta Was this translation helpful? Give feedback.
-
|
Hi @leaxoy! Lisette's syntax is mostly settled, but given your preference you might be interested in https://github.com/MadAppGang/dingo Moving to a discussion |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As a Go developer, I've had enough of Go's current syntax. I really like your approach, but I have a suggestion.
I believe that if this project wants to attract Go developers, it should use mainstream Go syntax instead of making extensive modifications. Otherwise, it will drastically increase the mental burden on Go developers, hindering its promotion and appeal.
Some examples:
keywork:
fn -> funccode block:
task {} -> go func() {}generics:
let (tx, rx) = Channel.new<string>().split() -> tx, rx := Channel.new[string]().split()from your code example in readme
Beta Was this translation helpful? Give feedback.
All reactions