mariusandra

10 ms·

31.
by mariusandra 3y ago
Hey, thanks for the feedback! The editor/controller itself is just a React+Kea app using React Flow for the diagramming part, and Flask for the backend. For now to test that the app you built works, you must deploy it on a frame. I hav
32.
by mariusandra 3y ago
I'd love it to work on the RP2040, and perhaps even an ESP32, but we're not there yet. Just yesterday I converted FrameOS from being an interpreted python app to a 3MB compiled binary, so we're half of the way there. I'm
33.
by mariusandra 3y ago
There's nothing built in now, but a common technique would be to make the image e.g. ~10px larger in each direction, and then choose a random crop every other second. It should be really easy to build a FrameOS app that does this. Add
34.
by mariusandra 3y ago
I'd love for FrameOS to support ESP32. Two days ago FrameOS was a slow and interpreted Python app. Today it's a 3MB statically linked binary. The margins are tight, and I'll likely need to cut out some features (e.g. threadin
35.
Show HN: FrameOS – operating system for single function smart frames(frameos.net)
474 points by mariusandra 3y ago|112 comments
36.
FrameOS Nim Rewrite(frameos.net)
6 points by mariusandra 3y ago|0 comments
37.
FrameOS – Control Raspberry Pi-powered picture frames(github.com)
1 points by mariusandra 3y ago|0 comments
38.
HogQL: Direct SQL Access for PostHog(posthog.com)
4 points by mariusandra 3y ago|0 comments
39.
Some people create work. Some people solve work(medium.com)
2 points by mariusandra 4y ago|0 comments
40.
Some people create work. Some people solve work(medium.com)
3 points by mariusandra 4y ago|0 comments
41.
by mariusandra 4y ago
You're asking very good questions. > I think you can map the example class I wrote to similar concepts - but instead of three+ different function calls to build a logic, you could do one, like `magical(classInstance)` - which would
42.
by mariusandra 4y ago
lol. First, it's 2 rewrites. Second, those were all 98% backwards compatible for the users (might need to upgrade plugins), and just refactored the internals. But sure, let's all write perfect code on day 0, taking into account al
43.
by mariusandra 4y ago
Depends what you mean with "readable". It's always easy to make a contrived example, and call that readable because it's shorter. I'm talking about huge apps maintained by multiple remote teams, all working independ
44.
Kea 3 introduction and getting started(youtube.com)
1 points by mariusandra 4y ago|0 comments
45.
by mariusandra 4y ago
Well, in PostHog (I'm a colleague of Twixes), we just decided here [1] to go with Kea, as I had more experience with it. Had Redux Toolkit been around when I started with Redux in 2016, I probably wouldn't have needed to write Kea
46.
by mariusandra 4y ago
OP here, so call me biased, but I tend to disagree. Curious to hear your thought on alternative or better approaches to system design here. In my experience you need some amount of boilerplate, or what I'd call _architecture_, to have
47.
Kea 3.0 – State Management via Logic Builders(keajs.org)
39 points by mariusandra 4y ago|18 comments
48.
Kea v3.0 Pre-Release(keajs.org)
4 points by mariusandra 4y ago|0 comments
49.
Automating a Software Company with GitHub Actions(posthog.com)
247 points by mariusandra 5y ago|69 comments
50.
by mariusandra 5y ago
In the approach described in the blog post, you only need two use*: `useValues` and `useAction` to pull in values and actions from the data layer. Nothing else. No local state with `useState`, no `useEffect` or `useRef` or anything else for
51.
by mariusandra 5y ago
Something that comes for free with Redux and its abstractions like Kea (the approach promoted in the linked blog post) is that you mostly avoid the problem of needless re-renders. Each `useSelector` call (and `useValues` call that uses it)
52.
by mariusandra 5y ago
Agreed that if your frontend is mostly GraphQL, and your data flow well taken care of, you shouldn't see a need for a separate state management solution. However sometimes you have to work with various APIs and filter/display&#x2F
53.
It's time for a data-first front end revolution(kea.js.org)
2 points by mariusandra 5y ago|0 comments
54.
It's time for a data-first front end revolution(kea.js.org)
1 points by mariusandra 5y ago|0 comments
55.
Keep your state in Kea and your views in React(kea.js.org)
1 points by mariusandra 5y ago|0 comments
56.
Pigeon Maps – ReactJS maps without external dependencies(pigeon-maps.js.org)
2 points by mariusandra 6y ago|0 comments
57.
Kea – Production Ready React State Management(kea.js.org)
1 points by mariusandra 6y ago|0 comments
58.
TypeScript Support in Kea (The Long Road)(kea.js.org)
2 points by mariusandra 6y ago|0 comments
59.
Kea-typegen – autogenerate TypeScript types for Kea (React state management)(youtube.com)
1 points by mariusandra 6y ago|0 comments
60.
by mariusandra 6y ago
Hey! Thanks for the comment and that's really cool! Your product looks really slick as well! Would you mind posting in this "who's using kea" issue about versoly as well? https://github.com/keajs/kea

More ›