Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mrkeen
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
27 ms
·
451.
▲
by
mrkeen
1y ago
Trying to find the key idea here, which I'm not picking up in the abstract. 3.4 Evaluation Strategy The confluence of our semantics enables us to soundly step statements in unusual orders. However, for an implementation, we need
452.
▲
by
mrkeen
1y ago
That is called a 'consumer group' which has been a part of Kafka for 15 years. The author is suggesting to avoid this solution and roll your own instead.
453.
▲
by
mrkeen
1y ago
It is a gigantic advantage! And you are missing something! ACID is an aspirational ideal - not something that 'just works' if you have a database that calls itself ACID. What ACID promises is essentially "single-threaded th
454.
▲
by
mrkeen
1y ago
Elm died however many years ago and it's still a more pleasant experience than a typical React stack.
455.
▲
by
mrkeen
1y ago
The tradeoff here is that Kafka will still work perfectly if one of its instances goes down. (Or you take it down, for upgrades, etc.) Can you lose one Postgres instance?
456.
▲
by
mrkeen
1y ago
Right, the author's worldview is that Kafka is resume-driven development, used by people "for speed" (even though they are only pushing 500KB/s). Of course the implementation based off that is going to miss a bit.
457.
▲
by
mrkeen
1y ago
Event-sourcing != queue. Event-sourcing is when you buy something and get a receipt, you go stick it in a shoe-box for tax time. A queue is you get given receipts, and you look at them in the correct order before throwing each one away.
458.
▲
by
mrkeen
1y ago
> I'd go a little further, though? Transactions have to be able to fail at the very last step. That could just be the "commit" stage. I don't know what you mean by going a little further. I said transactions are 
459.
▲
by
mrkeen
1y ago
Carmack is on the record as pro-Musk.
460.
▲
by
mrkeen
1y ago
> You really don't want And that's what this thread is filled with, and that's what I'm pushing back against. > the RAI pattern is nice > indicate if you are in different sections is nice Style doesn't matt
461.
▲
by
mrkeen
1y ago
And "I call it my billion-dollar mistake. It was the invention of the null reference in 1965" is from 2009. Hopefully by 2045 these ideas will have gotten a little more traction.
462.
▲
by
mrkeen
1y ago
> This works right up to the point where you try to make the code to support opening transactions Indeed. It's all well and good to impart some kind of flavour into your code and call it functional, but transactions do not give a c
463.
▲
by
mrkeen
1y ago
> you want to restrict the runtime substitution of function calls with their result values? I don't get how you got there from parent comment. Pascal just went with a needless syntax split of (side-effectful) methods and (side-effec
464.
▲
by
mrkeen
1y ago
* Government makes services available via auth app of their choosing. * Auth app deploys to one or two app stores. No financial incentive to do otherwise. * App stores remain within walled gardens. Tracking, DRM, proprietary drivers come
465.
▲
by
mrkeen
1y ago
> I’m still shocked by the number of people who seem to believe that the borrow checker is some kind of magic. It shouldn't be magic. It should be routine and boring, like no-nulls, pure functions, static typing and unit tests.
466.
▲
by
mrkeen
1y ago
I didn't see the Grok, but the Omarchy creator is quite openly problematic anyway: https://world.hey.com/dhh/as-i-remember-london-e7d38e64
467.
▲
by
mrkeen
1y ago
> Dana smirks. “Well, yeah. JavaScript is an eager language. Can’t use the Y combinator.” Does anyone know off the top of their head if the Z combinator would just work here? (Instead of switching to Skoobert)
468.
▲
by
mrkeen
1y ago
> we’ve decided mutation is evil The functional programmers have decided mutability is evil. The imperative programmers have not. We functional programmers do crazy stuff and pretend we're not on real hardware - a new variable inst
469.
▲
by
mrkeen
1y ago
> it seems that with signals you must use immutable values only. Imagine if you have, let's say, a text document model, and you need to create a new copy every time the user types a letter. Too small. Imagine if you have a 2GB muta
470.
▲
by
mrkeen
1y ago
> Not sure why there is so much hate on this thread. 1) "Kafka is resume-driven-development" is a meme. 2) Devs are in denial about being in a distributed system, and think that single-threaded thinking (in proximity to a DB th
471.
▲
by
mrkeen
1y ago
You're getting hung up on the "double" entries. That's mostly for reducing accidental and deliberate (fraud) calculation errors if you have humans crunching the numbers. The two entries can be in the same row if you li
472.
▲
by
mrkeen
1y ago
Your engineers are wrong. You're not going to be able to bridge that gap. Here's a scenario: you've partnered with a credit card provider. They charge some money each month per card, and you pass that onto your customers wh
473.
▲
by
mrkeen
1y ago
* Most single-db deployments give up on ACID for performance reasons (see READ_COMMITTED) * Even if you have ACID, it's not sufficient for distributed systems. Its guarantees will keep one node consistent with itself . No transact
474.
▲
by
mrkeen
1y ago
There is a very real chance of this happening, and two choices. One - bake whatever happens into your system permanently, like 99% of all apps, and disallow corrections. Two - keep the events around so that you can check and re-check your
475.
▲
by
mrkeen
1y ago
It would be outside of the normal exceptional cases, yes. Like buggy data that crashes the system. If you have the old events there, you can "measure twice, cut once", in the sense that you can keep re-running your old events and
476.
▲
by
mrkeen
1y ago
If logging is non-functional, then you can't log in a functional core. Luckily you can log functionally.
477.
▲
by
mrkeen
1y ago
I'm not sure if I missed this in the article, but what's the cost of failure? Why can't OpenAI keep projecting/promising massive data centre growth year after year, fail to deliver, and keep making Number Go Up?
478.
▲
by
mrkeen
1y ago
The first time it ran ok. But I had no way to do it again. Spent hours trying to get the Mac partitioner to just clear out the space so I could re-run the installer. No dice. In the end I did a factory reset of the whole macbook and then
479.
▲
by
mrkeen
1y ago
All of this! "Pure functional" isn't a style choice. The judges won't hold up big placards with 10 on them because you executed your business logic in style. It's a contract that your code will give the same output
480.
▲
by
mrkeen
1y ago
I have a pretty good time on Asahi Fedora (macbook air M1). It supposedly also supports M2 but no higher. And it's a PITA to install (needs to be started within macosx, using scripts, with the partitions already in a good state)
More ›