I see you are using a surgically altered MIT license. If you are concerned with commercial use, what is the benefit of this versus releasing under a standard copyleft license like GNU AGPL?
#...
unique jetty
grave wind
this is actually my first github repo ever, and I don't know much about licenses
It was actually AI written
have I done something wrong? someone gave a thumbs down
rapid hornet
you can ask them (mouse over to see who) but possibly because... AI slop overdose?
shrewd kelp
getting thumbs down in this discord is crazy work
naive solstice
em dash detected opinion rejected
(ik its not a valid take but unless its literature, em dashes aint acceptable)
grave wind
em dash detected opinion rejected
whats a em dash
naive solstice
vibe coding should never be acceptable unless you 100% understand above and beyond whatever you are trying to vibe code
which i damn as hell know you dont just looking at how properly you've setup the code
plush forge
It is non OSS AI slop, of course you get thumbs down. Most people enjoy learning journeys, mistakes and best practice, not vibe coding.
plush forge
just an example:
func throwError(err error) {
log.Fatal(err)
}
func ReadTextFile(path string) string {
bytes, err := os.ReadFile(path)
if err != nil {
throwError(err)
}
return string(bytes)
}
Why do you need a helpfer function, to use log.Fatal()? Why are you shipping binaries through an git repository, that is an anti pattern, Github knows Releases ....
Another example:
func is_value[T comparable](value T, values ...T) bool {
bool := slices.Contains(values, value)
return bool
}
And that is the slices.Contains upstream implementation:
// Contains reports whether v is present in s.
func Contains[S ~[]E, E comparable](s S, v E) bool {
return Index(s, v) >= 0
}
These are just two examples 🤷♂️
shrewd kelp
just an example:
```go
func throwError(err error) {
log.Fatal(err)
}
func R...
bool
bool := x()
return bool
is nice
plush forge
You are right, didn’t note this horrible detail 🫠
plush forge
Types are not keywords, so it only shadows an built in type.
plush forge
Vibe Coding is well defined, and easy to google, in short: Using AI tools without any knowledge. You write a prompt, and keep whatever happens, without knowing what it does.
grave wind
that's not what I did, I wrote this on my own from scratch
plush forge
func is_value[T comparable](value T, values ...T) bool {
bool := slices.Contains(values, value)
return bool
}
Is nothing a human would do
grave wind
whuhhh? is it the variable name?
plush forge
you literally copied slices.Contains without doing any modification or generating a profit
grave wind
wait, you're right
plush forge
same for this throw error thingy you did
grave wind
I never saw that. Well I've only had 2.5 months of go experience
plush forge
your issue is not 2.5 months of go experience, but lack of clean code
grave wind
same for this throw error thingy you did
that stays, i won't change that
plush forge
func throwError(err error) {
log.Fatal(err)
}
premature abstraction is the root of all evil. What kind of issues does this solve?
grave wind
in case I want to change how throwing an error works, believe me I have changed it a few times
however, I'm building the v0.2 that might be bytecode interpreted and AST interpreted at the same time. And thanks for the feedback
plush forge
you should also remove binaries from git, github knows releases (and doesn't waste repos space)
grave wind
hmm, thanks. I did think it was off
grave wind
you should also remove binaries from git, github knows releases (and doesn't wa...
So am i getting a thumbs down because the tag of this post was vibe coding??
plush forge
People hate reviewing AI generated code 🤷♂️
I don't make the rules, but I tend to agree.
grave wind
Its not AI generated though. I didn't even know that that's what vibe coding meant and the server forced me to give it a tag
plush forge
Maybe, but you also got guidance, like for your fancy error handling solution, and just didn't care about it
dry coral
I'm not even sure what the use of https://github.com/ECMA-King87/ArachnoScript-Programming-Language/blob/main/source/maps.go is for, isn't https://pkg.go.dev/maps sufficient ?
shrewd kelp
Well it’s safe for parallelism
rapid hornet
has() and get() in that code are ridiculous (iteration on a map… to find the key!!)
rapid hornet
(and locking in get but not in has...)
remote sandal
I'm curious, is this language trying to be different for the sake of it or because there's actually a good reason to do so? I have never seen another language use spawn for var, immortal for const, or static... for const?```js
$ these variables cannot be changed in any way unless changed internally
static spawn completely_static = { yo: 20 };
The language is not too much different actually, the language works very closely to JS
grave wind
...
rapid hornet
deleting/erasing something that got 50 replies isn’t great