1,970 karma · joined July 18, 2010
I remember being very interested in programming in middle/high school, but all the environments in our school computer lab had windows (this was in India), and I think at that time (maybe 2001-2003) I didn't even know there were other operating systems.
Our school was participating in something called International Cyber Olympiad, and of course I gave the eligibility exam.
They sent all students who passed a Knoppix Live CD to prepare for the actual competition. We did not have a PC at home until a couple of years later, but I used that CD in any PC I could find anywhere - the school computer lab, the school library computers, and my dad's office computers. It was my first experience with a Linux system (and I found it awesome). Also my first experience with gcc instead of borland c++.
https://www.erlang.org/doc/apps/erts/time_correction.html#ho...
> So if you positively encourage it to “think out loud”, it stands a much better chance of being able to use its deduction and reasoning capabilities (which are quite significant).
I'm imagining a categorized whitelist of domains based on purpose (essential, telemetry, ads) which the user would choose from at first run, and the program would just block the other domains without asking again and again.
For simple undo operations (recover a recently deleted file), Syncthing's version history is good enough.
One of the few projects I'm sponsoring on Github.
No.
But, you can use a cheap cache layer instead of expensive db layer - ETS.
Like all messaging mechanisms, this can be handled by passing a reference or id, and the receiver fetching the actual large data from db/file/source of truth.
[0] - http://erlang.2086793.n4.nabble.com/how-message-size-effects...
Effectively, mutations to the internal state are "serialized" by the owner process, so it's easier to handle possible race conditions without using explicit locks/semaphores.
To debug, there's a max_heap_size parameter which can be configured to log an error message when heap size of any process goes beyond a threshold, or it can even kill the process[0]. Although I don't know if this takes the "off-heap" messages into account.
Also, there are lots of libraries which can provide a "top" like view of the running system.
[0] - http://erlang.2086793.n4.nabble.com/Max-heap-size-td4716974....
I think what this adds is a better way of dump processing without using database specific features.
HTTP/1.1 200 OK
Vary: Accept-Encoding
Content-Type: text/html; charset=utf8
Connection: keep-alive
Server: You got SERVED!
X-Cache: MISS