HackerTrans
TopNewTrendsCommentsPastAskShowJobs

valcron1000

no profile record

comments

valcron1000
·18 giorni fa·discuss
This guy has been preaching against crypto for years, to the point of leaving the Haskell ecosystem just because the language was being used by Cardano. At some point you have to wonder what's going on with him...
valcron1000
·2 mesi fa·discuss
Damn, that looks awful.
valcron1000
·2 mesi fa·discuss
Where can we read the code?
valcron1000
·2 mesi fa·discuss
> if it’s a solo greenfield project

That's a big if. I don't have numbers but most professional engineers are not working on such projects
valcron1000
·4 mesi fa·discuss
I've been thinking of doing the exact same thing. Preserve context as images and die. Expose a single tool called "eval". You could have a extremely tight editor integration using something like SLIME.
valcron1000
·5 mesi fa·discuss
Still nothing to compete with GPT-OSS-20B for local image with 16 VRAM.
valcron1000
·6 mesi fa·discuss
> When something breaks, I SSH in, ask the agent what is wrong, and fix it.

> I am spending time using software, learning

What are you actually learning?

PSA: OP is a CEO of an AI company
valcron1000
·6 mesi fa·discuss
If international law had any effect people would believe in it. You're mixing cause/effect. This situation has been going on for years and the lack of response by international organizations makes people lose all confidence in them.
valcron1000
·7 mesi fa·discuss
I'm unfortunately on the same situation. We made a consultation with people from Baptist Health Miami and it seems like there are several non trivial requirements for such treatment (histotripsy), like the number and location of mets. Hope that this improves in the mear future.
valcron1000
·7 mesi fa·discuss
One of the first things I tried in Rust a couple of years ago coming from Haskell. Unfortunately it's still not stabilized :(
valcron1000
·8 mesi fa·discuss
> Memory safety is not that sacred. In fact, for many applications malfunctioning is better than crashing

Yeah, just another data leak, no biggie.
valcron1000
·8 mesi fa·discuss
Not at the same level. TRAMP is way behind feature-wise.
valcron1000
·8 mesi fa·discuss
> Zig must also be good for eliminating the same ones.

But Zig does not eliminate them, but rather it might catch them at runtime. The difference here is that Rust promises that it will detect them at compile time, long before I ship my code.

> The property of memory safety is itself not binary in both languages

In this case it is: either you catch the issue at compile time, or you don't. This is the same as type safety: just because Python can detect type errors at runtime it does not mean that it's as "type safe" as, for ex. Haskell. This might be due to imprecise usage of terms but that's just the way it's discussed in the craft.
valcron1000
·8 mesi fa·discuss
Yes, but instances require the user to provide shrinking while Hypothesis does not: shrinking is derived automatically.
valcron1000
·8 mesi fa·discuss
In the sense that you only need to work with the standard IO monad to get the benefits of the runtime.
valcron1000
·8 mesi fa·discuss
You don't need "monads" (in plural) since GHC provides a runtime where threads are not 1:1 OS threads but rather are managed at the user level, similar to what you have in Go. You can implement async/await as a library though [1]

[1] https://www.cambridge.org/core/services/aop-cambridge-core/c...
valcron1000
·8 mesi fa·discuss
> async/await is also available in a bunch of other languages, including F#, C#8, Haskell[...]

Haskell (GHC) does not provide async/await but uses a green thread model.
valcron1000
·8 mesi fa·discuss
> Knowing if a function will yield the thread is actually extremely relevant knowledge you want available.

When is this relevant beyond pleasing the compiler/runtime? I work in C# and JS and I could not care less. Give me proper green threads and don't bother with async.
valcron1000
·8 mesi fa·discuss
> I mean, Haskell has like what, 2, 3, 4? Major build systems and package repositories? It's a quagmire.

Don't know when was the last time you've used Haskell, but the ecosystem is mainly focused on Cabal as the build tool and Hackage as the official package repository. If you've used Rust:

- rustup -> ghcup - cargo -> cabal - crates.io -> hackage - rustc -> ghc
valcron1000
·8 mesi fa·discuss


    } catch (exception: Exception) {
      // log exception
      throw exception
    }
Probably the most harmful snippet ever written. Every blog post about errors has something similar written, regardless of the programming language. Please, don't write, suggest or even pretend that this should exist.