Taking a look at the Kafka docs [2] is also enlightening.
[1] https://www.amazon.com/Designing-Data-Intensive-Applications...
1,262 karma · joined May 23, 2015
From one orange to another
Taking a look at the Kafka docs [2] is also enlightening.
[1] https://www.amazon.com/Designing-Data-Intensive-Applications...
I'd say I spend probably 2-10x more time writing than I do "coding" - where writing is Hammock Driven Development[1] for others to consume
- lambda vending s3 pre signed urls with put only permissions
- a static page with 20 lines of js that requests one of those urls and does the put
I’m not aware of any existing solutions, but your problem seems simple enough that you could roll a solution yourself
I'm an advocate for this style of library/dependency development, unfortunately in my experience the average dependency doesn't have the discipline to pull it off.
Pipelines, BT and Isengard are absolutely what I'll miss the most as well (I handed in my resignation notice last week, prior to all this RTO2.0 kerfuffle)
Once you've got a repl up and running the JVM launch time isn't an issue and repl driven development lends itself well to data munging/exploration
Clojure's data centricity (functional, everything's a sequence, strong data manipulation std lib) really makes it a dream for these quick and dirty data transformation/exploration jobs
If you want to get fancy, https://github.com/nextjournal/clerk (notebook interface) and https://github.com/techascent/tech.ml.dataset (data frame library) will get you there
LiveView does serverside rendering and “streams” dom diffs afaik
Whereas electric is doing full client side rendering and sending data/code diffs “only”
Writing client side code seems lower friction in electric at the cost of the macro/client magic being a little more magic
https://www.abc.net.au/news/2024-08-13/trust-exchange-digita...
Admitting that doesn’t read like hubris to me
This is true for a surprising number of amzn/aws products
I'm absolutely not saying this to discredit the work that's gone into Clojure, Elixir et al, but it does lend credence to the idea of building for an existing ecosystem instead of bootstrapping your own (along with "seamless" interop as a first class concern)
If anyone can crack seamless interop between natively compiled languages to dodge ABI hell they'll earn a nice place in history
Incentives and adoption goals for internal tools are weird at large corps. Intentional suckage is just another tool to drive migration
I bumped my contactless limit from $100 -> $500 years ago through my bank's app. Leaves friends confused every time I cover a group dinner out
So much talk about change and large LoC deltas without capturing the expected behavior of the system first
I don't agree with TFA's take of "Nor does it make any sense to have caching at the function level?"
iPad pdf reader & annotator designed for sheet music. As a “tech” husband helping out a non technical musician wife it’s a game changer