skysight-inc/HackerNews huggingface dataset:
> React is better at anything else at making [a web application]

Mithril.js beats it in my opinion.

I’m sure many developers would argue in favor of other libraries over React.

React is simply the most popular.
"if let" is rusts answer to Java's "isPresent" method.

if let Some(val) = my_optional_value {
// perform some side effect with val
}
I lived for some time in eastern Canada and I have very fond memories of freshly picked McIntoshes and I even dare to say they were my favorites. Fresh and crisp with a good amount of acidity that balances the sweetness beautifully. That being said, they don't age super well.
Be on the lookout for Esopus Spitzenburg (maybe only in the US). It's a really tasty apple.
Perhaps Literature Map?

https://www.literature-map.com/

There are sites where book lists are collected:

https://www.goodreads.com/review/list/21394355-william-adams...

https://www.goodreads.com/review/list/21394355-william-adams...
I like how when you ask people why they approved something obviously broken, they’ll say something like “Oh, I didn’t really look at it.”

I mean, I do that too once in a while, but if bugs go through you own that.
> a web site [...] a web application

But is that not the crux of the article? So much of the web is the former but is built and distributed as if it's the latter, with all the end-user downsides that entails.
> Some things need preserving.

The bank accounts of the wealthy?
Apple Pay T&C Updated (US Entity Split into "Apple Payment Services LLC")
Received an e-mail stating T&C updated recently:

> We’ve made a few updates to the Apple Pay & Wallet Terms & Conditions. Here’s a summary of the key changes:

>

> We have simplified our Terms and Conditions for Apple Pay and Wallet so that your review and agreement of these Terms and Conditions is effective across all of your Apple devices.

> For our US customers, Apple Pay is a service provided by Apple Payments Services LLC, a subsidiary of Apple Inc.

> Our Terms and Conditions now include standard assignment provisions.

Anybody here understand the reasoning behind this? Is the recent litigation against banks and Apple Pay a possible reason (ie, reducing impact to LLC)? Or is this a direct cause of the CFPB ruling to bring oversight to digital payments [1]?

[1] https://www.consumerfinance.gov/about-us/newsroom/cfpb-final...
Oh, thanks for the clarification! No idea why I thought that...
If you understand unix pipes then node based programming can make sense, for example in the guise of node red.

Think of nodes representing computation and lines the flow of data between distinct computational units and you have unix pipelines. This is what node red does.

This editor is more complex since it’s connects output to individual inputs.
I've done a few press releases for my products over the last 20 years. Unless you are already very famous or are doing something very innovative, it is almost certainly a complete waste of time and money.
Normally you promote those people to ‘senior’ and then say that a review by at least one senior is required?
Will people keep writing these annoying posts with no insight just to complain about Exceptions (and Java in general)?

I've done a lot of Java. And quite a bit of Rust too. The least thing (or close to it) that annoys me with Java is Java's error handling. It only really makes me upset when a lambda needs to call some method that has a checked Exception in its signature, usually because it does IO... yeah that's annoying... but I still get the job done without losing more than 30 seconds. Otherwise, I just make a decision on whether to handle errors locally or propagate them, and that's all there's to it.

