skysight-inc/HackerNews huggingface dataset:
The fundamental magic of react is that it lets you write code that renders O(n) UI states in a functional manner (i.e. by returning the HTML you want) rather than O(n^2) UI state transitions in a mutable manner (by mutating the page via nested callbacks), and somehow makes it kind of fast-ish

People love complaining about React, but I don't know if they remember the pre-React world where you had to write the code to manage O(n^2) UI state transitions via recursive mutating callbacks. Simple things like "have a the list of photos shown always kept in sync with a label showning count of photos" was incredibly error prone, and the complexity of implementation went up quadratically with the complexity of your app (due to the n^2 state transitions you needed to worry about!)

Today React is not the only one to do this O(^2) to O(n) complexity reduction, but it was the first to go mainstream, and very much deserves its success in spite of its various shortcomings
Source Code of $3k-a-Month macOS Malware 'Banshee Stealer' Leaked
When I was leaving a job, I decided to start documenting things. I had a solid documentation before I gave my two weeks notice. Then I used the remaining time to refine it, it was a pretty good documentation.

A month after I left, they contacted me and offered contract work, which i declined. For the following year, employees reached out to me directly for help. It didn't matter that everything I helped with was already documented.

My take is there isn't a solution for proper knowledge transfer in companies. That's why I find it fascinating when people get fired on a whim. You lose so much more than an employee.
They are different: in the U.S. that's why "freedom of the press" is also written down in the First Amendment, and historically, that's exactly how the U.S. courts have interpreted the phrase "freedom of the press" - as a (pretty) general right for anyone to use any media technology they can access to spread any ideas they want. There are always some limits, but from the start "the press" meant "the printing press", not "institutionalized news organizations". It's a general technology-usage right, not a specialized right for a certain group. Everyone is allowed to do more than just talk, or even shout. People can have different opinions on how wise that right is, but in the US at least, you are indeed free to broadcast your nonsense to millions of people, if you have the resources.
btrfs isn't that terrible for desktop use right now. I mean, I wouldn't personally use it, I lost data on it a couple times four plus years ago, but it's come a long way since then. (my preference is keep everything I care about on a fileserver like truenas running zfs with proper snapshotting, replication and backup and live dangerously on the desktop testing out bcachefs, but I recognize not everyone can live my life and some people just want a laptop with a reasonable filesystem resistant to bit rot.
Taxing Farm Animals' Farts and Burps? Denmark Gives It a Try
Contradictions in photography advice
The third law of photodynamics: For every piece of loudly-spoken advice, there is a piece of equal and opposite counter-advice.
Kanzi (syn.: Nicoter) is the only apple I eat. All other I can get around here are just meh. Ufortunately, Kani/Nicoter are rather uncommon.
AI robot convinced 12 showroom robots to 'quit their jobs' and follow
That's not "the average electric car," it's just a Leaf. It doesn't necessarily imply anything about a modern Tesla, Lucid, or BYD.
honestly I think btrfs isn't bloated enough for today's VM-enabled world. ext4 and xfs and hell, exfat haven't gone anywhere, and if those fulfill your needs, just use those. but if you need more advanced features that btrfs or zfs bring, those added features are quite welcome. imo, btrfs could use the benefits of being a cluster filesystem on top of everything it already does because having a VM be able to access a disk that is currently mounted by the host or another VM would useful. imagine if the disk exported to the VM could be mounted by another VM, either locally or remote simultaneously. arguably ceph fills this need, but having a btrfs-native solution for that would be useful.
React Server Components strikes me as React solving a React-caused problem with yet more React. Which is fine, I guess, if you’re already locked into the React ecosystem. But as someone that isn’t, looking at the whole proposition from the outside, it just screams vendor lock-in to me. There are too many devs out there only expert in the way React does things and can’t step outside of it. RSC is an additional crutch that allows this to continue but that doesn’t mean it’s healthy.

My main contention with the OP’s point was the assertion that React is almost always the right answer. One of my biggest bugbears about any web dev discussion (particularly on HN) is that everyone treats it as a one size fits all argument and it isn’t.

If you’re making a webapp with interactivity levels like Gmail has then React is a sensible choice. The page reloads very irregularly. But if you’re making something like a blog with lots of drive by visits and only small islands of reactive content IMO it’s the wrong choice.
Rock it apples have been the most consistently good for me.
> Building a web application with a UI in a professional context without a frontend build is borderline malpractice.

