I'm incredibly grateful that Perl is dying...spending three hours on manually tracking down dependencies is no fun.
Especially when you're used to stack/cargo making it "just work".
STARTUP IDEA:
Gitcoin.
A distributed trustless proof-of-slack version-controlled currency where to gain credit you must create, and then abandon, an open source software project that ALMOST - but not entirely, and not well - solves a real world problem.
Bad idea of the day:
Altcoin where proof of work is dirty limericks. Must be hash-unique, contain only dictionary words, and scan. Owner of a hash owns the copyright so good ones will be more valuable.
Damnit, I might be a #datahoarder :/
I've recently downloaded ~30k classical pieces. If it were my job to listen through it, it would take 300 days of full-time work. At 2h per day, it'll take three years.
In other words: I've acquired a lifetime supply of classical music in 3 days.
Yet my impulsive question is "should I donate to the tracker to be able to grab more?", not "how the fuck will you listen to all of this?"
Fellow datahoarders: How *do* you listen/read through all of this?
Yes, images are gone, again thanks to Scaleway. It's being fixed, but just really slow.
there's nothing like reading through production python code and finding where they use exec and eval to load in a module and run a method whose names they get at runtime.
folks, python has some pretty amazing introspection capabilities that let you do this without opening a max-max-truck-sized security hole.
*checks history on this file*
yes, even in python 2.6, you could still avoid eval/exec.
For those who don't know the paper, this is a must read[0]. There is also a programming language based on its main contribution[1].
[0] Zongker, D: Chicken Chicken Chicken: Chicken Chicken (https://isotropic.org/papers/chicken.pdf)
[1] https://esolangs.org/wiki/Chicken
After a chat on #gentoo-haskell, it turns out that compiling on ramfs and Hardened do not go together.
ramfs does not support XATTRs (tmpfs does), which paxctl-ng uses to store PaX markings, so you end up with a GHC that has no -m (no MPROTECT, i.e. no W^X) marking set. And one of the very first things GHC does is a RWX mmap()...
1. Minor GHC breakage due to grsecurity
2. Recompile everything Haskell
3. ???
4. Complete GHC breakage due to RWX mmap() vs grsecurity
Not what I wanted.
This is a good repo (if you want to pull a little CSS prank on someone): https://github.com/queueRAM/aprilFools.css
[my impression of the state of AI in pop culture, snarky, sorry]
RESEARCHER: I have made yet another somewhat interesting way to transform one spreadsheet into another spreadsheet
JOURNALISTS: we're all doomed by robots lol
[fin]
CDs scare birds because they have good enough vision to see all the pits and troughs and theyre smart enough to decode a ISO 9660 filesystem on-the-fly (literally)
"/tmp: write failed, file system is full", buried under 1500 lines of other stderr. Slightly suboptimal.
Bah, OpenBSD's tar(1) is insane. Incredibly short filename limit (not even 128 chars, as it seems), simply breaks with "tar: End of archive volume 1 reached" for some as-of-yet unknown reason without any error message...not the kind of reliability I want :(
I'd been wanting to turn some of my conversations with @chris_martin into blog posts, because over the course of conversation we've covered some topics pretty thoroughly, this is how we're writing The Joy of Haskell, and also it allows for presentation of two perspectives on a subject naturally. First one is about do-notation:
https://joyofhaskell.com/posts/2017-05-07-do-notation.html
Oh. That's probably worth remembering. /\d/ in Perl finds Unicode numerals, which gets you much more than /[0-9]/ - unless you use the /a modifier for restricting to ASCII text.
http://blogs.perl.org/users/ben_bullock/2017/05/d-does-not-validate-numbers.html
So, things on my mind right now:
1) the computing platform I really want (and I do not have),
2) how to grab all that unhappy scientific talent in the US and bring it to Europe,
3) introducing liability in software "the right way",
4) a new processor design,
5) a resilient IoT basis design,
6) desperate desire to play waterpolo again,
7) several books to read and digest,
8) have tea with interesting people (not a conference).
Space for more...
kernel: [55672.113692] huawei_cdc_ncm 1-2:1.1 wwp0s20f0u2i1: renamed from wwan0
udev...stahp... >.<
Due to Rotational Velocidensity, compressed media files lose about 12 kbps per year.
https://www.urbandictionary.com/define.php?term=Rotational%20Velocidensity
#trollolol
(Can you imagine, though?)
