I feel any LLM discussion without mentioning concrete tooling choices are unproductive. Toolings are evolving so fast, many statements that were accurate two months ago are simply wrong today.
I wonder if it's the best outcome? The contributor doesn't seem to have a bad intention, could his energy be redirected more constructively? E.g. encouraging him to split up the PR, make a design proposal etc.
With pocket sunsetting, I have been searching for alternatives lately. After a few rounds of search, I can't convince myself to use specialized bookmarks tool over Notion / Obsidian. I wonder what other people feel?
I feel lots of the work described in the article can be automated by kops, probably in a much better way, especially when it comes to day 2 operations.
I wonder what is the motivation behind manually spinning up a cluster instead of going with more established tooling?
The fact that it requires slowly changing over years is a sign of getting stuck no?
We can theoretically slowly migrate anything. But when effort > X, we consider it being stuck.
I get why people hate new things in car as they often don't improve driving experience.
But smart tv? I think they genuinely improved my experience. I can pretty much watch any show anytime using my phone as the controller now, I don't see how it's possible with old TV?
Long time firefox user, absolutely love it. My only grudge is that on Android some tab will just randomly go black and blank. This problem has been there for at least 1 year, I think it has something to do with os memory collection but I can't prove anything.
And I still use chrome, because of the Chromecast.
Don't know if https://inertiajs.com can be classified as unpopular. but I think it's one of the best web solution combining the best of the both worlds ssr and spa.
I don't know about your org but in many companies changing from tech lead (a role) to IC (another role) isn't considered as demotion. I personally love being IC.
But I understand you might not want to be IC again, so I think you know what to do ;)
I sold my onewheel pint a few years back only after 200 miles because of a few uncontrollable crashes and nobody believed me that this is a dangerous product.
I warned the next buyer but he still bought it, just like me before crashes.
But I did convince him to join the Onewheel Crash Club Facebook group. For everyone who is interested to know how dangerous this is, check that page out.
Neither Litestream and LiteFS meet my SQL needs: Litestream is a single writer system, LiteFS has data consistency risk. I can't justify replacing Postgresql for them.
I do understand those tools expanded the use cases of sqlite a lot and they are pretty cool in how they pulled it off. But I'm surprised Fly's investing here; feels like it tarnishes their infra provider rep.
If they do want to continue this investment, maybe investing in things like rqlite will be more appropriate for an infra shop.
Hmm, when I search racket compilation, the top option is to compile to bytecode. Since the term "bytecode" is used, I thought that was different from Chez's machine code generation?
Distrust is building for Fly. Their articles ooze arrogance, whether it's hyping up their "unique" hiring methods or their "managed" Postgres service. They even gloss over serious flaws like data loss in LiteFS. Their latest article is another red flag for me. Started off intriguing, but now, I wouldn't trust them as far as I can throw them.
In all those SSR tools, my favorite is inertial.js, I think it combines the best of the both worlds. I am not sure why inertial wasn't getting more popularity though, anyone know why?