wruza
wruza on Hacker News
They still nail "state" to element trees, which creates unbenchmarkable but real update costs. Svelte does better than react, but only within the same paradigm.
Something is wrong with web developers culture, cause even in framework-free vanilla mode they cannot get rid of data localization and welding the data and "component" trees together irrepairably.
Rather than building a querySelector-able tree of elements to and monkey-patching mutiplexing nodes for syncing element counts, you invent the most bizarre ways to chain yourselves to the wall. For long time I couldn't understand what exactly drives this almost traumatic habit, and it's still a mystery.
For the interested, this is the outline I count as non-bizarre:
- make an html that draws your "form" with no values, but has ids/classes at the correct places
- singular updates are trivial with querySelector; write a few generic setters for strings, numbers, dates, visibility, disability, e.g. setDate(sel, date)
- sync array counts through cloning a child-template, which is d-hidden and locatable inside a querySelector-able container; make syncArray(array, parentSel, childSel) function
- fill new and update existing children through "<parent> :nth-child(n) <name>"
- update when your data changes
Data can change arbitrarily, doesn't require passing back and forth in any form. All you have to do is to update parts of your element tree based on your projections about affected areas.
And no, your forms are not so complex that you cannot track your changes or at least create functions that do the mass-ish work and update ui, so you don't have to. For all the forms you've done, the amount of work needed to ensure that updates are performed is amortized-comparable with all the learning cliffs you had to climb to turn updates into "automatic". Which itself is a lie basically, cause you still have to jump through hoops and know the pitfalls. The only difference is that rather than calling you inattentive, they now can call you stupid, cause you can't tell which useCrap section your code should go to.
At this point, graphics card MSRPs are just coolers for presentations. Like, look, we have such amazing cards for only $2k! Sounds much better than "you can't afford it anyway, otherwise expect $4-6k depending on bids in the long queue".
Aren't beliefs secondary guests in discussions about substance?
Edit: I'm not even a strict atheist if that matters much, but I wouldn't talk about it in assertive/provemewrong tone anywhere, cause it's not even remotely logical.
Agreed. What does this tell us in the context of this discussion?
Returning to the initial point, should people just build more houses?
More grass -> more rabbits -> less grass -> less rabbits -> (loop). You can mix different rabbits in, but the cycle is fundamental.
Because making even more people to nowhere to live is a popular no-brainer.
it's akin to an atheist proudly proclaiming there is definitely no such thing as godAlmost feels like you supposed that to sound bad.
Can it guess Senegal by sky color though?
I read half the article and little is told in it in general. You'd expect some deeper developer reflections on a 60kloc project. Like, much deeper. The part about "spacer" hints that the second half won't surprise either. There's just not enough general xp to make conclusions.
You can't upload much of what's rarely downloaded. The usual way to help the network is to download something popular that you don't need and to seed it. This removes some strain from big seeders and helps them seed other things you don't have.
But personally I believe you're not obliged to anything in torrents, especially with adsl. We got you covered with our multi-hundred u/d ratios. Everyone participating honestly and comfortably is enough, even if that means no upload. Just don't turn it off out of unnecessary principle after downloading.
Dang's analysis was funny:
don't site comment we here post that users against you're
Quite a stance, man :)
And me clearly inarticulate and less confident than some:
it may but that because or not and even these
I noticed that randomly remembered usernames tend to produce either lots of utility words like the above, or very few of them. Interestingly, it doesn't really correlate with my overall impression about them.
The dilemma as old as stacker and {double,drive}space. This is just a leaking abstraction. Leave it be cause there's no good solution for it. The best place for zfs-aware backup code is in a backup tool that cares.
Then it's of little use imo. Library decimals already exist in multiple optimized forms.
Bind substitutes `this`, not global scope. With function envs you can write functions like function () {a += 1} and have it increment `a` in some object.
Why do you focus on "performance" here?
What I don't like is lack of features that would erase whole classes of software around it. For example, function environments (substitute the global scope with another object for a single invocation) could delete lots of code and paradigm from vue/rx-likes.
It also neither supports operator overloads (good thing in general) nor has a decimal type which is a must for human numbers like euros and kilograms. Rather it includes the mostly useless bigint.
It also does nothing to fix the mentioned quirks like sort(). It could e.g. include cmp(a, b), and propcmp(name[,cmp]) off the shelf so the issue wasn't wordy at least: nums.sort(cmp), objs.sort(propcmp("id")).
Most movies don't even leave our stellar vicinity, because they want to use hyped star/constellation names and these are from the very local set of stars. Not only a naked eye sees only around a few thousands stars, but most of them are basically next door. The mean distance to the star that you can see is <1% of galaxy size. Almost everything you see is in a 10px circle on the 1080p fullscreen galaxy map.
Yeah why don't we learn what he wants and just give it to him, in return he'll properly rewrite all the broken shit we have. Phones, operating systems, desktop environments, countries, appstores, etc.
If one doesn't want to regenerate passwords, don't log people out. The only reason this "workflow" works is that email sessions work for years, sometimes decades, without nagging users to re-login.
Sites, do yourself a favor and store active sessions indefinitely and the only password-dealing scenario you'll ever see will be (1) at sign up, once per user, (2) when users clear cookies, which the login-problematic types rarely do for obvious reasons.
95% of my family password support is the sites that log them out on their own.
Edit: grammar/pronouns
Interestingly, when this happens on the other side of the world, these people are expected to rise and overthrow. Otoh, when it's a local soul at stake… maybe someone else can save it. As a US citizen, aren't you the hope? Not you specifically, but you get the idea. You were the hope in many countries for decades and advocated for peace and democracy everywhere. And the only ones who still have freedom, guns and visibly functioning courts all in the same place.
Poor guy but honestly he's stuck in 2000s, not even in pre-AI 2020s. Comparing yourself to the channels or "low effort" studios is pointless because they win through marketing, not content. There's a thousand, if not a million, losers in this game per one winner who makes a buck and doesn't pay you extra. You're not an exclusive. And no one wants to buy effort really, people are fine with mspaint memes cause everything done properly was just a gatekeeped waste of resources. Good production is akin to a diamond or a traditional japanese craft. People value it because they were told it's a must and a noble attribute. New people see through this and refuse to participate in this culture. There is good production, but it only gets employed in hundreds of millions of views sorts of situations.
It always bothered me that people go "ew, wikipedia" when you simply refer them to it rather than literally rewording the article (which they would accept, or at least reply with "source? source? s-s-source? so-source?" to which you could successfully post any source from the wiki article). Reference is not a proof, it's information that you have to check yourself if you want the latter. I guess same will happen with LLMs. Any link to a chat will be met by some with "ew, llm" regardless of the fact whether it's checked and informative and saves effort to formulate, or is just-generated crap. With all the issues with llms, it's us who don't understand the basics when it comes to handling the info. This is by semi-natural social design, I believe.
Pen and paper. I put a mm-high paper stack into a transparent file and take one sheet out and put it on top. This way it's comfy to write on (soft surface) and it leaves a nice afterimage on a file after a while, which is visible at an angle in daylight. Very cozy and professional, plus doesn't collect dust. I also put a sheet back under if it has any value, so I can address it later. But usually I strike out points, rewrite what's left on a new sheet and bin the old one. I tend to use thin-ish gel pens cause you can add details in fine strokes if needed. For space management I'm using an arm mount for the display, so that the keyboard can go all the way under it, leaving space for the paper. I also tend to work at long tables, at least outstretched arms long, so it has enough space for everything including "amenities", because otherwise the logistic issues start piling up and harm the setting.
Because it works, probably. Blogs (and blog making tutorials) get selected by reach, not content, and images add to that, like arrows and stupid face close ups do on youtube. What you see is a cost-driven transformation of the concept.
Why should it be hard to grok? Selection just happens, it doesn't "care" if it's natural or based on human preferences. Even human-free selection doesn't guarantee a long run since genes can paint themselves into a corner (see natural extinctions). Iow, it's what it is.
Variations of guns (high pressure tubes with plugs) also shoot nails, pilings, and can quickly split hard surfaces like rocks or pavement. They are also natural parents of internal combustion engines.
Not arguing, just saying.
Good thing you can bind arbitrarily complex action to a key/combination in a programmable editor and avoid this semantic fuss whatsoever.