wtetzner

31 ms·

511.
by wtetzner 4y ago
Standard ML, Scheme, Common Lisp, Java.
512.
by wtetzner 4y ago
He understood how to write Java, and attempted to do functional programming in Java, knowing full well that it wasn’t idiomatic.
513.
by wtetzner 4y ago
Sure, but it’s a lot of extra friction when iterating/debugging.
514.
by wtetzner 4y ago
> Believe who? I think they’re referring to Radio Free Asia.
515.
by wtetzner 4y ago
> Just takes one bad actor for LetsEncrypt to swallow your site whole. What do you mean by this?
516.
by wtetzner 4y ago
Just curious what you think the consequences could be? Worst case scenario people would need to find a new CA the next time they need a certificate, right?
517.
by wtetzner 4y ago
How could it be less efficient to soften less water?
518.
by wtetzner 4y ago
I think they meant that emacs is an example of programmable software.
519.
by wtetzner 4y ago
> That’s 5 runtimes each running it’s own garbage collection logic. If the WASM runtime provides a GC, then all of those languages can share a GC.
520.
by wtetzner 4y ago
But the competition is compile-to-javascript, which has exactly the same problem. With WASM, you get to choose between using a generic, potentially sub-optimal GC, or having a larger payload and including a GC bundled with the application.
521.
by wtetzner 4y ago
When I did Java, I found the Java ecosystem to be very productive because of the libraries available, but Spring was basically useless and was just a way to convert compile-time errors into confusing runtime errors. Most of the useful stuff
522.
by wtetzner 4y ago
Unfortunately I doubt Beyond/Impossible don’t involve killing animals.
523.
by wtetzner 4y ago
What do you mean by “strange performance outcomes”?
524.
by wtetzner 4y ago
> These animals consume the same products the vegan alternatives are made with... How many people are living off of grass?
525.
by wtetzner 4y ago
And one of the problems in California is how much water almonds use.
526.
by wtetzner 4y ago
We could also just eat grassfed beef instead of feeding animals soy.
527.
by wtetzner 4y ago
And if the reason bars aren’t implemented yet is because nobody requested it, then there is no tracking ticket.
528.
by wtetzner 4y ago
And that ticket will be forever ignored. On the other hand, if there’s a TODO in the code, someone might fix it the next time they’re editing that part of the code.
529.
by wtetzner 4y ago
Or it could be useful context for the next person to modify the code. Maybe it’s something that is only worth doing under certain conditions? // TODO: This is fine for now, but if we start handling `bar`s, we’ll need an extr
530.
by wtetzner 4y ago
I do both: put a TODO in the code with a ticket number. // TODO (<ticket-number>): Foo should be frobnicated
531.
by wtetzner 4y ago
> It wouldn't weirdly copy the entire object over and over again, it would directly manipulate the object, one piece at a time. I think this is the only part I disagree with. Immutable data types make it much easier to understand co
532.
by wtetzner 4y ago
> If you are using containers, always, always, always use immutable containers from Google Guava unless you have an exceptionally good reason. I actually prefer pcollections: https://github.com/hrldcpr/pcollections
533.
by wtetzner 4y ago
The problem is that if you have e.g. let x: u64|i32 = ... It's impossible for the compiler to do anything with x without adding some kind of runtime type tag. The representations of those types are different. But with somethin
534.
by wtetzner 4y ago
I like OCaml's approach, where you write types in module signatures, but don't need to put them in the implementation.
535.
by wtetzner 4y ago
An architecture astronauts in Java just use code generation and runtime reflection, which are bigger nightmares than type system features. Architecture astronauts are going to be a problem regardless of language features.
536.
by wtetzner 4y ago
Being able to have a generic "Mappable" trait seems like a good use case for the standard library. It's something I've wanted in the past, and was disappointed that it didn't exist.
537.
by wtetzner 4y ago
Really? You don't see the problem with trying to maintain code that's been copy-pasted everywhere with slight differences? Doesn't it seem easier to maintain one implementation of something than N implementations?
538.
by wtetzner 4y ago
It might still be cheaper than copying the values if they’re large.
539.
by wtetzner 4y ago
They’re also useful when you want to cheaply reorder nodes without copying the elements.
540.
by wtetzner 4y ago
> That only works if you allocate lists all at once and never modify them. You can reorder and modify the contents of the list without losing locality.

More ›