bcardarella.bsky.social
CEO of DockYard
Sailor
Creator of LiveView Native
twitch.tv/bcardarella
854 posts
1,196 followers
59 following
Regular Contributor
Active Commenter
comment in response to
post
I will be implementing the GenDOM query engine with this library today
comment in response to
post
Awesome! You should definitely apply, info is on the @elixir-lang.org website I believe.
comment in response to
post
What is the tldr of Lynx.js?
comment in response to
post
Does that make the other days "drink from home" day?
comment in response to
post
these are all extractions from things we spiked in @liveviewnative.dev we aren't certain if we'll use them in any project but figured people may find value in them
comment in response to
post
it is using the web-socket-dist wasm lib which handles all of the node management
comment in response to
post
And even the developers working on this stuff will end up on the short end. The only people who ultimately will win in this world are a very select few.
I simply don't see how a capitalist society functons when a significant % of the population has zero employment prospects.
comment in response to
post
Personally, anyone working on AI to replace actual jobs should feel immense remorse about what they're doing. Instead engineers do what they always do: it's a fun problem to solve.
There is no government regulation that will save us. And we certainly won't save ourselves.
comment in response to
post
Now they're told: too bad, you're replaced. The same people championing an entire life-long career path for everybody is gleeful about replacing them with zero wage workers. This furthers the divide between the haves and have-nots. It's going to end ugly.
comment in response to
post
I think it's more complex than that. For over a decade an entire generation was sold on the idea of becoming a developer. Presidents, leaders, everyone was telling them to learn to code. Blue collar workers who's jobs were being eliminated were told they can code.
comment in response to
post
I will never understand why people accept living under HOAs. Every time I hear about them they all sound horrible.
comment in response to
post
The current implementation is writte in SwiftWASM. Without any code stripping it weighs in at 55mb so not practical for production use right now but it demonstrates this is possible
comment in response to
post
We're writing some js wrappers and will be sharing it soon
comment in response to
post
apparently I invented a time machine, June 6
comment in response to
post
I will very likely refactor this over the weekend, I think my first implementation isn't the right one. I was mostly looking to just get nudged towards the process group one
comment in response to
post
I have and that would be part of a custom porc group implementation
comment in response to
post
I wonder what happens if they analyzed dolphin or whale song
comment in response to
post
No, it's not. It's to avoid being sued by providing as much deep detail as possible. And it's to ensure the next doctor that takes over the care has as much detail as possible. The problem is the repetition of paperwork required.
comment in response to
post
My wife is a physician. As much good as Obamacare did, one of the worst aspects of it is the paperwork burden it put on physicians. She works a 12 hour shift then comes home and spend another 4 hours doing notes. It's abusive.
comment in response to
post
its limits are data mutation and while loops
comment in response to
post
This is what's necessary to finally get @liveviewnative.dev
working with nested LiveViews and LiveComponents
comment in response to
post
We can do fast lookup by node ID. And I have an idea for doing parallel execution across the tree for query selection rather than doing a single tree walk.
comment in response to
post
This becomes interesting because we can then have SwiftUI views send messages and receive messages directly from the corresponding DOM node over our recent efforts to run Elixir on device and have Swift act as an Erlang node.
comment in response to
post
GenDOM is going to impement most of the W3C spec for DOM. Each node will be a GenServer. This will also allow us to implement the DOM Event system.
comment in response to
post
Day 2 Zach, pick up the slack!
comment in response to
post
Whoops, fixed!
comment in response to
post
Oh we are way *way* over subsidized. The real cost to do this stuff hasn't even been hinted at yet. What I'm concerned about is dev quality will drop as LLMs largely overtake that space. Then they'll have a talent monopoly and exploit it.
comment in response to
post
and for the record, Tidewave is great. I'm just pointing out the risk of going all-in on one thing.
comment in response to
post
Yes, +1 on local LLMs. I'm still waiting on the next gen as I think the past 3 months we've seen the hosted LLMs pull away from local
comment in response to
post
That's my point with some of the current efforts, we're downstream of providers and relying on them puts a lot of eggs in very few baskets. It's risky, could pay off, but still risky.
comment in response to
post
I agree on that, just that it can feel at times like we're chasing than leading
comment in response to
post
I'm back and forth on this stuff day to day. I am concerned that Elixir may be going too hard on AI stuff, if this bubble pops we're left with a lot of dead weight.
comment in response to
post
I guess this lib still doesn't satisfy @hauleth.dev 's CLI comment, as I presume Termite doesn't really allow you to back and distribute CLI apps but just provide TUI to an Elixir app, like mix tasks and such?
comment in response to
post
Wasn't there a terminal lib introduced at ElixirConf EU?
comment in response to
post
Mostly solved, not yet ready to share