skysight-inc/HackerNews huggingface dataset:
Essentially, this tells that:

1. how much psychological trauma it brings to average developer because today's most C/C++ library is not shipping static library by default.

2. how much pain it causes when the build system just can not copy the whole damn library into somewhere called lib and include instead spill into hundreds of random locations even we know that it will just build if we just copy it one place.

3. returning a struct with a integer status in it is so challenging for average programmers.

All these must be true because it seems it is the reality.
As a man of culture who has witnessed his fair share of illustrated hands and feet: "AI" reflect human failings at drawing appendages very, very well.
This is typically as far as I go with an ORM, CRUD operations on single tables that give you some type safety at compile time. If you need more complex data shapes I usually create a view or occasional stored procedure but that's about it. I use Entity Framework in my day job and do like the migrations though...
Every morning we begin stand-up with a ritual, our whole team simultaneously muttering something arcane whilst manipulating the inner workings of Teams, hoping to appease the MS gods.

Shortly after the ritual is complete you hear a cacophony of "fucking teams wouldn't find my headset/camera", and the day begins.
How are bonds "stupidly high risk"?
It's hard to explain to developers why an ORM isn't really that great of a solution....but at a high level:

* your database is the core of your app. Abstraction implies that you don't care about the details of your data store, which eventually will lead to two major problems:

1. When things are slow you won't be able to debug it, because you're abstracted away your database and don't understand what queries your ORM is using to do things, and

2. when your ORM migration fails you won't know what to do, because you don't understand your database. In general this happens with every ORM product, ever, because you didn't put in a constraint initially because you didn't know what that meant and then you did later, which caused the migration to fail because your constraint is being violated. Or the migration fails because the tool uses some attribute and not others for drift detection, so it tries to delete your table/database because it's detected drift.

* the way you deal with data in code and in a database are different. Code iterates over objects. If you just use your ORM naively you'll end up doing some ridiculous number of selects because in code it looks like you're just iterating over objects...when in reality the ORM is doing a select/join for each one of those objects. And if you start getting more complicated there are structures that are just harder to do with ORMs...because you have to map what you're trying to do in SQL to the way your ORM works. At that point why not ditch your ORM?

SQL isn't really that hard...but thinking about how do queries is harder than you would expect. It's almost an order of magnitude faster to do joins in the database than to join stuff in-code...but that also assumes that your schema isn't screwed up, it has indexes, etc.

Lastly, a lot of ORMs don't put indexes on columns for some reason, which kills performance. You'd think that would be a detail that would be abstracted away for you at the ORM level, but it isn't. I mean it knows what you're using to select data, so it should auto-create indexes for you, right?
Sounds like failure of financial due diligence. A proper due diligence could have uncovered the concealments.
What about post init? Ansible can be run regularly for maintenance patching too.
>I don't know that "bailout" is quite an accurate description of what is happening. AFAIK it isn't as if the money was/is lost; it is more of a timing issue that is being bridged.

Bridging that timing issue will cost a few billion dollars in real cash, and other banks are being fined to make up the difference.
Further to this: I’m reading this thread [1] from Mercury’s CEO, Immad Akhund (disclosure: a friend from my YC days many years ago though we’ve not had contact for years), that their neobank product automatically spreads funds across a sweep network and delivers $3M of insurance.

That seems like a simple and effective way for companies to manage their deposit risk.

If the government/president came out and said “we’re going to protect the system now but we may not/will not in the future and all companies should put their funds in sweep network accounts to be safe”, then it would be reasonable next time to say “should have known better”.

I understand your position that startup founders should already "have known better"; it's defensible on pure technical grounds, but just impractical/inefficient given contemporary realities.

[1] https://twitter.com/immad/status/1635302598831112192
The original source video by Marcel Vos that explains the premise: https://www.youtube.com/watch?v=4o0-0G2OjSg

