HackerLangs
TopNewTrendsCommentsPastAskShowJobs

mbo

1,253 karmajoined hace 9 años

comments

mbo
·hace 5 días·discuss
the show source toggle is using https://blog.glyphdrawing.club/font-with-built-in-syntax-hig... (and the author is infact the creator of it)
mbo
·hace 7 días·discuss
I'm not sure this is a helpful comment. This is a common story with many medications, where someone notices their feelings are off and suddenly remembers that there is a probable root cause. It's why medications list side effects.
mbo
·hace 17 días·discuss
Another company like this is Blackmagic Design. Despite being overwhelmingly based in Australia, you'd think it was an American company based on office listing ordering on https://www.blackmagicdesign.com/company/offices and /company page.
mbo
·hace 24 días·discuss
It is a win-win for Photobucket users who have their images (which OP is NOT a cohort of) preserved long term and the startup who snapped up Photobucket's data and liabilities. It is fair to say that OP experienced a win-loss in this specific situation.

I did not assume that OP got the images. That's why I explicitly called it out. In my first sentence. And again in my second last sentence. Jesus.
mbo
·hace 24 días·discuss
Yes that's exactly why I mentioned that in the first line of my comment. I quote directly:

> (I do agree that it's bad that there were no images preserved and that component of the post is justifiable)
mbo
·hace 24 días·discuss
Why are we complaining about this as a corporate greed thing? (I do agree that it's bad that there were no images preserved and that component of the post is justifiable)

Obviously Photobucket completely failed to properly monetize, and was sold to Fox and then offloaded to some no-name startup called Ontela (https://en.wikipedia.org/wiki/Photobucket). The service could have been shutdown completely and the harddrives fed into the shredder. Instead some former PE vulture did the math and figured out that preservation might make some money. You _can_ access old Photobucket images (when it works) that would otherwise get a median of 0 hits a month, while the rest of the internet succumbs to linkrot. Seems like a win-win for everyone involved.
mbo
·el mes pasado·discuss
Yes confirmed, I did not author the DALL-E paper lmao
mbo
·el mes pasado·discuss
Look, not to brag but DALL-E's "armchair in the shape of an avocado" was mine (https://openai.com/index/dall-e/). I remember trying to convey the gravity of this capability to my friends at the time, who I guess were not as impressed as me.
mbo
·hace 2 meses·discuss
I just messaged a few of my friends who I know are devoutly Catholic (and also happen to work in AI): 3 out of 4 are currently reading it this morning for their Memorial Day.
mbo
·hace 2 meses·discuss
It's not. 100% on Pangram.
mbo
·hace 2 meses·discuss
I feel like there needs to be some sort of intermediate black screen between the questions, a visual "palette cleanser" if you will. I was actively noticing the saturation of the color decline as I stared at the screen.
mbo
·hace 3 meses·discuss
Could this support a native datetime type? I shipped a much worse of this for managing repeated events and schedules.
mbo
·hace 3 meses·discuss
A commonly trotted out argument for continued investment in manned space flight is technological spillover: that all the money we give to NASA generates positive benefits in other sectors of the economy. I'm not so sure space toilets are generating that spillover. This seems like a uniquely expensive humans-in-space engineering problem. I echo the sentiments of Why Not Mars (https://idlewords.com/2023/1/why_not_mars.htm):

> The web of Rube Goldberg devices that recycles floating animal waste on the space station has already cost twice its weight in gold and there is little appetite for it here on Earth, where plants do a better job for free. [...] I would compare keeping primates alive in spacecraft to trying to build a jet engine out of raisins. Both are colossal engineering problems, possibly the hardest ever attempted, but it does not follow that they are problems worth solving. [...] Humanity does not need a billion dollar shit dehydrator that can work for three years in zero gravity, but a Mars mission can’t leave Earth without it.

Why are we doing human spaceflight again?
mbo
·hace 3 meses·discuss
Given some system under test (SUT) with inputs (T, G...) and expected outputs derived from the inputs T', G' etc., a property based testing framework attempts to exercise the entire domain of values assignable to T, G, etc. against the SUT.

The generators of T, typically called an Arbitrary<T> can be constrained, e.g Arbitrary<number> could generate any float or just non-negative integers. Ideally we would define an Arbitrary<float64> or Arbitrary<u64>.

A sufficiently expressive type system makes it easier to narrow the gap between what is generated and what is assignable to type T, making it clearer what the valid input domain to the SUT is.
mbo
·hace 3 meses·discuss
Pangram has a very low false positive rate, but not the best false negative rate: https://www.pangram.com/blog/third-party-pangram-evals
mbo
·hace 3 meses·discuss
Note that this is contrary to the convention used in the Erlang community, where the number is used to disambiguate function definitions with different parameter counts, e.g. in https://www.erlang.org/docs/18/man/supervisor.html we see definitions of `start_link/2` and `start_link/3`.

It is a stylistic convention to always add this number to any reference to a function, even if there is only one definition.
mbo
·hace 3 meses·discuss
PICA-3, per https://caseyhandmer.wordpress.com/2025/10/31/nasas-orion-sp...

> All this would be inexplicable enough if, indeed, AVCOAT was the only known material from which heat shields could be built. But while Lockheed continues to soak the US taxpayer and play chicken with the lives of NASA’s astronauts with this “flight proven” (but completely different) design, Lockheed happily built a PICA heat shield for JPL’s large Mars rovers Curiosity and Perseverance, and SpaceX’s Dragon capsule also uses PICA-3.
mbo
·hace 4 meses·discuss
man, this cat is ranking pretty high on the feline grimace scale :( https://meow.camera/#4258783365322591678 wondering how I would contact the hosts
mbo
·hace 4 meses·discuss
I'm not sure I'm understanding this workflow. Perhaps a small tutorial / walkthrough hosted on YouTube or asciinema might help people understand.
mbo
·hace 4 meses·discuss
I never understood why Rust couldn't figure this shit out. Scala did.

> If a crate doesn’t implement serde’s traits for its types then those types can’t be used with serde as downstream crates cannot implement serde’s traits for another crate’s types.

You are allowed to do this in Scala.

> Worse yet, if someone publishes an alternative to serde (say, nextserde) then all crates which have added support for serde also need to add support for nextserde. Adding support for every new serialization library in existence is unrealistic and a lot of work for crate authors.

You can easily autoderive a new typeclass instance. With Scala 3, that would be:

  trait Hash[A]:
    extension (a: A) def hash: Int

  trait PrettyPrint[A]:
    extension (a: A) def pretty: String

  // If you have Hash for A, you automatically get PrettyPrint for A
  given autoDerive[A](using h: Hash[A]): PrettyPrint[A] with
    extension (a: A) def pretty: String = s"<#${a.hash.toHexString}>"
> Here we have two overlapping trait impls which specify different values for the associated type Assoc.

  trait Trait[A]:
    type Assoc

  object A:
    given instance: Trait[Unit] with
      type Assoc = Long

    def makeAssoc: instance.Assoc = 0L

  object B:
    given instance: Trait[Unit] with
      type Assoc = String

    def dropAssoc(a: instance.Assoc): Unit =
      val s: String = a
      println(s.length)

  @main def entry(): Unit =
    B.dropAssoc(A.makeAssoc) // Found: Playground.A.instance.Assoc Required: Playground.B.instance².Assoc²

Scala catches this too.