Hacker Newsnew | past | comments | ask | show | jobs | submit | mossity's commentslogin

It looks pretty well archived to me, where are you seeing things missing?


99% of the spam email I've been getting has been using using static redirect sites hosted on GCS to try to get past spam filters too. I've tried reporting it via https://support.google.com/code/contact/cloud_platform_repor... but it's pretty exhausting.


This wasn't in the kernel, this was just a piece of malware targeting Linux systems


I started reading this thinking Nix was a programming language, became very confused when it started talking about files and an object database.


Smalltalk has object databases, as images.


I thought the book "Philosophy and Simulation" by Manuel de Landa did a really great job of tying together some threads around simulation and it's connection to reality. I haven't read Simulacra but it seems like Baudrillard has gone too far in the direction that French philosophy loves to go by claiming we have cannot have any connection "the real". While an amusing idea it just doesn't match up to our lived experience.


Have you ever shot a firearm? Have you ever played a video game where you shot a firearm? Given some assumptions of your demographic, based on your being here, this example should illustrate the issue Baudrillard foresaw in comprehending 'the real' in modernity.


According to the author, readers of the book are already translating the port of Git in the book to C++, Clojure, Elixir, Haskell, Java, Node, Rust, and Swift

https://twitter.com/mountain_ghosts/status/11148630508075499...


Not exactly what you're getting at but the artist Thijs Rijkers did a series of pieces similar to this, called Suicide Machines: https://vimeo.com/56871178


Reading about CVE-2017-9805 it was really interesting to learn that the company that discovered it was using a Datalog-like language in order to query Java code for vulnerability patterns.

https://en.wikipedia.org/wiki/Semmle


Process Hacker is much better than Process Explorer, plus it's open source :)



The points about the JVM not being able to guarantee that your code won't block the thread apply; it's left up to you to do it. This doesn't come as any surprise to me, nor I would guess to most users of the library, so I'm not sure this is really that damning. Core.async doesn't use bytecode weaving or fork/join, so those criticisms don't specifically apply.


It's damning because, rather than outsource the issue like the library makes you think you are doing (or like anyone writing erlang code actually is doing) you still have to deal with the hassle and the risk, so you're not really buying much.


Except you're using it Clojure, which makes it easier to avoid that kind of stuff and easier to spot when you count on Java APIs directly.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: