h0l0gr4ph1c

6 ms·

1.
by h0l0gr4ph1c 6y ago
so the firing party has an active homing beacon, aimed at you, just before they are about to fire? hmmmmmmmmmmmmmmmm yep no problems with that approach at all
2.
by h0l0gr4ph1c 6y ago
both contain water.
3.
by h0l0gr4ph1c 6y ago
If they got in this far, what else did they get access to? How long have they had access? Saying its only a db * that they know of* . What about the software repositories that they host somewhere?? Did the admin have access to that? This is
4.
by h0l0gr4ph1c 6y ago
A generation is generally defined as 20 years. So you mean 3.5 generations i guess?
5.
by h0l0gr4ph1c 6y ago
On another note, have you contacted facebook to get the data removed from their servers?
6.
by h0l0gr4ph1c 6y ago
Rust is a language that does things different to other languages because it is a better way. I challenge you to do the same with Async. There is a different better way.
7.
by h0l0gr4ph1c 6y ago
By opt in I mean I can opt in to using an executor if I want async. If I don't code still works and is might not be as performant. Couldn't you have made another hard constraint to make async code work as normal if the programmer
8.
by h0l0gr4ph1c 6y ago
I actively choose libraries that are non-async. I don't want to use the programming model. If aysnc could work like regular blocking code , if we want, and async code when you want, I think rust would be in a better place. Just because
9.
by h0l0gr4ph1c 6y ago
yes sorry, those were rhetorical questions. Your point about asking you fail to see why not using a blocking executor to deal with the async code. My problem is with needing the executor at all. I must have skipped a couple of you previous
10.
by h0l0gr4ph1c 6y ago
> "Using a proper, single-threaded executor and running it on the current thread seems like it would work, yes. (To be fair, I also feel like just having the sync version of a Python API call "trio.run(self.equivalent_async_api
11.
by h0l0gr4ph1c 6y ago
Complexity kills code. Being able to reason about what your code is doing, is FAR more valuable to me than async. Having tokio act as my runtime and switch tasks as it sees fit will be debug hell. The problem I see is the current async stor
12.
by h0l0gr4ph1c 6y ago
IIRC our system of time is more so aligned with midday rather than midnight. As that is when the sun is at its highest point in the sky, which allowed us to create a common point between timezones.
13.
by h0l0gr4ph1c 6y ago
As someone who bought a RX580 for playing with Deep learning with ROCm (It was supported at the time). After posting to one or two bug threads, I had the same experience as the gp -- our issues were ignored. The issues have recently closed
14.
by h0l0gr4ph1c 6y ago
It still won't. If you look at history we have been always shifting towards information storage that is easier and thus less energy intensive to copy. Art by definition has done the opposite. Unique pieces that are HARD to copy (IIRC a
15.
by h0l0gr4ph1c 6y ago
LOL, just had exactly the same thought.
16.
by h0l0gr4ph1c 6y ago
> And I'm no Rust developer, but it looks to me like it basically demonstrates how Rust is an abject failure in that regard. The developer has to jump through lots of nonobvious hoops and choose between competing libraries to get an
17.
by h0l0gr4ph1c 6y ago
Thanking you.
18.
by h0l0gr4ph1c 6y ago
You are say that the ReMarkable is open, but where is the GPLv2 code for the underlying Linux OS? As far as I can see there is nothing on the site that makes mention to it. That includes the Legal section which makes no mention of the GPL l