machuidel

3 ms·

1.
by machuidel 8y ago
I did something similar a while ago. Have a look at: https://gist.github.com/machuidel/d7cc099ddc4970c6ddf4
2.
by machuidel 9y ago
Oh oh. Young me will get into trouble again: https://bytes.com/topic/c/answers/214712-using-return-parant...
3.
by machuidel 10y ago
Which new languages?
4.
by machuidel 10y ago
I did the following experiment a while ago (map and flatmap in C): https://gist.github.com/machuidel/d7cc099ddc4970c6ddf4 By adding more abstractions it should even be possible to support semigroups, monoids etc. Of co
5.
by machuidel 10y ago
Several months ago I still used a multi-site licensed Windows 7 Ultimate and relied on the "Services for Unix" NFS support. My servers are Unix based. Went outside for a while and when I came back my Windows 7 Ultimate had been re
6.
by machuidel 11y ago
Yes, that would be good for development / debugging (like debug symbols) or as an optional way to give people access to the source.
7.
by machuidel 11y ago
Since I started hearing about WebAssembly I cannot stop thinking about the possibilities. For example: NPM compiling C-dependencies together with ECMAScript/JavaScript into a single WebAssembly package that can then run inside the brow
8.
by machuidel 11y ago
I've had many issues with NetworkManager, Avahi and Pulseaudio. I already decided to avoid them a long time ago. My distribution of choice, after using Slackware for several years, has always been Debian. There have been moments I trie
9.
by machuidel 11y ago
The state is passed back and forth. The server does not keep the state (that is why they call it stateless), the client may keep it. If something does need to be stored on the server a resource should be created. The state that is passed ba
10.
by machuidel 11y ago
Actually, they are all valid ways when using the ReST philosophy. The idea is that with every request from the client the latest state is sent along with it (if needed). This way the state of the request can be reconstructed on the server w
11.
by machuidel 11y ago
Have been using the ReST philosophy (or pattern?) for almost 15 years without any issues. ReST itself does not define the use of a specific technology and is not a standard by itself, it is pretty abstract. Using the URI and HTTP standards