skysight-inc/HackerNews huggingface dataset:
No, I'm not conflating quality with popularity; I am telling you the definition of the term I am using. You are welcome to your own definitions but you need to label them as such.

There was no option in the early 2000s of deploying any significant production software in ML. You can see this very easily, let me make a list: C++, C, Java, ML. Which one doesn't belong to the set "production-quality language in 2001"? Anyone who can't answer that is just being deliberately obtuse. Even though Java was jammed into that list more by executive fiat than anything else, it was still in that list. You may like ML a lot, you may have preferred to work in it, but it is very clearly not able to run in the same spaces as C++/C/Java.

I used Haskell circa 2012 to build a highly concurrent network server for a game contest. I'm glad it was just a game contest and the biggest stakes were which college student got the grand prize. It crashed under load. Really quite a bit; I was restarting it about every hour, under what would have been a trivial amount of load by any production standard. And it was just Haskell bugs; as Haskell advanced, the exact same code crashed less and less. Probably it would be fine today. But this is the sort of thing I mean; even if you like the language, production shines a really, really harsh light on a language. Having a theoretically superior concurrency solution didn't make my code not crash the runtime. Having a theoretically superior typing solution still leaves a language needing tested libraries, tested framework, exposure to real world situations. The odds of hitting a critical snag is just too high otherwise.

Even today, telling me that you're building a critical system in ML would basically be a firing offense (if you obstinately stuck by it). I'm as open minded about languages as anybody, but I know enough to know with close-enough-for-business-certainty that it's a bad business decision. Should the ML community suddenly revive and fix up the language over the next 5-10 years, I'd happily reconsider, but today? No question. Even Haskell would be a very uphill battle, for many good and sufficient business reasons, but maybe you could just about convince me there's some task you just need it for.
I am honestly looking to move to a competitor because of their podcasting and audiobook efforts. Well, and I don't necessarily care about those things per se but Spotify used to be a focused music app, and they keep removing things from the app in favor of whatever new "growth thing" they want to do this year. I never know when I load up the app what is going to have changed and take me an extra 5 minutes to find what I want.

They have done so much damage to their app's usability by trying to "grow" that someone could probably sell me on some ultra-premium subscription that actually had a good music player that functioned more like the music players of 15 years ago.
Note that market street around the Twitter building has never been a great area of SF. I think part of the hope was that it would re-vitalize that part a bit. Moving around SF is weird because the difference from street to street can be huge.
My best guess is that with the legalization of weed, dealers who used to sell it were pushed to sell harder drugs. These harder drugs come with more significant effects in destabilizing mental health.
Harvard gutted team examining Facebook Files following $500M Zuckerberg donation
it's not even ganging up, it's just hiring a middleman to do your negotiation for you, and they take a cut.

I'm good
You can't have your cake and eat it too. There are plenty of other lower risk companies that have way lower chances of layoffs, but they don't pay as well. Working at a company that tasks risks and has a high rate of return also has a higher chance of making the wrong bet and needing to cut you. If you want a perfectly stable job go work in the government: you'll be practically unfirable.

- someone who was layed off from a FAANG corp. I was not done a disservice, I knew what I was getting into.
> Just remember they signed Joe Rogan for over 200 million and he's not brought in nearly that amount for them.

The fact that they signed Joe for that amount, and continued to air everything throughout all the controversies, throughout all the COVID years, and through some artist departures over him, signals that he has more than recouped that investment for them.

https://www.newsweek.com/joe-rogan-more-popular-ever-statist...
"Gen Z shit" as I'd like to categorize it, no offense
Depends what you're solving for. Building a website that requires user authentication and basic relational DB... I default to Django. But if I'm building small internal services then I go FastAPI or Flask. Django's ORM is still dreamy.

