Preferences

gnarlouse
Joined 514 karma

  1. Hopefully this doesn’t stoke a third and final world war.
  2. Rivian coming for Teslas crown? I honestly think Rivians are unattractive. Like if a jeep and scion had a drunken tryst. Haven’t seen the interior before though.

    But I’d be glad if somebody was competitive enough to force Elon to behave again.

  3. I'd like to see this as a Windsurf plugin.
  4. I don’t think I’ve every heard of an Apple Services outage until today.
  5. Glass dick
  6. Totalitarianism is a form of class warfare. Make class warfare M.A.D.
  7. This is a good point, I hadn't considered that.
  8. Netflix is fucking its business up by trying to be a studio IMO. The service was perfect when they were a streaming platform. The studio arm's script selection and production quality makes me want to gauge my eyes out.

    When you pay an arm and a leg every month for Netflix, you're funding a studio that pumps out the equivalent of screeching goblin sounds. Makes no sense.

  9. Also don’t shove it up our
  10. I saw “boobs” so I ran.

    -Iran

  11. I think most of the time when small teams say “we should do microservices” what they really mean is “we should try a service oriented architecture.” Especially if you’re doing a monorepo, it becomes fairly routine to make choices around how to consolidate like modules.

    For example, I work in a small company with a data processing pipeline that has lots of human in the loop steps. A monolith would work, but a major consideration with it being a small company is cloud cost, and a monolith would mean slow load times in serverless or persistent node costs regardless of traffic. A lot of our processing steps are automated and ephemeral, and across all our customers, the data tends to look like a wavelet passing through the system with an average center of mass mostly orbiting around a given step. A service oriented architecture let us:

    - Separate steps into smaller “apps” that run on demand with serverless workers.

    - avoid the scaling issues of killing our database with too many concurrent connections by having a single “data service”—essentially organizing all the wires neatly.

    - ensure that data access (read/write on information extracted from our core business objects) happens in a unified manner, so that we don’t end up with weird, fucky API versioning.

    - for the human in the loop steps, data stops in the job queue at a CRUD app as a notification, where data analysts manually intervene.

    A monolith would have been an impedance mismatch for the inherent “assembly line” model here, regardless of dogma and the fact that yes, a monolith could conceivably handle a system like this without as much network traffic.

    You could argue that the data service is a microservice. It’s a single service that serves a single use case and guards its database access behind an API. I would reply to any consternation or foreboding due to its presence in a small company by saying “guess what, it works incredibly well for us. Architecture is architecture: the pros and cons will out, just read them and build what works accordingly.”

  12. Think of it like the Bro App from “Silicon Valley”, just with the charm of a doorstop. ;D
  13. I’m doing AoC on Zig this year. Zigtools will be my reference. Cheers!
  14. At one point they added a “R******D COMPLAINT” (censored for HN) ticket sticker to… idk, oppose AI-use accusations? Somebody seemingly talked them down from it though. Just bizarre. Like watching a midlife crisis through GitHub issues.
  15. @gregasadetsky: you should make it social… you know, like, just because. Like I want to be able to send my sister my latest “Boing,” and see what she thinks of my technique.
  16. My best offering is the engine sim which may or may not have a lib. https://github.com/ange-yaghi/engine-sim If nothing else, it’s a brilliant, novel oddity.
  17. Is this physics based audio?
  18. Had a conversation with the Zigbook maintainer. It’s either a young kid or somebody that has some serious growing up to do. Just generally weird behavior.
  19. I think Billionaire alignment is a much larger problem than AI alignment. To use Bostrom's language, it's not full-on owl domestication, but sparrows with owl-like powers that we need to worry about.

    https://lukemuehlhauser.com/bostroms-unfinished-fable-of-the...

  20. You should go see "Bugonia" by Yorgos Lanthimos, if you haven't yet, then! That movie might be straight up your alley.

This user hasn’t submitted anything.