He deserves the view and ad impression revenue more than PC Gamer talking about his video.
Would take a massive hit for sure.
Sounds like a tidy solution to the human rights violation that is arranged marriage, and the closely associated tradition of honor killings, the murder of a woman by her immediate family for refusing to submit herself sexually to those chosen by her family for her.

The idea that someone could hold such cultures up as an ideal is literally insane to me.

It seems to me that these systems stem from the basic concept that women and children are the personal inanimate property of their family unit, to be disposed of however the family wishes, like a used car or a plot of land. The idea that this is healthy or normal appears to be a rationalization and not rooted in any basis besides tradition.
No, it is not RLHF because there is no reward model involved. See also OpenAI's explanation here: https://platform.openai.com/docs/model-index-for-researchers
I think we already have moved in this direction, in the sense that a degree doesn't get you much in the job market. Employers tend to place much more importance on work experience, tangible accomplishments, certifications, and so on. (Even certs might not be so useful, since the ability to pass a test is often quite different than the ability to actually do a job.) In addition, landing a job often ultimately comes down to who you know (networking, or more cynically, nepotism) and luck.
Heatmaps for popular Starbucks drinks
Please make it so that I don't have to use an app to interface with it.
My gas-powered water heater failed in my northern US location. I asked a friend who’s a plumbing engineer (!) who said to get a heat pump. I called the HVAC company which had installed the gas water heater and gas furnace some years before and asked for a heat pump water hearer, and they said oh yeah we sell one of those and people love it. I get the feeling that as you say 5-15 years ago it would have been a different story but now it’s routine.
Heuristics for software-interrupt processing in Linux
I would always use an ORM over raw SQL but this doesn't make any sense, your ORM is still going to run a query on the same DB engine. It is much harder to optimize an ORM query, but if you're only writing very simple operations you don't typically need to. The power of ORMs (at least light weight ones) is compile time types and parameters by default.
Heat pumps are a mature and well adopted technology. Their efficiency and value will not be significantly improved. I have some ideas on how heat pumps could be turned into a more compelling offering. Improving the appearance and UI of the heat pump isn't on my list.
I disagree that you can't expect it to increase forever (it's like saying you can't expect evolution to go on forever), but why would you expect IQ to decrease rather than plateau?
The size ratings are confusing. This is really a ~19kbtu unit at 5F. Most homeowners do not want a DIY solution, they want it professionally installed. And this system lacks air quality features (HEPA, fresh air intake, humidifier) and the thermostat.
I think it's the British slang meaning "lie to get a reaction".

This is a fascinating story. How weird to look back and see someone saying "I don't see how a lot of money could be made from this" to something that became one of the fundamental money engines of the internet.
Takes like 30 minutes to set one up and they're cheap. So, yes.
That sounds bizarre. So this means that parents are potentially holding back programming language innovation? I hope I don’t have to consult with a lawyer every time I invent a new variation on the for loop. (I anticipate that someone will then tell me that there already is a patent for that…)
Create a CLI Chatbot with the ChatGTP API and Node.js
But you weren't talking about the ethical ramifications. You made a claim about a great filter, and that claim doesn't hold up.

If I say that using humans as batteries in the matrix doesn't make sense, that's not tacit approval of the rest of the scenario.
Wow that was quick, they only started in what, December?
Actually I am a bit on the fence with the SVB situation. I think they suffered from bad timing and an excessively cautious strategy. To be fair to them: one week back, given the asset allocation of SVB, how many of us could have predicted a collapse in the next two days? I could not. In fact, I would have said that investing in bonds is better than an equity-heavy allocation for a responsible bank. Hindsight about liquidity issues is fine, but I doubt that it was as clear as it is now made out to be.

Time to brush up on my Taleb again, sadly. Second time during my career.
Yeah, Django is a nice option for small proof of concepts like Instagram.
There are exactly two things to be outraged about here: First, that the data was sold, and second, what the people who bought it used it for.
I'll try! Last.fm started many years ago, in the early '00s (pretty much like Django!). They decided to use Django to serve their website and API. As the years went by, some issues and limitations started to show up: the API has several quirks they can't fix, the frontend -even after the redesign- is slow, and interactions feel clunky and outdated (like early AJAX attempts).