I used to like DRF (Django Rest Framework) and Django + DRF was a powerful combo to drive single-page-application sites. But DRF can get a little painful if you're not using some of the out-of-the-box classes. Painful as in... lots of code to right and very hard for someone to maintain without knowledge of how DRF magic is made under the hood.
In the last few months, several podcasts that were only available on Spotify, have become available via traditional podcast means. For example, Heavyweight. Others did so earlier, though for specific reasons (Science Vs had a spat with Rogan over "dis/misinformation", where I largely agree with them factually, but disagree with them on the use of those terms, etc.).

I think it's fair to say there's a reasonable indication that Spotify exclusivity has been a bad bet for a decent amount of their podcast portfolio. Maybe it works still for Rogan-sized podcasts, but even that's unknown.

I wouldn't be dismissive of a label of "sinking ship", even though it's stronger than how I would put it -- it's plausible enough.
I’m going to admit to a bit of confusion here.

“But that leaves large and important areas that GPTs are entirely unfit for: Real-time problem solving in dynamic environments.”

Isn’t Tesla using GPTs at least for vision? What do you call the AI technologies employed by self driving projects and robotics?
They're not refugees. They left 70 years ago. If Israel left them back, Israel would devolve into another failed middle eastern state.

For people who don't know, UNRWA says Palestinian refugees are the only ones who are defined as eternal. All children, including adopted (!), of Palestinian refugees are Palestinian refugees, and so on to eternity. [1]

[1]: https://en.wikipedia.org/wiki/UNRWA#Definition_of_refugee
Short term profits are almost completely defined by historic investment (and thus, historic staff).

How long term profits will react to those changes is entirely still to be seen. There's nothing telling you profits will get higher and higher, or that they will diminish, or anything else.
Today I would make the distinction between those that are readily end-user programmable (microprocessors) and those that aren't (microcontrollers).

Certainly many in this article were originally designed for what now would be microcontroller applications, but the fact that they couldn't then do on-chip ROM let hobbyists repurpose them into general-purpose microcomputers.
> Note that on the last time through the loop you are doing a wipe() that was not actually necessary to accomplish your cleaning goal, and thus wasting some paper

True! Although I'd argue that's just part of the human condition. How do we check if any given condition obtains? Very often the simplest and most effective approach is just to perform some action which depends on that condition for its success, and we conclude from the fact that our action succeeded/failed that the condition does/doesn't obtain. How do we check if a closed door is locked? Technically we could use a see-through camera to observe the lock mechanism, but it's more straightforward to just try to push it open and see if we succeed/fail to do so. Ideally we may prefer structured decision-making like if-else and switch-case statements but in reality we tend to go for the quick and dirty (if less elegant, and sometimes wasteful) try-catches. :)
Considering that entire nations were supposed to be wiped off the face of the Earth if climate changed weren’t reversed by 2000, I think we’ve done lots of progress.
I generally like the tool.

When your code review tool is really nice one unexpected negative is that it can create a culture of nitpicking. Sometimes it’s not worth arguing over small details like variable naming but the tool makes it really easy for things to head in that direction.

Sometimes variable naming isn’t a small detail. But sometimes it is and it’s a waste of everyone’s time to argue about it.
On the other hand, 17% of headcount had a job during that time. Which one is better?
Okay, a great setup for an example of what I mean.

Before the civil war ended, I could use the banana as food (which means it has intrinsic value), and I could use the paper money to represent work I'd done which is extremely useful, so useful in fact that I could use it to later buy the banana.

Passage of time occurred, the war is over and now the money is worthless/rotten and so is the banana.
Swiftie has been around for the better part of a decade I believe, and definitely pre-dates Tik Tok
I used significantly higher-rated omron relays in a project I did a few years back to switch a 2.5HP motor on/off a few times daily. This area shouldn't be skimped on; relay contact arcing isn't a joke.