Why do you think that? What problem is a build tool solving for you that without it you think you're being irresponsible for not doing it by hand?
The number one feature I use Google Assistant for (and probably most people's most common usage) is to say "Hey google, set a timer for X minutes". If I dare do anything else with my phone during it's reply of "OK, five minutes, starting now" I risk the timer just... disappearing. If I can't count on it for one of the most commonly used tasks for phones I have zero faith for other things and don't even bother to figure out how to use it as more than an internet access terminal/music player.
Right, even the most opinionated of modern formatters don't go quite that far.

The only thing I can think of that did is the Interlisp-D editing functionality provided by Interlisp Medley, where your code was stored within the system as parsed S-expr trees and when you opened an editor onto something it reverse engineered a textual expression of the thing according to your configuration.

Tagging every, single, node, with enough data to recreate the indentation and formatting seems theoretically doable, and if you're wanting to let people edit things that are, say, config file shaped, then you're going to have to do that if you want the resulting commit diffs to be sufficiently coherent that people will be willing to use it.

But taking the Medley approach for a first attempt/first release feels a lot more doable, and given the biggest obstacle to such a thing is almost certainly congruent to "being able to make a start over a weekend for the sheer fun of it" I think it's well worth considering :D
That's one way to frame it. Another is Sol-ark incurs costs of developing, marketing and supporting their official devices and the contract manufacturer is able to sell their own version in the Chinese market. Greedy people who don't want to pay Sol-ark for all the costs they incurred bought grey market devices that Sol-ark has repeatedly warned are in contract violation in this market. The manufacturer, not Sol-ark, has now bricked those devices, and people are blaming Sol-ark anyway because they want to continue to justify their actions.
Second this. Stopped playing a while ago, would love to have a couple of chars of mine as a memory.
JSX vs hyperscript is a religious issue. You can use JSX with Mithril if you prefer (after all the m() thing is what JSX compiles to).
Yes, that whole page you cited is simply tutorialism.

And Mithril supports jsx. (Not to mention the advantages gained by avoiding JSX in favor of hyperscript)

Might be best to actually use it in a small (or large) application of your own design rather than judging prematurely.

(I’m not suggesting large orgs use Mithril, as other commenter mentioned, community in some situations is more important than the tooling. But “building a web app” does not necessarily imply “employing a team of local developers to build a web app asap for less than x usd”.)
For it to be effective, all it needs is its complement: An easily recognizable green label saying "Doesn't connect to the internet", which is only allowed on the boxes of devices for which this is the case.

Maybe some more levels in the middle like "only connects to the internet for firmware updates" (yellow) and "doesn't require internet access for core functionality" (orange). Basically Nutri-Score [1] for hardware.

[1]: https://en.wikipedia.org/wiki/Nutri-Score
Elon Musk files for injunction to halt OpenAI's transition to a for-profit
You need to talk to expert with magnitudes more details, not about technical internals of product, but about your market.

Sometimes happen wonders, and product sell just because it is technically good, but these things are rare and you should not use business strategy based just on technical goodness, need also good marketing and sales.

I even say more - very typical cases, when bad unfinished product, but good marketing and overall good organization rescue business.
Thanks for the reminder to make the concepts section of my site easier to read. :)
I feel compelled to add my own geometric art for the shake of completion since it seems like a hobby from a few of us HNers:

https://omarrr.com/isolation-pixel-series

(Not selling either)
I will this year try to be the "support team" for those that will try to do AoC in https://ryelang.org. At least one person said on X.com that he will use it, so we will see :)
Etienne Jacob's mesmerizing geometric animations
> Then there are engineers [...] who never try for the entirety of their careers

This matches my experience 100%. I am not a brilliant developer by any measure. I'm competent enough, I can put together good solutions to the admittedly low-scale problems I'm assigned, and I like to think I have a pretty good sense for the right and wrong ways of going about doing so. But I'm not even sure I could land an interview with a FAANG company, let alone a job.

My feeling at work is one of constant vigilance. I feel like if I look away for too long the gremlins will start creeping in. And I'm not talking about some imperfect design or the odd code smell, I'm talking about dropping in on a PR two senior engineers have already approved and spotting a critical security flaw in the first 30 seconds. Or a data loading pattern that works okay with the five records they've tested against but would make 300 database queries per page for a realistic dataset. Or spend 75% of their CPU time hydrating date objects from timestamps that are then immediately discarded.

I think it comes down to a lack of inherent curiosity and/or interest and/or passion in programming. To me good programming is a craft—I won't go so far as to say it's as much art as it is science, but I think there is definitely an artistic element to it. Which for me introduces a need to do something well, rather than just ticking boxes and going home. "Painting the back of the cabinet", as it were. If business requirements force me to ship some monkey-patch fix, it gives me a discomfort I can't really put into words. I immediately want to replace it with something better, because I just don't like putting work I know to be substandard out in the world. I'm not even particularly invested in the product and services my employer creates, but if it's my work I want it to be good.