The API can't be easily modified -and sometimes XML responses have info JSON don't-, the website is stuck on being served through the framework instead of relying on a modern API... They even have an "old" and "new" database for albums, so when you query some of the albums through the API they come back with no tracks because the API is in the old codebase. It's a mess. And from my experience with Django, it feels a lot like the difficulties we had trying to scale and improve our existing code. It's not that you can't do things: it's just that Django isn't agile enough to adapt. You end up adapting to Django and its -beautiful and magical- ways.

Of course we could blame it on poor design choices, lack of Django knowledge or just call it technical debt... but I believe the framework is the major culprit.

For context: I haven't worked for last.fm, but I manage a third-party client (Open Scrobbler). I've been using their API for more than five years now, had interactions with their devs, read many replies in the API support forum and even tried to find undocumented endpoints that could help me (during this time I found some old profiles and test pages where you can even see screenshots of Django logs!).
'pip freeze' will generate the requirements.txt for you, including all those transitive dependencies.

It's still not great though, since that only pins version numbers, and not hashes.

You probably don't want to manually generate requirements.txt. Instead, list your project's immediate dependencies in the setup.cfg/setup.py file, install that in a venv, and then 'pip freeze' to get a requirements.txt file. To recreate this in a new system, create a venv there, and then 'pip install -c requirements.txt YOUR_PACKAGE'.

The whole thing is pretty finicky.
Former MS AI Platform IC here.

The main value of this team was likely internal, as a sort of gauze bandage on the conscience of the progressives (like myself) that MSFT has tried to court.

There was a time, not too long ago, where working at the new, 'refreshed' Microsoft meant ingesting an endless stream of news releases highlighting zero-carbon this, compostable cutlery that, and, of course, ethical AI. When Tegru was let go from GOOG we hosted a talk by her. That sort of thing. The point was to make you feel like you were one of the good guys -- your TC in effect included the intangible bonus of sleeping soundly at night, knowing that the Aethyr Council or whatever was doing all the handwringing for you. So, you know, no need to worry about social impact, just keep coding.

What this really means is, "the market is so bad right now for SWE that we no longer have to worry about the qualms of our staff, if you don't like us, the door is over this way"
At least parts of what you say ring true in my experience following GitLab releases more closely (e.g. 1-2 months behind). I would highly recommend not self-hosting if you're going to go with GitLab. Performance issues will appear and disappear between updates, and sometimes on a whim and you're never quite sure what you did or didn't do.

I did find the support staff to be fairly responsive, but most of that time felt like me collecting diagnostic information with little actionable material, and sometimes I would have to explain the same thing multiple times in the same support ticket because it switched hands.

If you do still opt to self-host, dig into their documentation: there are little nuggets and hacks they use internally that you'll want to use to get the right performance out of it.
The simple solution to this with pip is constraints file:

pip install <my_entire_universe_of_requirements>
pip freeze > constraints.txt

And now in any new environment:

pip install <any_subset_of_requirements> -c constraints.txt

Now you can install prod requirements or dev requirements or whatever other combination of requirements you have and you guarantee to have the exact same subset of packages, no matter what your transitive dependencies are doing.

You can use pip-compile from pip-tools if you want the file to include exact hashes.
SVB CEO Greg Becker lobbied the government to relax some Dodd-Frank provisions on regional lenders in 2015. Trump did in 2018.

https://fortune.com/2023/03/11/silicon-valley-bank-svb-ceo-g...
The fact that xterm supports Sixel, at least through a build flag, once more confirms my belief that this old and battle tested terminal emulator very much rocks.
If Moody didn't give them that rating somebody else would.
Good points, I didn't mean to come off abrasive but I can see why I would. My attention was to get attention on a thread where my new comment would be buried under the 8 other replies, so I put a big attention grabber at the start.

