268
points
synthc
Joined 864 karma
reach me at hackernews@chrisblom.net
- synthcThey made their home a concentration camp, no need for railroad cars this time...
- I'm thinking of using it to replace an analytics pipeline at my job, which now uses expensive batch jobs. If the tech is solid, we would have instant and incremental updates, instead of recomputing everything every X hours. This would simplify things a lot.
I think Materialize offers a similar product, but last I checked it was only available as a SaaS solution.
I hope to do a proof of concept soon, to compare both solutions
- Does anyone have experience with RisingWave in production? It seems like an interesting product but I can't find any experience reports.
- User name almost checks out
- Classic Dutch: “We need this talent… but financially, it is impossible to support them,”
- you get runtime errors with a long JVM stacktrace
- Immutability removes so much accidental complexity, it makes whole classes of mistakes dissapear. I'd also take immutability over types.
Clojure sort of guides you to simplicity, building everything out of functions and simple datastructures has big advantages when testing and reasoning about code.
I do find that in larger code bases, Clojure lack of types causes friction (spec is just a bandaid, not a fix).
There are languages with immutability and types (like Haskell), but these don't have the get-shit-done factor I seek.
- For me it just speeds up learning the language, so I think i'd become fluent faster.
I do thoroughly review of the the LLM answers, and hardly every directly copy paste answer, so I feel this way I still learn the language.
- about as much as I trust StackOverflow answers
- Seems like a bunch of go programmers really wanted to use go, no matter how impractical.
- Interesting! I did an internship where I tried to use transducers for fast information extraction. In theory, you can use FST's for fast approximate parsing. I didn't really work out, but I had lots of fun implementing a libary to compose FST's and explore cool algorithms to compose them. Not much business value was delivered, but I learned a lot.
- This year I switched to a new job, using programming languages that I was less familiar with.
Asking a LLM to translate between languages works really well most of the time. It's also a great way to learn which libraries are the standard solution for a language. It really accelerated my learning process.
Sure, there is the occasional too literal translation or hallucination, but I found this useful enough.
- Interesting deep dive on the internals of Caffeine, a widely used JVM caching library.
- This just proves to me Meta can't build a product users actually want to use, they can only acquire other products, or lobby.
- 'Serverless' has it's uses, but not for everything
- Serverless can get very expensive - DevEx is less than stellar, can't run a debugger - Vendor lock-in - You might be forced to update when they stop supporting older runtime versions
- My first job (around 2010) was to extract events from financial news and police reports.
We built this huge system with tons of regexes, custom parsers, word lists, ontologies etc. It was a huge effort to get somewhat acceptable accuracy.
It is humbling to see that these days a 100 line Python script can do the same thing but better: AI has basically taken over my first job.
- The difference is in how easy it is to detect the cause of problems. Mistakes like wrong function names are mostly easy to find and fix. Mistakes when using core.async can be very hard to track down.
- I wouldn't recommend it but I'd figure the hackernews crowd likes deep dives on wierd diets.
- 6 points