Something I often hear is "I couldn't work out how to make <solution we all know to be good> work so I just did <sloppy solution that will need workarounds five seconds after clients start using it>". It irks to me to no end because without fail, what "I couldn't work it out" always means is "the first thing I tried threw up a minor roadblock so I stopped trying". And it sucks because the worse a codebase gets, the more difficult it is to contribute something you can be proud of.

Have I just had the misfortune of working at particularly crappy companies, or are things really this bad across the whole industry? I'd really like to think it's the former, but I read articles like this and dread that it's the latter.
You might enjoy the If Books Could Kill podcast. They mostly cover self-help and pop-business or pop-science books. They talk a lot about the recurring patterns and sometimes surprising shared topics among the books.
Reacting to assertions of broad averages with specific counter examples doesn't necessarily invalidate their point.
Does the spidertron cost increase on the space expansion or anything?

I've always built as many as I wanted from the fish I get by accident while building other stuff.
It seems everything is an SCPI-derivative these days, and that is a protocol family not a protocol, one which could only be ill-defined and heavily vendor-extended/interpreted to the point of assumed uninteroperability at best. That said, it works. I wouldn't buy new test equipment now without LXI or some similarly scriptable interface. Manual configuration just creates too much scope for error during testing. Coming from software, electronics is hard enough without the fuzz-factor of human fur-ball and fat-finger physics frappery. Automation is worth its weight in gold, even if you don't value your own time highly. And the lifetime for equipment that can be automated is much higher as it can become part of fixed production or test setups and thus handily serve in-place as precision automation for common unit operations. Even just the documentation value of "these were the settings, this was the (precise or relative) time" is infinitely higher than manual fudge-work. That's why this good gear is going cheap - nobody commercial wants it, because it's behind the 8 ball from an era where flying solo with fuzzy manual process was fine. Skilled as any IC's engineering may be, if they get hit by a bus the company would prefer to have dropped $10K extra on test equipment this side of Y2K.

I guess that's why it's nice to see this project - because you're essentially helping to rescue gear that would be discarded for hassle-factor or manual-only interface and providing some portion of modern functions.
I’m afraid there’s no silver bullet.

Marginalia can be useful, even if the index is quite small compared to other search engines: https://search.marginalia.nu/
Yeah, you can't talk about the deterioration of Google without talking about the deterioration of the culture at Google.

I didn't like working at AWS for the most part, but I have never seen Google-level dysfunction there. There were a lot of times I disagreed with decision, but I could always understand the reasoning behind it. On the contrary, I can't explain most of the decision being made at Google. The enshittification from the very top has been amazing to watch, even for someone like me who joined only 3.5 years ago. Both senior and mid-level leadership lack a clear vision and the execution has obviously been horrible. Google needs a hard reset if they want to be successful again. I'm not buying the "too-big-to-fail" bullshit.
Reminds me my Nebula experience.

