inmysocks (version: awoo) @inmysocks@awoo.space

Now I get to figure out how to effectively use coroutines.

Because I am a professional engineer I have warnings like "Changing this setting may break everything and plunge the earth into a 1000 year reign of darkness. Or it may work just find and cause no trouble.'

Also just about every advanced setting that has the potential to break something is under the heading 'Here there be Dragons'.

Yep.

Every so often I realise just how terrible I am in node and javascript.

It is a bit weird

I need to update the instructions for making a pie server so other people can use set one up easily.

GitLab is done again, but this time I have all of the repos I need mirrored onto my pie server so it isn't very disruptive.

Yay pie server!

oh, and sub-organisations. Gitea doesn't let you have things like OokTech/Foo as an organisation.

Not the end of the world, but less than ideal.

I haven't looked into it much but it looks like the standards for federated pull requests and stuff for git are moving forward

Which is awesome and will make having a self-hosted gitea/gitlab/whatever server much more viable for open source projects

this comes up because the gitlab install on my local pieserver was way out of date. I had version 1.1.0 and the newest version is 1.9.6.

I need to figure out what the updates are, aside from topics. Topics are awesome and the one thing that I was missing compared to gitlab/hub.

Someone makes a huge complex piece of software and tries to sell administration and maintenance as a service, then someone else comes along and is like 'or you could do it in this really simple way that requires almost no resources'.

Not that I don't like gitlab, they are rather important in the alternative to GitHub sense, but you are going to have maybe 100 organisations in the world that need something that can support the type of traffic required to justify something that complex.

I will always be a bit entertained by how gitlab is a (relatively) big bulky installation that affects a bunch of stuff and takes up a bunch of resources. My pi 2 had some troubles with it with more than one person. then gitea is like 'the executable is less than 100mb, requires no external dependencies and it take about 30mb of ram if you have 2 or 3 people using it'

I get that gitlab is made for a much larger workload, but the difference in complexity is amusing.

also there is the whole npm vc thing going on.

That makes breaking the reliance on npm a bit urgent.

Disclaimer: There are plenty of amazing things about Node, I use it all the time.

My biggest complaint is still that node indicates synch/async backwards. Almost everything is synchronous aside from a few functions. But instead of naming the function that are different (in the sense of asynchronous) they label the versions that match the behaviour of everything else.

That is bad design.

Also:
path.delimiter
path.sep

WHAT THE FUCK? Pick a convention node, you're drunk.

and now, same douche, is pushing to follow the progressive web app standards because 'otherwise the available technologies won't be available to us'....

Somehow not fitting googles standards now mean that browser caches and the like aren't available to you?

This guy has to just be fucking with me.

also, progressive web apps certainly feel like a Trojan horse that is there to help move people from having any local applications to using applications that are purely on remote servers like chromebooks

this same douche keeps harping about how we can just make a progressive web app because they use localStorage which means we can save whatever we want to the local file system.

This is after me explaining multiple times that localStorage is not the same as file system access, it is a browser cache with some makeup on it.

And the 30 seconds later he says 'what do you have against progressive web apps? They would let us access the file system!'

CORS headers seem counter productive to me.

The browser doesn't allow cross-origin requests for security.

But there are times when you want to be able to do cross-origin things.

CORS to the rescue. But instead of going with the whole 'security' thing where your browser would determine if cross origin things are allowed, the remote server gets to tell your browser that it is allowed.

'Don't talk to strangers, unless the stranger says it is ok, then they can do whatever they want'