Man this is nice! Thanks.
Edit: Takes a bit slower than Kitty to zoom though. Slower than Alacritty too. But it looks ‘slicker’ in general.
Man this is nice! Thanks.
Edit: Takes a bit slower than Kitty to zoom though. Slower than Alacritty too. But it looks ‘slicker’ in general.
Can’t load this website, what is it?
Thanks for your help my good man.
This is so nice… Thanks.
It seems like reading the book is the only way. I shall do just that.
Understood. Thanks. I really wish they would allow people to upload their own games. Kinda like that old website (Newgrounds? idk).
++A; thanks! So, in a domain-specific language, like ASDL which I implemented, it’s mostly the denotational semantics at work, but in a GPL like C, it’s mostly operational. Am I right?
btw if you got the time, could you pls explain axiomatic semantics, that would be great. I don’t at all understand this one. Thanks.
This statement is completely wrong. Like, to a baffling degree. It kinda makes me wonder if you’re trolling.
No I just struggle at getting my meaning across + these stuff are new to me. What I meant was ‘Go does memory management LIKE a VM does’. Like ‘baking in the GC’. Does that make sense? Or am I still wrong?
I’m not American though :D
@Ferk @FizzyOrange @posgamer @reflectedodds @ExperimentalGuy: There are errors in what I said. I admit I am not an expert. I will come back with better explanations for my stance, after I have read more about it.
First off, I apologize if I did not add a disclaimer saying I could be wrong. But given this, what is exactly the difference between denotaional and operational semantics? I base what I said on [my understanding of books about language theory. But it seems like I got the wrong gist. Where do you recommend I start?
PS: I’ll add a void to the post rn.
First, tell me what you mean by ‘closure’. I did not mean ‘closure’ as an operational function literal. Keep that in mind.
If you use JVM 8 yes. Use Zero.
I know about all this — I actually began implementing my own JVM language a few days ago. I know Android uses Dalvik btw. But I guess a lot of people can use this info; infodump is always good. I do that.
btw I actually have messed around with libgcc-jit and I think at least on x86, it makes zero difference. I once did a test:
– Find /e/ with MAWK -> 0.9s – Find /e/ with JAWK -> 50s.
No shit! It’s seriously slow.
Now compare this with go-awk: 19s.
Go has reference counting and heap etc, basically a ‘compiled VM’. I think if you want fast code, ditch runtime.
I was mainly asking if this was even the case. If i go to the maintainers and say shit like this they b& me.
1- Not sure, I can’t read; 2- Yes, Fish; 3- Yes, it fixed it.
I think that happens when app developers learn2optimize. Stop using interpreted bytecode languages on small processors!
My man we have UNIX because PDP-11 was expensive!
This is EXPANSIVE! Wow.