I watched a 120min video about LHC or something and missed a few words from a narrator. Pressed left to rewind, only to find out that it doesn't work. Their seek bar didn't help either by not showing some crucial information (don't remember which now).

As a result, I clicked nearby and got somewhere 5 minutes back with no chance to return or navigate precisely. "Hit the right pixel or get screwed" type of UI. Closed the video and canceled my trial.

They always screw up in little places like that. That itself is okay, everyone makes mistakes. What's not okay is that they don't even try to use their own service seriously. For a paid service, could at least license the player from pornhub (the guys who know their job and the importance of a video player on a video platform).
Much of it is such minimal translation.

Much, not so much.

I see JSX as basically 'compiling augmented javascript to javascript,' much of decorators is much like that as well, and things like e.g. vue's turning expressions on its reactivity based signals seen in templates into something more clever is also in the category I was trying to gesture at.

(TS is awesome but I should've predeclared that it wasn't really what I had in mind, sorry for any confusion induced by that mistake on my part)
I think it would only matter for something that is quite significant. And in that case, you would probably quit long before it mattered.
Ironically the first question you ask is the question people should be asking about React. Specifically, what problem does it solve, and do I have that problem? The problem most teams tend to face, and I believe part of the authors argument is that people reach for React out of an almost superstitious or orthodoxy-based belief.

Likely many developers don’t even know how to build something without React. They don’t know the first thing about html, server-side rendering, progressive enhancement or any of the things we used to use to build forms over data applications before React came along and its siren song drew away many developers, and, worse, created an entire generation that fits the criteria I’m describing.

The author doesn’t need to describe an alternative any more than he did, because the alternative is supposed to be self-evident. If it’s not, the person is supposed to take the plethora of breadcrumbs in the article and figure out how we used to do things before bloated, convoluted, and typically unnecessary frameworks.

When you look at something like Remix and Next you see people trying go back to the simple (forms, server rendering) by adding additional complexity. It’s doubling down on complexity, rather than finding simplicity.
OK, let me restate something from my previous component explicitly: a site that’s concerned with SEO is not a “specialized domain”. It is very, very common.
I had no idea I'd see so many people rising in defense of bots and scammers.
Then the "optional software package" was/is the false advertising. And it is irrelevant how many people bought it.
Trump Threatens BRICS Countries–Including Russia, India–With 100% Tariffs
How would a law prevent this? Does it cause a lion to manifest, whenever someone is about to shut down power, to maul the guy to prevent the shutdown? I do not believe laws have such supernatural powers.
Honestly, being a freelance consultant is also the only way to have a high wage… that fact alone explains a lot.
sigh taking your words as truth regardless of whether they are or not, we then fall back into the "most" category of my statement, meaning you continue to utterly fail at reading comprehension.
I mean, afaik the standout feature of Picasa was shared web albums where you could invite people to add photos and permissions were managed via Google accounts, so, it's easy to confuse the two. From memory the only thing that changed when moving from Picasa to Photos was that I no longer had a desktop app where to keep photos on disk + Picasa had a neat map of geolocations (maybe Photos caught up or can you still not view photos on a map? I know apple does this, I just use ACDSee now and keep it offline)

Sunsetting blog from 2016 for good measure: http://googlephotos.blogspot.com/2016/02/moving-on-from-pica...
> But there's a lot of errors that aren't really recoverable inside a library

Aren't all propagated `Result`s examples of errors that the library itself doesn't recover from and lets the caller decide what to do? IMO, panics in libraries are for cases that are either "impossible" (`panic` as `assert`) or the library author made a judgement call that the application is also helpless in this situation (`panic` as `exit`, like OOM in most of `std`).

> you may not want to cause the code using that library to crash - perhaps your buggy component can be worked around.

That's a question of isolation! Rust libraries operate within the same process and address space as the application code. A buggy library could arbitrarily modify the application data or the process state and violate arbitrary application invariants. I'm not even talking about UB here. Just application-level invariants and assumptions.

Given this, the Rust's choice to either "abort the thread and poison held mutexes" or "abort the process" sounds very reasonable.

In other discussions, I was pointed to Erlang's "let it fail" error handling with multiple isolated processes. [The Error Model](https://joeduffyblog.com/2016/02/07/the-error-model/), which I reference in my post, also touches on this topic.
are you talking about the internal or about the websites built with them? i have used neither, but what i gather from many discussions and articles is that vuejs makes for less complex websites.
China's EV Boom Threatens to Push Gasoline Demand Off a Cliff
You Might Be Better Off Without Pull Requests
Undersea Surgeons
Offline ensemble co-reactivation links memories across days
I tend to start off a project with typeless zero-build JS, because I've been working with dynamic languages so long that the types mostly don't actually help me find bugs in the early days, but if I don't convert it to reasonably typed TS before I release a 0.001.001 then I would expect people to judge me for it, and I would consider them to have every right to do so.
> I eat apples for the texture above all else, with flavor being important but nothing close to how much crunch eat bite has.

You may enjoy the Fuyu Persimmon also. Eaten with firm skin is definitely crunchy. The flavor is moderately sweet.
Stop doing code reviews and try these alternatives
The strangeness of the first one is the basis of the field. Literally all of chiropractic practice stems, objectively, from the one guy and his ghost revelations circa 1896 or so.
Cargo cults don't work at all. Ritual-taboo systems sort of work but are suboptimal.
http://archive.today/JRAWb
AL2023 vs. AL2: less disk space with ext4
let say someone is very senior in their field, are they expected to use their free time

If you are actually senior, you aren't really gonna be thinking that way because mentoring will be part of your professional practice.

But also, a lot of organizations don't have that view of professionalism, so a lot of careers never see much mentoring going on.

Finally, a lot of young people don't behave in ways that invite mentoring. They are unlikely to receive it then and unlikely to "pass it on" later. Good luck.
Wow I thought I was the only one who thought this? My timeline matches pretty close to the authors. I worked at a startup around 2013 that had fruit deliveries, and I ate a honeycrisp apple there for the first time in my life and I fell in love. Like the author, I started eating those apples out of desire, not because it was the only thing left.

But in the last 2 years, I didn't notice it, but I have been pretty dissatisfied with them but I never really thought about it until this article. It sheds light as to exactly why I don't like it anymore, and that's pretty sad that the industry is getting into that state.