MIGRATION

I have decided to migrate this to github pages, using material for mkdocs:


https://faretek1.github.io/blog/

Comments

Post a Comment

Popular posts from this blog

Image
 supposedly im meant to make a new post now ig trying to make a comprehensive library for goboscript for my own use its a bit annoying to be using prefixes instead of namespaces because i want to have my internal module-wide 'global' vars to be restricted there without polluting the area without operator overloading, calculations with complex numbers/vectors are also annoying, but tolerable. The most annoying thing is that the macro system is a bit broken. You cant call a macro within a macro - but u can use a macro in a macro definition. This is a bit weird but i hope it gets fixed bcs it would be so useful for my struct system Im trying to refactor my old code but its so bad aaaa need to add testing for every module so i need assert.gs to work nicely first maybe macros for defining whole functions could be funny#] things im prolonging - easing testing (how.?) nvm thinking about credits in goboscript. not sure how that would work You can get the distance of a point to a line b...
Read more

setip

 yes that reads setip not setup Since this is supposed to be a blog for everything i do, perhaps i could just write as much stuff here as i want right? this is super casual stuff i enabled anonymous commenting because sometimes, its annoying to login to random services oh yes and iirc the real reason i wanted to make this was because i saw so many people using https://note.com/ but thats in japanese and i dont want to have to use google translate all the time so yes. setip is a reference to some scratch project a while back by the way goodbye
Read more

goboscript

What is goboscript actually useful for? Perhaps i would say that the reason why i use goboscript (gs) is because the scratch editor was lagging too much. But there are a couple of other things that are really nice about goboscript. abstractions like functions, macros and structs git(hub) being able to handle tons of variables/lists without the block palette becoming clogged But perhaps my favourite feature of them all, is the  %include <path> statement. This is because it opens up the door for library development in scratch. Library development in scratch would allow you to use other people's code easier. And being able to use other people's code without having to drag-and-drop out of your backpack is a wonder for the soul. Just a simple   %include <path>  statement is all you need. And of course, this is not limited to other people's code. The   %include  statement simple copy-pastes another goboscript file into another within the preproc...
Read more