preseinger

11 ms·

61.
by preseinger 3y ago
where do debug symbols exist, if not "interleaved" with the code?
62.
by preseinger 3y ago
can you point me to any meaningful use of the clr in the browser? i'm not aware of any
63.
by preseinger 3y ago
not really do you not do code review?
64.
by preseinger 3y ago
if you pass a logger to a foo as a parameter to the foo constructor, then missing a logger is a compile-time error if you pass a logger to a foo as a parameter in the request context, then missing a logger is a run-time error
65.
by preseinger 3y ago
your link describes a very narrowly scoped benchmark, not something that is generally applicable
66.
by preseinger 3y ago
wasm has properties that are unique versus other existing bytecode systems those properties are important
67.
by preseinger 3y ago
nobody is deploying clr applications anywhere where wasm applies
68.
by preseinger 3y ago
well, that, and performance and mindshare
69.
by preseinger 3y ago
it started there but that's not like the only goal of the thing and like there's plenty of people doing wasm on the server where performance is measured in microseconds
70.
by preseinger 3y ago
containers are FAR slower than regular processes, by almost all performance metrics wasm is orders of magnitude faster -- actually comparable to native execution, at least on the server
71.
by preseinger 3y ago
wasm compiles to "native" code, for whatever "native" means in your execution environment if you're deploying wasm to the browser, then native means your JS engine if you're deploying wasm to the server, then n
72.
by preseinger 3y ago
wasm doesn't give you a vm, it gives you a process
73.
by preseinger 3y ago
wasm is not bound to javascript in any meaningful sense
74.
by preseinger 3y ago
they're indeed very similar the main difference distills down to execution/implementation java applets were slow, wasm is fast that distinction makes a categorical difference
75.
by preseinger 3y ago
bad: first()?.second()?.third()? good: a = first() if a failed, handle that error b = second(a) if b failed, handle that error c = third(b) if c failed, handle that error yield c
76.
by preseinger 3y ago
huh? there's no dogma involved here, it's just an observation of the properties of the type a context is created with each request, and destroyed at the end of it and values stored in a context are accessible only through un-typed
77.
by preseinger 3y ago
yes, in general the context stores request-scoped data, whether or not the logger is a request-scoped value is a grey area and to reply to sibling comment, opentelemetry is basically a house of antipatterns, definitely do not look to it for
78.
by preseinger 3y ago
that person was wrong
79.
by preseinger 3y ago
"the language level" is not only what is defined and enforced by the compiler but i'm sure i won't convince you of anything here, so good luck to you
80.
by preseinger 3y ago
the question is: does it matter if a given expression fails? if so, get the error and evaluate it -- like if json.Marshal fails in your http.Handler if not, (shrug) -- like (maybe) if your fmt.Printf fails panics are for core assertion viol
81.
by preseinger 3y ago
chaining means combining a sequence of expressions that each take the same input as they give as output ; doesn't do this, afaict when you're writing imperative code it's important that control flow (return) is explicitly vis
82.
by preseinger 3y ago
nah go error messages are clear to users without being cryptic
83.
by preseinger 3y ago
you know i looked into it and it turns out that there is no actual consensus on what "the _right_ way" to treat errors is! huh! how about that
84.
by preseinger 3y ago
some keywords are types, but not all types are keywords, right? like, it's not as if the go type `float64` is also a go keyword but i guess the java type `byte` is a java keyword? according to https://docs.oracle.com/ja
85.
by preseinger 3y ago
true! of course.
86.
by preseinger 3y ago
supercharged!!! how much faster are your development workflows now, versus before? like 100x? how complex were your previous development workflows? what did that complexity manifest as? how has nix made it less complex? i'm excited to
87.
by preseinger 3y ago
if we say a language "addresses" a given concern, is it necessary that this is accomplished in the compiler, and that the rules for that concern, whatever they are, are enforced at compile-time? (spoiler: no)
88.
by preseinger 3y ago
yeah it is literally a non-issue in practice, and yet
89.
by preseinger 3y ago
> The goto pattern in particular is found all over the stdlib. in generated code, sure -- that's why it exists, to support codegen it's sometimes abused to manage for loop control flow but the stdlib is definitely not some plat
90.
by preseinger 3y ago
it is my very clear experience that rust programs are more brittle than go programs, precisely because rust makes it possible (even encourages) error "bubbling" via `?` in practice, go code bases that are subject to even minimal c

More ›