skysight-inc/HackerNews huggingface dataset:
To be fair one of the most common ways of managing Kubernetes clusters and what is deployed on them is to use ArgoCD, which gives you the same issue of dual stateful control planes.

Even more fun is if you then run your Kubernetes cluster on top of a VM orchestrator such as vSphere, that way you have multiple layers of stateful control planes and compute orchestrators fighting each other.
> Kotlin and Swift have declined in the ratings because they are both mainly used for a particular mobile platform, Kotlin for Android and Swift for iOS, Jansen said. There are other sufficiently good languages and frameworks to use for cross-platform development now,

Yeah that sounds about right, native work has been drying up quite a bit in the past couple of years and React Native is all everyone is after, it seems. YMMV

RN also has a very unfair advantage where you can use Codepush to OTA updates, bypassing Apple/Google's reviews (within its limits of course). It's against the TOS, but the store caretakers have no way (or don't want to) of policing apps that do that, so in the end if you do native only - you're playing with one hand behind your back.

And it's not only small devs that do that - all the major automotive manufacturers like BMW (Flutter), GM (React Native), etc do it.
5 years on: Brexit's affects on scientists who had moved to the UK from Europe
Rethinking AI Agent Architecture with MCP
As per HN guidelines, I'm available for questions.
I write Java for Android. But I'm more like jack of all trades, I'm not specializing on Android development. I know Kotlin, but it's too complex for my taste, so I'm avoiding it, Java works just fine.

Actually the same for iOS and Objective C. I learned Objective C like 15 years ago and it didn't change much since then. I also learned Swift the day it was released and I know nothing about modern Swift, it changes so fast. I don't really care. Objective C works just fine for me too.
This page has horrible scrolling. I really don't understand why anybody creates this kind of scroll. Are they not using what they create?
You're talking about artistic tradeoffs. That's fine.

I'm asking, how do you quantitatively measure in the first place so you can even define the tradeoffs quantitatively?

You say how in your opinion, different algorithms preserve detail better in different areas. My question is, how do we define that numerically so it's not a matter of opinion? If it depends on contrast levels, you can then test with images of different contrast levels.

It doesn't seem unreasonable that we should be able to define metrics for these things.
A junior engineer makes 70-100k in most places. The Bay Area distorts the actual market.
The movie: https://www.imdb.com/title/tt0162711
The Infocom games were also super-tight on memory. There’s a presentation by Dave Liebling I think at some game developers conference on YouTube someplace that goes into this among other things.
> C doesn't try to save you from making mistakes. It has very few opinions about your code and happily assumes that you know exactly what you're doing. Freedom with responsibility.

I love C because it doesn't make my life very inconvenient to protect me from stubbing my toe in it. I hate C when I stub my toe in it.
I was living overseas (Australia) and went into the GP to request the 10 year booster for TDAP as I have been accustomed to thinking is necessary.

The doctor just laughed and said "You must have spent time in America." The only recommendation for TDAP for adults is during pregnancy. See https://www.health.qld.gov.au/__data/assets/pdf_file/0031/98...

Meanwhile, in the UK, the T and D of TDAP are given just once (part of Td/IPV), with the P given only to pregnant women. See https://www.nhs.uk/vaccinations/nhs-vaccinations-and-when-to...

Upon return to the U.S., my doctor strongly recommended getting the TDAP again since it had been well over 10 years, with 5 shots for kids and then again every 10 years. See https://www.cdc.gov/diphtheria/hcp/vaccine-recommendations/i...

I will admit that now I have no idea what the actual best schedule for these is.
And people wonder why American manufacturing (and Detroit in particular) has done so poorly for the past 50 years. It's starts at the top. Here is an incredibly candid (and depressing) example of this.

Perhaps if they paid attention this closely to market conditions and manufacturing innovations, Ford wouldn't have this embarrassing example of a corporate executive that is so out of touch.
BSE: Semantic compression for LLMs, built by a starving creator
Built solo. Semantic compression engine for LLMs.

– Extracts subject-verb-object structure
– Detects questions and figurative language
– Works with text, image, and audio
– CPU compatible
– Outputs clean semantic JSON

Demo: https://huggingface.co/spaces/Sibyl-V/BSE_demo
GitHub: https://github.com/SibylVeradis/BrambleStudio
Step right up kids! talk to a dolphin for 50 cents!!!
My grandfather was well known at work for, uh, creative sayings. Malapropisms, misheard cliches, or just wild-ass new phrases. His coworkers took to secretly writing them down over the years, and they read them off during his retirement party to universal delight.

A copy of the list ended with us, the family, and has come up during my grandfather's wake and a few times since then.

Absolutely agree that it might not be nice, but context depending it absolutely can be -- as well as a really touching legacy.
I agree this is not a good strategy, but I found it curious that Kotlin seems to have stalled and maybe is even declining. After all, it really seems what many developers would like Java to be. The article also mentions the existence of better alternatives in the form of some other languages' cross-platform frameworks, but doesn't make any concrete example. Anyone has ideas on which frameworks those could be?
Btw, Kotlin isn't platform-specific as they seems to say in the article, it's cross-platform as well.
How much of this in influenced by the base rate of partisanship among medical doctors? 50 years ago, both Republicans and Democrats were equally likely to hold a prestigious occupation, but now, along with the yawning educational gap, there is a huge gap in prestigious occupations favoring people with liberal political beliefs. If I hear about a doctor who advertises their service on "conservativeprofessionals dot com" I think I would be right to wonder if they were some kind of disbarred chiropractor hawking steroids and horse drugs.
One thing that I have hypothesized about, is can material embedding vectors be extracted which are then used to predict prices?

In theory, this is what value investors are doing to some extent. However, embedding vectors often to do match intuition very well.
As someone who has a file with similar hacks, I will say this: I am not a C++ fan, but if you find yourself writing C code where you simulate methods via structs with function pointers often, just use C++ as a basic "C with classes" at that point. You want methods anyway, you have to go through a pointer dereference to call the function, it's just not worth the code weirdness. If you have the grit to use structs with function pointers everywhere, you have the grit to stick to the simpler subset of C++.
Gleam v1.10.0 Released
> If this is "just a job" as you can expect to be laid off at a moment's notice with no care for the value of your contributions, then what is the point in doing anything more than what the job description entails

I guess the half million dollars yearly (I'm assuming he made) and the fact there aren't tons of other places he can get that kind of money and prestige for doing that kind of job.
I'm not saying I'm loving any of this, but yeah the system we've built treats all of us like replaceable cogs. During good economic times we don't really feel it, but we are now in a rough patch and we see the capitalist economic reality for what it is.
It's in there briefly in the llm limitations section.
I think this is an eggcorn/mondegreen for “all of a sudden”.

Seems weird for the WSJ.
There is Metal-cpp though.
I think they suggested that in the US employees are paid better than contractors, but have low job security.
You can find detailed search (including title/content) using the bookmarks endpoint. Snapshot search is currently only for finding multiple snapshots for a single URL/domain. Probably it should be emphasized, or content based search should be available there as well. Thanks for the feedback!
The only issue I've ever had with archive.* links had to do with compatibility with Cloudflare's DNS but those just fail to resolve. I'm not sure what three lines that fade out is all about -- extensions, maybe?
It always boggles my mind that python is so popular while being so unfriendly and hard to use. Terrible package management. Poor typing system. Useless stack traces. Unintuitive syntax (no ternary operator?!). And yet it has become the default language almost.

I guess the way forward now would be to "make python good". Thank goodness uv is trying.
Maybe the fame, but I've only recently taken up Kotlin and... I can't say anything bad about it. Yes, Java is catching up, to a degree, but Kotlin is really nice to use if you're on the JVM anyway. (non-mobile btw)
In Brazil, people who support bolsonaro are more likely to believe in conspiracy theories and not trust doctors, vaccine or science.

I also think it is reasonable for everyone to have a tendency to not trust a doctor who is a bolsonaro supporter.

There is a very emblematic case, although not very known, of a doctor who refused to treat the child a a Lula supporter: https://www.jusbrasil.com.br/noticias/medica-se-recusa-a-ate...
Maintainer here (and fan of ETV)! Currently, the most fundamental difference between Tunarr and ETV is scheduling methodology, though this is on the road to change. ETV takes a top-down approach; you schedule lists/collections (either custom, or just a whole series, for instance), clump those choices together, and customize how they "play out" their contents, e.g. "play 2 programs from series A, then play 4 programs at random from collection X".

Tunarr is, currently (and like it's predecessor dizqueTV), a bottom-up scheduler. You create a schedule with a flat list of programs (episodes, movies, etc). Then, you apply transformations to that list (grouping, padding, etc) in order to build your schedule. This is a bit of a simplification.

Both programs have a range of tedium in their scheduling, depending on how particular you are about your schedule.

Of course, ETV is more mature than Tunarr, so there are a lot of other features it has that Tunarr does not. It is also, likely, more stable. However Tunarr's streaming stability has come a long way and was the primary focus in the beginning of the project.
Stop playing pong with your build server
>So your response is to accept someone's speculation when the company themselves says they are piloting a recording program in the US (however they say the case in the article was not part of this). Given what is in the article, the speculation you linked to is irrelevant.

I don't see how it's irrelevant given the recording program was in the US, and contrary to Trump's bluster, Canada isn't the 51st state yet.

>You are taking a threat model that assumes all recordings have equivalent risk of leakage. On a long enough time scale, you're probably right. I think there is a spectrum of risk that is also based on trust. I trust a company focused on audio/video to handle the materials appropriately a lot more than I do a company where this isn't their core competency.

The problem isn't necessarily that Zoom itself will get hacked, it's that such recordings can get leaked by someone else. Zoom has a quota for recordings, so they often get uploaded to the company's network share/sharepoint, which are routinely targeted in ransomware attacks. Moreover, that's not even the only threat I mentioned. Zoom might be a well known company that has reputation at stake, but the lowest bidder that a megacorp contracted out to provide call center software might not. Finally, if voice cloning is as easy as you claim, there are far easier ways to get a sample. It's not hard to call you with a made up pretense (eg. "are you [spouse]'s emergency contact?") to coax you into producing enough speech samples for voice cloning.

>While /any/ recording presents a risk, recordings you are unaware of are significantly higher risk because you can't do much of anything about them.

Is anyone seriously going to stop calling customer support because of "voice cloning"?

>You are making a false equivalence and desperately trying to defend it. The two things are not the same.

I'm not claiming they're equivalent. Quoting my initial comment:

"you should be far more concerned about recorded zoom meetings or customer support calls"

I'm not sure how you can possibly interpret that to mean "zoom recordings are the same as lyft recordings"
The TIOBE index is widely regarded as mostly useless for the kind of thing people try to use it for. Their own description of the index shows the problem:

> Basically the calculation comes down to counting hits for the search query +"<language> programming"

That's it. The rest of the definition hinges on weighting the different search engines and deciding what counts as a programming language. So the index is actually just measuring a proxy (search hits) for the number of online pages that contain the words "$LANG programming" in them.

A number of problems become evident with that definition, but most important here is that common linguistic usage patterns in a community have an enormous impact in rating. "Swift programming" may get fewer hits, but "iOS development" is a synonymous search term these days that gets ignored by TIOBE. The same for "Rails" and "Ruby" and "Android" and "Kotlin".

TIOBE is fine as a tool if you understand its limitations, but articles like this rarely do.

https://www.tiobe.com/tiobe-index/programminglanguages_defin...
X is still fairly sticky, it's never truly lost all the great things that brought people to Twitter in the first place. Sure it's swung from left to right, but that's irrelevant because politics wasn't what brought people to Twitter.
I hadn’t thought about it but you’re right. If the iOS 19 UI rumors are true, non-native is going to stick out in a bad way. Even RN apps aren’t going to be spared, because even though RN uses native widgets in parts they still do a lot of custom styling which will look downright broken mixing in with a pseudo-3D visionOS-like UI.
The Moho is in reach of ocean drilling with the Meng Xiang
Go's map[string]any type
> The comparison really isn't even close.

IMO it's close. Lisp isn't much worse than other languages. Tho it needs special syntax for some common constructs. It helps the human.

Regarding the for loop, if you only loop one statement, you do

for (int i = 0; i < 5; i++) printf("%d\n", i);

If you loop several statements, you do

(loop for i from 0 below 5
do (progn
(format t "~A~%" i)
(format t "~A~%" i)))

again, lisp lacks the syntax to group several statements together. In C it ends with );} , indicating a function call inside a control flow or a block. In lisp ))) can be anything from function definition to assigning variables or arrays/collections or anything.
If someone offers to contribute a README translation and to keep it updated with every change, you can consider merging it. It indicates that there are existing users who want to talk about the project in their native language. And that somebody could e.g. open an issue in that language to ask questions and get help.

