louissm_it

I think we're at the point where the people who are going to throw trash are going to throw trash, and I don't believe something like the ocean cleanup will increase how much trash people throw into nature.

You can make the same argument that you shouldn't clean your own house because that will just encourage others to make it dirty again. And thats obviously not how it works. Some people throw trash and some don't.

We should clean it up anyways.

I don't understand why people (Greenpeace) are so against The Ocean Cleanup - complaining that we need to fix the problem at the root instead of cleaning up the mess afterwards. Why can't we do both?

Kicking and screaming, I finally succumbed to TypeScript on the server. I used to do everything with Phoenix or Rails, but nowadays its hard to fight the full-stack type safety (even if its mostly an illusion) of something like Remix/Hono with React + Drizzle/Kysely.

I hate having to wire everything together, and how I might have to rewrite it next month, and how there is no standardised way to do anything, and how I have to install a library for everything and figure out how to make them work together.

But the types won me over.

Storing the data directly inside the application still means you need to store it somewhere, likely a SQL database (such as PostgreSQL). These databases are insanely well engineered and very very fast, but compared to a key value store such as Redis and Memchached they are comparatively slow and resource hungry (because they are optimized for different things).

So if you can fetch some cached data from a Redis key, even if on the same machine, it will cost you significantly less than querying a relational database.

As someone who upgraded from an Intel Mac to an M1 mac, the memory is a non-issue. Three years ago I would have laughed if you said I would be happy with "only" 8GB, but now I am.

Alright, that is a very good point. If the possibility of other nodes interacting with your service is high (ie “you’re gonna need an API eventually”), this might well be the best option.

Congrats! I've been keeping up with Redwood since the original announcement, and the progress they've made has been incredible. The generators and command line utilities are top notch (compared to Rails, thats a high bar to clear) and the general structure of everything seems very well thought out. Still missing a good official solution for background jobs, but I see there is a workaround in the 'How To' section on the documentation. The core team members are super nice and the community is very welcoming.

I'm not convinced the "client side app + Graphql server" is the best model for most startups, however. I tend to lean more on server rendered pages with a little bit of progressive enhancement. But I assume the people who made Redwood are more knowledgeable than me :)

Fantastic. I did not expect to enjoy using the custom widgets or "Kinos" this much.

You nailed it. I work with Ruby, TypeScript (React, Node) and Elixir.

While Elixir has more than enough uses and I love it dearly, nothing comes close to the productivity and expressiveness of Ruby (+ Rails).

I have very high hopes for JS/TS. Using a single isomorphic language for web development must have some benefits, but I'm afraid it's not there yet.

I’m genuinely curious, how would that solve the problem? The real world event - say, delivery a purchased good - would still have to be flagged by both parties as “delivered” before the smart contract can execute. If you only allow the receiver to flag, then the problem inverts! Now the receiver can just deny the item was delivered.

Middlemen are useful, as annoying as they may be. I’d love to be proven wrong here.

Fair enough :) Growing up there you never consider it like that.

Cool. I've only been to London once, but I distinctly remember being disturbed by how dead everything was. I'm not sure how accurate the stat, but I recall Table Mountain having more floral species than the entire UK.