Viewing profile — jeremiep

Read "The Structure of Scientific Revolutions" recently, science ignoring what it does not understand is far from a new phenomenon. Science is fantastic to dig into areas it can al…

Been using react transparently through clojurescript's reagent for years and was never hit by any of react's API changes. The problem usually isn't react, but that most projects us…

That's not a step further, you lose the ability to use the latest version without code changes.

I find D to be a good tradeoff between C++ and Rust. I can't stand not having compile-time evaluation, code generation and reflection in Rust and C++ is just too slow to iterate wi…

> because they make our work easier This seems to be my biggest pet peeve with the JS ecosystem as a whole; people chase things that are easy to learn rather than simple to reason …

I'm perfectly happy in ClojureScript to be skipping TypeScript and most of the JS ecosystem :) Not everything on the web has to use the normal stacks. I used TypeScript in the past…

I see your point, thanks for the precision. I can agree perpetuated inequality does give kids a huge head start. Taxation is already high for the rich, but the top bracket is usual…

Its not like the poor is going down, they're also going up but not nearly as fast. Almost all of our poor people are rich by global standards is an argument I hear often. Most poor…

You can also take "modern design patterns" out of that sentence and still be accurate. Its usually just a form of cargo-cult-programming that hasn't been found out to be terrible y…

They seem to be benchmarking very specific things and not actual applications. These numbers do not hold in the real world.

Talks from Mike Acton and Scott Meyers, specifically "Data-Driven Development" and "CPU Caches and why you should care" respectively. I forgot exactly where I got that number, but …

When you realize the compiler's optimizations only account for about 10% of the total program's performance you find that the other 90% is entirely up to the programmer. Architectu…

> Wow, who writes that crap? Have you read your own comment?

But that is precisely how undo is currently implemented most of the time. Its a series of actions where you know how to undo the side-effects, or you know it was a destructive upda…

> but probably not practical in reality. Thats how I've been building UIs for the last few years. `re-frame` in ClojureScript for one is a fantastic framework built on top of these…

A render list would be more efficient than a tree, simply because you're not jumping left and right in RAM with cache misses on every jump. A hashmap of nodes on screen is still ve…

This assumes the web rendering context is the proper abstraction to build application UIs. Its not. Its too complex and object-oriented to be efficient. It was intended for documen…

Anything where your app state is modelled as a series of actions over immutable data, undo and replay will be essentially free to implement :)

I feel React's best use case is as a view backend in micro-frameworks like re-frame in ClojureScript. React only gets complicated when you use states and mutable props, or when log…

I found about proton-native earlier this week! Sadly it doesn't have a ` ` element thats required for the project I'm building :(

Same, no way we're using a fork while the main project is still actively maintained and putting out great features. The added value of built-in SSL doesn't even justify losing half…

Not everything has to be "look at what I did in the trendy language of the week".

What guarantees? Nothing prevents a function receiving a nursery from not using it. Unless the language can enforce it you don't really gain anything valuable over returning a Prom…

I agree, but I still wouldn't call a nursery an abstraction; its an indirection, and a mutable one at that. I also disagree with the goto analogy; concurrency and control flow are …

At this point you're pretty much reinventing Monads.