This brings me to my second point: I don't see a cycle rating on those relays from the datasheet provided. Most relays are rated for ~1M cycles, some for ~10M or more, but beyond that solid-state relays start to be a thing. And so, I question if people are using mechanical relays to chop 50/60Hz AC power, which from my 30 seconds looking at the article/schematic appear to be what is happening here... That seems crazy to me, and I imagine it requires some exotic contacts in the relays to avoid failure in short order, which these relays don't appear to be. The data sheet mentions they are used for chargers/solar inverters/etc but that doesn't mean they are used at 50/60Hz cycling but likely just as a disconnect/power on function which cycles once per charge/day/etc.

Then again, I don't really want to be this guys neighbor since chopping an AC line with that much load is going to generate an insane amount of noise, and I don't see anything in the circuit designed to damp it either.
The logic for some is undermining western liberal capitalism to create either a national socialist or marxist leninist dictatorship in it's ruins.
Prior to agriculture human beings got the vast vast majority of their calories from meat. We followed a carnivore diet as a species for about 200,000 years until basically yesterday.
That ML-sidecar for recommending the actual change is a very correct place to put that technology: right in the line where someone is already reviewing the code, so they can confirm the ML suggestion looks correct before adding it.

I can't overstate how valuable it is for reviewers to give the actual change they're recommending alongside the description, but it happens too infrequently if we make the reviewer write it every time. Actual code is the cleanest language to communicate ideas, but it's a time-sink and a mental drain to turn the English description into code snippets every time. Automating that is precisely the right place to save time for reviewers.
The release process is time-based as to roughly every 8 months[1] with X.0, X.1, and X.2 (LTS). This is mostly to communicate which release has long term support.

The deprecation policy[2] is taken very seriously and Django doesn't opt to break things if it can.

Recently there was a very interesting discussion[3] between the Fellows as to whether the version numbering is confusing as this doesn't follow the same pattern as other libraries.

1: https://docs.djangoproject.com/en/dev/internals/release-proc...

2: https://docs.djangoproject.com/en/dev/internals/release-proc...

3: https://fosstodon.org/@carlton/111300877531721385
Obviously it is policies and San Francisco has stuck to the policies against all evidence to them not working. Moreover, the politicians that put in place those policies get reelected and elected to higher offices. The governor of California is the former mayor of San Francisco under whom the situation has turned "dire," as many have attested.
Well, he described the single board version as a trainer: a way to demonstrate how the larger model works. That's likely why the address/data lines are toggle switches and the close is a button. People can setup the state then execute when ready. The much larger version is the thing you see behind him on the wall (it is a work in progress). It is also intended to go to events, but it is much harder to understand ... thus the trainer.
I think this conversation is absolutely worth having. It's great to see that 1.10 is ~3x faster here, and there's probably another ~2 to 3x improvement or so from profiling DynamicalSystems to see where the time is going. That said, for sub second startup time with lots of packages, I highly recommend using PackageCompiler to make a custom system image which brings the using time down to roughly 0.
Israel never could have launched this extensive a military campaign with international support on the basis of an intelligence report from Egypt, Mossad or otherwise. People would say that any time someone wanted to invade a country without provocation, they could just accuse the other side of wanting to attack. It's also possible that Netanyahu knew of a planned attack but not of the severity. Netanyahu is a hawkish zealot, obsessed with reclaiming the West Bank. It's not hard to imagine an aging political leader wanting to take over the settlement as part of his legacy.
Show HN: BuyMyGPT – monetize your custom GPT today
> 2) QUESTION: Are there simple programming languages so that HALT restricted to them is decidable but not primitive recursive? I suspect one could contrive such a language so I ask for both natural and contrived examples.