But if there is no such community, a translated README on its own is pointless in my opinion.
Yeah the demographic transition is something nobody predicted (afaik). On the other hand, LTG (https://en.wikipedia.org/wiki/The_Limits_to_Growth) is a neo-Malthusian prediction that seems to match early data, and a surprising number of people revisit it and find its conclusions seem to hold. We'll be finding out around 2040, give or take. ¯\_(ツ)_/¯
Here was the 1980 explanation

https://archive.org/details/creativecomputing-1980-07/page/n...
No, it's not strictly voluntary, because the existence of a market sets a price for a product, and materially differing from that price either puts you at a disadvantage (deprives you of voluntary trading partners) or creates opportunities for arbitrage (disadvantaging those who would otherwise voluntarily trade exclusively with you). And if your competitor has a massive pre-existing wealth advantage, they'll happily eat the loss and undercut you until you're out of business. This produces worse outcomes in the long run.
"Sequential thinking" is one that I tried recently because so many people recommend it, and I have never, ever, seen the chatbot actually do anything but write to it. It never follows up any of it's chains of thoughts or refers to it's notes.
Well. To repurpose you knife analogy, they (we?) duct-taped a knife on an erratic, PRNG-controlled roomba and now discover that people are getting their Achilles tendons sliced. Technically, it's all functioning exactly as intended, but: this knife was designed specifically to be attached to such roombas, and apparently nobody stopped to think whether it was such a great idea.

And admonishments of "don't use it when people are around, but if you do, it's those people's fault when they get cut: they should've be more careful and probably wore some protective foot-gear" while technically accurate, miss the bigger problem. That is, that somebody decided to strap a sharp knife to a roomba and then let it whiz around in the space full of people.

Mind you, we have actual woodcutting table saws with built-in safety measures: they instantly stop when they detect contact with human skin. So you absolutely can have safe knives. They just cost more, and I understand that most people value (other) people's health and lives quite cheaply indeed, and so don't bother buying/designing/or even considering such frivolities.
Why would they be complaining about working 40h a week? You will obviously hear more about bad experiences than the norm.
Kubernetes added "image volumes" so this will probably become more and more common: https://kubernetes.io/blog/2024/08/16/kubernetes-1-31-image-...
This is an important point.

Especially overt the last two (three now?) years, it's become pretty apparent many software jobs are superfluous, even those that are ostensibly "skilled" or "difficult."

I do wonder what the actual "needed" number of technical staff these companies would have in a perfectly "efficient" environment. Let's hope we don't have to find out.
> Google has traditionally had a fair number of developer relations engineers

I wish them all well, but things can change fast depending on how the economy is doing and where the company is headed priority wise.
Any style of layoff is going to be bad for morale, but rumors floating around tank morale for as long as those rumors exist, and then moral takes another hit on the actual day. In that way it makes sense to just rip the Band-Aid off.

Of course, if you ask me, a more sensible plan to keep morale and lower costs would be getting rid of a few executives, but what do I know? I'm just a number on a spreadsheet.
Some points about the introduction, but otherwise this seems like an interesting collection of (slightly deranged?) patterns in C.

> The truth is that any reasonably complicated software system created by humans will have bugs, regardless of what technology was used to create it.

"Drivers wearing seatbelts still die in car accidents and in some cases seatbelts prevent drivers from getting out of the wreckage so we're better off without them." This is cope.

> Using a stricter language helps with reducing some classes of bugs, at the cost of reduced flexibility in expressing a solution and increased effort creating the software.

...and a much smaller effort debugging the software. A logic error is much easier to reason about than memory corruption or race condition on shared memory. The time you spend designing your system and handling the errors upfront pays dividends later when you get the inevitable errors.

I'm not saying that all software should be rewritten in memory-safe languages, but I'd rather those who choose to use the only language where this kind of errors regularly happens be honest about it.
The issue with TurboTax that the author ran into:

>I’d entered my ISO info in two different forms in TurboTax – once after searching TurboTax Help for ISO and AMT, and again when TurboTax asked me about ISOs near the end. I’d originally assumed it was just validating or overwriting the numbers I’d already put in, but it was actually creating duplicates! (C’mon, how does software like TurboTax not validate against duplicate entry???)

That's pretty astonishing and I guess their testing missed it too or assumed the usual ISO field and searching help about ISO were different ... but that maybe should have raised questions for them. You would think just a couple extra sets of human eyes would catch that one.
My experience is that anyone who is sufficiently specialized in either platform will select to develop natively for that platform over using RN, since RN imposes lowest common denominator UX for both platforms, more or less.
In the days of yore, didn't a decent chunk of people literally have their name come from a family profession? I.e. John Smith, Jan Schmidt, Carl Maria von Weber.

As in it wouldn't be just your worth tied to the profession, but N generations of your parents, etc.
Interesting how the people with the most distrust for authority are also the most in favor of authoritarianism.
This article is sort of just a paraphrase of the Tiobe release announcement: https://www.tiobe.com/tiobe-index/
China and America Agree: Apple Is Too Big to Fail
I don't understand what you don't understand?

If you have a recurring lunch, it's always at the same local time interval, but not the same UTC interval, because of DST. Calculating with it requires datetimes, not just times or UTC from the start, contrary to who I was responding to. What is unclear about that?
It's a quote from a source so at most I would expect a "[sic]". Thinking about it more... it seems like an intentional mistake by the speaker to demonstrate the sort of verbal flub the quote is about. In which case it's pretty clever and a "[sic]" would kind of ruin the subtlety of the joke.
It would be fantastic if large non-corporate org's had no need for buzzword bingo games.

But alas! Nope.
> Because it's where important information gets distributed and discussed

This seems less relevant each day. Even here on HN, Twitter used to be on front page almost every day. Now it is pretty rare. Which makes sense when most people are not able to see Twitter threads (if it works for non-logged at all).

> when literally every other social media platform is worse

This is based on?
I just had this same thought this morning. I sure do with OCaml was far more popular. Right now, if you're planning a startup, you want something that you can just snap together a bunch of well-tested libraries. You want DB libraries, S3, message queue stuff, Kafka stream stuff. OCaml does have a lot of these things but they just aren't well known. If they exist, they're just poorly documented. This is why people opt for Java/Typescript/Ruby/Python. It's easy to hire devs, and the tools they'll use are fairly well understodd.

OCaml suffers greatly from a lack of unified practice. There's a YouTube playlist, a Udemy course... an Apress book and those two other ones with camels on the cover. That's about it for stock OCaml. If you want to learn Jane Street flavored OCaml, there's Real World OCaml.