krig

10 ms·

91.
by krig 8y ago
Ehm, this is just a fundamental misunderstanding. UUIDs are not and are not supposed to be random. They are not even unique. They are just reasonably likely to be unique enough for most purposes.
92.
by krig 8y ago
This made me think about how I learned to program on the Commodore 64: By typing in listings from magazines on little games, like Snake or a little text adventure game etc. When teaching kids I think that could be a great method: Usually, k
93.
by krig 8y ago
If you switch and then quickly switch back because you realised that it was a mistake - that's no big deal. If you switch roles and after a couple of years switch back again - no problem! If you start to have a history of every six mon
94.
by krig 8y ago
First of all, I would say it is absolutely normal to fall out of love with coding, and I wouldn't worry about it! If you're enjoying what you are doing, that's a good thing. Unlike the top comment, I don't think this has
95.
Why So Many People Hate Winter(theatlantic.com)
2 points by krig 8y ago|0 comments
96.
by krig 8y ago
It's also misleading because it's talking about a bomb 1/10th the size of the Hiroshima nuclear detonation, while today, even just India and Pakistan alone have nuclear capabilities that are a hundred times beyond that. The i
97.
by krig 8y ago
I find calling the potential deployment of nuclear missiles at this point ”world war three” slightly misleading. A war has a beginning and an end. There is no end other than the end of the world as we know it on the other side of such strik
98.
by krig 8y ago
”at the same time”
99.
by krig 8y ago
That is certainly a good point. The problem I felt with dropping below malloc is that the code becomes very platform-dependent.
100.
by krig 8y ago
Cool, that's an interesting solution! I tried hard to keep the GC implementation as straight-forward as possible, as a teaching aid, but I'll admit that debugging the GC was a bit of a struggle when roots weren't clearly indi
101.
by krig 8y ago
Yeah the TCO is not complete, it allocates a call frame for each call regardless which is why it ran out of memory. It doesn’t use up the C call stack though, so you could in theory increase the GC heap size to make it survive longer. Due t
102.
by krig 8y ago
I felt the same way about Norvigs version which was one reason to do this. I feel like the recursive lisp interpreter-on-an-interpreter thing is not as clear when so much of the host language is relied on. Oh, and I hear you about integers
103.
by krig 8y ago
Thanks! Yeah, I am thinking that adding a similarly minimal compiler to this would be interesting as a next step. There is a previous effort in the ”old-version” directory which had tagged integers and strings and an attempt at macros, but
104.
by krig 8y ago
Thanks!
105.
by krig 8y ago
Well, I’m also learning to play the piano, and that had certainly been done before and better than me. But the reason for both is that it’s fun and I enjoy doing it.
106.
by krig 8y ago
It works surprisingly well, and appeals to me for its compactness. But i maybe I’ll switch to hashing if I can squeeze that in.
107.
by krig 8y ago
The base language interpreter written in C is a lisp-1, and it’s not even close to a full scheme implementation but it is a subset of scheme. The LISP 1.5 interpreter runs on top and is implemented in the base language.
108.
Show HN: Lisp with copying GC in 537 lines of C (plus Lisp 1.5 on top)(github.com)
152 points by krig 8y ago|34 comments
109.
by krig 8y ago
Just a FYI: SUSE is still developing and using btrfs, both in openSUSE and in the enterprise edition.
110.
by krig 8y ago
"Still, anyone expecting Bitcoin to provide a haven from turbulence in global markets will have been disappointed." No judgment on the future of cryptocurrencies (I'm not prescient), but wouldn't you have to be incredibl
111.
by krig 8y ago
Did you reply to the wrong comment? I honestly don’t understand what you’re talking about, although it sounds like you’re not too happy about MS buying github. I certainly agree about that.
112.
by krig 8y ago
That ”developers” has become synonymous with Open Source shows how far things have come since then. :)
113.
by krig 9y ago
Monorepos are great if you are a monoculture. I don't find it surprising that Google, Facebook and Twitter all enjoy and benefit from monorepos. I also don't find life inside the monochromatic empire particularly appealing. I thin
114.
by krig 9y ago
You’re kind of describing the whole point of Zen, no? ”don't hesitate get laid that's wisdom sitting around chanting what crap” - Ikkyu
115.
by krig 9y ago
Yeah, in hindsight it wasn't a great time for programming languages in general...
116.
by krig 9y ago
> I started developing in Java, late 2001. At that time, Java was really cool. As someone who was there in 2001, I just have to say: Java was never cool, and especially not at that time. It was bloated and ugly and slow, the GC was terri
117.
Cephalocon 2017 is cancelled(ceph.com)
3 points by krig 9y ago|0 comments
118.
by krig 9y ago
There's a swedish company that does houses in a similar style to this, at least close enough to remind me of them. Unfortunately the website is only in swedish as far as I can see, but the photos should translate: http://www
119.
by krig 10y ago
To be fair, the main reason for algorithmic fonts is so that non-latin characters scale up nicely. Storing chinese characters at a high bitmap resolution gets expensive fast, and you'd need several bitmaps for each character to keep th
120.
by krig 10y ago
From the introduction: > In this paper, we describe an algorithm to create a wait-free stack. A concurrent data structure is said to be wait-free if each operation is guaranteed to complete within a finite number of steps. In comparison,

More ›