But again good points about the nuances of lower precision. For LLMs at least 'The Case for 4-bit Precision' and 'GPTQ' seem fairly conclusive that over ~10B parameters even 3-bit precision has virtually undetectable loss with the right trircks. Levels which, if they even mattered, can easily be overcome with a little additional training.

Newer ongoing research on LLaMA specifically[0] shows we can reduce the model's size around 84% without any meaningful performance loss through a combination of GPTQ, binning, and 3-bit.

[0] https://nolanoorg.substack.com/p/int-4-llama-is-not-enough-i...
I wish some company would make more aesthetically pleasing ceiling cassette units suitable for residential use instead of the wall mounted mini-splits. Most cassettes are 24x24 which is great for commercial applications but a nonstarter for residential ceiling joist widths.
People are trying to build games based on LLM generation since 2019. Problem is, the models are too flexible for this purpose - you can easily break the world rules and make the game look like nonsense. And games are all about comprehensible rules and properly placed restrictions.

So these attempts are currently concentrated on two things:

1. How to make the model play by the rules.

2. How to translate the model output into something concrete in terms of game mechanics.
> These were designed for over millions of years in differing circumstances.

Designed or occurred by accident?
Here's their operating margin for the last 4 quarters:

Q1: -49%

Q2: -65%

Q3: -50%

Q4: -38%

So what you want is a business model where the company runs purely on VC money instead of on actual profit. SaaS companies like Gitlab usually can't operate at a profit with only free-tier and cheap-tier users - their overhead is way too high. Those tiers are a gateway drug offered at a loss to get people on board so that eventually the actually-profitable enterprise accounts will stack up enough to make up the loss. It's kind of a standard bait-and-switch pushed by the whole VC model. I'm personally hoping we see less of it now that the money spigot is drying up.
Yes, but "just don't do that" doesn't scale to large teams with varying levels of experience and discipline. It sounds like you have rules that even you disobey on this project.
Lord, save us from your followers
I should've realized as I wrote that that there is a real cost (time == money).
Do you know whether the other banks are being compelled? Or are they doing it willingly to shoulder their own kind?
And as a user trying to know how your computer works, you are totally hosed until a year latter someone deep-dives & writes it up.

This article shows clear cases where this crude idea just doesn't work. And it seemingly serves no clear purpose at all right now.

This idea that the vendor's OS is their to do whatever they want with, that they have all rights reserved & anything not announced is 100% caveat emptor, good luck, is a really really shitty & corporate-egoistic way of dealing with the world. There should be a greater than 0 try here, to make things make sense.
"Mess everything up" is not a real state, it can always be fixed. However it might be faster, if you're using source control and short on time, to simply delete the folder(s), then re-clone and reinstall.

Beginner-friendly is to avoid all this complexity in the first place. I think it's a mistake to mention venvs to newbies until they are comfortable with python, paths, links, and environment vars.
Baikonur seized. End of Russian space age looming
> but website stats is one of the biggest losses in modern web dev

That seems a bit overly dramatic. If you look at your log files these days you'll see that a high percentage of it is just scrapers, bots, scripts trying to access wp-admin etc.

Collecting this information somewhere else (instrumented backend, client-side script) makes a lot more sense now where you can filter out noise more easily. There's also very light client-side scripts like https://plausible.io which are a nice trade-off between privacy and useful information while not being too heavy.
Thanks for your perspective. What do you think is needed to move the needle on heat pump adoption/ make them a more compelling product?
1. There may have been a sale without restrictions on purpose or usage of the data attached.

2. There may have been a sale to a third party, from which the group bought the data.

3. The group may have used a shell entity to buy the data.
Why bother with pingig? Write answer, text-to-speech it and fake-voice it so it sounds like you.