I like the lexicographic descent criterion as a not too contrived example of a class of programs larger than primitive recursion, and yet for which it's easy to prove termination (e.g., https://goto.ucsd.edu/~gridaphobe/liquid/haskell/blog/blog/2...). That's apparently equivalent to the class of multiply-recursive functions (https://dl.acm.org/doi/abs/10.5555/860256.860258)
The alternative is just specifying the value on each item. These two are equivalent:

<ol reversed>
<li>Three
<li>Two
<li>One
</ol>

<ol>
<li value=3>Three
<li value=2>Two
<li value=1>One
</ol>

Note also that reversing content via CSS is generally unwise, because things like screen readers, text selection and tab indexing operate on DOM tree order.
On the flip side you have cases like this after Hurricane Ike

https://www.cnn.com/2008/US/09/18/ike.last.house.standing/
I recently left Spotify for Apple Music, in large part because of this new development path. I don't want podcasts, audiobooks, etc mixed in with my music. I prefer separate apps.

I think what bothered me more was the focus on branching into these new paths without any innovation in the music department--I'm sure there was innovation that wasn't visible to me. I'm tired of the same black and green color scheme. I don't like that I don't have a 'Library' and everything just goes in liked or a playlist.

I think their expansion into other media was a signal to me to look for someone doing a better job at specializing.
I suspect the losing side often ends up with “better looking” generals because they end up fighting defensively. If you lose long enough you end up in familiar terrain, with a sympathetic populace, and your supply lines get shorter!

Eventually the war gets truly hopeless. Without any feasible objectives to go for, the loser has incredible latitude to try and stay alive and inflict harm. Never any need to take a tactically disadvantageous battle for strategic reasons if there’s no strategic hope, after all!
I don't mean that running in Bash should be THE workflow. But I think it should be supported and it's used widely and lack of support for it is a major reason why Julia is not taking off. I'm not proposing taking REPL/stateful-notebook away from those who want to use it (although I'll advise them against it if asked).

I don't find my plt.plot(x,y); plt.show() in a script ideal either. Something like Pluto.jl (given it's easy to modularize and preferably can be run without a notebook environment) is most likely better for a typical data analysis workflow (and will likely lead to more reproducible results and better tracking of result provenance).
Show HN: Trendin.dev
Get trends from hacker news, GitHub, and other platforms in the same place.
> No mentioning of semantic tags.

Yes, because it’s an article about attributes…
Maybe if your business model includes putting things in an inconvenient format that could best be replaced by a bulleted list, you should rethink your business model.
Yeah, but you can talk to an LLM.
I think the most compelling use for LLMs is “tool use.”

Imagine if everyone could write simple automation scripts in literal English. We’re there.
I wonder if the purpose of this store in a downtown location like this is more about promoting the brand for all the tourists that walk or ride by, rather than actually selling Legos.
Bitcoin is up 143% the past year; this isn’t only a week or two thing.
I've been considering adopting the gob package. I haven't used it before, so I only know what's in the docs -- and all of your claims are surprising to me. Could you share more information?

How is it possible that they were getting malformed input? This was happening in go-to-go communication, or was there some kind of cross-language interop?

Any idea why the performance was so much slower than JSON in your case? The technique described in the OP would seem to make that impossible.

Do you think it's possible the database column type or collation was somehow affecting the gob?
I once wrote out a job hunting goal on a sheet of paper and read it 3x per day for a few months, with “crazy” salary and everything. And then, I got it.

I did similar thing later with multiple goals in Google docs. Found that I’m not as consistent with it and haven’t achieved those same goals.

Could be consistency, more goals vs fewer, or the paper vs digital

There’s something about paper that feels more real. It also forces some focus as you only have so much room on paper
I don't know where I said it was caused by bad real estate, and if you understood so I did not mean to say it.

But thanks for bringing the point though because I think real estate shows the huge inequality that exists in places like SF, it is interesting to listen to the testimonies from both videos and their thoughts about it.
Organizing and keeping a photo album seems a much lower barrier and mental load for most people than the steps in paragraph 2. Let alone paragraph 3.

