tinyspacewizard · HackerTrans

tinyspacewizard

no profile record

Submissions

Tying the Knot

wiki.haskell.org

3 pointsby tinyspacewizard10 miesięcy temu0 comments

Zippers: Making Functional "Updates" Efficient (2010)

goodmath.org

63 pointsby tinyspacewizard10 miesięcy temu15 comments

Why isn't differential dataflow more popular? (2021)

scattered-thoughts.net

2 pointsby tinyspacewizard12 miesięcy temu0 comments

RelationalFactQA: A Benchmark for Evaluating Tabular Fact Retrieval from LLMs

arxiv.org

1 pointsby tinyspacewizardw zeszłym roku0 comments

Higher-kinded bounded polymorphism in OCaml (2021)

okmij.org

141 pointsby tinyspacewizard2 lata temu10 comments

The Moirai Programming Language

github.com

2 pointsby tinyspacewizard2 lata temu0 comments

The Kernel Programming Language

web.cs.wpi.edu

2 pointsby tinyspacewizard4 lata temu1 comments

UK to extend compulsory math education to 18

bbc.co.uk

9 pointsby tinyspacewizard4 lata temu1 comments

Why calculating is better than scheming (1987) [pdf]

cs.kent.ac.uk

3 pointsby tinyspacewizard4 lata temu1 comments

comments

tinyspacewizard

9 miesięcy temudiscuss

Start-ups should strongly consider F#.

It's a force multiplier when you have a small team of strong developers.

tinyspacewizard

10 miesięcy temudiscuss

What should we use instead?

tinyspacewizard

10 miesięcy temudiscuss

> Why two cloud providers? Initially we used only DigitalOcean, but a data intensive SaaS like tap needs a lot of cloud resources and AWS have a generous $1,000 credit package for self-funded startups.

So some Kubernetes experts migrated to AWS for $1k in credits. This is madness. That's weeks of migration work to save the equivalent of a day of contracting.

tinyspacewizard

10 miesięcy temudiscuss

> Of course you can inspect it: open the source code you wrote and read it. Also, don't write the code you don't want to be executed?

This is not what they meant by inspection.

What they mean is that you can write a function, in Haskell, that given a value in the DSL, it returns the list of all requests it will perform on execution.

This can be useful for tests, security, caching, performance, debugging...

tinyspacewizard

10 miesięcy temudiscuss

This seems like a cool article, but it isn't readable without Haskell background knowledge.

> For an intuition why this is true, consider that the constant functor Const r has an Applicative instance whenever r is a monoid, because pure stores a mempty value and (<*>) combines the held values with (<>). For a fun exercise, implement runAp_ in terms of runAp and Const.

Really?

tinyspacewizard

10 miesięcy temudiscuss

Weird feeling knowing that an ecommerce / wallet store has employees with more advanced programming knowledge than most financial institutions.

tinyspacewizard

10 miesięcy temudiscuss

1. Wrapping is more code than using a built-in pipe operator

2. There is a run-time overhead to wrapping

IMO a design goal of programming langauges should be for the most readable code to also be the most performant.

Language features tend to be controversial until they are mainstream.

tinyspacewizard

10 miesięcy temudiscuss

There is more than one proposal; the F#-style one doesn't have the (weird) placeholder syntax.

> You can still make it work by adding it to the prototype

This is exactly what we want to avoid!

tinyspacewizard

10 miesięcy temudiscuss

Pipes are great where you want to chain several operations together. Piping is very common in statically typed functional langauges, where there are lots of different types in play.

Sequences are a common example.

So this:

    xs.map(x => x * 2).filter(x => x > 4).sorted().take(5)

In pipes this might look like:

    xs |> map(x => x * 2) |> filter(x => x > 4) |> sorted() |> take(5)

In functional languages (of the ML variety), convention is to put each operation on its own line:

    xs 
    |> map(x => x * 2) 
    |> filter(x => x > 4) 
    |> sorted() 
    |> take(5)

Note this makes for really nice diffs with the standard Git diff tool!

But why is this better?

Well, suppose the operation you want is not implemented as a method on `xs`. For a long time JavaScript did not offer `flatMap` on arrays.

You'll need to add it somehow, such as on the prototype (nasty) or by wrapping `xs` in another type (overhead, verbose).

With the pipe operator, each operation is just a plain-ol function.

This:

    xs |> f

Is syntactic sugar for:

    f(xs)

This allows us to "extend" `xs` in a manner that can be compiled with zero run-time overhead.

tinyspacewizard

10 miesięcy temudiscuss

Sad that the pipe operator proposal seems to have stalled.

The F# version of the proposal was probably the simplest choice.

tinyspacewizard

2 lata temudiscuss

Brexit made this far less likely - but perhaps people in France, Germany, Spain, etc. could do this.

tinyspacewizard

2 lata temudiscuss

Functional Programming hasn't even been tried for game development, really. There is a lack of overlap between the game dev industry and academia. The studios are (rightly) risk averse and try to use the same broad strategies to build games - OOP, maybe ECS for large swarms, etc.

Personally, I think that FP could be a great fit, but we first need to come up with architectures that solve real game development problems. We have to do this with small scale experiments first (game jams are perfect for this) and then scale up only if they succeed.

This project is exactly that - kudos to the author.

tinyspacewizard

2 lata temudiscuss

You should put this online somewhere!

tinyspacewizard

2 lata temudiscuss

Expect a wave of artists moving into education to make ends meet.

tinyspacewizard

2 lata temudiscuss

Also a bit scary to have a system without a scaling mechnism built-in in the path of customer traffic. At some point you may be racing to upgrade it.

tinyspacewizard

2 lata temudiscuss

Python is really bad at recursion (part of why it's not appropriate for functional programming), so perhaps an unfair benchmark?

A Pythonic implementation would use loops and mutation.

tinyspacewizard

2 lata temudiscuss

I think what Meta is doing is really smart.

We don't really know where AI will be useful in a business sense yet (the apps with users are losing money) but a good bet is that incumbent platforms stand to benefit the most once these uses are discovered. What Meta is doing is making it easier for other orgs to find those use-cases (and take on the risk) whilst keeping the ability to jump in and capitalize on it when it materializes.

As for X-Risk? I don't think any of the big tech leadsership actually beleive in that. I also think that deep down a lot of the AI safety crowd love solving hard problems and collecting stock options.

On cost, the AI hype raises Met's valuation by more than the cost of engineers and server farms.

tinyspacewizard

2 lata temudiscuss

Terraform is not really a competitor. Maybe Nomad is? I expect most K8s shops use a bit of Terraform, maybe Vault, etc.

tinyspacewizard

2 lata temudiscuss

Could easily be leverage in the negotiation.

tinyspacewizard

2 lata temudiscuss

Google support Kubernetes, so there's precedent there.

I could see Microsoft keeping things open too. So far they have done OK with GitHub and NPM.