nsonha

27 ms·

481.
by nsonha 2y ago
Is it just me who doesn't need jQuery or anything like that anymore? What kind of crazy direct dom query/manipulation do you need? The manipulation should be on the backing state, and then the dom should just derive from that, suc
482.
by nsonha 2y ago
simply replying to (on ARM) "linux works pretty well these days"
483.
by nsonha 2y ago
Other than nostalgia, what makes this email client so special?
484.
by nsonha 2y ago
Really? I got a bunch of error upgrading my Arch-based Asahi and now chromium doesn't work anymore. Oh and no external display, or speaker.
485.
by nsonha 2y ago
That's not a thing that AI can reliably do yet. If any code AI, including Cursor, can do that, it would be pretty ground breaking. There are some projects iterating on that front though. For example, one VSCode extension called Clide c
486.
by nsonha 2y ago
> cursor and its tab completion If this is how you use Cursor then you dont need Cursor. Autocomplete has existed even before AI, but Cursor's selling point is in multi-files editing and a sensible workflow that let users iterate th
487.
by nsonha 2y ago
I think the title misses the "Honey, " part
488.
by nsonha 2y ago
Everheard of copy/paste? Not unlike the way you copy/paste these css classes from the last project to the next. Guess what? Taiwind has components too, but the built-in of course is never the exact thing people want, so they had t
489.
by nsonha 2y ago
Too many functional css frameworks like this around, nothing novel, all kinda the same, including that super popular one everyone is using these days... Just write css and save your brain space for actually useful abstractions.
490.
by nsonha 2y ago
Is it a new Linux distro (cool) or just another android fork that... can't run android apps (lame)?
491.
by nsonha 2y ago
Sorry I just can't
492.
by nsonha 2y ago
no one is talking about transaction. I'm talking about state machine which is what most program boils down to. The problem with OOP is, AGAIN that all states are lumped together in a single type (class) and so are all the state transit
493.
by nsonha 2y ago
Like Haskell or F#? Already exist.
494.
by nsonha 2y ago
So imagine what already happens and makes no impact to how I write code? How exciting!
495.
by nsonha 2y ago
Didn't they say it? If you turn on the react directive then it outputs the react prop. Btw, you seem to have missed the new jsx transformer, className has been a thing of the past even in React.
496.
by nsonha 2y ago
Don't understand the boner for infix notation, you find an usecase for it like... once every year?
497.
by nsonha 2y ago
The JS community needs a Martin Odersky who will one day drops a JS 3 with indent-significant syntax upon them. F# had the same transition too.
498.
by nsonha 2y ago
> avoid coupling logic and state as much as possible period depending on how you define "state". In OOP, the coupling is between a bunch of transitions (as a single class) to a bunch of states (as a single type). It's actu
499.
by nsonha 2y ago
> Tight coupling is the basis of oop. A method is tied to an instance. Methods cannot be composed with other methods or functions without instantiating state. Methods cannot be moved into other scope. > The literal definition of an ob
500.
by nsonha 2y ago
no one ever brought up "inheritance as reuse" in this thread, don't straw man. It's called OOP, NONE of those letters stands for "inheritance"
501.
by nsonha 2y ago
obviously when they refer to loose coupling, they're refer to that between interface and hidden states/implementation of object. It's very easy to deliberately miss the point and complain about the "tight coupling"
502.
by nsonha 2y ago
My React fomula is React + MobX, keep the hook use to minimum, single state object per component (the classic React way), do not bother with server components at this point, you should be fine.
503.
by nsonha 2y ago
There was a sweet spot in the past when React was actually simple and clean. I really do want to escape it these days but quite frankly every frontend framework is the same and they are just shitty in different ways, not really better than
504.
by nsonha 2y ago
It's funny because very early on the key selling point of Svelte was that you just mutate objects and it compiles to the observable pattern, unlike React's clunky setState syntax. Now, somehow magic symbols in the code is supposed
505.
by nsonha 2y ago
This article isn't about compile-time regex (which is in many languages, including javascript) though? It's compile-time regex MATCHING.
506.
by nsonha 2y ago
Why does self-hosting mean not using docker. Some people don't like overhead, but that's not the point. The point is to control your own stack and docker can make it more managable. If you dont like docker I guess just copy the sc
507.
by nsonha 2y ago
That puts it at the same level as every other framework, who is not owned by a hosting company and doesn't even have an official solution to scale and deploy "properly"
508.
by nsonha 2y ago
Which argument? Pretty obvious the bezel is that way for usability (so you can hold the device). That other devices exist with thin bezel does not prove anything.
509.
by nsonha 2y ago
It's more like the other way around. Veteran web devs are stockholm-syndromed into thinking the web should always work how it used to work, they tend to think about the web as some sort of sacred internet document. Most devs these days
510.
by nsonha 2y ago
how does this compare to Autogen and LangGraph? As someone new to this space, I tried to look into the other 2 but got pretty overwhelmed. Context is making multi agents, multi steps reasoning workflows

More ›