I am all for it, and practice something similar. I don't know anyone else though.
Critique is nice but the ML suggested edits are a waste of attention and cant be disabled.
Be careful though, my father in law has told stories about people who made themselves irreplaceable by being the only person who can fix a machine because they allegedly fixed it in a way that breaks often enough that they can be the hero. A stain like that on your resume means your burned trust for potentially short term gains and may find trust is not given as easily as a result.
It can be tricky to find a balance point here. At Google scale (in time-of-maintenance, not space... Code can last for years and will be worked on by multiple engineers disconnected from the original project), the hard problem of naming things becomes real.

I find that it's useful to keep context. Even though one can never predict with certainty, sometimes you can be real confident that some code is prototype that will be thrown away in six months. And there's a big difference between the code that makes up an API layer and the code that implements a feature constrained to one module.
Interesting way to look at it, a bet. A bet involving people's livelivehoods.
You can tell the writers and designers hate the PDF format because they made the damn thing so difficult to read, layout-wise. They went 1990s PageMaker/QuarkXpress crazy here.
Have you considered paying for the patreon regardless because you consume his content one way or another and value it?
The descent continues ...

I was 100% aware of this word ... but ... Oxford Word of the Year?

Slow year.
Yes, it depends on those factors. One other factor is what would have happened at his old job. I have a friend who went from one big tech company to another was then laid off recently. There's a good chance the result would have been the same either way, since the first company cut a lot as well.

One factor that keeps people at a company is the knowledge that, all things equal, last hired is first fired. It's not hard and fast, but you tend to have fewer allies at a company you just joined, making you more susceptible. When someone decides to leave one company and join a new one, they know that they're giving up this advantage.
I agree with you, but these features have been around for years. music radios, discover weekly, their premade mixes. Spotify has genuinely great recommendation algorithms. But they've had them the whole time. I don't know what they've been doing for the past few years, but I haven't seen any additional value add. They still don't even support Airplay 2.
FWIW I switched to Apple Music and the player is pretty good, plus the music is lossless.
I've always felt, and this hasn't changed recently, that if you're going to need more than, say, 3 of the cross cutting concerns that Django provides for, then it'll be much more maintainable in the long run to just use Django rather than effectively building a custom solution out of parts. The flip side: if you're building a small internal API that only needs a couple of these, Django might be overkill.

What do I mean by "cross cutting concerns"? I'm thinking about ORM/models, migrations, admin UI, caching, sessions, misc security middleware, user accounts, validation/forms, templating, RSS feeds, logging, testing infrastructure, etc. Django's pieces all fit together well, and any time I've done this with Flask/etc I've found myself spending so much time solving issues gluing these bits together and working around impedance mismatches between libraries.

We had a large Django site at my last place and would just suggest new starters worked through the Django tutorial, because our site basically still worked like that.
What's the current miss-rate on them? In principle, it seems brilliant, but I can see that value dropping off a cliff if more than half of them are worthless.
Can someone explain to me what is so difficult about writing security policies? Are people really deploying services in production without understanding the upstream and downstream dependencies of the service?

Also at cloud-scale 95% accuracy is completely unacceptable.
Advent of Code with SpinalHDL
As awkward as Protobufs might be - is there any similar format with so many client bindings? I tried comparing the message formats I could find (e.g. Cap'n'Proto, Protobuf, msgpack and others), and still Protobuf seems to have the most supported languages. I'd be happy for any other suggestions!
You sound like a fucking tyrant, my guy.
This is a known tactic by the well funded propaganda campaign waged by oil companies.

If it’s too late we can’t do anything about it, so might as well do nothing.
It seems to have been hackernews'd:

https://web.archive.org/web/20231204144437/https://www.paral...

It's an entertaining link
Mods: I'm not sure how I managed to grab this URL, but I believe the canonical version is actually https://whistlebloweraid.org/joan-donovan-press-release/
I'm no expert, but note that finite loops were allowed. In the case of any tree or graph traversal, you could replace it by a loop bounded by the tree/graph size plus an if...