Don't forget to wrap it with supervisor AI so you can replicate minions 100x+ times.
Yes and indeed organisms (and further down a level, cells) themselves are merely a substrate that allows genes to replicate.
But doesn't that imply that the company also can't trademark the name for themselves? Being able to protect your own name seems important.
I’m sorry but if you think someone won’t harm you only because you have dirt on them, then neither of you really trust each other. Trust means you are confident that other person will not harm you regardless of what you have.
That's the paper I referenced. But newer research is already challenging it.

'Int-4 llama is not enough [0] - Int-3 and beyond' suggests 3-bit is best for models larger than ~10B parameters when combining binning and GPTQ.

[0] https://nolanoorg.substack.com/p/int-4-llama-is-not-enough-i...
Not sure why repeatable deployments would be a problem. You can pin all dependencies by issuing a

pip freeze > requirements.txt

if you want. The only catch is you should be using a similar architecture and Python version in both development and production.

This would also pin a few non-project dependencies such as `disttools` but that shouldn't be a problem.

Edit: TIL that pip constraints is a thing. See the comment posted by oblvious-earth for an even better approach.
Not a dumb question, you've hit on one of the best features of these systems. They act as a heater in the winter and as AC in the summer. Same system.
What is the context? What suit do you have in mind?
Ask HN: Have you heard of a private equity firm focused on cutting cloud costs?
Every once in a while I see posts discussing how ridiculously overpriced cloud providers are (e.g. the recent "How Ahrefs Saved US$400M in 3 Years by NOT Going to the Cloud" https://tech.ahrefs.com/how-ahrefs-saved-us-400m-in-3-years-by-not-going-to-the-cloud-8939dd930af8)

As someone who works with AWS/Azure/GCP a lot I've always found these articles to be mostly overblown PR-seeking pieces, but self-hosting IS much cheaper for many applications if you have the right team to manage your servers.

Has anyone here ever encountered a private equity firm that focuses on acquiring sizable cloud-hosted software companies and converting them to run on self-hosted colo servers in order to radically improve profit margins?

It seems like a difficult act to pull off, but if any of these "we're saving SO MUCH MONEY self-hosting" people can actually run insanely cheap servers with similar robustness/security levels as the major cloud providers then it's a massive business opportunity for such a team.

Anyone capitalizing on this?
My complaints stem from libraries/OSes requiring different tools. So conda is sometimes required, and pip is also sometimes required, and some provide documentation only for pipenv rather than venv. And then you've got Jupyter, which needs to be configured for each environment.

On top of that there are some large libraries that need to only be installed once per system because they're large, which you can do but does mess with dependency resolution, and god help you if you have multiple shadowing versions of the same library installed.

I wish it was simpler. I agree the underlying system is solid, but the fact that it doesn't solve some issues means we have multiple standards layered on top, which is itself a problem.

And great if you've been using vanilla venvs. Good for those that can. If I want hardware support for Apple's hardware I need to use fucking conda. Heaven help me if I want to combine that in a project with something that only uses pip.
apple product will only work if the headset is not a headset and instead is something that replaces the simple casual glasses

anything else will be an industrial flop for apple
No, SV has always been Gomorrah, vs. SF's Sodom.

California is a vast cesspool.
Only C++20 has concepts, which is a lot newer than Rust is. I've yet to ever see a C++20 concept in the wild or anyone using one outside of an example.

Heck, if you ask the average C++ programmer about concepts they'll likely have not even heard of them.
I read the article but missed what exactly the skill based input is - just the timing on holding the automatic launcher on or off?
> why are only gay priests outed in this way

you know why.
> being homosexual automatically makes you a "leftist"?

god if only that were true
Long past the beginning stages. Closer to the end than the beginning.

The world and his dog have been expecting this for at least twenty years, if not thirty.

The US was "lucky" (/s) to have the World's Reserve Currency in the late 1980s.
Cynical and interesting commentary from academics in the comments of this blog post: http://nanoscale.blogspot.com/2023/03/aps-march-meeting-day-...