jeremiep

10 ms·

1.
by jeremiep 4y ago
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 already see, and terrible at seeing new areas from t
2.
by jeremiep 6y ago
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 using it directly use it wrong.
3.
by jeremiep 8y ago
That's not a step further, you lose the ability to use the latest version without code changes.
4.
by jeremiep 8y ago
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 with.
5.
by jeremiep 8y ago
> 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 about once learned and the result is almost always a conv
6.
by jeremiep 8y ago
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 but didn't enjoy the complexity of most JS libs,
7.
by jeremiep 8y ago
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 usually quite low. I don't think the solution is more taxes,
8.
by jeremiep 8y ago
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 also end up middle class as they grow up, take respons
9.
by jeremiep 8y ago
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 yet.
10.
by jeremiep 8y ago
They seem to be benchmarking very specific things and not actual applications. These numbers do not hold in the real world.
11.
by jeremiep 8y ago
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 it's been a pretty good metric so f
12.
by jeremiep 8y ago
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. Architecture, data structures, batching operations, memory l
13.
by jeremiep 8y ago
> Wow, who writes that crap? Have you read your own comment?
14.
by jeremiep 8y ago
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 update and you just skip the undo of that step. Where I have iss
15.
by jeremiep 8y ago
> 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 concepts. > I don't see the point of having
16.
by jeremiep 8y ago
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 very high level; you're basically replacing the DOM
17.
by jeremiep 8y ago
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 documents and is a general pain to work with for applications. For
18.
by jeremiep 8y ago
Anything where your app state is modelled as a series of actions over immutable data, undo and replay will be essentially free to implement :)
19.
by jeremiep 8y ago
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 logic is put inside components. As a view backend it just
20.
by jeremiep 8y ago
I found about proton-native earlier this week! Sadly it doesn't have a `<video>` element thats required for the project I'm building :(
21.
by jeremiep 8y ago
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 the value of using the main project.
22.
by jeremiep 8y ago
Not everything has to be "look at what I did in the trendy language of the week".
23.
by jeremiep 8y ago
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 Promise, except more complex code that doesn't compose
24.
by jeremiep 8y ago
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 two distinct things, they have much more differences th
25.
by jeremiep 8y ago
At this point you're pretty much reinventing Monads.
26.
by jeremiep 8y ago
Agreed, I'd rather have a few simple constructs, especially if they compose. Still, there's value in unification and generality, at least when the result is simple, even if that covers only 80% of cases. For example you generally
27.
by jeremiep 8y ago
Or just use Clojure and get live coding for free. Its far more powerful than hot reloading.
28.
by jeremiep 8y ago
I get compile-time warnings or runtime errors when I create unhandled promises. What more is needed?
29.
by jeremiep 8y ago
> This can change if OSes start optimizing for the proposed convention. What conventions? Its not realistic to assume the world will change to fit your views of software :p > At least in C/C++ it doesn't. Sure does; it adds
30.
by jeremiep 8y ago
Whats the difference between taking a nursery and returning a promise? Both put the context in the signature, but the later is actually composable.

More ›