HN user

knoebber

209 karma

My email is my HN username at gmail dot com.

Posts1
Comments89
View on HN

Grinnell 17' here. At first I didn't enjoy intro with Racket. But by the end I changed my mind and it ended up being one of my favorite courses. In retrospect that class easily had the most impact on me during my CS major... I still have quite a few functional programming habits. These days I like to code in elixir for side projects, which has quite a few similarities.

Anyways, cool to see another alum here! I hope the department keeps it around for a while longer :)

Fair criticisms, but at the end of the day, Kagi offers a better search experience then all the alternatives for a fair price, so I pay for it. I don't really need to have 'faith' in it, though I do hope it sticks around.

Also, can't wait to get my tshirt! (closed beta user here)

I think the main use case today is the dom traversal API. It makes operations like "add the 'error' class to all <input> elements in the form" simple:

    $('#some-form').find('input').addClass('error')
Obviously you can do this in vanilla JS, but it's more cumbersome so you'll probably end up rewriting your own less complete version of jquery. There is some value to using a well worn library with public documentation that other developers can find/extend instead of a home grown solution.

With that said, I wouldn't use it for a green field project. For sites that require lots of interactivity I would pick a modern front end framework that doesn't require this kind of manual dom traversal (probably phoenix/liveview).

two reasons:

1. you prefer functional style languages, such as elixir 2. you want to avoid `pip install` ing dependencies

I'm a happy paying user... I almost never have to !g. I tried DDG before kagi, and it just seemed like a worse version of google to me. I definitely prefer the kagi results.

A postgres database that is managed by a custom app that I wrote in Elixir / Phoenix / LiveView. Hosted for free on fly.io.

it stores:

- My TODO list (items -> entries -> checkboxes)

- My credit card transactions (scraped from alert emails with gmail api)

- A running log with miles/times/routes

i've implemented misc features to organize everything like content tagging, custom markdown rendering, etc.

I spent about 2 years at my last job building a greenfield react app mostly by myself (around 10k sloc). I enjoyed it for the most part. But I did run into all the issues raised here, they are valid. I think the worst issue with React is the dependency arrays that get sprinkled around everywhere - in my opinion the framework is unusable without a 3rd party linting tool that points out when your dependency array is missing something. If you accidentally add the wrong value in there, hello infinite render loop!

One of the biggest level ups I had was extracting complex hooks into their own .js files instead of stuffing next to component code. This helps a lot with readability/reusability.

Overall I liked what I came up with, but it felt like a lot of inventing stuff on my own, which I'm not sure if the next developer who comes along will appreciate.

2000-Watt Society 4 years ago

I'm living/working remotely off grid with a solar panels, batteries, and a 2000w inverter. It's comfortable. I usually have a few lights, the wifi router, a monitor, laptop charger, and a fridge plugged in. This comes out between 100w and 300w, so I have room to spare for bigger items like power tools.

I do cheat by using a propane range for cooking and wood for heat. At some point I'd like to move to an electric induction stove, but I need to do some research how efficient they are.