Rust is nice and all. But the kind of annoyance I get with Result values are probably worse than is the case in Java with Exceptions. For example, as mentioned in the article, when you end up having multiple incompatible errors and you have to manually hack something, usually losing context, to make the compiler happy. Almost every project just adds yet another dependency on one of the error handling libraries (because this problem and similar ones, like losing the stack trace entirely, are all too common so there's lots of libraries to fix that) and you probably will end up with all of them in your project once you've written anything non-trivial.

The problem with API changes in Java are real, but the same exact issue exists in Rust: you inevitably have to end up adding new error scenarios as you add features to a library. Instead of a new Exception, you just end up with a new Error variant in Result.

Anyway, even though in the beginning I also got all euphoric with Rust, thinking it fixed every issue with every language, today I think it just shifted the sorts of problems you have to deal with. It definitely went in the right direction (specially with handling of closable resources and concurrency) and it's a better language in almost every way than Java and most languages. But sorry, with regards to error handling, it's a minor improvement at best.
There have been previous reports of similar behavior. Including a fascinating error potentially caused by AI brain damage due to ingesting the Reddit thread devoted to counting to infinity.
https://www.vice.com/en/article/ai-chatgpt-tokens-words-brea...
YES!!!!!

there's plenty of REAL privacy matters to address than to invent demons and then undermine genuine issues with 'boy who cried wolf'!!!
What people want when you sit them down and have them try apples side by side is different from what they want when they are in a supermarket, tired from working all day, and starring out at a sea of apples and not quite remembering which one it was they liked.
Founder of Not Quite Past Adam here — that's such a lovely idea. We've done some work recently on automatically generating themed sets, but describing the relationships automagically would definitely be a nice addition!
> Just FYI, we also have simple helm charts, and the repository is hosted on https://vinceanalytics.com/charts

Oh cool, didn't see that in the docs.

> Does it always pull the latest vince image?

Yes haven't specified any tag so should default to latest.
Merge before you’ve written 3000 lines of code?
Retail US$ prices for Lego-branded kits are usually about $0.10 per piece. So I would expect this kit would cost about $85 if Lego were selling it, implying a +170% premium.
> the U.S. used force to either displace, subjugate, or kill all of those people.

Except for all the land we paid for.
I think they're talking about joining a holding pattern as inbound traffic to an aerodrome
UK changes to inheritance tax for farmers could help in the long run
DeepMasking
Also check out https://umami.is
> Can you guess why I used an intermediate variable instead of calling f(g(x)) and f(gException) in try-catch?

I can't guess why. Could someone explain why the intermediate variable is important?
Second this. For any reasonably popular language you can ask for the variation of dev env boilerplate you specifically need, and also ask questions about it and why it’s setup that way. Specifically what certain configurations do and why. Getting this info through an LLM is so much better than doing it by google search or reading docs.
Granny Smith is ubiquitous. It's often difficult to get a more sour apple than a Granny Smith. Pink Lady is less sour IIRC. McIntosh or Braeburn are definitely less sour.

If you're in the Midwest (especially MN, WI, Iowa, etc) you can get Haralson, which are kinda like Granny Smith but more just straight sour.

Haralson is probably my favorite. But disclaimer, I also like eating straight lemons, so ... yea. Many people will use Haralson only for baking.

I hear that in Europe they have a few types that are more sour, idk.
Maybe I should give it a second look, then.
Node red is different since it defines message passing between computational units. It describes the flow of data between computational units.
My family has been going to the same orchard in SW Michigan for maybe 8 years in a row.

At first, they only had 2 rows of Honeycrisp apples. Maybe 2% of the trees there...

Now more rows are 'Honeycrisp' than not. As far as I know, they didn't replace all those previously 'not Honeycrisp' trees, though.

And they taste like paint. Ugh.
Okay. Doesn't change the fact that it is widely used in Europe and it's secure.
Thanks for the reply!

> one-to-one transformation function to the original training set, and so not increasing the inherent entropy of the _distribution being learned_.

I disagree. Entropy of the model? The language? The sentence? The tokens? The distinction is subtle but important. A one-to-one mapping is not structure preserving. For a trivial example: {a,b,c} -> {c,a,b} doesn't preserve alphabetical ordering. The distribution the LM is learning is that of the intractable(?) distribution of the language itself. Certainty the entropy here changes, and I believe your results demonstrate this. I think the entropy would only be the same if we preserved all structure[0], but my understanding of the impossible languages is that they remove (all) structure. I'm not sure if that'd yield worthwhile results, but I think it could be a good sanity check -- or at least assumption check -- to do deterministic permutations based on syntactic structure. E.g. replace all S,V,O -> O,V,S for all sentences.

> because the tokenizers we use are based on the frequency distribution of "words" identified by whitespaces, but we'll have to check.

Maybe I was mislead by Table 1. Noting that "bookshelf" -> {books,he,lf}. That isn't whitespace delimited. The examples only show "bookshelf" being preserved in the Shuffle (s=21) and the HOP cases (well... split by the hop token). Partial reverse showing {books, [R], ., lf, he}. I think this is a good example of token bias as our token "he" can hold multiple meanings, but I suspect that the statistics changes when we consider the word structure and how that these tokens will appear conditionally. I think this is a good example where I think Figure 2 doesn't do a great job at proving the conclusion. The differences are small, so are they completely offset by the bias? HOP seems even more convincing as the results converge and this bias should be much more easily accounted for. What is unclear to me here is why there's a significant difference in the beginning of training. I am a bit surprised that training from scratch would have this initialization bias.

(Also, just to note, I wouldn't reject this paper were it to come across my desk, but I bias towards accepting works. I am picking on you because you won best paper and a lot of the narrative that formed around the paper)

[0] I think we have "natural experiments" here w.r.t learning other languages and translation. Though not al structure is preserved. Some are lost and some are gained. But this again can be affected by the tokenizer and if you are doing things like stripping accent. Clearly that removes structure, but isn't going to have a big effect on English.
My constant problem with React-based tools is that they don't support deep links properly. You want to right-click on a product description to open it in a different tab to check later, and you can't.

Even freaking Google (who really should know better) suffers from that. Amazon's retail frontend uses plain HTML, so it works fine.
I agree that Cosmic Crisp are better. But I still prefer MacIntosh, Empire or Cortland, though.
Smoothing a Python and OpenCV AR App with a Kalman Filter
Very tasteful title animation I must say. It’s fast enough, you feel it, and not distracting, gives a vibe even from glancing
Or Biome for both. And in 1 second instead of 10 minutes.

Sure, eslint has a few extra rules, but in my opinion it just doesn’t beat getting results at sub second speeds.
I thought he was saying "provide your feedback on a thumb drive" as a humorous way of indicating that you shouldn't even email it lest it leak before the vote.
Albumentations: Fastest and most flexible image augmentation library
In the context of this blog post, an example with Result would be more suitable though.

if let Ok(value) = fun_can_fail() {
// success, use value
} else {
// error, but we don't care which one when using if-let
}
From the view of the team the ideal manager is a shield overhead protecting them from the crap coming down from above, the manager should refuse and push back.

From the view of “is this good for the company?” the manager should push back on bogus bad faith tasks and the structures which make them exist.

I understand that from the manager’s own perspective their income might be priority one - but then I wonder if they are just a conduit for senior management crap to flow through, harming their team morale, what are they actually doing that’s worthwhile?

If it is bogus, hopefully it still won’t be out of the blue - warning to the team that it’s coming to someone - and they could try and arrange it as an encouragement to leave, with payout, with recommendation, before it’s a total surprise. The manager must know whom they would and would not fake-PIP, and from Yossi Kreinin’s assertions that employees know their managers’ minds better than they say, the employees likely know who is in favour and who isn’t.

https://www.yosefk.com/blog/people-can-read-their-managers-m...
Maybe that's because it's a one man show?

https://en.wikipedia.org/wiki/Syrian_Observatory_for_Human_R...
Google search results now are nearly unusable, most look like this:

- Top of the page is slow loading AI regurgitation of deeply buried real web results, but often wildly inaccurate. No thanks.

- Next are a bunch of YouTube videos you don't want to watch where you have to wade through dozens of ads and hours of content to get the 3 seconds of information you're looking for. No thanks.

- "Related search" nonsense that nobody ever wants to see but if you click on those you will get more of the above. No thanks.

- Some useless unrelated shopping links you almost certainly don't want. No thanks.

- Way down at the bottom, 2-3 real web search results, non-keyword matched, and only from major mainstream outlets that are part of the Trusted News Initiative (Orwell?!) that have turned into glorified content farms which spit out non-expert written content on every conceivable subject for Googlebot (and now most of this content is AI written or from the cheapest possible third world contractors). No thanks.

Those "real web search results" used to be independent publishers that are referenced in this article, which were often topical experts with deep knowledge on their respective subjects, and those people and businesses have been destroyed over the last few years by Google updates that clearly prioritize their own slop and their "trusted" corporate ally content farms over the independent web.

They also disappears tons of content, and anything critical or outside of the mainstream acceptable narrative is nowhere to be found, sort of like searching for "tank man" from inside China, something everyone in the west used to poke fun of and point to as an example of digital totalitarianism.

If I were running Google search I would immediately roll back all of their search changes to somewhere around 2014-2016, which was roughly the last time you could find true keyword matched web results from a hugely diverse array of expert sources, and then very cautiously reassess. Obviously they would never do that, so I am not sure they can recover from their own demise.

BTW I don't find DuckDuckGo or Bing to be much better, they seem to just mimic Google results. Search is in real trouble.
This is just semantics I think. Certainly some people may express a desire to learn but not be able to motivate themselves to read a book. However people who actually want to learn are intrinsically motivated to read and don't fall into that group.
Fuel tanks are in the back for solid reasons. But they are placed before the second wheel axis. In case of crash that area will protect the tank. Pinto had it after the rear tires, so totally unprotected.

A big battery in the place of the motor will turn you into a BBQ in case of collision because fire will fall directly towards the driver. Lithium batteries start burning when hit with some force, and can't be stopped once they start burning.
> Why are you taking hits for him? Does he somehow pay your bills?

I responded to your pointless, inaccurate and rude conjecture with an equally pointless, rude, and what I assumed was an equally inaccurate conjecture to suggest that perhaps we keep our conversation substantive.

If the sense in that still isn’t clear, you might check out the guidelines on this site for keeping discussion constructive.

> What "success"? The stuff that other people have made happen that he takes credit for?

I don’t know how “success” could be any more evident.

But if you believe you see shortcuts that were taken, then perhaps take your insight and do something comparable? Good luck!
If the three sit next to one another I agree that PR’s are overkill. If they’re remote it becomes harder I think.
Check out their cloud API dash board it’s like the nuclear power station control room. 50 toggles, I would have went default to simple mode and an advanced mode. But no, they put every dial and switch in front
Click the triangle icon next to that question to see the answer. :-)
Received wisdom in the indie developer community is that B2B is an easier way to make money than B2C.

Generally, buyers don't know if you are 1 guy in his bedroom or 100 guys in California. In my experience, they also don't care that much as long as they like the product and price (might be different for mission critical software). I am a 1-man band and I have sold software to lots of big and famous companies and organizations.
They're still doing B2B sales after, so unless they're only making those deals under stringent contract, maybe some company will pick up the market and retail them.

Curious if they're stopping it because writing your own blu rays is relatively rare, or if they're hoping to cripple the bootleg movie industry from using them. Given this is Sony, I'm partial to think the latter may be the case.
What is the relevance of your anecdote? I’m genuinely confused.
They were definitely already grafted, that's how the cloning works.
Another thing is that almost every complaint I see about React (except bundle size maybe, but who cares?) exists in the APP context.

If your use case is a simple website, React is just a nice templating lib and you won't need to use any of the things people generally dislike about it. That AND your experience when you inevitably have to add some interactivity is going to be 100x better than vanilla JS.

As for the build step, there are many turn key solutions nowadays that "just work". And isn't a small build step a plus, compared to being at the mercy of a typo breaking everything? To me that piece of mind if worth a lot, compared to whatever manual testing you'd have to do if you work with "text" files.
> It's basically a declarative statement that's almost english-like and it's specifically DESIGNED to be more readable and easier to use by humans

It has categorically failed at this task. That is what we have an entire ecosystem of tools to allow people to query and interact with databases without using SQL.

Developers need to understand that SQL is an abstraction for developers, analysts, data engineers etc not end users.

And only basic SQL statements are English like.
But why would OP or I switch away from React when we believe it's mature, stable, fast enough, and has a huge community, resources, and ecosystem?

And perhaps most important of all: it's the tool we know.
> Any web application with a UI _requires_ a frontend build for CSS/JS.

Except it really doesn't. Core web technologies have gotten so much better since the jQuery/pre-SASS days that you can absolutely get by without a build step.

- http/2 makes bundling a questionable choice

- polyfills are pretty much no longer a thing

- CSS now has most (all?) of the features that people used SASS for (variables, nesting, etc.)

- es6 modules work

This has been a big talking point in the Rails community lately — one of the big selling points of Rails 8 was the fact that you can, by default, ship a whole webapp without a build step, and that this is considered the "happy path".
Reading over the authors primary reasons to not use React, they strike me as fundamentally misguided - mostly solving problems that most people don’t have.

One reason it says that React is a poor choice is performance issues. But front end performance issues are almost never the most pressing issue to deal with. React performance concerns in the real world are typically measured in, at worst, hundreds of milliseconds. Yes, there are a few specialized domains where this will matter. No, you probably don’t work in one. Greater leverage can almost always be derived from improving the backend.

The second reason the author says is that it’s based on a legacy eventing system which supports IE. The author goes on for quite a while to say how bad this is, but I question the assumption it’s predicated on: the legacy eventing system never bothers me, and it doesn’t create issues visible to my users. As far as it seems to me, this argument is akin to saying that React hasn’t bothered refactoring an old part of the code base. Yes, that’s not great, but it hardly strikes me as a reason to drop a framework entirely.

Finally, the author doesn’t actually give a prescription as to what to use instead of React. This is, personally, where the argument really falls apart. React does make a set of tradeoffs, I don’t deny that, but most alternatives I’ve seen make a worse set of tradeoffs that shift more work onto the engineer. Of course, since the author doesn’t actually highlight any alternative, we can’t have a discussion about what you’re trading away, but I suspect that the author makes no proposal because he knows that any alternative would immediately be shot down as obviously worse than React.
I am most productive, from day to day, when I’m also reading. It somehow strokes my mind and encourages my creativity.
I spent a year working on visual versioning for NodeRED flows because that was the first thing I felt was missing with NodeRED.

The result was FlowHub.org which differentiates between visual changes and textual changes. Which was my main focus.

There is no visual concept for merge conflict or similar but at least versioning is far simpler since comparison between versions is much simpler.
ck2 can you say exactly which js noscript is blocking?

I block all js and I'm only seeing the blue butterfly, no text.

In the twitverse, I could at least read the post with js disabled, but I'm not getting there on bluesky...
Well, you won't be the first to build something users love but their employer/your customer won't be willing to buy.

Have you found the small hospital you will be selling this to? Or made a list of such potential clients?

And why would a small hospital be more willing to buy than other, bigger ones?

Maybe there's a feature or two that you/doctors have not considered useful but your clients find crucial, and you must focus on those ones more than anything else.

Maybe there's a reason almost all hospital/health-related software is bloated and sucks for anyone actually using it.

Maybe you should be spending more of your time thinking about these questions and how to answer them before spending any more money on this.

I'm not trying to stop you, just point you to what I think is the right direction. I could be very wrong here, is what I mean.
> I genuinely can't think of one impressive thing Google has done in the last 15 years.

Meet team ported advanced audio processing, environmental noise cancelling and camera effects to Firefox, and they work really well.

It's not impressive of course, but interesting enough to notice.
So who and why will produce the news for your friend to steal? The horse and buggy metaphor is getting tiresome when its used as some sort signalling of "progress oriented minds" and creative destruction enthusiasts versus the luddites.