blog/atom.xml (view raw)
1<feed xmlns="http://www.w3.org/2005/Atom"><title>pagong</title><id>pagong</id><updated>2020-07-02T22:00:00+00:00</updated><entry><title>University posts</title><id>dist/university/index.html</id><updated>2020-07-02T22:00:00+00:00</updated><published>2020-07-02T22:00:00+00:00</published><summary>During university, there were a few subjects where I had to write blog posts for (either as</summary><content type="html" src="dist/university/index.html"><!DOCTYPE html>
2<html>
3<head>
4<meta charset="utf-8" />
5<meta name="viewport" content="width=device-width, initial-scale=1" />
6<title>University posts</title>
7<link rel="stylesheet" href="../css/style.css">
8</head>
9<body>
10<main>
11<h1 class="title" id="university_posts"><a class="anchor" href="#university_posts">¶</a>University posts</h1>
12<div class="date-created-modified">2020-07-03</div>
13<p>During university, there were a few subjects where I had to write blog posts for (either as
14evaluable tasks or just for fun). Currently, these are:</p>
15<ul>
16<li><a href="/blog/mdad">Data Mining and Data Warehousing</a></li>
17<li><a href="/blog/ribw">Information Retrieval and Web Search</a></li>
18</ul>
19</main>
20</body>
21</html>
22 </content></entry><entry><title>Atemporal Blog Posts</title><id>dist/posts/index.html</id><updated>2020-07-02T22:00:00+00:00</updated><published>2020-07-02T22:00:00+00:00</published><summary>These are some interesting posts and links I've found around the web. I believe they are quite interesting and nice reads, so if you have the time, I encourage you to check some out.</summary><content type="html" src="dist/posts/index.html"><!DOCTYPE html>
23<html>
24<head>
25<meta charset="utf-8" />
26<meta name="viewport" content="width=device-width, initial-scale=1" />
27<title>Atemporal Blog Posts</title>
28<link rel="stylesheet" href="../css/style.css">
29</head>
30<body>
31<main>
32<h1 class="title" id="atemporal_blog_posts"><a class="anchor" href="#atemporal_blog_posts">¶</a>Atemporal Blog Posts</h1>
33<div class="date-created-modified">2020-07-03</div>
34<p>These are some interesting posts and links I've found around the web. I believe they are quite interesting and nice reads, so if you have the time, I encourage you to check some out.</p>
35<h2 id="algorithms"><a class="anchor" href="#algorithms">¶</a>Algorithms</h2>
36<ul>
37<li>http://www.tannerhelland.com/4660/dithering-eleven-algorithms-source-code/. Image Dithering: Eleven Algorithms and Source Code. What does it mean and how to achieve it?</li>
38<li>https://cristian.io/post/bloom-filters/. Idempotence layer on bloom filters. What are they and how can they help?</li>
39<li>https://en.wikipedia.org/wiki/Huffman_coding. Huffman coding. This encoding is a simple yet interesting way of compressing information.</li>
40<li>https://github.com/mxgmn/WaveFunctionCollapse. Wave Function Collapse. Bitmap &amp; tilemap generation from a single example with the help of ideas from quantum mechanics.</li>
41<li>https://blog.nelhage.com/2015/02/regular-expression-search-with-suffix-arrays/. Regular Expression Search with Suffix Arrays. A way to efficiently search large amounts of text.</li>
42</ul>
43<h2 id="culture"><a class="anchor" href="#culture">¶</a>Culture</h2>
44<ul>
45<li>https://www.wired.com/story/ideas-joi-ito-robot-overlords/. Why Westerners Fear Robots and the Japanese Do Not. Explains some possible reasons for this case.</li>
46<li>http://catb.org/~esr/faqs/smart-questions.html. How To Ask Questions The Smart Way. Some bits of hacker culture and amazing tips on how to ask a question.</li>
47<li>http://apenwarr.ca/log/?m=201809#14. XML, blockchains, and the strange shapes of progress. Some of history about XML and blockchain.</li>
48<li>https://czep.net/17/legion-of-lobotomized-unices.html. Legion of lobotomized unices. A time where computers are treated a lot more nicely.</li>
49<li>https://eli.thegreenplace.net/2016/the-expression-problem-and-its-solutions/. The Expression Problem and its solutions. What is it and what can we do to solve it?</li>
50<li>http://allendowney.blogspot.com/2015/08/the-inspection-paradox-is-everywhere.html. The Inspection Paradox is Everywhere. Interesting and very common phenomena.</li>
51<li>https://github.com/ChrisKnott/Algojammer. An experimental code editor for writing algorithms. Contains several links to different tools for reverse debugging.</li>
52<li>http://habitatchronicles.com/2017/05/what-are-capabilities/. What Are Capabilities? Good ideas with great security implications.</li>
53<li>https://blog.aurynn.com/2015/12/16-contempt-culture. Contempt Culture. Or why you should not speak crap about your non-favourite programming languages.</li>
54<li>https://www.lesswrong.com/posts/tscc3e5eujrsEeFN4/well-kept-gardens-die-by-pacifism. Well-Kept Gardens Die By Pacifism. Risks any online community can run into.</li>
55<li>https://ncase.me/. It's Nicky Case! They make some cool things worth checking out, I really like &quot;we become what we behold&quot;.</li>
56</ul>
57<h2 id="debate"><a class="anchor" href="#debate">¶</a>Debate</h2>
58<ul>
59<li>https://steemit.com/opensource/@crell/open-source-is-awful. Open Source is awful. Has some points about why is it bad and how it could improve.</li>
60<li>http://www.mondo2000.com/2018/01/17/pink-lexical-goop-dark-side-autocorrect/. Pink Lexical Goop: The Dark Side of Autocorrect. It can shape how you think.</li>
61<li>http://blog.ploeh.dk/2015/08/03/idiomatic-or-idiosyncratic/. Idiomatic or idiosyncratic? Can porting code constructs from other languages have a positive effect?</li>
62<li>https://gamasutra.com/view/news/169296/Indepth_Functional_programming_in_C.php. In-depth: Functional programming in C++. Is it useful to bother with functional concepts in a language like C++?</li>
63<li>https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/. Notes on structured concurrency, or: Go statement considered harmful.</li>
64<li>https://queue.acm.org/detail.cfm?id=3212479. C Is Not a Low-level Language. Could there be alternative programming models designed for more specialized CPUs?</li>
65</ul>
66<h2 id="food_for_thought"><a class="anchor" href="#food_for_thought">¶</a>Food for Thought</h2>
67<ul>
68<li>https://www.hillelwayne.com/post/divide-by-zero/. 1/0 = 0. Explores why it makes sense to redefine mathemathics under some circumstances, and why it is possible to do so.</li>
69<li>https://jeremykun.com/2018/04/13/for-mathematicians-does-not-mean-equality/. For mathematicians, = does not mean equality. What other definitions does the equal sign have?</li>
70<li>https://www.lesswrong.com/posts/2MD3NMLBPCqPfnfre/cached-thoughts. Cached Thoughts. How is it possible that our brains work at all?</li>
71<li>http://tonsky.me/blog/disenchantment/. Software disenchantment. Faster hardware and slower software is a trend.
72<ul>
73<li>https://blackhole12.com/blog/software-engineering-is-bad-but-it-s-not-that-bad/. Software Engineering Is Bad, But That's Not Why. This post has some good counterpoints to Software disenchantment.</li>
74</ul>
75</li>
76<li>http://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/. What Color is Your Function? Spoiler: can we approach asynchronous IO better?</li>
77<li>https://hackernoon.com/im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5. I'm harvesting credit card numbers and passwords from your site. A word of warning when mindlessly adding dependencies.</li>
78<li>https://medium.com/message/everything-is-broken-81e5f33a24e1. Everything Is Broken. Some of the (probable) truths about our world.</li>
79</ul>
80<h2 id="funny"><a class="anchor" href="#funny">¶</a>Funny</h2>
81<ul>
82<li>http://thedailywtf.com/articles/We-Use-BobX. We Use BobX. BobX.</li>
83<li>http://thedailywtf.com/articles/the-inner-json-effect. The Inner JSON Effect. For some reason, custom languages are in.</li>
84<li>https://thedailywtf.com/articles/exponential-backup. Exponential Backup. Far better than git.</li>
85<li>https://thedailywtf.com/articles/ITAPPMONROBOT. ITAPPMONROBOT. Solving software problems with hardware.</li>
86<li>https://thedailywtf.com/articles/a-tapestry-of-threads. A Tapestry of Threads.More threads must mean faster code, right?</li>
87<li>https://medium.com/commitlog/a-brief-totally-accurate-history-of-programming-languages-cd93ec806124. A Brief Totally Accurate History Of Programming Languages. Don't take offense for it!</li>
88</ul>
89<h2 id="graphics"><a class="anchor" href="#graphics">¶</a>Graphics</h2>
90<ul>
91<li>http://shaunlebron.github.io/visualizing-projections/. Visualizing Projections. Small post about different projection methods.</li>
92<li>http://www.iquilezles.org/www/index.htm. A <em>lot</em> of useful and quality articles regarding computer graphics.</li>
93</ul>
94<h2 id="history"><a class="anchor" href="#history">¶</a>History</h2>
95<ul>
96<li>https://twobithistory.org/2018/08/18/ada-lovelace-note-g.html. What Did Ada Lovelace's Program Actually Do?. And other characters that took part in the beginning's of programming.</li>
97<li>https://chrisdown.name/2018/01/02/in-defence-of-swap.html. In defence of swap: common misconceptions. Swap is still an useful concept.</li>
98<li>https://www.pacifict.com/Story/. The Graphing Calculator Story. A great classic Apple tale.</li>
99<li>https://twobithistory.org/2018/10/14/lisp.html. How Lisp Became God's Own Programming Language. Lisp as a foundational programming language.</li>
100</ul>
101<h2 id="motivational"><a class="anchor" href="#motivational">¶</a>Motivational</h2>
102<ul>
103<li>https://www.joelonsoftware.com/2002/01/06/fire-and-motion/. Fire And Motion. What does actually take to get things done?</li>
104<li>https://realmensch.org/2017/08/25/the-parable-of-the-two-programmers/. The Parable of the Two Programmers. This tale is about two different types of programmer and their respective endings in a company, illustrating how the one you wouldn't expect to actually ends in a better situation.</li>
105<li>https://byorgey.wordpress.com/2018/05/06/conversations-with-a-six-year-old-on-functional-programming/. Conversations with a six-year-old on functional programming. Little kids today can be really interested in technological topics.</li>
106<li>https://bulletproofmusician.com/how-many-hours-a-day-should-you-practice/. How Many Hours a Day Should You Practice?. While the article is about music, it applies to any other areas.</li>
107<li>http://nathanmarz.com/blog/suffering-oriented-programming.html. Suffering-oriented programming. A possibly new approach on how you could tackle your new projects.</li>
108<li>https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/. Things You Should Never Do, Part I. There is no need to rewrite your code.</li>
109</ul>
110<h2 id="optimization"><a class="anchor" href="#optimization">¶</a>Optimization</h2>
111<ul>
112<li>http://blog.llvm.org/2011/05/what-every-c-programmer-should-know.html. What Every C Programmer Should Know About Undefined Behavior #1/3. Explains what undefined behaviour is and why it makes sense.</li>
113<li>http://ridiculousfish.com/blog/posts/labor-of-division-episode-i.html. Labor of Division (Episode I). Some tricks to divide without division.</li>
114<li>http://blog.moertel.com/posts/2013-12-14-great-old-timey-game-programming-hack.html. A Great Old-Timey Game-Programming Hack. Abusing instructions to make games playable even on the slowest hardware.</li>
115<li>https://web.archive.org/web/20191213224640/https://people.eecs.berkeley.edu/~sangjin/2012/12/21/epoll-vs-kqueue.html. Scalable Event Multiplexing: epoll vs kqueue. How good OS primitives can really help performance and scability.</li>
116<li>https://adamdrake.com/command-line-tools-can-be-235x-faster-than-your-hadoop-cluster.html. Command-line Tools can be 235x Faster than your Hadoop Cluster. Or how to use the right tool for the right job.</li>
117<li>https://nullprogram.com/blog/2018/05/27/. When FFI Function Calls Beat Native C. How lua beat C at it and the explanation behind it.</li>
118<li>http://igoro.com/archive/gallery-of-processor-cache-effects/. Gallery of Processor Cache Effects. Knowing a few things about the cache can make a big difference.</li>
119</ul>
120</main>
121</body>
122</html>
123 </content></entry><entry><title>Python ctypes and Windows</title><id>dist/ctypes-and-windows/index.html</id><updated>2020-07-02T22:00:00+00:00</updated><published>2019-06-18T22:00:00+00:00</published><summary>Python</summary><content type="html" src="dist/ctypes-and-windows/index.html"><!DOCTYPE html>
124<html>
125<head>
126<meta charset="utf-8" />
127<meta name="viewport" content="width=device-width, initial-scale=1" />
128<title>Python ctypes and Windows</title>
129<link rel="stylesheet" href="../css/style.css">
130</head>
131<body>
132<main>
133<h1 class="title" id="python_ctypes_and_windows"><a class="anchor" href="#python_ctypes_and_windows">¶</a>Python ctypes and Windows</h1>
134<div class="date-created-modified">Created 2019-06-19<br>
135Modified 2020-07-03</div>
136<p><a href="https://www.python.org/">Python</a>'s <a href="https://docs.python.org/3/library/ctypes.html"><code>ctypes</code></a> is quite a nice library to easily load and invoke C methods available in already-compiled <a href="https://en.wikipedia.org/wiki/Dynamic-link_library"><code>.dll</code> files</a> without any additional dependencies. And I <em>love</em> depending on as little as possible.</p>
137<p>In this blog post, we will walk through my endeavors to use <code>ctypes</code> with the <a href="https://docs.microsoft.com/en-us/windows/desktop/api/">Windows API</a>, and do some cool stuff with it.</p>
138<p>We will assume some knowledge of C/++ and Python, since we will need to read and write a bit of both. Please note that this post is only an introduction to <code>ctypes</code>, and if you need more information you should consult the <a href="https://docs.python.org/3/library/ctypes.html">Python's documentation for <code>ctypes</code></a>.</p>
139<p>While the post focuses on Windows' API, the code here probably applies to unix-based systems with little modifications.</p>
140<h2 id="basics"><a class="anchor" href="#basics">¶</a>Basics</h2>
141<p>First of all, let's learn how to load a library. Let's say we want to load <code>User32.dll</code>:</p>
142<pre><code class="language-python">import ctypes
143
144ctypes.windll.user32
145</code></pre>
146<p>Yes, it's that simple. When you access an attribute of <code>windll</code>, said library will load. Since Windows is case-insensitive, we will use lowercase consistently.</p>
147<p>Calling a function is just as simple. Let's say you want to call <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-setcursorpos"><code>SetCursorPos</code></a>, which is defined as follows:</p>
148<pre><code class="language-c">BOOL SetCursorPos(
149 int X,
150 int Y
151);
152</code></pre>
153<p>Okay, it returns a <code>bool</code> and takes two inputs, <code>x</code> and <code>y</code>. So we can call it like so:</p>
154<pre><code class="language-python">ctypes.windll.user32.SetCursorPos(100, 100)
155</code></pre>
156<p>Try it! Your cursor will move!</p>
157<h2 id="funky_stuff"><a class="anchor" href="#funky_stuff">¶</a>Funky Stuff</h2>
158<p>We can go a bit more crazy and make it form a spiral:</p>
159<pre><code class="language-python">import math
160import time
161
162for i in range(200):
163 x = int(500 + math.cos(i / 5) * i)
164 y = int(500 + math.sin(i / 5) * i)
165 ctypes.windll.user32.SetCursorPos(x, y)
166 time.sleep(0.05)
167</code></pre>
168<p>Ah, it's always so pleasant to do random stuff when programming. Sure makes it more fun.</p>
169<h2 id="complex_structures"><a class="anchor" href="#complex_structures">¶</a>Complex Structures</h2>
170<p><code>SetCursorPos</code> was really simple. It took two parameters and they both were integers. Let's go with something harder. Let's go with <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-sendinput"><code>SendInput</code></a>! Emulating input will be a fun exercise:</p>
171<pre><code class="language-c">UINT SendInput(
172 UINT cInputs,
173 LPINPUT pInputs,
174 int cbSize
175);
176</code></pre>
177<p>Okay, <code>LPINPUT</code>, what are you? Microsoft likes to prefix types with what they are. In this case, <code>LP</code> stands for &quot;Long Pointer&quot; (I guess?), so <code>LPINPUT</code> is just a Long Pointer to <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winuser/ns-winuser-taginput"><code>INPUT</code></a>:</p>
178<pre><code class="language-c">typedef struct tagINPUT {
179 DWORD type;
180 union {
181 MOUSEINPUT mi;
182 KEYBDINPUT ki;
183 HARDWAREINPUT hi;
184 } DUMMYUNIONNAME;
185} INPUT, *PINPUT, *LPINPUT;
186</code></pre>
187<p>Alright, that's new. We have a <code>struct</code> and <code>union</code>, two different concepts. We can define both with <code>ctypes</code>:</p>
188<pre><code class="language-python">INPUT_MOUSE = 0
189INPUT_KEYBOARD = 1
190INPUT_HARDWARE = 2
191
192class INPUT(ctypes.Structure):
193 _fields_ = [
194 ('type', ctypes.c_long),
195 ...
196 ]
197</code></pre>
198<p>Structures are classes that subclass <code>ctypes.Structure</code>, and you define their fields in the <code>_fields_</code> class-level variable, which is a list of tuples <code>(field name, field type)</code>.</p>
199<p>The C structure had a <code>DWORD type</code>. <code>DWORD</code> is a <code>c_long</code>, and <code>type</code> is a name like any other, which is why we did <code>('type', ctypes.c_long)</code>.</p>
200<p>But what about the union? It's anonymous, and we can't make anonymous unions (<em>citation needed</em>) with <code>ctypes</code>. We will give it a concrete name and a type.</p>
201<p>Before defining the union, we need to define its inner structures, <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winuser/ns-winuser-tagmouseinput"><code>MOUSEINPUT</code></a>, <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winuser/ns-winuser-tagkeybdinput"><code>KEYBDINPUT</code></a> and <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winuser/ns-winuser-taghardwareinput"><code>HARDWAREINPUT</code></a>. We won't be using them all, but since they count towards the final struct size (C will choose the largest structure as the final size), we need them, or Windows' API will get confused and refuse to work (personal experience):</p>
202<pre><code class="language-python">class MOUSEINPUT(ctypes.Structure):
203 _fields_ = [
204 ('dx', ctypes.c_long),
205 ('dy', ctypes.c_long),
206 ('mouseData', ctypes.c_long),
207 ('dwFlags', ctypes.c_long),
208 ('time', ctypes.c_long),
209 ('dwExtraInfo', ctypes.POINTER(ctypes.c_ulong))
210 ]
211
212
213class KEYBDINPUT(ctypes.Structure):
214 _fields_ = [
215 ('wVk', ctypes.c_short),
216 ('wScan', ctypes.c_short),
217 ('dwFlags', ctypes.c_long),
218 ('time', ctypes.c_long),
219 ('dwExtraInfo', ctypes.POINTER(ctypes.c_ulong))
220 ]
221
222
223class HARDWAREINPUT(ctypes.Structure):
224 _fields_ = [
225 ('uMsg', ctypes.c_long),
226 ('wParamL', ctypes.c_short),
227 ('wParamH', ctypes.c_short)
228 ]
229
230
231class INPUTUNION(ctypes.Union):
232 _fields_ = [
233 ('mi', MOUSEINPUT),
234 ('ki', KEYBDINPUT),
235 ('hi', HARDWAREINPUT)
236 ]
237
238
239class INPUT(ctypes.Structure):
240 _fields_ = [
241 ('type', ctypes.c_long),
242 ('value', INPUTUNION)
243 ]
244</code></pre>
245<p>Some things to note:</p>
246<ul>
247<li>Pointers are defined as <code>ctypes.POINTER(inner type)</code>.</li>
248<li>The field names can be anything you want. You can make them more &quot;pythonic&quot; if you want (such as changing <code>dwExtraInfo</code> for just <code>extra_info</code>), but I chose to stick with the original naming.</li>
249<li>The union is very similar, but it uses <code>ctypes.Union</code> instead of <code>ctypes.Structure</code>.</li>
250<li>We gave a name to the anonymous union, <code>INPUTUNION</code>, and used it inside <code>INPUT</code> with also a made-up name, <code>('value', INPUTUNION)</code>.</li>
251</ul>
252<p>Now that we have all the types we need defined, we can use them:</p>
253<pre><code class="language-python">KEYEVENTF_KEYUP = 0x0002
254
255def press(vk, down):
256 inputs = INPUT(type=INPUT_KEYBOARD, value=INPUTUNION(ki=KEYBDINPUT(
257 wVk=vk,
258 wScan=0,
259 dwFlags=0 if down else KEYEVENTF_KEYUP,
260 time=0,
261 dwExtraInfo=None
262 )))
263 ctypes.windll.user32.SendInput(1, ctypes.byref(inputs), ctypes.sizeof(inputs))
264
265
266for char in 'HELLO':
267 press(ord(char), down=True)
268 press(ord(char), down=False)
269</code></pre>
270<p>Run it! It will press and release the keys <code>hello</code> to type the word <code>&quot;hello&quot;</code>!</p>
271<p><code>vk</code> stands for &quot;virtual key&quot;. Letters correspond with their upper-case ASCII value, which is what we did above. You can find all the available keys in the page with all the <a href="https://docs.microsoft.com/en-us/windows/desktop/inputdev/virtual-key-codes">Virtual Key Codes</a>.</p>
272<h2 id="dynamic_inputs_and_pointers"><a class="anchor" href="#dynamic_inputs_and_pointers">¶</a>Dynamic Inputs and Pointers</h2>
273<p>What happens if a method wants something by reference? That is, a pointer to your thing? For example, <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-getcursorpos"><code>GetCursorPos</code></a>:</p>
274<pre><code class="language-c">typedef struct tagPOINT {
275 LONG x;
276 LONG y;
277} POINT, *PPOINT, *NPPOINT, *LPPOINT;
278
279BOOL GetCursorPos(
280 LPPOINT lpPoint
281);
282</code></pre>
283<p>It wants a Long Pointer to <a href="https://docs.microsoft.com/en-us/windows/desktop/api/windef/ns-windef-point"><code>POINT</code></a>. We can do just that with <code>ctypes.byref</code>:</p>
284<pre><code class="language-python">class POINT(ctypes.Structure):
285 _fields_ = [
286 ('x', ctypes.c_long),
287 ('y', ctypes.c_long)
288 ]
289
290
291def get_mouse():
292 point = POINT()
293 ctypes.windll.user32.GetCursorPos(ctypes.byref(point))
294 # pass our point by ref ^^^^^
295 # this lets GetCursorPos fill its x and y fields
296
297 return point.x, point.y
298
299
300while True:
301 print(get_mouse())
302 time.sleep(0.05)
303</code></pre>
304<p>Now you can track the mouse position! Make sure to <code>Ctrl+C</code> the program when you're tired of it.</p>
305<p>What happens if a method wants a dynamically-sized input?</p>
306<pre><code class="language-python">buffer = ctypes.create_string_buffer(size)
307</code></pre>
308<p>In that case, you can create an in-memory <code>buffer</code> of <code>size</code> with <code>ctypes.create_string_buffer</code>. It will return a character array of that size, which you can pass as a pointer directly (without <code>ctypes.byref</code>).</p>
309<p>To access the buffer's contents, you can use either <code>.raw</code> or <code>.value</code>:</p>
310<pre><code class="language-python">entire_buffer_as_bytes = buffer.raw
311up_until_null = buffer.value
312</code></pre>
313<p>When the method fills in the data, you can <code>cast</code> your buffer back into a pointer of a concrete type:</p>
314<pre><code class="language-python">result_ptr = ctypes.cast(buffer, ctypes.POINTER(ctypes.c_long))
315</code></pre>
316<p>And you can de-reference pointers with <code>.contents</code>:</p>
317<pre><code class="language-python">first_result = result_ptr.contents
318</code></pre>
319<h2 id="arrays"><a class="anchor" href="#arrays">¶</a>Arrays</h2>
320<p>Arrays are defined as <code>type * size</code>. Your linter may not like that, and if you don't know the size beforehand, consider creating a 0-sized array. For example:</p>
321<pre><code class="language-python"># 10 longs
322ten_longs = (ctypes.c_long * 10)()
323for i in range(10):
324 ten_longs[i] = 2 ** i
325
326# Unknown size of longs, e.g. inside some Structure
327longs = (ctypes.c_long * 0)
328
329# Now you know how many longs it actually was
330known_longs = ctypes.cast(
331 ctypes.byref(longs),
332 ctypes.POINTER(ctypes.c_long * size)
333).contents
334</code></pre>
335<p>If there's a better way to initialize arrays, please let me know.</p>
336<h2 id="wintypes"><a class="anchor" href="#wintypes">¶</a>wintypes</h2>
337<p>Under Windows, the <code>ctypes</code> module has a <code>wintypes</code> submodule. This one contains definitions like <code>HWND</code> which may be useful and can be imported as:</p>
338<pre><code class="language-python">from ctypes.wintypes import HWND, LPCWSTR, UINT
339</code></pre>
340<h2 id="callbacks"><a class="anchor" href="#callbacks">¶</a>Callbacks</h2>
341<p>Some functions (I'm looking at you, <a href="https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-enumwindows"><code>EnumWindows</code></a>) ask us to pass a callback. In this case, it wants a <a href="https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/ms633498(v=vs.85)"><code>EnumWindowsProc</code></a>:</p>
342<pre><code class="language-c">BOOL EnumWindows(
343 WNDENUMPROC lpEnumFunc,
344 LPARAM lParam
345);
346
347BOOL CALLBACK EnumWindowsProc(
348 _In_ HWND hwnd,
349 _In_ LPARAM lParam
350);
351</code></pre>
352<p>The naive approach won't work:</p>
353<pre><code class="language-python">def callback(hwnd, lParam):
354 print(hwnd)
355 return True
356
357ctypes.windll.user32.EnumWindows(callback, 0)
358# ctypes.ArgumentError: argument 1: &lt;class 'TypeError'&gt;: Don't know how to convert parameter 1
359# Aww.
360</code></pre>
361<p>Instead, you must wrap your function as a C definition like so:</p>
362<pre><code class="language-python">from ctypes.wintypes import BOOL, HWND, LPARAM
363
364EnumWindowsProc = ctypes.WINFUNCTYPE(BOOL, HWND, LPARAM)
365
366def callback(hwnd, lParam):
367 print(hwnd)
368 return True
369
370# Wrap the function in the C definition
371callback = EnumWindowsProc(callback)
372
373ctypes.windll.user32.EnumWindows(callback, 0)
374# Yay, it works.
375</code></pre>
376<p>You may have noticed this is what decorators do, wrap the function. So…</p>
377<pre><code class="language-python">from ctypes.wintypes import BOOL, HWND, LPARAM
378
379@ctypes.WINFUNCTYPE(BOOL, HWND, LPARAM)
380def callback(hwnd, lParam):
381 print(hwnd)
382 return True
383
384ctypes.windll.user32.EnumWindows(callback, 0)
385</code></pre>
386<p>…will also work. And it is a <em>lot</em> fancier.</p>
387<h2 id="closing_words"><a class="anchor" href="#closing_words">¶</a>Closing Words</h2>
388<p>With the knowledge above and some experimentation, you should be able to call and do (almost) anything you want. That was pretty much all I needed on my project anyway :)</p>
389<p>We have been letting Python convert Python values into C values, but you can do so explicitly too. For example, you can use <code>ctypes.c_short(17)</code> to make sure to pass that <code>17</code> as a <code>short</code>. And if you have a <code>c_short</code>, you can convert or cast it to its Python <code>.value</code> as <code>some_short.value</code>. The same applies for integers, longs, floats, doubles… pretty much anything, char pointers (strings) included.</p>
390<p>If you can't find something in their online documentation, you can always <a href="https://github.com/BurntSushi/ripgrep"><code>rg</code></a> for it in the <code>C:\Program Files (x86)\Windows Kits\10\Include\*</code> directory.</p>
391<p>Note that the <code>ctypes.Structure</code>'s that you define can have more methods of your own. For example, you can write them a <code>__str__</code> to easily view its fields, or define a <code>@property</code> to re-interpret some data in a meaningful way.</p>
392<p>For enumerations, you can pass just the right integer number, make a constant for it, or if you prefer, use a <a href="https://docs.python.org/3/library/enum.html#enum.IntEnum"><code>enum.IntEnum</code></a>. For example, <a href="https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism/dismloglevel-enumeration"><code>DismLogLevel</code></a> would be:</p>
393<pre><code class="language-python">class DismLogLevel(enum.IntEnum):
394 DismLogErrors = 0
395 DismLogErrorsWarnings = 1
396 DismLogErrorsWarningsInfo = 2
397</code></pre>
398<p>And you <em>should</em> be able to pass <code>DismLogLevel.DismLogErrors</code> as the parameter now.</p>
399<p>If you see a function definition like <code>Function(void)</code>, that's C's way of saying it takes no parameters, so just call it as <code>Function()</code>.</p>
400<p>Make sure to pass all parameters, even if they seem optional they probably still want a <code>NULL</code> at least, and of course, read the documentation well. Some methods have certain pre-conditions.</p>
401<p>Have fun hacking!</p>
402</main>
403</body>
404</html>
405 </content></entry><entry><title>Shattered Pixel Dungeon</title><id>dist/pixel-dungeon/index.html</id><updated>2020-07-02T22:00:00+00:00</updated><published>2019-06-02T22:00:00+00:00</published><summary>Shattered Pixel Dungeon</summary><content type="html" src="dist/pixel-dungeon/index.html"><!DOCTYPE html>
406<html>
407<head>
408<meta charset="utf-8" />
409<meta name="viewport" content="width=device-width, initial-scale=1" />
410<title>Shattered Pixel Dungeon</title>
411<link rel="stylesheet" href="../css/style.css">
412</head>
413<body>
414<main>
415<h1 class="title" id="shattered_pixel_dungeon"><a class="anchor" href="#shattered_pixel_dungeon">¶</a>Shattered Pixel Dungeon</h1>
416<div class="date-created-modified">Created 2019-06-03<br>
417Modified 2020-07-03</div>
418<p><a href="https://shatteredpixel.com/shatteredpd/">Shattered Pixel Dungeon</a> is the classic roguelike RPG game with randomly-generated dungeons. As a new player, it was a bit frustrating to be constantly killed on the first levels of the dungeon, but with some practice it's easy to reach high levels if you can kill the first boss.</p>
419<h2 id="basic_tips"><a class="anchor" href="#basic_tips">¶</a>Basic Tips</h2>
420<p>The game comes with its own tips, but here's a short and straight-forward summary:</p>
421<ul>
422<li><strong>Don't rush into enemies</strong>. Abuse doors and small corridors to kill them one by one. You can use the clock on the bottom left to wait a turn without moving.</li>
423<li><strong>Explore each level at full</strong>. You will find goodies and gain XP while doing so.</li>
424<li><strong>Upon finding a special room</strong> (e.g. has a chest but is protected by piranhas), drink all potions that you found in that level until there's one that helps you (e.g. be invisible so piranhas leave you alone). There is guaranteed to be a helpful one per level with special rooms.</li>
425<li><strong>Drink potions as early as possible</strong>. Harmful potions do less damage on early levels (and if you die, you lose less). This will keep them identified early for the rest of the game.</li>
426<li><strong>Read scrolls as early as possible</strong> as well. This will keep them identified. It may be worth to wait until you have an item which may be cursed and until the level is clear, because some scrolls clean curses and others alert enemies.</li>
427<li><strong>Food and health are resources</strong> that you have to <em>manage</em>, not keep them always at full. Even if you are starving and taking damage, you may not need to eat <em>just yet</em>, since food is scarce. Eat when you are low on health or in possible danger.</li>
428<li><strong>Piranhas</strong>. Seriously, just leave them alone if you are melee. They're free food if you're playing ranged, though.</li>
429<li><strong>Prefer armor over weapons</strong>. And make sure to identify or clean it from curses before wearing anything!</li>
430<li><strong>Find a dew vial early</strong>. It's often a better idea to store dew (health) for later than to use it as soon as possible.</li>
431</ul>
432<h2 id="bosses"><a class="anchor" href="#bosses">¶</a>Bosses</h2>
433<p>There is a boss every 5 levels.</p>
434<ul>
435<li><strong>Level 5 boss</strong>. Try to stay on water, but don't let <em>it</em> stay on water since it will heal. Be careful when he starts enraging.</li>
436<li><strong>Level 10 boss</strong>. Ranged weapons are good against it.</li>
437<li><strong>Level 15 boss</strong>. I somehow managed to tank it with a health potion.</li>
438<li><strong>Level 20 boss</strong>. I didn't get this far just yet. You are advised to use scrolls of magic mapping in the last levels to skip straight to the boss, since there's nothing else of value.</li>
439<li><strong>Level 25 boss</strong>. The final boss. Good job if you made it this far!</li>
440</ul>
441<h2 id="mage"><a class="anchor" href="#mage">¶</a>Mage</h2>
442<p>If you followed the basic tips, you will sooner or later make use of two scrolls of upgrade in a single run. This will unlock the mage class, which is ridiculously powerful. He starts with a ranged-weapon, a magic missile wand, which is really helpful to keep enemies at a distance. Normally, you want to use this at first to surprise attack them soon, and if you are low on charges, you may go melee on normal enemies if you are confident.</p>
443<h2 id="luck"><a class="anchor" href="#luck">¶</a>Luck</h2>
444<p>This game is all about luck and patience! Some runs will be better than others, and you should thank and pray the RNG gods for them. If you don't, they will only give you cursed items and not a single scroll to clean them. So, good luck and enjoy playing!</p>
445</main>
446</body>
447</html>
448 </content></entry><entry><title>Breaking Risk of Rain</title><id>dist/breaking-ror/index.html</id><updated>2020-07-02T22:00:00+00:00</updated><published>2019-01-11T23:00:00+00:00</published><summary>Risk of Rain</summary><content type="html" src="dist/breaking-ror/index.html"><!DOCTYPE html>
449<html>
450<head>
451<meta charset="utf-8" />
452<meta name="viewport" content="width=device-width, initial-scale=1" />
453<title>Breaking Risk of Rain</title>
454<link rel="stylesheet" href="../css/style.css">
455</head>
456<body>
457<main>
458<h1 class="title" id="breaking_risk_of_rain"><a class="anchor" href="#breaking_risk_of_rain">¶</a>Breaking Risk of Rain</h1>
459<div class="date-created-modified">Created 2019-01-12<br>
460Modified 2020-07-03</div>
461<p><a href="https://riskofraingame.com/">Risk of Rain</a> is a fun little game you can spend a lot of hours on. It's incredibly challenging for new players, and fun once you have learnt the basics. This blog will go through what I've learnt and how to play the game correctly.</p>
462<h2 id="getting_started"><a class="anchor" href="#getting_started">¶</a>Getting Started</h2>
463<p>If you're new to the game, you may find it frustrating. You must learn very well to dodge.</p>
464<p>Your first <a href="http://riskofrain.wikia.com/wiki/Category:Characters">character</a> will be <a href="http://riskofrain.wikia.com/wiki/Commando">Commando</a>. He's actually a very nice character. Use your third skill (dodge) to move faster, pass through large groups of enemies, and negate fall damage.</p>
465<p>If there are a lot of monsters, remember to <strong>leave</strong> from there! It's really important for survival. Most enemies <strong>don't do body damage</strong>. Not even the body of the <a href="http://riskofrain.wikia.com/wiki/Magma_Worm">Magma Worm</a> or the <a href="http://riskofrain.wikia.com/wiki/Wandering_Vagrant">Wandering Vagrant</a> (just dodge the head and projectiles respectively).</p>
466<p>The first thing you must do is always <strong>rush for the teleporter</strong>. Completing the levels quick will make the game easier. But make sure to take note of <strong>where the chests are</strong>! When you have time (even when the countdown finishes), go back for them and buy as many as you can. Generally, prefer <a href="http://riskofrain.wikia.com/wiki/Chest">chests</a> over <a href="http://riskofrain.wikia.com/wiki/Shrine">shrines</a> since they may eat all your money.</p>
467<p>Completing the game on <a href="http://riskofrain.wikia.com/wiki/Difficulty">Drizzle</a> is really easy if you follow these tips.</p>
468<h2 id="requisites"><a class="anchor" href="#requisites">¶</a>Requisites</h2>
469<p>Before breaking the game, you must obtain several <a href="http://riskofrain.wikia.com/wiki/Item#Artifacts">artifacts</a>. We are interested in particular in the following:</p>
470<ul>
471<li><a href="http://riskofrain.wikia.com/wiki/Sacrifice">Sacrifice</a>. You really need this one, and may be a bit hard to get. With it, you will be able to farm the first level for 30 minutes and kill the final boss in 30 seconds.</li>
472<li><a href="http://riskofrain.wikia.com/wiki/Command">Command</a>. You need this unless you want to grind for hours to get enough of the items you really need for the rest of the game. Getting this one is easy.</li>
473<li><a href="http://riskofrain.wikia.com/wiki/Glass">Glass</a>. Your life will be very small (at the beginning…), but you will be able to one-shot everything easily.</li>
474<li><a href="http://riskofrain.wikia.com/wiki/Kin">Kin</a> (optional). It makes it easier to obtain a lot of boxes if you restart the first level until you get <a href="http://riskofrain.wikia.com/wiki/Lemurian">lemurians</a> or <a href="http://riskofrain.wikia.com/wiki/Jellyfish">jellyfish</a> as the monster, since they're cheap to spawn.</li>
475</ul>
476<p>With those, the game becomes trivial. Playing as <a href="http://riskofrain.wikia.com/wiki/Huntress">Huntress</a> is excellent since she can move at high speed while killing everything on screen.</p>
477<h2 id="breaking_the_game"><a class="anchor" href="#breaking_the_game">¶</a>Breaking the Game</h2>
478<p>The rest is easy! With the command artifact you want the following items.</p>
479<h3 id="<a href="http://riskofrain.wikia.com/wiki/Category:Common_Items">common_items"><a class="anchor" href="#common_items">¶</a>Common Items</a></h3>
480<ul>
481<li><a href="http://riskofrain.wikia.com/wiki/Soldier&#x27;s_Syringe">Soldier's Syringe</a>. <strong>Stack 13</strong> of these and you will triple your attack speed. You can get started with 4 or so.</li>
482<li><a href="http://riskofrain.wikia.com/wiki/Paul&#x27;s_Goat_Hoof">Paul's Goat Hoof</a>. <strong>Stack +30</strong> of these and your movement speed will be insane. You can get a very good speed with 8 or so.</li>
483<li><a href="http://riskofrain.wikia.com/wiki/Crowbar">Crowbar</a>. <strong>Stack +20</strong> to guarantee you can one-shot bosses.</li>
484</ul>
485<p>If you want to be safer:</p>
486<ul>
487<li><a href="http://riskofrain.wikia.com/wiki/Hermit&#x27;s_Scarf">Hermit's Scarf</a>. <strong>Stack 6</strong> of these to dodge 1/3 of the attacks.</li>
488<li><a href="http://riskofrain.wikia.com/wiki/Monster_Tooth">Monster Tooth</a>. <strong>Stack 9</strong> of these to recover 50 life on kill. This is plenty, since you will be killing <em>a lot</em>.</li>
489</ul>
490<p>If you don't have enough and want more fun, get one of these:</p>
491<ul>
492<li><a href="http://riskofrain.wikia.com/wiki/Gasoline">Gasoline</a>. Burn the ground on kill, and more will die!</li>
493<li><a href="http://riskofrain.wikia.com/wiki/Headstompers">Headstompers</a>. They make a pleasing sound on fall, and hurt.</li>
494<li><a href="http://riskofrain.wikia.com/wiki/Lens-Maker&#x27;s_Glasses">Lens-Maker's Glasses</a>. <strong>Stack 14</strong> and you will always deal a critical strike for double the damage.</li>
495</ul>
496<h3 id="<a href="http://riskofrain.wikia.com/wiki/Category:Uncommon_Items">uncommon_items"><a class="anchor" href="#uncommon_items">¶</a>Uncommon Items</a></h3>
497<ul>
498<li><a href="http://riskofrain.wikia.com/wiki/Infusion">Infusion</a>. You only really need one of this. Your life will skyrocket after a while, since this gives you 1HP per kill.</li>
499<li><a href="http://riskofrain.wikia.com/wiki/Hopoo_Feather">Hopoo Feather</a>. <strong>Stack +10</strong> of these. You will pretty much be able to fly with so many jumps.</li>
500<li><a href="http://riskofrain.wikia.com/wiki/Guardian&#x27;s_Heart">Guardian's Heart</a>. Not really necessary, but useful for early and late game, since it will absorb infinite damage the first hit.</li>
501</ul>
502<p>If, again, you want more fun, get one of these:</p>
503<ul>
504<li><a href="http://riskofrain.wikia.com/wiki/Ukulele">Ukelele</a>. Spazz your enemies!</li>
505<li><a href="http://riskofrain.wikia.com/wiki/Will-o&#x27;-the-wisp">Will-o'-the-wisp</a>. Explode your enemies!</li>
506<li><a href="http://riskofrain.wikia.com/wiki/Chargefield_Generator">Chargefield Generator</a>. It should cover your entire screen after a bit, hurting all enemies without moving a finger.</li>
507<li><a href="http://riskofrain.wikia.com/wiki/Golden_Gun">Golden Gun</a>. You will be rich, so this gives you +40% damage.</li>
508<li><a href="http://riskofrain.wikia.com/wiki/Predatory_Instincts">Predatory Instincts</a>. If you got 14 glasses, you will always be doing critical strikes, and this will give even more attack speed.</li>
509<li><a href="http://riskofrain.wikia.com/wiki/56_Leaf_Clover">56 Leaf Clover</a>. More drops, in case you didn't have enough.</li>
510</ul>
511<h3 id="<a href="http://riskofrain.wikia.com/wiki/Category:Rare_Items">rare_items"><a class="anchor" href="#rare_items">¶</a>Rare Items</a></h3>
512<ul>
513<li><a href="http://riskofrain.wikia.com/wiki/Ceremonial_Dagger">Ceremonial Dagger</a>. <strong>Stack +3</strong>, then killing one thing kills another thing and makes a chain reaction.</li>
514<li><a href="http://riskofrain.wikia.com/wiki/Alien_Head">Alien Head</a>. <strong>Stack 3</strong>, and you will be able to use your abilities more often.</li>
515</ul>
516<p>For more fun:</p>
517<ul>
518<li><a href="http://riskofrain.wikia.com/wiki/Brilliant_Behemoth">Brilliant Behemoth</a>. Boom boom.</li>
519</ul>
520<h2 id="closing_words"><a class="anchor" href="#closing_words">¶</a>Closing Words</h2>
521<p>You can now beat the game in Monsoon solo with any character. Have fun! And be careful with the sadly common crashes.</p>
522</main>
523</body>
524</html>
525 </content></entry><entry><title>My new computer</title><id>dist/new-computer/index.html</id><updated>2020-06-21T22:00:00+00:00</updated><published>2020-06-18T22:00:00+00:00</published><summary>This post will be mostly me ranting about setting up a new laptop, but I also just want to share my upgrade. If you're considering installing Arch Linux with dual-boot for Windows, maybe this post will help. Or perhaps you will learn something new to troubleshoot systems in the future. Let's begin!</summary><content type="html" src="dist/new-computer/index.html"><!DOCTYPE html>
526<html>
527<head>
528<meta charset="utf-8" />
529<meta name="viewport" content="width=device-width, initial-scale=1" />
530<title>My new computer</title>
531<link rel="stylesheet" href="../css/style.css">
532</head>
533<body>
534<main>
535<h1 class="title" id="my_new_computer"><a class="anchor" href="#my_new_computer">¶</a>My new computer</h1>
536<div class="date-created-modified">Created 2020-06-19<br>
537Modified 2020-06-22</div>
538<p>This post will be mostly me ranting about setting up a new laptop, but I also just want to share my upgrade. If you're considering installing Arch Linux with dual-boot for Windows, maybe this post will help. Or perhaps you will learn something new to troubleshoot systems in the future. Let's begin!</p>
539<p>Last Sunday, I ordered a Asus Rog Strix G531GT-BQ165 for 900€ (on a 20% discount) with the following specifications:</p>
540<ul>
541<li>Intel® Core i7-9750H (6 cores, 12MB cache, 2.6GHz up to 4.5GHz, 64-bit)</li>
542<li>16GB RAM (8GB*2) DDR4 2666MHz</li>
543<li>512GB SSD M.2 PCIe® NVMe</li>
544<li>Display 15.6&quot; (1920x1080/16:9) 60Hz</li>
545<li>Graphics NVIDIA® GeForce® GTX1650 4GB GDDR5 VRAM</li>
546<li>LAN 10/100/1000</li>
547<li>Wi-Fi 5 (802.11ac) 2x2 RangeBoost</li>
548<li>Bluetooth 5.0</li>
549<li>48Wh battery with 3 cells</li>
550<li>3 x USB 3.1 (GEN1)</li>
551</ul>
552<p>I was mostly interested in a general upgrade (better processor, disk, more RAM), although the graphics card is a really nice addition which will allow me to take some time off on more games. After using it for a bit, I really love the feel of the keyboard, and I love the lack of numpad! (No sarcasm, I really don't like numpads.)</p>
553<p>This is an upgrade from my previous laptop (Asus X554LA-XX822T), which I won in a competition before entering university in a programming challenge. It has served me really well for the past five years, and had the following specifications:</p>
554<ul>
555<li>Intel® Core™ i5-5200U</li>
556<li>4GB RAM DDR3L 1600MHz (which I upgraded to have 8GB)</li>
557<li>1TB HDD</li>
558<li>Display 15.6&quot; (1366x768/16:9)</li>
559<li>Intel® HD Graphics 4400</li>
560<li>LAN 10/100/1000</li>
561<li>Wifi 802.11 bgn</li>
562<li>Bluetooth 4.0</li>
563<li>Battery 2 cells</li>
564<li>1 x USB 2.0</li>
565<li>2 x USB 3.0</li>
566</ul>
567<p>Prior to this one, I had a Lenovo (also won in the same competition of the previous year), and prior to that (just for the sake of history), it was HP Pavilion, AMD A4-3300M processor, which unfortunately ended with heating problems. But that's very old now.</p>
568<h2 id="laptop_arrival"><a class="anchor" href="#laptop_arrival">¶</a>Laptop arrival</h2>
569<p>The laptop arrived 2 days ago at roughly 19:00, which I put charged for 3 hours as the book said. The day after, nightmares began!</p>
570<p>Trying to boot it the first two times was fun, as it comes with a somewhat loud sound on boot. I don't know why they would do this, and I immediately turned it off in the BIOS.</p>
571<h2 id="installation_journey"><a class="anchor" href="#installation_journey">¶</a>Installation journey</h2>
572<p>I spent all of yesterday trying to setup Windows and Arch Linux (and didn't even finish, it took me this morning too and even now it's only half functional). I absolutely <em>hate</em> the amount of partitions the Windows installer creates on a clean disk. So instead, I first went with Arch Linux, and followed the <a href="https://wiki.archlinux.org/index.php/Installation_guide">installation guide on the Arch wiki</a>. Pre-installation, setting up the wireless network, creating the partitions and formatting them went all good. I decided to avoid GRUB at first and go with rEFInd, but alas I missed a big warning on the wiki and after reboot (I would later find out) it was not mounting root properly, so all I had was whatever was in the Initramfs. Reboot didn't work, so I had to hold the power button.</p>
573<p>Anyway, once the partitions were created, I went to install Windows (there was a lot of back and forth burning different <code>.iso</code> images on the USB, which was a bit annoying because it wasn't the fastest thing in the world). This was pretty painless, and the process was standard: select advanced to let me choose the right partition, pick the one, say &quot;no&quot; to everything in the services setup, and done. But this was the first Windows <code>.iso</code> I tried. It was an old revision, and the drivers were causing issues when running (something weird about their <code>.dll</code>, manually installing the <code>.ini</code> driver files seemed to work?). The Nvidia drivers didn't want to be installed on such an old revision, after updating everything I could via Windows updates. So back I went to burning a newer Windows <code>.iso</code> and going through the same process again…</p>
574<p>Once Windows was ready and I verified that I could boot to it correctly, it was time to have a second go at Arch Linux. And I went through the setup at least three times, getting it wrong every single time, formatting root every single time, redownloading the packages every single pain. If only had I known earlier what the issue was!</p>
575<p>Why bother with Arch? I was pretty happy with Linux Mint, and I lowkey wanted to try NixOS, but I had used Arch before and it's a really nice distro overall (up-to-date, has AUR, quite minimal, imperative), except for trying to install rEFInd while chrooted…</p>
576<p>In the end I managed to get something half-working, I still need to properly configure WiFi and pulseaudio in my system but hey it works.</p>
577<p>I like to be able to dual-boot Windows and Linux because Linux is amazing for productivity, but unfortunately, some games only work fine on Windows. Might as well have both systems and use one for gaming, while the other is my daily driver.</p>
578<h2 id="setting_up_arch_linux"><a class="anchor" href="#setting_up_arch_linux">¶</a>Setting up Arch Linux</h2>
579<p>This is the process I followed to install Arch Linux in the end, along with a brief explanation on what I think the things are doing and why we are doing them. I think the wiki could do a better job at this, but I also know it's hard to get it right for everyone. Something I do dislike is the link colour, after opening a link it becomes gray and it's a lot easier to miss the fact that it is a link in the first place, which was tough when re-reading it because some links actually matter a lot. Furthermore, important information may just be a single line, also easy to skim over. Anyway, on to the installation process…</p>
580<p>The first thing we want to do is configure our keyboard layout or else the keys won't correspond to what we expect:</p>
581<pre><code class="language-sh">loadkeys es
582</code></pre>
583<p>Because we're on a recent system, we want to verify that UEFI works correctly. If we see files listed, then it works fine:</p>
584<pre><code class="language-sh">ls /sys/firmware/efi/efivars
585</code></pre>
586<p>The next thing we want to do is configure the WiFi, because I don't have any ethernet cable nearby. To do this, we check what network interfaces our laptop has (we're looking for the one prefixed with &quot;w&quot;, presumably for wireless, such as &quot;wlan0&quot; or &quot;wlo1&quot;), we set it up, scan for available wireless network, and finally connect. In my case, the network has WPA security so we rely on <code>wpa_supplicant</code> to connect, passing the SSID (network name) and password:</p>
587<pre><code class="language-sh">ip link
588ip link set &lt;IFACE&gt; up
589iw dev &lt;IFACE&gt; scan | less
590wpa_supplicant -B -i &lt;IFACE&gt; -c &lt;(wpa_passphrase &lt;SSID&gt; &lt;PASS&gt;)
591</code></pre>
592<p>After that's done, pinging an IP address like &quot;1.1.1.1&quot; should Just Work™, but to be able to resolve hostnames, we need to also setup a nameserver. I'm using Cloudflare's, but you could use any other:</p>
593<pre><code class="language-sh">echo nameserver 1.1.1.1 &gt; /etc/resolv.conf
594ping archlinux.org
595^C
596</code></pre>
597<p>If the ping works, then network works! If you still have issues, you may need to <a href="https://wiki.archlinux.org/index.php/Network_configuration#Static_IP_address">manually configure a static IP address</a> and add a route with the address of your, well, router. This basically shows if we have any address, adds a static address (so people know who we are), shows what route we have, and adds a default one (so our packets know where to go):</p>
598<pre><code class="language-sh">ip address show
599ip address add &lt;YOUR ADDR&gt;/24 broadcast + dev &lt;IFACE&gt;
600ip route show
601ip route add default via &lt;ROUTER ADDR&gt; dev &lt;IFACE&gt;
602</code></pre>
603<p>Now that we have network available, we can enable NTP to synchronize our system time (this may be required for network operations where certificates have a validity period, not sure; in any case nobody wants a wrong system time):</p>
604<pre><code class="language-sh">timedatectl set-ntp true
605</code></pre>
606<p>After that, we can manage our disk and partitions using <code>fdisk</code>. We want to define partitions to tell the system where it should live. To determine the disk name, we first list them, and then edit it. <code>fdisk</code> is really nice and reminds you at every step that help can be accessed with &quot;m&quot;, which you should constantly use to guide you through.</p>
607<pre><code class="language-sh">fdisk -l
608fdisk /dev/&lt;DISK&gt;
609</code></pre>
610<p>The partitions I made are the following:</p>
611<ul>
612<li>A 100MB one for the EFI system.</li>
613<li>A 32GB one for Linux' root <code>/</code> partition.</li>
614<li>A 200GB one for Linux' home <code>/home</code> partition.</li>
615<li>The rest was unallocated for Windows because I did this first.</li>
616</ul>
617<p>I like to have <code>/home</code> and <code>/</code> separate because I can reinstall root without losing anything from home (projects, music, photos, screenshots, videos…).</p>
618<p>After the partitions are made, we format them in FAT32 and EXT4 which are good defaults for EFI, root and home. They need to have a format, or else they won't be usable:</p>
619<pre><code class="language-sh">mkfs.fat -F32 /dev/&lt;DISK&gt;&lt;PART1&gt;
620mkfs.ext4 /dev/&lt;DISK&gt;&lt;PART2&gt;
621mkfs.ext4 /dev/&lt;DISK&gt;&lt;PART3&gt;
622</code></pre>
623<p>Because the laptop was new, there was no risk to lose anything, but if you're doing a install on a previous system, be very careful with the partition names. Make sure they match with the ones in <code>fdisk -l</code>.</p>
624<p>Now that we have usable partitions, we need to mount them or they won't be accessible. We can do this with <code>mount</code>:</p>
625<pre><code class="language-sh">mount /dev/&lt;DISK&gt;&lt;PART2&gt; /mnt
626mkdir /mnt/efi
627mount /dev/&lt;DISK&gt;&lt;PART1&gt; /mnt/efi
628mkdir /mnt/home
629mount /dev/&lt;DISK&gt;&lt;PART3&gt; /mnt/home
630</code></pre>
631<p>Remember to use the correct partitions while mounting. We mount everything so that the system knows which partitions we care about, which we will let know about later on.</p>
632<p>Next step is to setup the basic Arch Linux system on root, which can be done with <code>pacstrap</code>. What follows the directory is a list of packages, and you may choose any you wish (at least add <code>base</code>, <code>linux</code> and <code>linux-firmware</code>). These can be installed later, but I'd recommend having them from the beginning, just in case:</p>
633<pre><code class="language-sh">pacstrap /mnt base linux linux-firmware sudo vim-minimal dhcpcd wpa_supplicant man-db man-pages intel-ucode grub efibootmgr os-prober ntfs-3g
634</code></pre>
635<p>Because my system has an intel CPU, I also installed <code>intel-ucode</code>.</p>
636<p>Next up is generating the <code>fstab</code> file, which we tell to use UUIDs to be on the safe side through <code>-U</code>. This file is important, because without it the system won't know what partitions exist and will happily only boot with the initramfs, without anything of what we just installed at root. Not knowing this made me restart the entire installation process a few times.</p>
637<pre><code class="language-sh">genfstab -U /mnt &gt;&gt; /mnt/etc/fstab
638</code></pre>
639<p>After that's done, we can change our root into our mount point and finish up configuration. We setup our timezone (so DST can be handled correctly if needed), synchronize the hardware clock (to persist the current time to the BIOS), uncomment our locales (exit <code>vim</code> by pressing ESC, then type <code>:wq</code> and press enter), generate locale files (which some applications need), configure language and keymap, update the hostname of our laptop and what indicate what <code>localhost</code> means…</p>
640<pre><code class="language-sh">ln -sf /usr/share/zoneinfo/&lt;REGION&gt;/&lt;CITY&gt; /etc/localtime
641hwclock --systohc
642vim /etc/locale.gen
643locale-gen
644echo LANG=es_ES.UTF-8 &gt; /etc/locale.conf
645echo KEYMAP=es &gt; /etc/vconsole.conf
646echo &lt;HOST&gt; /etc/hostname
647cat &lt;&lt;EOF &gt; /etc/hosts
648127.0.0.1 localhost
649::1 localhost
650127.0.1.1 &lt;HOST&gt;.localdomain &lt;HOST&gt;
651EOF
652</code></pre>
653<p>Really, we could've done all of this later, and the same goes for setting root's password with <code>passwd</code> or creating users (some of the groups you probably want are <code>power</code> and <code>wheel</code>).</p>
654<p>The important part here is installing GRUB (which also needed the <code>efibootmgr</code> package):</p>
655<pre><code class="language-sh">grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB
656</code></pre>
657<p>If we want GRUB to find our Windows install, we also need the <code>os-prober</code> and <code>ntfs-3g</code> packages that we installed earlier with <code>pacstrap</code>, and with those we need to mount the Windows partition somewhere. It doesn't matter where. With that done, we can generate the GRUB configuration file which lists all the boot options:</p>
658<pre><code class="language-sh">mkdir /windows
659mount /dev/&lt;DISK&gt;&lt;PART5&gt; /windows
660grub-mkconfig -o /boot/grub/grub.cfg
661</code></pre>
662<p>(In my case, I installed Windows before completing the Arch install, which created an additional partition in between).</p>
663<p>With GRUB ready, we can exit the chroot and reboot the system, and if all went well, you should be greeted with a choice of operating system to use:</p>
664<pre><code class="language-sh">exit
665reboot
666</code></pre>
667<p>If for some reason you need to find what mountpoints were active prior to rebooting (to <code>unmount</code> them for example), you can use <code>findmnt</code>.</p>
668<p>Before GRUB I tried rEFInd, which as I explained had issues with for missing a warning. Then I tried systemd-boot, which did not pick up Arch at first. That's where the several reinstalls come from, I didn't want to work with a half-worked system so I mostly redid the entire process quite a few times.</p>
669<h2 id="migrating_to_the_new_laptop"><a class="anchor" href="#migrating_to_the_new_laptop">¶</a>Migrating to the new laptop</h2>
670<p>I had a external disk formatted with NTFS. Of course, after moving every file I cared about from my previous Linux install caused all the permissions to reset. All my <code>.git</code> repositories, dirty with file permission changes! This is going to take a while to fix, or maybe I should just <code>git config core.fileMode false</code>. Here is a <a href="https://stackoverflow.com/a/2083563">lovely command</a> to sort them out on a per-repository basis:</p>
671<pre><code class="language-sh">git diff --summary | grep --color 'mode change 100644 =&gt; 100755' | cut -d' ' -f7- | xargs -d'\n' chmod -x
672</code></pre>
673<p>I never realized how much I had stored over the years, but it really was a lot. While moving things to the external disk, I tried to do some cleanup, such as removing some build artifacts which needlessly occupy space, or completely skipping all the binary application files. If I need those I will install them anyway. The process was mostly focused on finding all the projects and program data that I did care about, or even some game saves. Nothing too difficult, but definitely time consuming.</p>
674<h2 id="tuning_arch"><a class="anchor" href="#tuning_arch">¶</a>Tuning Arch</h2>
675<p>Now that our system is ready, install <code>pacman-contrib</code> to grab a copy of the <code>rankmirrors</code> speed. It should help speed up the download of whatever packages you want to install, since it will help us <a href="https://wiki.archlinux.org/index.php/Mirrors#List_by_speed">rank the mirrors by download speed</a>. Making a copy of the file is important, otherwise whenever you try to install something it will fail saying it can't find anything.</p>
676<pre><code class="language-sh">cp /etc/pacman.d/mirrorlist /etc/pacman.d/mirrorlist.backup
677sed -i 's/^#Server/Server/' /etc/pacman.d/mirrorlist.backup
678rankmirrors -n 6 /etc/pacman.d/mirrorlist.backup | tee /etc/pacman.d/mirrorlist
679</code></pre>
680<p>This will take a while, but it should be well worth it. We're using <code>tee</code> to see the progress as it goes.</p>
681<p>Some other packages I installed after I had a working system in no particular order:</p>
682<ul>
683<li><code>xfce4</code> and <code>xorg-server</code>. I just love the simplicity of XFCE.</li>
684<li><code>xfce4-whiskermenu-plugin</code>, a really nice start menu.</li>
685<li><code>xfce4-pulseaudio-plugin</code> and <code>pavucontrol</code>, to quickly adjust the audio with my mouse.</li>
686<li><code>xfce4-taskmanager</code>, a GUI alternative I generally prefer to <code>htop</code>.</li>
687<li><code>pulseaudio</code> and <code>pulseaudio-alsa</code> to get nice integration with XFCE4 and audio mixing.</li>
688<li><code>firefox</code>, which comes with fonts too. A really good web browser.</li>
689<li><code>git</code>, to commit <del>crimes</del> code.</li>
690<li><code>code</code>, a wonderful editor which I used to write this blog entry.</li>
691<li><code>nano</code>, so much nicer to write a simple commit message.</li>
692<li><code>python</code> and <code>python-pip</code>, my favourite language to toy around ideas or use as a calculator.</li>
693<li><code>telegram-desktop</code>, for my needs on sharing memes.</li>
694<li><code>cmus</code>, a simple terminal music player.</li>
695<li><code>openssh</code>, to connect into any VPS I have access to.</li>
696<li><code>base-devel</code>, necessary to build most projects I'll find myself working with (or even compiling some projects Rust which I installed via <code>rustup</code>).</li>
697<li><code>flac</code>, <code>libmad</code>, <code>opus</code>, and <code>libvorbis</code>, to be able to play more audio files.</li>
698<li><code>inkscape</code>, to make random drawings.</li>
699<li><code>ffmpeg</code>, to convert media or record screen.</li>
700<li><code>xclip</code>, to automatically copy screenshots to my clipboard.</li>
701<li><code>gvfs</code>, needed by Thunar to handle mounting and having a trash (perma-deletion by default can be nasty sometimes).</li>
702<li><code>noto-fonts</code>, <code>noto-fonts-cjk</code> and <code>noto-fonts-extra</code>, if you don't want missing gliphs everywhere.</li>
703<li><code>xfce4-notifyd</code> and <code>libnotify</code>, for notifications.</li>
704<li><code>cronie</code>, to be able to <code>crontab -e</code>. Make sure to <code>system enable cronie</code>.</li>
705</ul>
706<p>After that, I configured my Super L key to launch <code>xfce4-popup-whiskermenu</code> so that it opens the application menu, pretty much the same as it would on Windows, moved the panels around and configured them to my needs, and it feels like home once more.</p>
707<p>I made some mistakes while <a href="https://wiki.archlinux.org/index.php/Systemd-networkd">configuring systemd-networkd</a> and accidentally added a service that was incorrect, which caused boot to wait for it to timeout before completing. My boot time was taking 90 seconds longer because of this! <a href="https://www.reddit.com/r/archlinux/comments/4nv9yi/my_arch_greets_me_now_with_a_start_job/">The solution was to remove said service</a>, so this is something to look out for.</p>
708<p>In order to find what was taking long, I had to edit the <a href="https://wiki.archlinux.org/index.php/kernel_parameters">kernel parameters</a> to remove the <code>quiet</code> option. I prefer seeing the output on what my computer is doing anyway, because it gives me a sense of progress and most importantly is of great value when things go wrong. Another interesting option is <code>noauto,x-systemd.automount</code>, which makes a disk lazily-mounted. If you have a slow disk, this could help speed things up.</p>
709<p>If you see a service taking long, you can also use <code>systemd-analyze blame</code> to see what takes the longest, and <code>systemctl list-dependencies</code> is also helpful to find what services are active.</p>
710<p>My <code>locale charmap</code> was spitting out a bunch of warnings:</p>
711<pre><code class="language-sh">$ locale charmap
712locale: Cannot set LC_CTYPE to default locale: No such file or directory
713locale: Cannot set LC_MESSAGES to default locale: No such file or directory
714locale: Cannot set LC_ALL to default locale: No such file or directory
715ANSI_X3.4-1968
716</code></pre>
717<p>…ANSI encoding? Immediately I added the following to <code>~/.bashrc</code> and <code>~/.profile</code>:</p>
718<pre><code class="language-sh">export LC_ALL=en_US.UTF-8
719export LANG=en_US.UTF-8
720export LANGUAGE=en_US.UTF-8
721</code></pre>
722<p>For some reason, I also had to edit <code>xfce4-terminal</code>'s preferences in advanced to change the default character encoding to UTF-8. This also solved my issues with pasting things into the terminal, and also proper rendering! I guess pastes were not working because it had some characters that could not be encoded.</p>
723<p>To have working notifications, I added the following to <code>~/.bash_profile</code> after <code>exec startx</code>:</p>
724<pre><code class="language-sh">systemctl --user start xfce4-notifyd.service
725</code></pre>
726<p>I'm pretty sure there's a better way to do this, or maybe it's not even necessary, but this works for me.</p>
727<p>Some of the other things I had left to do was setting up <code>sccache</code> to speed up Rust builds:</p>
728<pre><code class="language-sh">cargo install sccache
729echo export RUSTC_WRAPPER=sccache &gt;&gt; ~/.bashrc
730</code></pre>
731<p>Once I had <code>cargo</code> ready, installed <code>hacksaw</code> and <code>shotgun</code> with it to perform screenshots.</p>
732<p>I also disabled the security delay when downloading files in Firefox because it's just annoying, in <code>about:config</code> setting <code>security.dialog_enable_delay</code> to <code>0</code>.</p>
733<p>The <code>utils-linux</code> comes with a <code>fstrim</code> utility to <a href="https://wiki.archlinux.org/index.php/Solid_state_drive#Periodic_TRIM">trim the SSD weekly</a>, which I want enabled via <code>systemctl enable fstrim.timer</code> (you may also want to <code>start</code> it if you don't reboot often). For more SSD tips, check <a href="https://easylinuxtipsproject.blogspot.com/p/ssd.html">How to optimize your Solid State Drive</a>.</p>
734<p>If the sound is funky prior to reboot, try <code>pulseaudio --kill</code> and <code>pulseaudio --start</code>, or delete <code>~/.config/pulse</code>.</p>
735<h2 id="tuning_windows"><a class="anchor" href="#tuning_windows">¶</a>Tuning Windows</h2>
736<p>On the Windows side, I disabled the annoying Windows defender by running (<kbd>Ctrl+R</kbd>) <code>gpedit.msc</code> and editing:</p>
737<ul>
738<li><em>Computer Configuration &gt; Administrative Templates &gt; Windows Components &gt; Windows Defender » Turn off Windows Defender » Enable</em></li>
739<li><em>User Configuration &gt; Administrative Templates &gt; Start Menu and Taskbar » Remove Notifications and Action Center » Enable</em></li>
740</ul>
741<p>I also updated the <a href="https://github.com/WindowsLies/BlockWindows/raw/master/hosts"><code>hosts</code> file</a> (located at <code>%windir%\system32\Drivers\etc\hosts</code>) with the hope that it will stop some of the telemetry.</p>
742<p>All this time, my laptop had the keyboard lights on, which have been quite annoying. Apparently, they also can cause <a href="https://www.reddit.com/r/ValveIndex/comments/cm6pos/psa_uninstalldisable_aura_sync_lighting_if_you/">massive FPS drops</a>. I headed over to <a href="https://rog.asus.com/downloads/">Asus Rog downloads</a>, selected Aura Sync…</p>
743<pre><code class="language-md"># Not Found
744
745The requested URL /campaign/aura/us/Sync.html was not found on this server.
746
747Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
748</code></pre>
749<p>…great! I'll just find the <a href="https://www.asus.com/campaign/aura/global/">Aura site</a> somewhere else…</p>
750<pre><code class="language-md"># ASUS
751
752# We'll be back.
753
754Hi, our website is temporarily closed for service enhancements.
755
756We'll be back shortly.Thank you for your patience!
757</code></pre>
758<p>Oh come on. After waiting for the next day, I headed over, downloaded their software, tried to install it and it was an awful experience. It felt like I was purposedly installing malware. It spammed and flashed a lot of <code>cmd</code>'s on screen as if it was a virus. It was stuck at 100% doing that and then, Windows blue-screened with <code>KERNEL_MODE_HEAP_CORRUPTION</code>. Amazing. How do you screw up this bad?</p>
759<p>Well, at least rebooting worked. I tried to <a href="https://answers.microsoft.com/en-us/windows/forum/all/unable-to-uninstall-asus-aura-sync-utility/e9bec36c-e62f-4773-80be-88fb68dace16">uninstall Aura, but of course that failed</a>. Using the <a href="https://support.microsoft.com/en-us/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed">troubleshooter to uninstall programs</a> helped me remove most of the crap that was installed.</p>
760<p>After searching around how to disable the lights (because <a href="https://rog.asus.com/forum/showthread.php?112786-Option-to-Disable-Aura-Lights-on-Strix-G-series-(G531GT)-irrespective-of-OSes">my BIOS did not have this setting</a>), I stumbled upon <a href="https://rog.asus.com/us/innovation/armoury_crate/">&quot;Armoury Crate&quot;</a>. Okay, fine, I will install that.</p>
761<p>The experience wasn't much better. It did the same thing with a lot of consoles flashing on screen. And of course, it resulted in another blue-screen, this time <code>KERNEL_SECURITY_CHECK_FAILURE</code>. To finish up, the BSOD kept happening as I rebooted the system. Time to reinstall Windows once more.</p>
762<p>Asus software might be good, but the software is utter crap.</p>
763<p>After trying out <a href="https://github.com/wroberts/rogauracore">rogauracore</a> (which didn't list my model), it worked! I could disable the stupid lights from Linux, and <a href="https://gitlab.com/CalcProgrammer1/OpenRGB/-/wikis/home">OpenRGB</a> also works on Windows which may be worth checking out too.</p>
764<p>Because <code>rougauracore</code> helped me and they linked to <a href="https://github.com/linuxhw/hw-probe/blob/master/README.md#appimage">hw-probe</a>, I decided to <a href="https://linux-hardware.org/?probe=0e3e48c501">run it on my system</a>, with the hopes it is useful for other people.</p>
765<h2 id="closing_words"><a class="anchor" href="#closing_words">¶</a>Closing words</h2>
766<p>I hope the installation journey is at least useful to someone, or that you enjoyed reading about it all. If not, sorry!</p>
767</main>
768</body>
769</html>
770 </content></entry><entry><title>Tips for Outpost</title><id>dist/tips-outpost/index.html</id><updated>2020-05-21T22:00:00+00:00</updated><published>2020-05-09T22:00:00+00:00</published><summary>Outpost</summary><content type="html" src="dist/tips-outpost/index.html"><!DOCTYPE html>
771<html>
772<head>
773<meta charset="utf-8" />
774<meta name="viewport" content="width=device-width, initial-scale=1" />
775<title>Tips for Outpost</title>
776<link rel="stylesheet" href="../css/style.css">
777</head>
778<body>
779<main>
780<h1 class="title" id="tips_for_outpost"><a class="anchor" href="#tips_for_outpost">¶</a>Tips for Outpost</h1>
781<div class="date-created-modified">Created 2020-05-10<br>
782Modified 2020-05-22</div>
783<p><a href="https://store.steampowered.com/app/1127110/Outpost/">Outpost</a> is a fun little game by Open Mid Interactive that has popped in recently in my recommended section of Steam, and I decided to give it a try.</p>
784<p>It's a fun tower-defense game with progression, different graphics and random world generation which makes it quite fun for a few hours. In this post I want to talk about some tips I found useful to get past night 50.</p>
785<h2 id="build_pattern"><a class="anchor" href="#build_pattern">¶</a>Build Pattern</h2>
786<p>At first, you may be inclined to design a checkerboard pattern like the following, where &quot;C&quot; is the Crystal shrine, &quot;S&quot; is a stone launcher and &quot;B&quot; is a booster:</p>
787<div class="image-container">
788<img src="outpost-bad-pattern.svg" alt="Bad Outpost build pattern" />
789<div class="image-caption"></div>
790</div>
791<p>
792<p>Indeed, this pattern will apply <strong>4</strong> boosts to every turret, but unfortunately, the other 4 slots of the booster are wasted! This is because boosters are able to power 8 different towers, and you really want to maximize that. Here's a better design:</p>
793<div class="image-container">
794<img src="outpost-good-pattern.svg" alt="Good Outpost build pattern" />
795<div class="image-caption"></div>
796</div>
797<p>
798<p>The shrine's tower does get boosted, but it's still not really worth it to boost it. This pattern works good, and it's really easy to tile: just repeat the same 3x3 pattern.</p>
799<p>Nonetheless, we can do better. What if we applied multiple boosters to the same tower while still applying all 8 boosts?</p>
800<div class="image-container">
801<img src="outpost-best-pattern.svg" alt="Best Outpost build pattern" />
802<div class="image-caption"></div>
803</div>
804<p>
805<p>That's what peak performance looks like. You can actually apply multiple boosters to the same tower, and it works great.</p>
806<p>Now, is it really worth it building anywhere except around the shrine? Not really. You never know where a boss will come from, so all sides need a lot of defense if you want to stand a chance.</p>
807<p>The addition of traps in 1.6 is amazing. You want to build these outside your strong &quot;core&quot;, mostly to slow the enemies down so your turrets have more time to finish them off. Don't waste boosters on the traps, and build them at a reasonable distance from the center (the sixth tile is a good spot):</p>
808<div class="image-container">
809<img src="outpost-trap-pattern.svg" alt="Trap Outpost build pattern" />
810<div class="image-caption"></div>
811</div>
812<p>
813<p>If you gather enough materials, you can build more trap and cannon layers outside, roughly at enough distance to slow them for enough duration until they reach the next layer of traps, and so on. Probably a single gap of &quot;cannon, booster, cannon&quot; is enough between trap layers, just not in the center where you need a lot of fire power.</p>
814<h2 id="talents"><a class="anchor" href="#talents">¶</a>Talents</h2>
815<p>Talents are the way progression works in the game. Generally, after a run, you will have enough experience to upgrade nearly all talents of roughly the same tier. However, some are worth upgrading more than others (which provide basically no value).</p>
816<p>The best ones to upgrade are:</p>
817<ul>
818<li>Starting supplies. Amazing to get good tools early.</li>
819<li>Shrine shield. Very useful to hold against tough bosses.</li>
820<li>Better buildings (cannon, boosters, bed and traps). They're a must to deal the most damage.</li>
821<li>Better pickaxe. Stone is limited, so better make good use of it.</li>
822<li>Better chests. They provide an insane amount of resources early.</li>
823<li>Winter slow. Turrets will have more time to deal damage, it's perfect.</li>
824<li>More time. Useful if you're running out, although generally you enter nights early after having a good core anyway.</li>
825<li>More rocks. Similar to a better pickaxe, more stone is always better.</li>
826</ul>
827<p>Some decent ones:</p>
828<ul>
829<li>In-shrine turret. It's okay to get past the first night without building but not much beyond that.</li>
830<li>Better axe and greaves. Great to save some energy and really nice quality of life to move around.</li>
831<li>Tree growth. Normally there's enough trees for this not to be an issue but it can save some time gathering wood.</li>
832<li>Wisps. They're half-decent since they can provide materials once you max out or max out expensive gear.</li>
833</ul>
834<p>Some okay ones:</p>
835<ul>
836<li>Extra XP while playing. Generally not needed due to the way XP scales per night, but can be a good boost.</li>
837<li>Runestones. Not as reliable as chests but some can grant more energy per day.</li>
838</ul>
839<p>Some crap ones:</p>
840<ul>
841<li>Boosts for other seasons. I mean, winter is already the best, no use there.</li>
842<li>Bow. The bow is very useless at the moment, it's not worth your experience.</li>
843<li>More energy per bush. Not really worth hunting for bushes since you will have enough energy to do well.</li>
844</ul>
845<h2 id="turrets"><a class="anchor" href="#turrets">¶</a>Turrets</h2>
846<p>Always build the highest tier, there's no point in anything lower than that. You will need to deal a lot of damage in a small area, which means space is a premium.</p>
847<h2 id="boosters"><a class="anchor" href="#boosters">¶</a>Boosters</h2>
848<p>If you're very early in the game, I recommend alternating both the flag and torch in a checkerboard pattern where the boosters should go in the pattern above. This way your towers will get extra speed and extra range, which works great.</p>
849<p>When you're in mid-game (stone launchers, gears and campfires), I do not recommend using campfires. The issue is their range boost is way too long, and the turrets will miss quite a few shots. It's better to put all your power into fire speed for increased DPS, at least near the center. If you manage to build too far out and some of the turrets hardly ever shoot, you may put campfires there.</p>
850<p>In end-game, of course alternate both of the highest tier upgrades. They are really good, and provide the best benefit / cost ratio.</p>
851<h2 id="gathering_materials"><a class="anchor" href="#gathering_materials">¶</a>Gathering Materials</h2>
852<p>It is <strong>very</strong> important to use all your energy every day! Otherwise it will go to waste, and you will need a lot of materials.</p>
853<p>As of 1.6, you can mine two things at once if they're close enough! I don't know if this is intended or a bug, but it sure is great.</p>
854<p>Once you're in mid-game, your stone-based fort should stand pretty well against the nights on its own. After playing for a while you will notice, if your base can defend a boss, then it will have no issue carrying you through the nights until the next boss. You can (and should!) spend the nights gathering materials, but only when you're confident that the night won't run out.</p>
855<p>Before the boss hits (every fifth night), come back to your base and use all of your materials. This is the next fort upgrade that will carry it the five next nights.</p>
856<p>You may also speed up time during night, but make sure you use all your energy before hand. And also take care, in the current version of the game speeding up time only speeds up monster movement, not the fire rate or projectile speed of your turrets! This means they will miss more shots and can be pretty dangerous. If you're speeding up time, consider speeding it up for a little bit, then go back to normal until things are more calm, and repeat.</p>
857<p>If you're in the end-game, try to rush for chests. They provide a huge amount of materials which is really helpful to upgrade all your tools early so you can make sure to get the most out of every rock left in the map.</p>
858<p>In the end-game, after all stone has been collected, you don't really need to use all of your energy anymore. Just enough to have enough wood to build with the remaining stone. This will also be nice with the bow upgrades, which admitedly can get quite powerful, but it's best to have a strong fort first.</p>
859<h2 id="season"><a class="anchor" href="#season">¶</a>Season</h2>
860<p>In my opinion, winter is just the best of the seasons. You don't <em>really</em> need that much energy (it gets tiresome), or extra tree drops, or luck. Slower movement means your turrets will be able to shoot enemies for longer, dealing more damage over time, giving them more chance to take enemies out before they reach the shrine.</p>
861<p>Feel free to re-roll the map a few times (play and exit, or even restart the game) until you get winter if you want to go for The Play.</p>
862<h2 id="gear"><a class="anchor" href="#gear">¶</a>Gear</h2>
863<p>In my opinion, you really should rush for the best pickaxe you can afford. Stone is a limited resource that doesn't regrow like trees, so once you run out, it's over. Better to make the best use out of it with a good pickaxe!</p>
864<p>You may also upgrade your greaves, we all known faster movement is a <em>really</em> nice quality of life improvement.</p>
865<p>Of course, you will eventually upgrade your axe to chop wood (otherwise it's wasted energy, really), but it's not as much of a priority as the pickaxe.</p>
866<p>Now, the bow is completely useless. Don't bother with it. Your energy is better spent gathering materials to build permanent turrets that deal constant damage while you're away, and the damage adds up with every extra turret you build.</p>
867<p>With regards to items you carry (like sword, or helmet), look for these (from best to worst):</p>
868<ul>
869<li>Less minion life.</li>
870<li>Chance to not consume energy.</li>
871<li>+1 turret damage.</li>
872<li>Extra energy.</li>
873<li>+1 drop from trees or stones.</li>
874<li>+1 free wood or stone per day.</li>
875</ul>
876<p>Less minion life, nothing to say. You will need it near end-game.</p>
877<p>The chance to not consume energy is better the more energy you have. With a 25% chance not to consume energy, you can think of it as 1 extra energy for every 4 energy you have on average.</p>
878<p>Turret damage is a tough one, it's <em>amazing</em> mid-game (it basically doubles your damage) but falls short once you unlock the cannon where you may prefer other items. Definitely recommended if you're getting started. You may even try to roll it on low tiers by dying on the second night, because it's that good.</p>
879<p>Extra energy is really good, because it means you can get more materials before it gets too rough. Make sure you have built at least two beds in the first night! This extra energy will pay of for the many nights to come.</p>
880<p>The problem with free wood or stone per day is that you have, often, five times as much energy per day. By this I mean you can get easily 5 stone every day, which means 5 extra stone, whereas the other would provide just 1 per night. On a good run, you will get around 50 free stone or 250 extra stone. It's a clear winner.</p>
881<p>In end-game, more quality of life are revealing chests so that you can rush them early, if you like to hunt for them try to make better use of the slot.</p>
882<h2 id="closing_words"><a class="anchor" href="#closing_words">¶</a>Closing words</h2>
883<p>I hope you enjoy the game as much as I do! Movement is sometimes janky and there's the occassional lag spikes, but despite this it should provide at least a few good hours of gameplay. Beware however a good run can take up to an hour!</p>
884</main>
885</body>
886</html>
887 </content></entry><entry><title>Installing NixOS, Take 2</title><id>dist/installing_nixos_2/index.html</id><updated>2019-02-15T23:00:00+00:00</updated><published>2019-02-14T23:00:00+00:00</published><summary>This is my second take at installing NixOS, after a while being frustrated with Arch Linux and the fact that a few kernel upgrades ago, the system crashed randomly from time to time. </summary><content type="html" src="dist/installing_nixos_2/index.html"><!DOCTYPE html>
888<html>
889<head>
890<meta charset="utf-8" />
891<meta name="viewport" content="width=device-width, initial-scale=1" />
892<title>Installing NixOS, Take 2</title>
893<link rel="stylesheet" href="../css/style.css">
894</head>
895<body>
896<main>
897<h1 class="title" id="installing_nixos_take_2"><a class="anchor" href="#installing_nixos_take_2">¶</a>Installing NixOS, Take 2</h1>
898<div class="date-created-modified">Created 2019-02-15<br>
899Modified 2019-02-16</div>
900<p>This is my second take at installing NixOS, after a while being frustrated with Arch Linux and the fact that a few kernel upgrades ago, the system crashed randomly from time to time. <code>journalctl</code> did not have any helpful hints and I thought reinstalling could be worthwhile anyway.</p>
901<p>This time, I started with more knowledge! The first step is heading to the <a href="https://nixos.org">NixOS website</a> and downloading their minimal installation CD for 64 bits. I didn't go with their graphical live CD, because their <a href="https://nixos.org/nixos/manual">installation manual</a> is a wonderful resource that guides you nicely.</p>
902<p>Once you have downloaded their <code>.iso</code>, you should probably verify it's <code>sha256sum</code> and make sure that it matches. The easiest thing to do in my opinion is using an USB to burn the image in it. Plug it in and check its device name with <code>fdisk -l</code>. In my case, it was <code>/dev/sdb</code>, so I went ahead with it and ran <code>dd if=nixos.iso of=/dev/sdb status=progress</code>. Make sure to run <code>sync</code> once that's done.</p>
903<p>If either <code>dd</code> or <code>sync</code> seem &quot;stuck&quot; in the end, they are just flushing the changes to disk to make sure all is good. This is normal, and depends on your drives.</p>
904<p>Now, reboot your computer with the USB plugged in and make sure to boot into it. You should be welcome with a pretty screen. Just select the first option and wait until it logs you in as root. Once you're there you probably want to <code>loadkeys es</code> or whatever your keyboard layout is, or you will have a hard time with passwords, since the characters are all over the place.</p>
905<p>In a clean disk, you would normally create the partitions now. In my case, I already had the partitions made (100MB for the EFI system, where <code>/boot</code> lives, 40GB for the root <code>/</code> partition with my old Linux installation, and 700G for <code>/home</code>), so I didn't need to do anything here. The manual showcases <code>parted</code>, but I personally use <code>fdisk</code>, which has very helpful help I check every time I use it.</p>
906<p><strong>Important</strong>: The <code>XY</code> in <code>/dev/sdXY</code> is probably different in your system! Make sure you use <code>fdisk -l</code> to see the correct letters and numbers!</p>
907<p>With the partitions ready in my UEFI system, I formatted both <code>/</code> and <code>/boot</code> just to be safe with <code>mkfs.ext4 -L nixos /dev/sda2</code> and <code>mkfs.fat -F 32 -n boot /dev/sda1</code> (remember that these are the letters and numbers used in my partition scheme). Don't worry about the warning in the second command regarding lowercase letters and Windows. It's not really an issue.</p>
908<p>Now, since we gave each partition a label, we can easily mount them through <code>mount /dev/disk/by-label/nixos /mnt</code> and, in UEFI systems, be sure to <code>mkdir -p /mnt/boot</code> and <code>mount /dev/disk/by-label/boot /mnt/boot</code>. I didn't bother setting up swap, since I have 8GB of RAM in my laptop and that's really enough for my use case.</p>
909<p>With that done, we will now ask the configuration wizard to do some work for us (in particular, generate a template) with <code>nixos-generate-config --root /mnt</code>. This generates a very well documented file that we should edit right now (and this is important!) with whatever editor you prefer. I used <code>vim</code>, but you can change it for <code>nano</code> if you prefer.</p>
910<p>On to the configuration file, we need to enable a few things, so <code>vim /mnt/etc/nixos/configuration.nix</code> and start scrolling down. We want to make sure to uncomment:</p>
911<pre><code># We really want network!
912networking.wireless.enable = true;
913
914# This &quot;fixes&quot; the keyboard layout. Put the one you use.
915i18n = {
916consoleKeyMap = &quot;es&quot;;
917}
918
919# Timezones are tricky so let's get this right.
920time.timeZone = &quot;Europe/Madrid&quot;;
921
922# We *really* want some base packages installed, such as
923# wpa_supplicant, or we won't have a way to connect to the
924# network once we install...
925environment.systemPackages = with pkgs; [
926wpa_supplicant wget curl vim neovim cmus mpv firefox git tdesktop
927];
928
929# Printing is useful, sure, enable CUPS
930services.printing.enable = true;
931
932# We have speakers, let's make use of them.
933sound.enable = true;
934hardware.pulseaudio.enable = true;
935
936# We want the X11 windowing system enabled, in Spanish.
937services.xserver.enable = true;
938services.xserver.layout = &quot;es&quot;;
939
940# I want a desktop manager in my laptop.
941# I personally prefer XFCE, but the manual shows plenty
942# of other options, such as Plasma, i3 WM, or whatever.
943services.xserver.desktopManager.xfce.enable = true;
944services.xserver.desktopManager.default = &quot;xfce&quot;;
945
946# Touchpad is useful (although sometimes annoying) in a laptop
947services.xserver.libinput.enable = true;
948
949# We don't want to do everything as root!
950users.users.lonami = {
951isNormalUser = true;
952uid = 1000;
953home = &quot;/home/lonami&quot;;
954extraGroups = [ &quot;wheel&quot; &quot;networkmanager&quot; &quot;audio&quot; ];
955};
956</code></pre>
957<p><em>(Fun fact, I overlooked the configuration file until I wrote this and hadn't noticed sound/pulseaudio was there. It wasn't hard to find online how to enable it though!)</em></p>
958<p>Now, let's modify <code>hardware-configuration.nix</code>. But if you have <code>/home</code> in a separate partition like me, you should run <code>blkid</code> to figure out its UUID. To avoid typing it out myself, I just ran <code>blkid &gt;&gt; /mnt/etc/nixos/hardware-configuration.nix</code> so that I could easily move it around with <code>vim</code>:</p>
959<pre><code># (stuff...)
960
961fileSystems.&quot;/home&quot; =
962{ device = &quot;/dev/disk/by-uuid/d344c686-cae7-4dd3-840e-308eddf86608&quot;;
963fsType = &quot;ext4&quot;;
964};
965
966# (more stuff...)
967</code></pre>
968<p>Note that, obviously, you should put your own partition's UUID there. Modifying the configuration is where I think the current NixOS' manual should have made more emphasis, at this step of the installation. They do detail it below, but that was already too late in my first attempt. Anyway, you can boot from the USB and run <code>nixos-install</code> as many times as you need until you get it working!</p>
969<p>But before installing, we need to configure the network since there are plenty of things to download. If you want to work from WiFi, you should first figure out the name of your network card with <code>ip link show</code>. In my case it's called <code>wlp3s0</code>. So with that knowledge we can run <code>wpa_supplicant -B -i wlp3s0 -c &lt;(wpa_passphrase SSID key)</code>. Be sure to replace both <code>SSID</code> and <code>key</code> with the name of your network and password key, respectively. If they have spaces, surround them in quotes.</p>
970<p>Another funny pitfall was typing <code>wpa_supplicant</code> in the command above twice (instead of <code>wpa_passphrase</code>). That sure spit out a few funny errors! Once you have ran that, wait a few seconds and <code>ping 1.1.1.1</code> to make sure that you can reach the internet. If you do, <code>^C</code> and let's install NixOS!</p>
971<pre><code>nixos-install
972</code></pre>
973<p>Well, that was pretty painless. You can now <code>reboot</code> and enjoy your new, functional system.</p>
974<h2 id="afterword"><a class="anchor" href="#afterword">¶</a>Afterword</h2>
975<p>The process of installing NixOS was really painless once you have made sense out of what things mean. I was far more pleased this time than in my previous attempt, despite the four attempts I needed to have it up and running.</p>
976<p>However not all is so good. I'm not sure where I went wrong, but the first time I tried with <code>i3</code> instead of <code>xfce</code>, all I was welcome with was a white, small terminal in the top left corner. I even generated a configuration file with <code>i3-config-wizard</code> to make sure it could detect my Mod1/Mod4 keys (which, it did), but even after rebooting, my commands weren't responding. For example, I couldn't manage to open another terminal with <code>Mod1+Enter</code>. I'm not even sure that I was in <code>i3</code>…</p>
977<p>In my very first attempt, I pressed <code>Alt+F8</code> as suggested in the welcome message. This took me an offline copy of the manual, which is really nicely done. Funny enough, though, I couldn't exit <code>w3m</code>. Both <code>Q</code> and <code>B</code> to quit and take me back wouldn't work. Somehow, it kept throwing me back into <code>w3m</code>, so I had to forcibly shutdown.</p>
978<p>In my second attempt, I also forgot to configure network, so I had no way to download <code>wpa_supplicant</code> without having <code>wpa_supplicant</code> itself to connect my laptop to the network! So, it was important to do that through the USB before installing it (which comes with the program preinstalled), just by making sure to add it in the configuration file.</p>
979<p>Some other notes, if you can't reach the internet, don't add any DNS in <code>/etc/resolv.conf</code>. This should be done declaratively in <code>configuration.nix</code>.</p>
980<p>In the end, I spent the entire afternoon playing around with it, taking breaks and what-not. I still haven't figured out why <code>nvim</code> was printing the literal escape character when going from normal to insert mode in the <code>xfce4-terminal</code> (and other actions also made it print this &quot;garbage&quot; to the console), why sometimes the network can reach the internet (and only some sites!) and sometimes not, and how to setup dualboot.</p>
981<p>But despite all of this, I think it was a worth installing it again. One sure sees things from a different perspective, and gets the chance to write another blog post!</p>
982<p>If there's something I overlooked or that could be done better, or maybe you can explain it differently, please be sure to <a href="https://lonami.dev/contact">contact me</a> to let me know!</p>
983<h2 id="update"><a class="anchor" href="#update">¶</a>Update</h2>
984<p>Well, that was surprisingly fast feedback. Thank you very much <a href="https://bb010g.keybase.pub/">@bb010g</a> for it! As they rightfully pointed out, one can avoid adding <code>/home</code> manually to <code>hardware-configuration.nix</code> if you mount it before generating the configuration files. However, the installation process doesn't need <code>/home</code> mounted, so I didn't do it.</p>
985<p>The second weird issue with <code>w3m</code> is actually a funny one. <code>Alt+F8</code> <em>switches to another TTY</em>! That's why quitting the program wouldn't do anything. You'd still be in a different TTY! Normally, this is <code>Ctrl+Alt+FX</code>, so I hadn't even thought that this is what could be happening. Anyway, the solution is not quitting the program, but rather going back to the main TTY with <code>Alt+F1</code>. You can switch back and forth all you need to consult the manual.</p>
986<p>More suggestions are having <a href="https://github.com/rycee/home-manager"><code>home-manager</code></a> manage the graphical sessions, since it should be easier to deal with than the alternatives.</p>
987<p>Despite having followed the guide and having read it over and over several times, it seems like my thoughts in this blog post may be a bit messy. So I recommend you also reading through the guide to have two versions of all this, just in case.</p>
988<p>Regarding network issues, they use <code>connman</code> so that may be worth checking out.</p>
989<p>Regarding terminal issues with <code>nvim</code> printing the literal escape character, I was told off for not having checked what my <code>$TERM</code> was. I hadn't really looked into it much myself, just complained about it here, so sorry for being annoying about that. A quick search in the <code>nixpkgs</code> repository lets us find <a href="https://github.com/NixOS/nixpkgs/blob/release-18.09/pkgs/applications/editors/neovim/default.nix">neovim/default.nix</a>, with version 0.3.1. Looking at <a href="https://github.com/neovim/neovim">Neovim's main repository</a> we can see that this is a bit outdated, but that is fine.</p>
990<p>If only I had bothered to look at <a href="https://github.com/neovim/neovim/wiki/FAQ#nvim-shows-weird-symbols-2-q-when-changing-modes">Neovim's wiki</a>, (which they found through <a href="https://github.com/neovim/neovim/issues/7749">Neovim's GitHub issues</a>) I would've seen that some terminals just don't support the program properly. The solution is, of course, to use a different terminal emulator with better support or to disable the <code>guicursor</code> in Neovim's config.</p>
991<p>This is a pretty good life lesson. 30 seconds of searching, maybe two minutes and a half for also checking XFCE issues, are often more than enough to troubleshoot your issues. The internet is a big place and more people have surely came across the problem before, so make sure to look online first. In my defense I'll say that it didn't bother me so much so I didn't bother looking for that soon either.</p>
992</main>
993</body>
994</html>
995 </content></entry><entry><title>Installing NixOS</title><id>dist/installing_nixos/index.html</id><updated>2019-02-15T23:00:00+00:00</updated><published>2017-05-12T22:00:00+00:00</published><summary>Please see </summary><content type="html" src="dist/installing_nixos/index.html"><!DOCTYPE html>
996<html>
997<head>
998<meta charset="utf-8" />
999<meta name="viewport" content="width=device-width, initial-scale=1" />
1000<title>Installing NixOS</title>
1001<link rel="stylesheet" href="../css/style.css">
1002</head>
1003<body>
1004<main>
1005<h1 class="title" id="installing_nixos"><a class="anchor" href="#installing_nixos">¶</a>Installing NixOS</h1>
1006<div class="date-created-modified">Created 2017-05-13<br>
1007Modified 2019-02-16</div>
1008<h2 id="update"><a class="anchor" href="#update">¶</a>Update</h2>
1009<p><em>Please see <a href="../installing_nixos_2/index.html">my followup post with NixOS</a> for a far better experience with it</em></p>
1010<hr />
1011<p>Today I decided to install <a href="http://nixos.org/">NixOS</a> as a recommendation, a purely functional Linux distribution, since <a href="https://xubuntu.org/">Xubuntu</a> kept crashing. Here's my journey, and how I managed to install it from a terminal for the first time in my life. Steps aren't hard, but they may not seem obvious at first.</p>
1012<ul>
1013<li>
1014<p>Grab the Live CD, burn it on a USB stick and boot. I recommend using <a href="https://etcher.io/">Etcher</a>.</p>
1015</li>
1016<li>
1017<p>Type <code>systemctl start display-manager</code> and wait.<sup class="footnote-reference" id="r.1"><a href="#f.1">1</a></sup></p>
1018</li>
1019<li>
1020<p>Open both the manual and the <code>konsole</code>.</p>
1021</li>
1022<li>
1023<p>Connect to the network using the GUI.</p>
1024</li>
1025<li>
1026<p>Create the disk partitions by using <code>fdisk</code>.</p>
1027<p>You can list them with <code>fdisk -l</code>, modify a certain drive with <code>fdisk /dev/sdX</code> (for instance, <code>/dev/sda</code>) and follow the instructions.</p>
1028<p>To create the file system, use <code>mkfs.ext4 -L &lt;label&gt; /dev/sdXY</code> and swap with <code>mkswap -L &lt;label&gt; /dev/sdXY</code>.</p>
1029<p>The EFI partition should be done with <code>mkfs.vfat</code>.</p>
1030</li>
1031<li>
1032<p>Mount the target to <code>/mnt</code> e.g. if the label was <code>nixos</code>, <code>mount /dev/disk/by-label/nixos /mnt</code></p>
1033</li>
1034<li>
1035<p><code>mkdir /mnt/boot</code> and then mount your EFI partition to it.</p>
1036</li>
1037<li>
1038<p>Generate a configuration template with <code>nixos-generate-config --root /mnt</code>, and modify it with <code>nano /etc/nixos/configuration.nix</code>.</p>
1039</li>
1040<li>
1041<p>While modifying the configuration, make sure to add <code>boot.loader.grub.device = &quot;/dev/sda&quot;</code></p>
1042</li>
1043<li>
1044<p>More useful configuration things are:</p>
1045<ul>
1046<li>Uncomment the whole <code>i18n</code> block.</li>
1047<li>Add some essential packages like <code>environment.systemPackages = with pkgs; [wget git firefox pulseaudio networkmanagerapplet];</code>.</li>
1048<li>If you want to use XFCE, add <code>services.xserver.desktopManager.xfce.enable = true;</code>, otherwise, you don't need <code>networkmanagerapplet</code> either. Make sure to add <code>networking.networkmanager.enable = true;</code> too.</li>
1049<li>Define some user for yourself (modify <code>guest</code> name) and use a UID greater than 1000. Also, add yourself to <code>extraGroups = [&quot;wheel&quot; &quot;networkmanager&quot;];</code> (the first to be able to <code>sudo</code>, the second to use network related things).</li>
1050</ul>
1051</li>
1052<li>
1053<p>Run <code>nixos-install</code>. If you ever modify that file again, to add more packages for instance (this is how they're installed), run <code>nixos-rebuild switch</code> (or use <code>test</code> to test but don't boot to it, or <code>boot</code> not to switch but to use on next boot.</p>
1054</li>
1055<li>
1056<p><code>reboot</code>.</p>
1057</li>
1058<li>
1059<p>Login as <code>root</code>, and set a password for your user with <code>passwd &lt;user&gt;</code>. Done!</p>
1060</li>
1061</ul>
1062<p>I enjoyed the process of installing it, and it's really cool that it has versioning and is so clean to keep track of which packages you install. But not being able to run arbitrary binaries by default is something very limitting in my opinion, though they've done a good job.</p>
1063<p>I'm now back to Xubuntu, with a fresh install.</p>
1064<h2 id="update_2"><a class="anchor" href="#update_2">¶</a>Update</h2>
1065<p>It is not true that &quot;they don't allow running arbitrary binaries by default&quot;, as pointed out in their <a href="https://nixos.org/nixpkgs/manual/#sec-fhs-environments">manual, buildFHSUserEnv</a>:</p>
1066<blockquote>
1067<p><code>buildFHSUserEnv</code> provides a way to build and run FHS-compatible lightweight sandboxes. It creates an isolated root with bound <code>/nix/store</code>, so its footprint in terms of disk space needed is quite small. This allows one to run software which is hard or unfeasible to patch for NixOS -- 3rd-party source trees with FHS assumptions, games distributed as tarballs, software with integrity checking and/or external self-updated binaries. It uses Linux namespaces feature to create temporary lightweight environments which are destroyed after all child processes exit, without root user rights requirement.</p>
1068</blockquote>
1069<p>Thanks to <a href="https://github.com/bb010g">@bb010g</a> for pointing this out.</p>
1070<h2 id="notes"><a class="anchor" href="#notes">¶</a>Notes</h2>
1071<p class="footnote" id="f.1"><sup>1</sup> The keyboard mapping is a bit strange. On my Spanish keyboard, the keys were as follows: <a href="#r.1">↩</a></p>
1072<table><thead><tr><th>Keyboard</th><th>Maps to</th><th>Shift</th></tr></thead><tbody>
1073<tr><td>'</td><td>-</td><td>_</td></tr>
1074<tr><td>´</td><td>'</td><td>&quot;</td></tr>
1075<tr><td>`</td><td>[</td><td></td></tr>
1076<tr><td>+</td><td>]</td><td></td></tr>
1077<tr><td>¡</td><td>=</td><td></td></tr>
1078<tr><td>-</td><td>/</td><td></td></tr>
1079<tr><td>ñ</td><td>;</td><td></td></tr>
1080</tbody></table>
1081</main>
1082</body>
1083</html>
1084 </content></entry><entry><title>WorldEdit Commands</title><id>dist/world_edit/index.html</id><updated>2018-07-10T22:00:00+00:00</updated><published>2018-07-10T22:00:00+00:00</published><summary>WorldEdit</summary><content type="html" src="dist/world_edit/index.html"><!DOCTYPE html>
1085<html>
1086<head>
1087<meta charset="utf-8" />
1088<meta name="viewport" content="width=device-width, initial-scale=1" />
1089<title>WorldEdit Commands</title>
1090<link rel="stylesheet" href="../css/style.css">
1091</head>
1092<body>
1093<main>
1094<h1 class="title" id="worldedit_commands"><a class="anchor" href="#worldedit_commands">¶</a>WorldEdit Commands</h1>
1095<div class="date-created-modified">2018-07-11</div>
1096<p><a href="https://dev.bukkit.org/projects/worldedit">WorldEdit</a> is an extremely powerful tool for modifying entire worlds within <a href="https://minecraft.net">Minecraft</a>, which can be used as either a mod for your single-player worlds or as a plugin for your <a href="https://getbukkit.org/">Bukkit</a> servers.</p>
1097<p>This command guide was written for Minecraft 1.12.1, version <a href="https://dev.bukkit.org/projects/worldedit/files/2460562">6.1.7.3</a>, but should work for newer versions too. All WorldEdit commands can be used with a double slash (<code>//</code>) so they don't conlict with built-in commands. This means you can get a list of all commands with <code>//help</code>. Let's explore different categories!</p>
1098<h2 id="movement"><a class="anchor" href="#movement">¶</a>Movement</h2>
1099<p>In order to edit a world properly you need to learn how to move in said world properly. There are several straightforward commands that let you move:</p>
1100<ul>
1101<li><code>//ascend</code> goes up one floor.</li>
1102<li><code>//descend</code> goes down one floor.</li>
1103<li><code>//thru</code> let's you pass through walls.</li>
1104<li><code>//jumpto</code> to go wherever you are looking.</li>
1105</ul>
1106<h2 id="information"><a class="anchor" href="#information">¶</a>Information</h2>
1107<p>Knowing your world properly is as important as knowing how to move within it, and will also let you change the information in said world if you need to.</p>
1108<ul>
1109<li><code>//biomelist</code> shows all known biomes.</li>
1110<li><code>//biomeinfo</code> shows the current biome.</li>
1111<li><code>//setbiome</code> lets you change the biome.</li>
1112</ul>
1113<h2 id="blocks"><a class="anchor" href="#blocks">¶</a>Blocks</h2>
1114<p>You can act over all blocks in a radius around you with quite a few commands. Some won't actually act over the entire range you specify, so 100 is often a good number.</p>
1115<h3 id="filling"><a class="anchor" href="#filling">¶</a>Filling</h3>
1116<p>You can fill pools with <code>//fill water 100</code> or caves with <code>//fillr water 100</code>, both of which act below your feet.</p>
1117<h3 id="fixing"><a class="anchor" href="#fixing">¶</a>Fixing</h3>
1118<p>If the water or lava is buggy use <code>//fixwater 100</code> or <code>//fixlava 100</code> respectively.</p>
1119<p>Some creeper removed the snow or the grass? Fear not, you can use <code>//snow 10</code> or <code>//grass 10</code>.</p>
1120<h3 id="emptying"><a class="anchor" href="#emptying">¶</a>Emptying</h3>
1121<p>You can empty a pool completely with <code>//drain 100</code>, remove the snow with <code>//thaw 10</code>, and remove fire with <code>//ex 10</code>.</p>
1122<h3 id="removing"><a class="anchor" href="#removing">¶</a>Removing</h3>
1123<p>You can remove blocks above and below you in some area with the <code>//removeabove N</code> and <code>//removebelow N</code>. You probably want to set a limit though, or you could fall off the world with <code>//removebelow 1 10</code> for radius and depth. You can also remove near blocks with <code>//removenear block 10</code>.</p>
1124<h3 id="shapes"><a class="anchor" href="#shapes">¶</a>Shapes</h3>
1125<p>Making a cylinder (or circle) can be done with through <code>//cyl stone 10</code>, a third argument for the height. The radius can be comma-separated to make a ellipses instead, such as <code>//cyl stone 5,10</code>.</p>
1126<p>Spheres are done with <code>//sphere stone 5</code>. This will build one right at your center, so you can raise it to be on your feet with <code>//sphere stone 5 yes</code>. Similar to cylinders, you can comma separate the radius <code>x,y,z</code>.</p>
1127<p>Pyramids can be done with <code>//pyramic stone 5</code>.</p>
1128<p>All these commands can be prefixed with &quot;h&quot; to make them hollow. For instance, <code>//hsphere stone 10</code>.</p>
1129<h2 id="regions"><a class="anchor" href="#regions">¶</a>Regions</h2>
1130<h3 id="basics"><a class="anchor" href="#basics">¶</a>Basics</h3>
1131<p>Operating over an entire region is really important, and the first thing you need to work comfortably with them is a tool to make selections. The default wooden-axe tool can be obtained with <code>//wand</code>, but you must be near the blocks to select. You can use a different tool, like a golden axe, to use as your &quot;far wand&quot; (wand usable over distance). Once you have one in your hand type <code>//farwand</code> to use it as your &quot;far wand&quot;. You can select the two corners of your region with left and right click. If you have selected the wrong tool, use <code>//none</code> to clear it.</p>
1132<p>If there are no blocks but you want to use your current position as a corner, use <code>//pos1</code> or 2.</p>
1133<p>If you made a region too small, you can enlarge it with <code>//expand 10 up</code>, or <code>//expand vert</code> for the entire vertical range, etc., or make it smaller with <code>//contract 10 up</code> etc., or <code>//inset</code> it to contract in both directions. You can use short-names for the cardinal directions (NSEW).</p>
1134<p>Finally, if you want to move your selection, you can <code>//shift 1 north</code> it to wherever you need.</p>
1135<h3 id="information_2"><a class="anchor" href="#information_2">¶</a>Information</h3>
1136<p>You can get the <code>//size</code> of the selection or even <code>//count torch</code> in some area. If you want to count all blocks, get their distribution <code>//distr</code>.</p>
1137<h3 id="filling_2"><a class="anchor" href="#filling_2">¶</a>Filling</h3>
1138<p>With a region selected, you can <code>//set</code> it to be any block! For instance, you can use <code>//set air</code> to clear it entirely. You can use more than one block evenly by separting them with a comma <code>//set stone,dirt</code>, or with a custom chance <code>//set 20%stone,80%dirt</code>.</p>
1139<p>You can use <code>//replace from to</code> instead if you don't want to override all blocks in your selection.</p>
1140<p>You can make an hollow set with <code>//faces</code>, and if you just want the walls, use <code>//walls</code>.</p>
1141<h3 id="cleaning"><a class="anchor" href="#cleaning">¶</a>Cleaning</h3>
1142<p>If someone destroyed your wonderful snow landscape, fear not, you can use <code>//overlay snow</code> over it (although for this you actually have <code>//snow N</code> and its opposite <code>//thaw</code>).</p>
1143<p>If you set some rough area, you can always <code>//smooth</code> it, even more than one time with <code>//smooth 3</code>. You can get your dirt and stone back with <code>//naturalize</code> and put some plants with <code>//flora</code> or <code>//forest</code>, both of which support a density or even the type for the trees. If you already have the dirt use <code>//green</code> instead. If you want some pumpkins, with <code>//pumpkins</code>.</p>
1144<h3 id="moving"><a class="anchor" href="#moving">¶</a>Moving</h3>
1145<p>You can repeat an entire selection many times by stacking them with <code>//stack N DIR</code>. This is extremely useful to make things like corridors or elevators. For instance, you can make a small section of the corridor, select it entirely, and then repeat it 10 times with <code>//stack 10 north</code>. Or you can make the elevator and then <code>//stack 10 up</code>. If you need to also copy the air use <code>//stackair</code>.</p>
1146<p>Finally, if you don't need to repeat it and simply move it just a bit towards the right direction, you can use <code>//move N</code>. The default direction is &quot;me&quot; (towards where you are facing) but you can set one with <code>//move 1 up</code> for example.</p>
1147<h3 id="selecting"><a class="anchor" href="#selecting">¶</a>Selecting</h3>
1148<p>You can not only select cuboids. You can also select different shapes, or even just points:</p>
1149<ul>
1150<li><code>//sel cuboid</code> is the default.</li>
1151<li><code>//sel extend</code> expands the default.</li>
1152<li><code>//sel poly</code> first point with left click and right click to add new points.</li>
1153<li><code>//sel ellipsoid</code> first point to select the center and right click to select the different radius.</li>
1154<li><code>//sel sphere</code> first point to select the center and one more right click for the radius.</li>
1155<li><code>//sel cyl</code> for cylinders, first click being the center.</li>
1156<li><code>//sel convex</code> for convex shapes. This one is extremely useful for <code>//curve</code>.</li>
1157</ul>
1158<h2 id="brushes"><a class="anchor" href="#brushes">¶</a>Brushes</h2>
1159<p>Brushes are a way to paint in 3D without first bothering about making a selection, and there are spherical and cylinder brushes with e.g. <code>//brush sphere stone 2</code>, or the shorter form <code>//br s stone</code>. For cylinder, one must use <code>cyl</code> instead <code>sphere</code>.</p>
1160<p>There also exists a brush to smooth the terrain which can be enabled on the current item with <code>//br smooth</code>, which can be used with right-click like any other brush.</p>
1161<h2 id="clipboard"><a class="anchor" href="#clipboard">¶</a>Clipboard</h2>
1162<p>Finally, you can copy and cut things around like you would do with normal text with <code>//copy</code> and <code>//cut</code>. The copy is issued from wherever you issue the command, so when you use <code>//paste</code>, remember that if you were 4 blocks apart when copying, it will be 4 blocks apart when pasting.</p>
1163<p>The contents of the clipboard can be flipped to wherever you are looking via <code>//flip</code>, and can be rotated via the <code>//rotate 90</code> command (in degrees).</p>
1164<p>To remove the copy use <code>//clearclipboard</code>.</p>
1165</main>
1166</body>
1167</html>
1168 </content></entry><entry><title>An Introduction to Asyncio</title><id>dist/asyncio/index.html</id><updated>2018-06-14T22:00:00+00:00</updated><published>2018-06-12T22:00:00+00:00</published><summary>After seeing some friends struggle with </summary><content type="html" src="dist/asyncio/index.html"><!DOCTYPE html>
1169<html>
1170<head>
1171<meta charset="utf-8" />
1172<meta name="viewport" content="width=device-width, initial-scale=1" />
1173<title>An Introduction to Asyncio</title>
1174<link rel="stylesheet" href="../css/style.css">
1175</head>
1176<body>
1177<main>
1178<h1 class="title" id="an_introduction_to_asyncio"><a class="anchor" href="#an_introduction_to_asyncio">¶</a>An Introduction to Asyncio</h1>
1179<div class="date-created-modified">Created 2018-06-13<br>
1180Modified 2018-06-15</div>
1181<h2 id="index"><a class="anchor" href="#index">¶</a>Index</h2>
1182<ul>
1183<li><a href="#background">Background</a></li>
1184<li><a href="#inputoutput">Input / Output</a></li>
1185<li><a href="#divingin">Diving In</a></li>
1186<li><a href="#toyexample">A Toy Example</a></li>
1187<li><a href="#example">A Real Example</a></li>
1188<li><a href="#extra">Extra Material</a></li>
1189</ul>
1190<h2 id="background"><a class="anchor" href="#background">¶</a>Background</h2>
1191<p>After seeing some friends struggle with <code>asyncio</code> I decided that it could be a good idea to write a blog post using my own words to explain how I understand the world of asynchronous IO. I will focus on Python's <code>asyncio</code> module but this post should apply to any other language easily.</p>
1192<p>So what is <code>asyncio</code> and what makes it good? Why don't we just use the old and known threads to run several parts of the code concurrently, at the same time?</p>
1193<p>The first reason is that <code>asyncio</code> makes your code easier to reason about, as opposed to using threads, because the amount of ways in which your code can run grows exponentially. Let's see that with an example. Imagine you have this code:</p>
1194<pre><code class="language-python">def method():
1195 line 1
1196 line 2
1197 line 3
1198 line 4
1199 line 5
1200</code></pre>
1201<p>And you start two threads to run the method at the same time. What is the order in which the lines of code get executed? The answer is that you can't know! The first thread can run the entire method before the second thread even starts. Or it could be the first thread that runs after the second thread. Perhaps both run the &quot;line 1&quot;, and then the line 2. Maybe the first thread runs lines 1 and 2, and then the second thread only runs the line 1 before the first thread finishes.</p>
1202<p>As you can see, any combination of the order in which the lines run is possible. If the lines modify some global shared state, that will get messy quickly.</p>
1203<p>Second, in Python, threads <em>won't</em> make your code faster. It will only increase the concurrency of your program, allowing you to run several things at the same time, so using threads for speed isn't a real advantage. Indeed, your code will probably run slower under the most common Python implementation, CPython, which makes use of a Global Interpreter Lock (GIL) that only lets a thread run at once.</p>
1204<h2 id="input_output"><a class="anchor" href="#input_output">¶</a>Input / Output</h2>
1205<p>Before we go any further, let's first stop to talk about input and output, commonly known as &quot;IO&quot;. There are two main ways to perform IO operations, such as reading or writing from a file or a network socket.</p>
1206<p>The first one is known as &quot;blocking IO&quot;. What this means is that, when you try performing IO, the current application thread is going to <em>block</em> until the Operative System can tell you it's done. Normally, this is not a problem, since disks are pretty fast anyway, but it can soon become a performance bottleneck. And network IO will be much slower than disk IO!</p>
1207<pre><code class="language-python"># &quot;open&quot; will block until the OS creates a new file in the disk.
1208# this can be really slow if the disk is under heavy load!
1209with open('hello.txt', 'w') as fd:
1210 fd.write('hello!\n')
1211
1212 # &quot;flush&quot; will block until the OS has written all data to disk*
1213 fd.flush()
1214
1215# * the reality is a bit more complicated, since writes to disk are
1216# quite expensive, the OS will normally keep the data in RAM until
1217# it has more stuff to write to disk, and then it will `sync`
1218# everything after a few seconds
1219</code></pre>
1220<p>Blocking IO offers timeouts, so that you can get control back in your code if the operation doesn't finish. Imagine that the remote host doesn't want to reply, your code would be stuck for as long as the connection remains alive!</p>
1221<p>But wait, what if we make the timeout small? Very, very small? If we do that, we will never block waiting for an answer. That's how asynchronous IO works, and it's the opposite of blocking IO (you can also call it non-blocking IO if you want to).</p>
1222<p>How does non-blocking IO work if the IO device needs a while to answer with the data? In that case, the operative system responds with &quot;not ready&quot;, and your application gets control back so it can do other stuff while the IO device completes your request. It works a bit like this:</p>
1223<pre><code class="language-python">&amp;lt;app&amp;gt; Hey, I would like to read 16 bytes from this file
1224&amp;lt;OS&amp;gt; Okay, but the disk hasn't sent me the data yet
1225&amp;lt;app&amp;gt; Alright, I will do something else then
1226(a lot of computer time passes)
1227&amp;lt;app&amp;gt; Do you have my 16 bytes now?
1228&amp;lt;OS&amp;gt; Yes, here they are! &quot;Hello, world !!\n&quot;
1229</code></pre>
1230<p>In reality, you can tell the OS to notify you when the data is ready, as opposed to polling (constantly asking the OS whether the data is ready yet or not), which is more efficient.</p>
1231<p>But either way, that's the difference between blocking and non-blocking IO, and what matters is that your application gets to run more without ever needing to wait for data to arrive, because the data will be there immediately when you ask, and if it's not yet, your app can do more things meanwhile.</p>
1232<h2 id="diving_in"><a class="anchor" href="#diving_in">¶</a>Diving In</h2>
1233<p>Now we've seen what blocking and non-blocking IO is, and how threads make your code harder to reason about, but they give concurrency (yet not more speed). Is there any other way to achieve this concurrency that doesn't involve threads? Yes! The answer is <code>asyncio</code>.</p>
1234<p>So how does <code>asyncio</code> help? First we need to understand a very crucial concept before we can dive any deeper, and I'm talking about the <em>event loop</em>. What is it and why do we need it?</p>
1235<p>You can think of the event loop as a <em>loop</em> that will be responsible for calling your <code>async</code> functions:</p>
1236<div class="image-container">
1237<img src="eventloop.svg" alt="The Event Loop" />
1238<div class="image-caption"></div>
1239</div>
1240<p>
1241<p>That's silly you may think. Now not only we run our code but we also have to run some &quot;event loop&quot;. It doesn't sound beneficial at all. What are these events? Well, they are the IO events we talked about before!</p>
1242<p><code>asyncio</code>'s event loop is responsible for handling those IO events, such as file is ready, data arrived, flushing is done, and so on. As we saw before, we can make these events non-blocking by setting their timeout to 0.</p>
1243<p>Let's say you want to read from 10 files at the same time. You will ask the OS to read data from 10 files, and at first none of the reads will be ready. But the event loop will be constantly asking the OS to know which are done, and when they are done, you will get your data.</p>
1244<p>This has some nice advantages. It means that, instead of waiting for a network request to send you a response or some file, instead of blocking there, the event loop can decide to run other code meanwhile. Whenever the contents are ready, they can be read, and your code can continue. Waiting for the contents to be received is done with the <code>await</code> keyword, and it tells the loop that it can run other code meanwhile:</p>
1245<div class="image-container">
1246<img src="awaitkwd1.svg" alt="Step 1, await keyword" />
1247<div class="image-caption"></div>
1248</div>
1249<p>
1250<div class="image-container">
1251<img src="awaitkwd2.svg" alt="Step 2, await keyword" />
1252<div class="image-caption"></div>
1253</div>
1254<p>
1255<p>Start reading the code of the event loop and follow the arrows. You can see that, in the beginning, there are no events yet, so the loop calls one of your functions. The code runs until it has to <code>await</code> for some IO operation to complete, such as sending a request over the network. The method is &quot;paused&quot; until an event occurs (for example, an &quot;event&quot; occurs when the request has been sent completely).</p>
1256<p>While the first method is busy, the event loop can enter the second method, and run its code until the first <code>await</code>. But it can happen that the event of the second query occurs before the request on the first method, so the event loop can re-enter the second method because it has already sent the query, but the first method isn't done sending the request yet.</p>
1257<p>Then, the second method <code>await</code>'s for an answer, and an event occurs telling the event loop that the request from the first method was sent. The code can be resumed again, until it has to <code>await</code> for a response, and so on.</p>
1258<p>There are some important things to note here. The first is that we only need one thread to be running! The event loop decides when and which methods should run. The second is that we know when it may run other methods. Those are the <code>await</code> keywords! Whenever there is one of those, we know that the loop is able to run other things until the resource (again, like network) becomes ready.</p>
1259<p>So far, we already have two advantages. We are only using a single thread so the cost for switching between methods is low, and we can easily reason about where our program may interleave operations.</p>
1260<p>Another advantage is that, with the event loop, you can easily schedule when a piece of code should run, such as using the method <a href="https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.call_at"><code>loop.call_at</code></a>, without the need for spawning another thread at all.</p>
1261<p>To tell the <code>asyncio</code> to run the two methods shown above, we can use <a href="https://docs.python.org/3/library/asyncio-future.html#asyncio.ensure_future"><code>asyncio.ensure_future</code></a>, which is a way of saying &quot;I want the future of my method to be ensured&quot;. That is, you want to run your method in the future, whenever the loop is free to do so. This method returns a <code>Future</code> object, so if your method returns a value, you can <code>await</code> this future to retrieve its result.</p>
1262<p>What is a <code>Future</code>? This object represents the value of something that will be there in the future, but might not be there yet. Just like you can <code>await</code> your own <code>async def</code> functions, you can <code>await</code> these <code>Future</code>'s.</p>
1263<p>The <code>async def</code> functions are also called &quot;coroutines&quot;, and Python does some magic behind the scenes to turn them into such. The coroutines can be <code>await</code>'ed, and this is what you normally do.</p>
1264<h2 id="a_toy_example"><a class="anchor" href="#a_toy_example">¶</a>A Toy Example</h2>
1265<p>That's all about <code>asyncio</code>! Let's wrap up with some example code. We will create a server that replies with the text a client sends, but reversed. First, we will show what you could write with normal synchronous code, and then we will port it.</p>
1266<p>Here is the <strong>synchronous version</strong>:</p>
1267<pre><code class="language-python"># server.py
1268import socket
1269
1270
1271def server_method():
1272 # create a new server socket to listen for connections
1273 server = socket.socket()
1274
1275 # bind to localhost:6789 for new connections
1276 server.bind(('localhost', 6789))
1277
1278 # we will listen for one client at most
1279 server.listen(1)
1280
1281 # *block* waiting for a new client
1282 client, _ = server.accept()
1283
1284 # *block* waiting for some data
1285 data = client.recv(1024)
1286
1287 # reverse the data
1288 data = data[::-1]
1289
1290 # *block* sending the data
1291 client.sendall(data)
1292
1293 # close client and server
1294 server.close()
1295 client.close()
1296
1297
1298if __name__ == '__main__':
1299 # block running the server
1300 server_method()
1301</code></pre>
1302<pre><code class="language-python"># client.py
1303import socket
1304
1305
1306def client_method():
1307 message = b'Hello Server!\n'
1308 client = socket.socket()
1309
1310 # *block* trying to stabilish a connection
1311 client.connect(('localhost', 6789))
1312
1313 # *block* trying to send the message
1314 print('Sending', message)
1315 client.sendall(message)
1316
1317 # *block* until we receive a response
1318 response = client.recv(1024)
1319 print('Server replied', response)
1320
1321 client.close()
1322
1323
1324if __name__ == '__main__':
1325 client_method()
1326</code></pre>
1327<p>From what we've seen, this code will block on all the lines with a comment above them saying that they will block. This means that for running more than one client or server, or both in the same file, you will need threads. But we can do better, we can rewrite it into <code>asyncio</code>!</p>
1328<p>The first step is to mark all your <code>def</code>initions that may block with <code>async</code>. This marks them as coroutines, which can be <code>await</code>ed on.</p>
1329<p>Second, since we're using low-level sockets, we need to make use of the methods that <code>asyncio</code> provides directly. If this was a third-party library, this would be just like using their <code>async def</code>initions.</p>
1330<p>Here is the <strong>asynchronous version</strong>:</p>
1331<pre><code class="language-python"># server.py
1332import asyncio
1333import socket
1334
1335# get the default &quot;event loop&quot; that we will run
1336loop = asyncio.get_event_loop()
1337
1338
1339# notice our new &quot;async&quot; before the definition
1340async def server_method():
1341 server = socket.socket()
1342 server.bind(('localhost', 6789))
1343 server.listen(1)
1344
1345 # await for a new client
1346 # the event loop can run other code while we wait here!
1347 client, _ = await loop.sock_accept(server)
1348
1349 # await for some data
1350 data = await loop.sock_recv(client, 1024)
1351 data = data[::-1]
1352
1353 # await for sending the data
1354 await loop.sock_sendall(client, data)
1355
1356 server.close()
1357 client.close()
1358
1359
1360if __name__ == '__main__':
1361 # run the loop until &quot;server method&quot; is complete
1362 loop.run_until_complete(server_method())
1363</code></pre>
1364<pre><code class="language-python"># client.py
1365import asyncio
1366import socket
1367
1368loop = asyncio.get_event_loop()
1369
1370
1371async def client_method():
1372 message = b'Hello Server!\n'
1373 client = socket.socket()
1374
1375 # await to stabilish a connection
1376 await loop.sock_connect(client, ('localhost', 6789))
1377
1378 # await to send the message
1379 print('Sending', message)
1380 await loop.sock_sendall(client, message)
1381
1382 # await to receive a response
1383 response = await loop.sock_recv(client, 1024)
1384 print('Server replied', response)
1385
1386 client.close()
1387
1388
1389if __name__ == '__main__':
1390 loop.run_until_complete(client_method())
1391</code></pre>
1392<p>That's it! You can place these two files separately and run, first the server, then the client. You should see output in the client.</p>
1393<p>The big difference here is that you can easily modify the code to run more than one server or clients at the same time. Whenever you <code>await</code> the event loop will run other of your code. It seems to &quot;block&quot; on the <code>await</code> parts, but remember it's actually jumping to run more code, and the event loop will get back to you whenever it can.</p>
1394<p>In short, you need an <code>async def</code> to <code>await</code> things, and you run them with the event loop instead of calling them directly. So this…</p>
1395<pre><code class="language-python">def main():
1396 ... # some code
1397
1398
1399if __name__ == '__main__':
1400 main()
1401</code></pre>
1402<p>…becomes this:</p>
1403<pre><code class="language-python">import asyncio
1404
1405
1406async def main():
1407 ... # some code
1408
1409
1410if __name__ == '__main__':
1411 asyncio.get_event_loop().run_until_complete(main)
1412</code></pre>
1413<p>This is pretty much how most of your <code>async</code> scripts will start, running the main method until its completion.</p>
1414<h2 id="a_real_example"><a class="anchor" href="#a_real_example">¶</a>A Real Example</h2>
1415<p>Let's have some fun with a real library. We'll be using <a href="https://github.com/LonamiWebs/Telethon">Telethon</a> to broadcast a message to our three best friends, all at the same time, thanks to the magic of <code>asyncio</code>. We'll dive right into the code, and then I'll explain our new friend <code>asyncio.wait(...)</code>:</p>
1416<pre><code class="language-python"># broadcast.py
1417import asyncio
1418import sys
1419
1420from telethon import TelegramClient
1421
1422# (you need your own values here, check Telethon's documentation)
1423api_id = 123
1424api_hash = '123abc'
1425friends = [
1426 '@friend1__username',
1427 '@friend2__username',
1428 '@bestie__username'
1429]
1430
1431# we will have to await things, so we need an async def
1432async def main(message):
1433 # start is a coroutine, so we need to await it to run it
1434 client = await TelegramClient('me', api_id, api_hash).start()
1435
1436 # wait for all three client.send_message to complete
1437 await asyncio.wait([
1438 client.send_message(friend, message)
1439 for friend in friends
1440 ])
1441
1442 # and close our client
1443 await client.disconnect()
1444
1445
1446if __name__ == '__main__':
1447 if len(sys.argv) != 2:
1448 print('You must pass the message to broadcast!')
1449 quit()
1450
1451 message = sys.argv[1]
1452 asyncio.get_event_loop().run_until_complete(main(message))
1453</code></pre>
1454<p>Wait… how did that send a message to all three of
1455my friends? The magic is done here:</p>
1456<pre><code class="language-python">[
1457 client.send_message(friend, message)
1458 for friend in friends
1459]
1460</code></pre>
1461<p>This list comprehension creates another list with three
1462coroutines, the three <code>client.send_message(...)</code>.
1463Then we just pass that list to <code>asyncio.wait</code>:</p>
1464<pre><code class="language-python">await asyncio.wait([...])
1465</code></pre>
1466<p>This method, by default, waits for the list of coroutines to run until they've all finished. You can read more on the Python <a href="https://docs.python.org/3/library/asyncio-task.html#asyncio.wait">documentation</a>. Truly a good function to know about!</p>
1467<p>Now whenever you have some important news for your friends, you can simply <code>python3 broadcast.py 'I bought a car!'</code> to tell all your friends about your new car! All you need to remember is that you need to <code>await</code> on coroutines, and you will be good. <code>asyncio</code> will warn you when you forget to do so.</p>
1468<h2 id="extra_material"><a class="anchor" href="#extra_material">¶</a>Extra Material</h2>
1469<p>If you want to understand how <code>asyncio</code> works under the hood, I recommend you to watch this hour-long talk <a href="https://youtu.be/M-UcUs7IMIM">Get to grips with asyncio in Python 3</a> by Robert Smallshire. In the video, they will explain the differences between concurrency and parallelism, along with others concepts, and how to implement your own <code>asyncio</code> &quot;scheduler&quot; from scratch.</p>
1470</main>
1471</body>
1472</html>
1473 </content></entry><entry><title>Sentences</title><id>dist/sentences/index.html</id><updated>2018-01-30T23:00:00+00:00</updated><published>2018-01-30T23:00:00+00:00</published><summary>Don't know English? </summary><content type="html" src="dist/sentences/index.html"><!DOCTYPE html>
1474<html>
1475<head>
1476<meta charset="utf-8" />
1477<meta name="viewport" content="width=device-width, initial-scale=1" />
1478<title>Sentences</title>
1479<link rel="stylesheet" href="../css/style.css">
1480</head>
1481<body>
1482<main>
1483<h1 class="title" id="sentences"><a class="anchor" href="#sentences">¶</a>Sentences</h1>
1484<div class="date-created-modified">2018-01-31</div>
1485<blockquote>
1486<p>Don't know English? <a href="spanish.html">Read the Spanish version instead</a>.</p>
1487</blockquote>
1488<p>Just a few sentences that I've been gathering among the years and I think are worthy of being kept somewhere.</p>
1489<ul>
1490<li>So far, you've survived 100% of your worst days. You're doing great</li>
1491<li>Money is not a concern, perfection is</li>
1492<li>The only limit to our realization of tomorrow will be our doubts today</li>
1493<li>Not all cultures deserve respect.</li>
1494<li>It's not the same knowing that you're not free that not being free.</li>
1495<li>Being alive is not a biolgical matter, rather mental.</li>
1496<li>Every mountain starts off as a grain of sand.</li>
1497<li>Time goes against desire.</li>
1498<li>The only way to respect is fear.</li>
1499<li>For those who have nothing I have so much.</li>
1500<li>One isn't what they think, it's what they do.</li>
1501<li>When your goal seems impossible, don't change the goal. Find new ways to get to it.</li>
1502<li>Be the change you wish to see in the world.</li>
1503<li>Tell me something, I'll forget. Show me something, I'll remember. But make me part of it and I'll understand it.</li>
1504<li>If you want something to happen, go and do it. Or wait sitting like a stupid until it happens that it never happens.</li>
1505<li>I'd rather be happy than be right.</li>
1506<li>The engines don’t move the ship at all. The ship stays where it is and the engines move the universe around it.</li>
1507<li>If I never try getting there, I'll never get there.</li>
1508</ul>
1509</main>
1510</body>
1511</html>
1512 </content></entry><entry><title>Blog de Lonami</title><id>dist/index/index.html</id><updated>2018-01-30T23:00:00+00:00</updated><published>2016-03-03T23:00:00+00:00</published><summary>Hola | Hi.</summary><content type="html" src="dist/index/index.html"><!DOCTYPE html>
1513<html>
1514<head>
1515<meta charset="utf-8" />
1516<meta name="viewport" content="width=device-width, initial-scale=1" />
1517<title>Blog de Lonami</title>
1518<link rel="stylesheet" href="../css/style.css">
1519</head>
1520<body>
1521<main>
1522<h1 class="title" id="blog_de_lonami"><a class="anchor" href="#blog_de_lonami">¶</a>Blog de Lonami</h1>
1523<div class="date-created-modified">Created 2016-03-04<br>
1524Modified 2018-01-31</div>
1525<p>Hola | Hi.</p>
1526<p>Choose your language below:</p>
1527<ul>
1528<li><a href="#bienvenido-al-blog">Leer entradas en español</a></li>
1529<li><a href="#welcome-to-the-blog">Read English entries</a></li>
1530</ul>
1531<h2 id="bienvenido_al_blog"><a class="anchor" href="#bienvenido_al_blog">¶</a>Bienvenido al blog</h2>
1532<p>Bienvenido al mejor (o no) blog del mundo. En esta sección publicaré de manera muy puntual algunas entradas que espero resulten interesantes para el gran público.</p>
1533<h2 id="welcome_to_the_blog"><a class="anchor" href="#welcome_to_the_blog">¶</a>Welcome to the blog</h2>
1534<p>Welcome to the best (or not) blog in the entire world. On this blog I will occasionally post new entries which I find interesting.</p>
1535</main>
1536</body>
1537</html>
1538 </content></entry><entry><title>Graphs</title><id>dist/graphs/index.html</id><updated>2017-06-01T22:00:00+00:00</updated><published>2017-06-01T22:00:00+00:00</published><summary>There are a few things which won't render unless you enable</summary><content type="html" src="dist/graphs/index.html"><!DOCTYPE html>
1539<html>
1540<head>
1541<meta charset="utf-8" />
1542<meta name="viewport" content="width=device-width, initial-scale=1" />
1543<title>Graphs</title>
1544<link rel="stylesheet" href="../css/style.css">
1545</head>
1546<body>
1547<main>
1548<script src='https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/MathJax.js?config=TeX-MML-AM_CHTML' async></script>
1549<div class="date-created-modified">2017-06-02</div>
1550<noscript>There are a few things which won't render unless you enable
1551JavaScript. No tracking, I promise!</noscript>
1552<h1 class="title" id="graphs"><a class="anchor" href="#graphs">¶</a>Graphs</h1>
1553<blockquote>
1554<p>Don't know English? <a href="spanish.html">Read the Spanish version instead</a>.</p>
1555</blockquote>
1556<p>Let's imagine we have 5 bus stations, which we'll denote by \(s_i\):</p>
1557<p>(\begin{bmatrix}
1558&amp; s_1 &amp; s_2 &amp; s_3 &amp; s_4 &amp; s_5 \
1559s_1 &amp; &amp; V &amp; &amp; &amp; \
1560s_2 &amp; V &amp; &amp; &amp; &amp; V \
1561s_3 &amp; &amp; &amp; &amp; V &amp; \
1562s_4 &amp; &amp; V &amp; V &amp; &amp; \
1563s_5 &amp; V &amp; &amp; &amp; V &amp;
1564\end{bmatrix})</p>
1565<p>This is known as a <i>"table of direct interconnections"</i>.</p>
1566 <p>The \(V\) represent connected paths. For instance, on the first
1567 row starting at \(s_1\), reaching the \(V\),
1568 allows us to turn up to get to \(s_2\).</p>
1569<p>We can see the above table represented in a more graphical way:</p>
1570 <img src="example1.svg" />
1571 <p>This type of graph is called, well, a <i>graph</i>, and it's a directed
1572 graph (or <i>digraph</i>), since the direction on which the arrows go does
1573 matter. It's made up of vertices, joined together by edges (also known as
1574 lines or directed <b>arcs</b>).</p>
1575<p>One can walk from a node to another through different <b>paths</b>. For
1576 example, \(s_4 \rightarrow s_2 \rightarrow s_5\) is an indirect path of <b>order</b>
1577 two, because we must use two edges to go from \(s_4\) to
1578 \(s_5\).</p>
1579<p>Let's now represent its adjacency matrix called A which represents the
1580 same table, but uses <mark>1</mark> instead </mark>V</mark> to represent
1581 a connection:</p>
1582<p>(\begin{bmatrix}
15830 &amp; 1 &amp; 0 &amp; 0 &amp; 0 \
15841 &amp; 0 &amp; 0 &amp; 0 &amp; 1 \
15850 &amp; 0 &amp; 0 &amp; 1 &amp; 0 \
15860 &amp; 1 &amp; 1 &amp; 0 &amp; 0 \
15871 &amp; 0 &amp; 0 &amp; 1 &amp; 0
1588\end{bmatrix})</p>
1589<p>This way we can see how the \(a_{2,1}\) element represents the
1590 connection \(s_2 \rightarrow s_1\), and the \(a_{5,1}\) element the
1591 \(s_5 \rightarrow s_1\) connection, etc.</p>
1592<p>In general, \(a_{i,j}\) represents a connection from
1593 \(s_i \rightarrow s_j\)as long as \(a_{i,j}\geq 1\).</p>
1594<p>Working with matrices allows us to have a computable representation of
1595 any graph, which is very useful.</p>
1596<hr />
1597<p>Graphs have a lot of interesting properties besides being representable
1598 by a computer. What would happen if, for instance, we calculated
1599 \(A^2\)? We obtain the following matrix:</p>
1600<p>(\begin{bmatrix}
16011 &amp; 0 &amp; 0 &amp; 0 &amp; 1 \
16021 &amp; 1 &amp; 0 &amp; 1 &amp; 0 \
16030 &amp; 1 &amp; 1 &amp; 0 &amp; 0 \
16041 &amp; 0 &amp; 0 &amp; 1 &amp; 1 \
16050 &amp; 2 &amp; 1 &amp; 0 &amp; 0
1606\end{bmatrix})</p>
1607<p>We can interpret this as the paths of order <b>two</b>.</p>
1608 <p>But what does the element \(a_{5,2}=2\) represent? It indicates
1609 the amount of possible ways to go from \(s_5 \rightarrow s_i \rightarrow s_2\).</p>
1610<p>One can manually multiply the involved row and column to determine which
1611 element is the one we need to pass through, this way we have the row
1612 \([1 0 0 1 0]\) and the column \([1 0 0 1 0]\) (on
1613 vertical). The elements \(s_i\geq 1\) are \(s_1\) and
1614 \(s_4\). This is, we can go from \(s_5\) to
1615 \(s_2\) via \(s_5 \rightarrow s_1 \rightarrow s_2\) or via
1616 \(s_5 \rightarrow s_4 \rightarrow s_2\):</p>
1617 <img src="example2.svg" />
1618<p>It's important to note that graphs to not consider self-connections, this
1619 is, \(s_i \rightarrow s_i\) is not allowed; neither we work with multigraphs
1620 here (those which allow multiple connections, for instance, an arbitrary
1621 number \(n\) of times).</p>
1622<p>(\begin{bmatrix}
16231 &amp; 1 &amp; 0 &amp; 1 &amp; 0 \
16241 &amp; 2 &amp; \textbf{1} &amp; 0 &amp; 1 \
16251 &amp; 0 &amp; 0 &amp; 1 &amp; 1 \
16261 &amp; 2 &amp; 1 &amp; 1 &amp; 0 \
16272 &amp; 0 &amp; 0 &amp; 1 &amp; 2
1628\end{bmatrix})</p>
1629<p>We can see how the first \(1\) just appeared on the element
1630 \(a_{2,3}\), which means that the shortest path to it is at least
1631 of order three.</mark>
1632<hr />
1633<p>A graph is said to be <b>strongly connected</b> as long as there is a
1634 way to reach <i>all</i> its elements.</p>
1635<p>We can see all the available paths until now by simply adding up all the
1636 direct and indirect ways to reach a node, so for now, we can add
1637 \(A+A^2+A^3\) in such a way that:</p>
1638<p>(\begin{bmatrix}
16392 &amp; 2 &amp; 0 &amp; 1 &amp; 1 \
16403 &amp; 3 &amp; 1 &amp; 1 &amp; 3 \
16411 &amp; 1 &amp; 1 &amp; 2 &amp; 1 \
16422 &amp; 3 &amp; 2 &amp; 2 &amp; 1 \
16433 &amp; 2 &amp; 1 &amp; 2 &amp; 2
1644\end{bmatrix})</p>
1645<p>There isn't a connection between \(s_1\) and \(s_3\) yet.
1646 If we were to calculate \(A^4\):</p>
1647<p>(\begin{bmatrix}
16481 &amp; 2 &amp; 1 &amp; &amp; \
1649&amp; &amp; &amp; &amp; \
1650&amp; &amp; &amp; &amp; \
1651&amp; &amp; &amp; &amp; \
1652&amp; &amp; &amp; &amp;<br />
1653\end{bmatrix})</p>
1654<p>We don't need to calculate anymore. We now know that the graph is
1655 strongly connected!</p>
1656<hr />
1657<p>Congratulations! You've completed this tiny introduction to graphs.
1658 Now you can play around with them and design your own connections.</p>
1659<p>Hold the left mouse button on the above area and drag it down to create
1660 a new node, or drag a node to this area to delete it.</p>
1661<p>To create new connections, hold the right mouse button on the node you
1662 want to start with, and drag it to the node you want it to be connected to.</p>
1663<p>To delete the connections coming from a specific node, middle click it.</p>
1664<table><tr><td style="width:100%;">
1665 <button onclick="resetConnections()">Reset connections</button>
1666 <button onclick="clearNodes()">Clear all the nodes</button>
1667 <br />
1668 <br />
1669 <label for="matrixOrder">Show matrix of order:</label>
1670 <input id="matrixOrder" type="number" min="1" max="5"
1671 value="1" oninput="updateOrder()">
1672 <br />
1673 <label for="matrixAccum">Show accumulated matrix</label>
1674 <input id="matrixAccum" type="checkbox" onchange="updateOrder()">
1675 <br />
1676 <br />
1677 <div class="matrix">
1678 <table id="matrixTable"></table>
1679 </div>
1680 </td><td>
1681 <canvas id="canvas" width="400" height="400" oncontextmenu="return false;">
1682 Looks like your browser won't let you see this fancy example :(
1683 </canvas>
1684 <br />
1685 </td></tr></table>
1686<script src="tinyparser.js"></script>
1687<script src="enhancements.js"></script>
1688<script src="graphs.js"></script>
1689</main>
1690</body>
1691</html>
1692 </content></entry><entry><title>Apuntes de bachillerato de Filosofía</title><id>dist/filosofia/index.html</id><updated>2016-06-20T22:00:00+00:00</updated><published>2016-06-20T22:00:00+00:00</published><summary>Hay asignaturas que merecen la pena, y una de ellas es la filosofía. De verdad. Aprendes un montón de cosas y abres tu mente, comparas muchos puntos de vista y te das cuenta de grandes cosas. Por eso, quiero compartir mis apuntes con todo aquel interesado.</summary><content type="html" src="dist/filosofia/index.html"><!DOCTYPE html>
1693<html>
1694<head>
1695<meta charset="utf-8" />
1696<meta name="viewport" content="width=device-width, initial-scale=1" />
1697<title>Apuntes de bachillerato de Filosofía</title>
1698<link rel="stylesheet" href="../css/style.css">
1699</head>
1700<body>
1701<main>
1702<h1 class="title" id="apuntes_de_bachillerato_de_filosofía"><a class="anchor" href="#apuntes_de_bachillerato_de_filosofía">¶</a>Apuntes de bachillerato de Filosofía</h1>
1703<div class="date-created-modified">2016-06-21</div>
1704<p>Hay asignaturas que merecen la pena, y una de ellas es la filosofía. De verdad. Aprendes un montón de cosas y abres tu mente, comparas muchos puntos de vista y te das cuenta de grandes cosas. Por eso, quiero compartir mis apuntes con todo aquel interesado.</p>
1705<p>Personalmente, mi autor favorito es Friedrich Nietzsche (se pronuncia <em>/niche/</em>). Está en el tercer trimestre, el más interesante, aunque si prefieres algo de contexto, te recomiendo leerlo todo. Puedes leerlo como si fuera un libro cualquiera:</p>
1706<ul>
1707<li>Descargar en .pdf
1708<ul>
1709<li><a href="filo_trimestre1.pdf">Filosofía - Primer trimestre</a></li>
1710<li><a href="filo_trimestre2.pdf">Filosofía - Segundo trimestre</a></li>
1711<li><a href="filo_trimestre3.pdf">Filosofía - Tercer trimestre</a></li>
1712</ul>
1713</li>
1714<li>Descargar en .odt (lo puedes editar)
1715<ul>
1716<li><a href="filo_trimestre1.odt">Filosofía - Primer trimestre</a></li>
1717<li><a href="filo_trimestre2.odt">Filosofía - Segundo trimestre</a></li>
1718<li><a href="filo_trimestre3.odt">Filosofía - Tercer trimestre</a></li>
1719</ul>
1720</li>
1721</ul>
1722<p>Nota: Hay algunas palabras un tanto soez. ¡Añaden emoción y no son para tanto, a lo sumo dos o tres! :)</p>
1723</main>
1724</body>
1725</html>
1726 </content></entry><entry><title>Reflexión sobre la Inteligencia artificial</title><id>dist/reflexion_ia/index.html</id><updated>2016-06-12T22:00:00+00:00</updated><published>2016-06-12T22:00:00+00:00</published><summary>Nota: esta reflexión ha sido sacada de una conversación en Telegram, aunque ha sido lo más adaptada posible a formato de blog.</summary><content type="html" src="dist/reflexion_ia/index.html"><!DOCTYPE html>
1727<html>
1728<head>
1729<meta charset="utf-8" />
1730<meta name="viewport" content="width=device-width, initial-scale=1" />
1731<title>Reflexión sobre la Inteligencia artificial</title>
1732<link rel="stylesheet" href="../css/style.css">
1733</head>
1734<body>
1735<main>
1736<h1 class="title" id="reflexión_sobre_la_inteligencia_artificial"><a class="anchor" href="#reflexión_sobre_la_inteligencia_artificial">¶</a>Reflexión sobre la Inteligencia artificial</h1>
1737<div class="date-created-modified">2016-06-13</div>
1738<blockquote>
1739<p>Nota: esta reflexión ha sido sacada de una conversación en Telegram, aunque ha sido lo más adaptada posible a formato de blog.</p>
1740</blockquote>
1741<h2 id="conversación_del_12_03_16"><a class="anchor" href="#conversación_del_12_03_16">¶</a>Conversación del 12.03.16</h2>
1742<p>Pienso que para conseguir una verdadera inteligencia artificial debemos abstraernos mucho. Es decir, siempre hay una pequeña parte de <em>Pero es que el ser humano, los sentimientos, tal, cual</em>... Igual simplemente, absolutamente todo esté programado. Cuando actúas de manera que no sabes por qué por ejemplo, seguramente sea una serie de estímulos adecuados que producen esa respuesta porque se ha formado ese camino de neuronas en tu mente. Por ejemplo, el arco reflejo, que es un arco innato.</p>
1743<ul>
1744<li><em>Sensación de quemar → retirar</em></li>
1745<li><em><a href="https://es.wikipedia.org/wiki/Condicionamiento_cl%C3%A1sico">Un estímulo X → una respuesta Y</a></em></li>
1746</ul>
1747<p>Es una ida y vuelta instantanea entre sensación y respuesta. El cerebro simplemente es capaz de trabajar con combinaciones más complejas, como por ejemplo la suma, este número con este otro → sale otro número, y se le añade a otro... Hay una especie de <a href="https://es.wikipedia.org/wiki/Recursi%C3%B3n">recursión</a> también, aunque en realidad es que es el mismo estímulo el que <a href="https://es.wikipedia.org/wiki/M%C3%A9todo_%28inform%C3%A1tica%29">&quot;llama&quot;</a> a un determinado camino.</p>
1748<p>Pero lo verdaderamente impresionante es la consciencia, igual no tenemos consciencia de verdad, igual es como lo sentimos. Siempre nos han hablado de la consciencia pero nadie ha sabido probarla, por lo que sólo tenemos una idea, un concepto. Es aún más impresionante es el hecho de recordar y <a href="https://es.wikipedia.org/wiki/Memoria_de_trabajo">trabajar</a> con la información.</p>
1749<p>Cuando hablamos de consciencia, estamos simplemente tratando información sobre esa misma información, ¿cómo cojones sentimos lo que pensamos? Yo sé que estoy pensando porque hemos definido <em>pensar</em> como este proceso. ¿Pero cómo coño entiendo yo eso? Es decir, ¿cómo me doy cuenta? por qué lo situo en mi cabeza? Probablemente, aunque el cerebro esté trabajando con todo eso, la sensación sea externa a nosotros, es decir, ocurre en mi cabeza. ¿Pero de verdad lo siento en mi cabeza?</p>
1750<p>Me estoy rayando.</p>
1751<p>El verdadero problema está en saber cómo sabemos que estamos pensando. El cerebro se compone de neuronas y conexiones, esa es la base a parte de donde se encuentra todo y tal la base es esa, y las sensaciones táctiles son igual de complejas, las procesa mi cerebro pero las siento en mi mano. ¿Será cosa de costumbre? Yo siento algo y lo situo ahí. Sin embargo sentimos ahí y no por encima o por debajo de, vamos a poner, los dedos de la mano, lo siento justo ahí. ¿Qué coño es realmente la <a href="https://es.wikipedia.org/wiki/Memoria_a_corto_plazo">memoria a corto plazo</a>? (porque lo de la <a href="https://es.wikipedia.org/wiki/Memoria_a_largo_plazo">memoria a largo plazo</a> se traslada ahí cuando la necesitamos para trabajar con ella, por eso es <em>MCP</em> o memoria de trabajo según ciertas teorías).</p>
1752<p>En fin.</p>
1753</main>
1754</body>
1755</html>
1756 </content></entry><entry><title>Inteligencia artificial</title><id>dist/inteligencia_artificial/index.html</id><updated>2016-03-04T23:00:00+00:00</updated><published>2016-02-23T23:00:00+00:00</published><summary>La inteligencia artificial es una rama apasionante que tiene su origen en la </summary><content type="html" src="dist/inteligencia_artificial/index.html"><!DOCTYPE html>
1757<html>
1758<head>
1759<meta charset="utf-8" />
1760<meta name="viewport" content="width=device-width, initial-scale=1" />
1761<title>Inteligencia artificial</title>
1762<link rel="stylesheet" href="../css/style.css">
1763</head>
1764<body>
1765<main>
1766<h1 class="title" id="inteligencia_artificial"><a class="anchor" href="#inteligencia_artificial">¶</a>Inteligencia artificial</h1>
1767<div class="date-created-modified">Created 2016-02-24<br>
1768Modified 2016-03-05</div>
1769<h2 id="índice"><a class="anchor" href="#índice">¶</a>Índice</h2>
1770<ul>
1771<li><a href="#qu%C3%A9_es">Qué es</a></li>
1772<li><a href="#en_qu%C3%A9_consiste">En qué consiste</a></li>
1773<li><a href="#l%C3%ADmites">Límites</a></li>
1774<li><a href="#tipos_de_inteligencia_artificial">Tipos de inteligencia artificial</a></li>
1775<li><a href="#aplicaciones_pr%C3%A1cticas">Aplicaciones prácticas</a></li>
1776<li><a href="#implicaciones_%C3%A9ticas">Implicaciones éticas</a></li>
1777<li><a href="#ejemplos">Ejemplos</a></li>
1778<li><a href="#conceptos">Conceptos</a></li>
1779<li><a href="#fuentes">Fuentes</a></li>
1780</ul>
1781<h2 id="qué_es"><a class="anchor" href="#qué_es">¶</a>Qué es</h2>
1782<p>La inteligencia artificial es una rama apasionante que tiene su origen en la <strong>informática</strong> y se basa en el concepto de conseguir <em>emular</em><sup class="footnote-reference" id="r.1"><a href="#f.1">1</a></sup> al cerebro humano, mediante el desarrollo un programa que sea capaz de <strong>aprender y mejorar por sí sólo</strong> (normalmente bajo algún tipo de supervisión)</p>
1783<p>Fue un concepto acuñado por <em>John McCarthy</em> en un congreso de informática de 1956, y desde entonces este campo ha crecido de manera exponencial con unas buenas previsiones de futuro.</p></p>
1784<div class="image-container">
1785<img src="human_progress_edge.svg" alt="Progreso humano en la inteligencia artificial" />
1786<div class="image-caption"></div>
1787</div>
1788<p>
1789<p><em>Progreso humano en la inteligencia artificial. <a href="http://waitbutwhy.com/2015/01/artificial-intelligence-revolution-1">Fuente</a></em></p>
1790<h2 id="en_qué_consiste"><a class="anchor" href="#en_qué_consiste">¶</a>En qué consiste</h2>
1791<p>La inteligencia artificial no consiste en escribir unas pautas fijas y finitas al igual que hacen la gran mayoría de programas, en los cuales introduces unos datos y producen siempre la misma salida, una salida predecible, programada e invariable, que además, tiene sus límites, ya que si introduces datos para los que la aplicación no está programada, esta aplicación no será capaz de manejarlos. No los entenderá y no producirá ningún resultado.</p>
1792<p>La inteligencia artificial consiste en dar un paso <strong>más allá</strong>. Una inteligencia artificial <em>entrenada</em> es capaz de manejar datos para los cuales no ha sido programada de manera explícita<sup class="footnote-reference" id="r.2"><a href="#f.2">2</a></sup></sup></p>
1793<h2 id="límites"><a class="anchor" href="#límites">¶</a>Límites</h2>
1794<p>Actualmente, la inteligencia artificial se ve limitada por la velocidad y capacidad de los dispositivos (ordenadores, teléfonos inteligentes).</p>
1795<p>A día de hoy, ya hemos conseguido emular el cerebro de un gusano de un milímetro de longitud, que consiste de un total de trescientas dos neuronas. El <strong>cerebro humano</strong> contiene unas <strong>cien mil millones de neuronas</strong>.</p>
1796<div class="image-container">
1797<img src="exponential_grow.gif" alt="Progreso en la velocidad de los dispositivos" />
1798<div class="image-caption"></div>
1799</div>
1800<p>
1801<p><em>Crecimiento en la velocidad de procesado de los dispositivos. <a href="http://waitbutwhy.com/2015/01/artificial-intelligence-revolution-1">Fuente</a></em></p>
1802<p>Comparado con las neuronas de un cerebro humano (cuya velocidad<sup class="footnote-reference" id="r.3"><a href="#f.3">3</a></sup> máxima oscilan entre los 200Hz), los procesadores de hoy en día (mucho más lentos que los que tendremos dentro de algunos años) ya tienen una velocidad superior a los 2Ghz, es decir, <strong>10 millones de veces</strong> más rápidos que las neuronas. Y la comunicación interna del cerebro, que oscila entre los 120m/s, queda infinitamente distante de la velocidad de los ordenadores que se comunican de manera óptica a la <strong>velocidad de la luz</strong>.</p>
1803<p>Además de todo esto, la capacidad de los dispositivos puede ser <strong>ampliada</strong>, a diferencia del cerebro que tiene un tamaño ya determinado. Y, por último, un procesador puede estar <strong>trabajando sin parar</strong> nunca, sin cansarse.</p></p>
1804<!-- Boston dynamics artificial intelligence put some more examples, like Google or predicting models or big data, ocr -->
1805<h2 id="tipos_de_inteligencia_artificial"><a class="anchor" href="#tipos_de_inteligencia_artificial">¶</a>Tipos de inteligencia artificial</h2>
1806<h3 id="según_el_tipo_de_aprendizaje"><a class="anchor" href="#según_el_tipo_de_aprendizaje">¶</a>Según el tipo de aprendizaje</h3>
1807<ul>
1808<li><strong>Aprendizaje supervisado</strong>: se le presenta una entrada de datos y produce una salida de los datos procesados, y un &quot;tutor&quot; es el que determina si la salida es correcta o no.</li>
1809<li><strong>Aprendizaje sin supervisar</strong>: se le presenta una entrada de datos sin presentarle ningún otro tipo de información, para que encuentre la estructura de los datos por sí sóla.</li>
1810<li><strong>Aprendizaje por refuerzo</strong>: un ordenador interactua con un entorno variable en el que debe llevar a cabo una tarea concreta, sin que un tutor le indique cómo explícitamente.</li>
1811</ul>
1812<h3 id="según_la_forma_de_llevarlo_a_cabo_principales_métodos_"><a class="anchor" href="#según_la_forma_de_llevarlo_a_cabo_principales_métodos_">¶</a>Según la forma de llevarlo a cabo (principales métodos)</h3>
1813<ul>
1814<li>
1815<p><strong>Aprendizaje por árbol de decisiones</strong>. Este aprendizaje usa un árbol de decisiones, que almacena observaciones y conclusiones.</p>
1816<div class="image-container">
1817<img src="decision_tree.svg" alt="Árbol de decisiones" />
1818<div class="image-caption"></div>
1819</div>
1820<p>
1821</li>
1822<li>
1823<p><strong>Aprendizaje por asociación de reglas</strong>. Utilizado para descubrir relaciones en grandes bases de datos<sup class="footnote-reference" id="r.4"><a href="#f.4">4</a></sup>.</p>
1824</li>
1825<li>
1826<p><strong>Red neuronal artificial (RNA)</strong>. Inspirado en redes neuronales biológicas**. Los cálculos se estructuran en un grupo de neuronas artificiales interconectadas.</p>
1827</li>
1828<li>
1829<p><strong>Programación lógica inductiva (PLI)</strong>. Se aproxima de manera hipotética, dado un transfondo lógico y una entrada, a una solución que no se le había presentado antes.</p>
1830</li>
1831<li>
1832<p><strong>Máquinas de soporte vectorial (MSV)</strong>. Se usan para clasificar y problemas que necesitan de regresión<sup class="footnote-reference" id="r.5"><a href="#f.5">5</a></sup>. Dado una serie de ejemplos, una entrada será clasificada de una forma u otra.</p>
1833</li>
1834<li>
1835<p><em><strong>Clustering</strong></em>. Este tipo de análisis consiste en asignar observaciones a ciertas subcategorías (denominadas <em>clústeres</em>), para que aquellas que están en el mismo <em>clúster</em> sean similares**. Este tipo de aprendizaje es una técnica común en análisis estadístico.</p>
1836</li>
1837<li>
1838<p><strong>Redes bayesianas</strong>. Es un modelo probabilístico que organiza variables al azar según unas determinadas condiciones mediante un gráfico**. Un ejemplo de red bayesiana es el siguiente:</p>
1839<div class="image-container">
1840<img src="bayesian_network.svg" alt="Red bayesiana" />
1841<div class="image-caption"></div>
1842</div>
1843<p>
1844</li>
1845<li>
1846<p><strong>Algoritmos genéticos</strong>. Imita el proceso evolutivo de la selección natural, y usa métodos como la mutación para generar nuevos &quot;genotipos&quot; que, con algo de suerte, serán mejores en encontrar la solución correcta.</p>
1847</li>
1848</ul>
1849<h2 id="aplicaciones_prácticas"><a class="anchor" href="#aplicaciones_prácticas">¶</a>Aplicaciones prácticas</h2>
1850<p>La inteligencia artificial ya se encuentra desde hace algún tiempo entre nosotros, como por ejemplo el archiconocido <strong>buscador Google</strong>, que filtra los resultados más relevantes mediante una inteligencia artificial. Otros ejemplos son el reconocimiento de caracteres a partir de una foto, o incluso reconocimiento del habla con <strong>asistentes virtuales como Cortana o Siri</strong>, en los videojuegos, en bolsa, en los <strong>hospitales</strong>, industria pesada, transportes, juguetes, música, aviación, robótica, filtros anti-spam... y un largo etcétera.</p>
1851<h2 id="implicaciones_éticas"><a class="anchor" href="#implicaciones_éticas">¶</a>Implicaciones éticas</h2>
1852<p>Una vez tengamos la tecnología necesaria para recrear un cerebro humano, si enseñáramos a esta inteligencia artificial al igual que un humano, ¿llegaría a tener <strong>sentimientos</strong>? ¿Sería consciente de su existencia? ¿Podría sentir felicidad, alegría, tristeza, enfado? ¿Tendría <strong>creatividad</strong>? ¿Derecho a propiedad? Si la respuesta es que sí, y es la respuesta más lógica, significa que, en realidad, los sentimientos no son nada más que una manera de entender las cosas. No tienen valor por sí mismos. Seríamos capaces de recrearlos, y tendrían el mismo valor que un sentimiento humano, aunque esa inteligencia viviera dentro de un ordenador. Y acabar con esta inteligencia sería acabar con esta vida, <strong>una vida</strong> casi, por no decir enteramente, <strong>humana</strong>. Además, todo esto implicaría que todo comportamiento humano es predecible. Por último, si esta inteligencia es realmente como un humano, al utilizarla, ¿la estaríamos esclavizando al obligarla a trabajar para nosotros? ¿En qué momento dejaremos de llamarlos &quot;ordenadores&quot; y comenzaremos a tratarles como &quot;humanos&quot;? ¿Será la humanidad capaz de adaptarse al cambio?</p>
1853<!-- ¿y si sólo somos cerebro y logramos recrearlo? ¿tendría sentimientos? -->
1854<h2 id="ejemplos"><a class="anchor" href="#ejemplos">¶</a>Ejemplos</h2>
1855<p>En el siguiente algorítmo genético podemos ver como una figura aprende a saltar, obedeciendo a las leyes físicas (ver en <a href="https://youtu.be/Gl3EjiVlz_4">YouTube</a>):</p>
1856<iframe width="420" height="315" src="https://www.youtube.com/embed/Gl3EjiVlz_4" frameborder="0" allowfullscreen></iframe>
1857<p>Por el contrario, en el siguiente ejemplo, un algorítmo genético aprende a &quot;luchar&quot; contra otra figura: (ver en <a href="https://youtu.be/u2t77mQmJiY">YouTube</a>):</p>
1858<iframe width="560" height="315" src="https://www.youtube.com/embed/u2t77mQmJiY" frameborder="0" allowfullscreen></iframe>
1859<p>Estos cuatro increíbles ejemplos siguientes muestran un proceso evolutivo similar al sufrido por cualquier tipo de ser (ver en <a href="https://youtu.be/GOFws_hhZs8">YouTube</a>):</p>
1860<iframe width="560" height="315" src="https://www.youtube.com/embed/GOFws_hhZs8" frameborder="0" allowfullscreen></iframe>
1861<iframe width="560" height="315" src="https://www.youtube.com/embed/31dsH2Fs1IQ" frameborder="0" allowfullscreen></iframe>
1862<iframe width="560" height="315" src="https://www.youtube.com/embed/IVcvvqxtNwE" frameborder="0" allowfullscreen></iframe>
1863<iframe width="560" height="315" src="https://www.youtube.com/embed/KrTbJUJsDSw" frameborder="0" allowfullscreen></iframe>
1864<h2 id="conceptos"><a class="anchor" href="#conceptos">¶</a>Conceptos</h2>
1865<p class="footnote" id="f.1"><sup>1</sup> <strong>Emular</strong>. Tratar de imitar un modelo, aproximarse a este. Copiar su comportamiento o incluso mejorarlo. <a href="#r.1">↩</a></p>
1866
1867<p class="footnote" id="f.2"><sup>2</sup> <strong>Explícito</strong>. Suceso que ocurre de manera previamente avisada de una forma directa, anticipado <em>sin rodeos</em>. <a href="#r.2">↩</a></p>
1868
1869<p class="footnote" id="f.3"><sup>3</sup> <strong>Velocidad (en hercios)</strong>. Número de cálculos realizados por segundo. Un procesador con una velocidad de 100Hz es capaz de realizar 100 cálculos por segundo. <a href="#r.3">↩</a></p>
1870
1871<p class="footnote" id="f.4"><sup>4</sup> <strong>Base de datos</strong>. Lugar en el que se almacena de manera estructurada una información, como por ejemplo un censo que indique el nombre de las personas, sus apellidos, edad, etcétera. <a href="#r.4">↩</a></p>
1872
1873<p class="footnote" id="f.5"><sup>5</sup> <strong>Regresión</strong>. Las pruebas de regresión consisten en someter a un programa a una serie de pruebas para descubrir fallos en este cometidos accidentalmente con anterioridad en versiones anteriores. <a href="#r.5">↩</a></p>
1874
1875<h2 id="fuentes"><a class="anchor" href="#fuentes">¶</a>Fuentes</h2>
1876<ul>
1877<li><a href="http://waitbutwhy.com/2015/01/artificial-intelligence-revolution-1">Evolución de la inteligencia artificial - Wait but why</a></li>
1878<li><a href="https://en.wikipedia.org/wiki/Machine_learning"><em>Machine learning</em> - Wikipedia</a></li>
1879</ul>
1880</main>
1881</body>
1882</html>
1883 </content></entry></feed>