skysight-inc/HackerNews huggingface dataset:
Many churches are legally classified as non-profits-which is a broader category than charities-the local bridge club is likely to be a non-profit but not a charity. It depends on the country, but in many countries the majority of the tax exemptions religions get are just the general exemptions to which all non-profits are entitled. To deny those non-profit tax exemptions to a church, while allowing them to the local bridge club, would be a form of state discrimination against religion, which (in many countries) would be unconstitutional, and may even violate international human rights law
A lot of what Erlang/Elixir offer have been cribbed by cloud architecture, so in terms of direct comparisons you may find that a sufficiently well-architected microservices system has similar properties and will make Erlang/Elixir less desirable.

But Erlang/Elixir can probably accomplish many of those properties at a fraction of the cost.

The core advantages of these languages are (a) a runtime which is highly optimized for running a large set of preemptable concurrent tasks with very minimal shared memory and (b) an ecosystem designed around building fault-tolerant applications out of many independent communicating processes that "supervise" one another to detect failures and gracefully heal them.

There are many details about how those things work, but I'll reiterate: together they offer a system with many robustness properties similar to that of an idealized large microservices architecture but with much less complexity and cost.
Gitlab code suggestions for all during beta
Heads up for those into AI/ML and programming: Code Suggestions available to all GitLab tiers while in Beta
See my take on this here: https://www.readcodon.com/p/extinction

Basically, it will be quite challenging and I think they are over-promising on the timeline. They are also not even going to make a wooly mammoth, but rather a hairy elephant.
> Its convenient if you can stay below ~100 nodes.

There's not much of a node limit. When I was at WhatsApp (through 2019) we ran thousands of nodes in some of our dist clusters. Unmodified pg2 was challenging at that scale (and modified pg2 was still sometimes challenging), but the new pg module doesn't rely on global:set_lock (or any form of global locking), and eliminates that scaling hurdle. Mnesia would likely get unmanagable with many nodes in a shared schema, but I'm not really sure why one would want to have that many nodes in a shared schema (with persistent nodes, we'd usually run 4 nodes in a mnesia schema cluster, with ocassional additional nodes added to facilitate resplitting data across more schema clusters. with ephemeral nodes, I believe it was typically 6 nodes).

I was always confused when other groups suggested a node limit like 100 nodes. I just don't know where it comes from, and it doesn't match my experience. Hard limits come from the atom table and port limits, both of which are pretty easy to expand. Certainly if we could manage on the order of millions of connections to clients (that specific number dropped over time as the server did more work per connection and then when switching to the smaller node types that were the path of least resistance in FB hosting), a couple thousand for dist wasn't going to impinge on port limits.
I'm giving a KDE a go as I finally convinced the wifey (non-technical human) to use "the Linux" daily. I haven't used KDE myself for past decade so should be fun.
The Annexes ( https://artificialintelligenceact.eu/annexes/ ) contain a definition of "High risks AI systems" at Annex III.

--

Incidentally, for the many who claimed on these pages that we would not "have a definition of AI" (actually we have several), well, this legislative text provides one:

software with the ability, for a given set of human-defined objectives, to generate outputs such as content, predictions, recommendations, or decisions which influence the environment with which the system interacts, employing techniques including (a) Machine learning approaches, including supervised, unsupervised and reinforcement learning, using a wide variety of methods including deep learning; (b) Logic- and knowledge-based approaches, including knowledge representation, inductive (logic) programming, knowledge bases, inference and deductive engines, (symbolic) reasoning and expert systems; (c) Statistical approaches, Bayesian estimation, search and optimization methods
Obligatory reminder: the goal of mass-surveillance is never to prevent terrorist acts or protect the children from predators. It is to have a dossier on everyone.
Yeah, I notice many/most images are based on a recent Debian base if they aren't on Alpine or closer to bare images. I don't consider even Alpine as a base too bad for a lot of apps.
Britain goes further than many countries: once you've stopped, you aren't allowed to start again until the whole crossing is clear of pedestrians.
Like this? https://github.com/jamesroutley/news.routley.io
Yes, it's an idea, but in the 1980s when arcade games were common, many "normal" bars had video games and pinball machines in them. These days they seem absent except in those dedicated barcades.
Is there a good tiled window manager for KDE such as Pop Shell for Gnome? That's the only thing keeping me back on gnome.
The first 20 versions I write usually do. Make that 50.
Bot answer
> never got close to the car

Yes, because the pedestrian slowed down when it saw the Tesla was not giving them right of way (as the Tesla is required to in the state of california).

> In my state that's perfectly legal.

In most states its illegal to force a vehicle or pedestrian or whatever that has right of way to slow to a near stop to avoid a collision with you that you could have easily stopped and avoided. I don't know of a state where a pedestrian in a crosswalk would not have right of way in this situation.

Now, there are many states where a pedestrian in a crosswalk doesn't have like right of way over everything (though, technically, not california), but for the most part this applies to vehicles that could cross the crosswalk without affecting the pedestrian.
> seems like a power grab to me

If you're not at the table, you're on the menu.
Red Hat and SUSE (Maybe not anymore?) pay for a lot of the developer time.
Soros is a holocaust survivor, everything he does that you label as leftist is to avoid a repetition of that horror.
Musk has shown his true colors many times before, this is just more of the same and confirming how despicable a person he is.
There's probably other cases of people like me deleting our videos to avoid Google trying to monetize things I don't want ads on.
Yeah, when I became a deacon I started reading the bible way more, with the thought that I could provide helpful/supportive quotes to people like some others can. I really don't understand how anyone can read it and not become skeptical.
I would start without AI first. We do pretty well without it already and there will be complications if you start adding in the AI hype.

The first question should be, what are your goals in analyzing logs? Then, what existing tools are there that are already addressing this?

Only if you find a problem, should you seek out new solutions, and then AI is just one of the tools you might try, but you should tread carefully, as AI is slow and expensive.
These new drugs, or something else? https://www.science.org/content/blog-post/are-anti-amyloid-a...
"This comment" is referring to lbatross13, not to you. I'm uninterested in talking to lbatross13; I was adding context for other readers.
I've been using default GNOME for ages and I'm happy with it. I use the keyboard very heavily so I've never been bothered with the window controls. Saying KDE has too much customization is putting it mildly, the thing feels like an Airbus cockpit. There's unironically half a dozen menus to change themes alone. Like Windows it feels like you're on three versions of the system at the same time ranging 15 years back.

Say what you want about ripping stuff out but GNOME has what I also appreciate about macs, it has a coherent design language.
Gnome is the default desktop of Red Hat, whose target audience is definitely business. There hopefully are some breakdowns somewhere of where they get funding from. But I expect Red Hat gives them a bunch of money.

Whether their income is "vast" or not, my statement was specifically about the relative proportions of where it comes from. I definitely expect them to have an overall fairly mild budget. But where it comes from, I think, has largely shaped their current strategy, which is to target extreme end users with little customizability.
Capitalism collects profits and wealth in the hands of a minority who use that power to capture the Government and ensure that they don't have to face serious competition that would put their future profits at risk and to only regulate them such that the regulatory barrier to entry is a net benefit to their businesses.

Your idea of how Capitalism should work isn't a stable political equilibrium and can't exist.
What about this one?

https://news.ycombinator.com/item?id=35957726
I thing that mammoth is a really poor choice for de-extinction. I would wish to be wrong, but is not a really well matured plan.
"Systems that run forever self-heal and scale" by Joe Armstrong (2013) [0] is a great talk too.

[0] https://youtu.be/cNICGEwmXLU
It doesn't HAVE to be that bulky or complex. You have a lighter space like Dokku or just direct scripted deployments pretty easily. As to the size, you can use debian-slim or alpine as a base for smaller options. There's also bare containers, or close to bare for some languages and platforms as well (go in particular).
It would be helpful to see how Bun's minifier compares to the others with popular libraries:

https://github.com/privatenumber/minification-benchmarks
With collisions and perhaps a few other things, couldn't it be used in a game to design machines? Seems fun.
Well, fingers crossed about the Parkinson's, then!
It is possible if you design the corporate structure right to prevent that. See my other comment about the Scott Trust - https://news.ycombinator.com/item?id=35967694
European AI Act: a step closer to the first rules on Artificial Intelligence
Nope. It refers to what ever people want it to refer to, because it's a label used by detractors, not a cohesive thing.
It's interesting how all it takes for something sometimes to boom is to just make it available at a venue with food and alcohol. People mentioned barcades. This also goes for things like throwing axes at a plywood board. Swinging a golf club for people who have good odds of sendign the club farther than the ball. Throwing a duckpin bowling ball like its 1905 again. Shuffleboard is a thing among millenials now, sleepy old person shuffleboard! All because you can get a nice IPA with friends over it or some food. It's too bad a lot of cities are so hard up with liquor licensing or even make a racket out of granting the licenses. Stuff like this should be easy.
This would be awesome. Use bun as the main process (replacing node) and have the front end use the system webview. The system webviews are good these days.
Photomator for Mac
Check out terminusdb. Has most/many of the same features and is open source.
His last thing is "WorldCoin" which, before pretty much completely failing did manage to scan the irises of 20% of the world's low income people which they definitely were all properly informed about.

He's a charlatan, which makes sense he gets most of his money from Thiel and Musk. Why do so many supposedly smart people worship psychotic idiots?
Should You Mask 15% in Masked Language Modeling?
Mmmm. That's the case with programs, but it's definitely not the case with neural nets. Much like you or I, NNs do things based on training, experience, and data.
> It's actually extra flexibility meant for two things: being able to override the getter/setter in a subclass, and keeping a consistent interface so users don't need to change how it's called if there was a refactor that adds something to the getter/setter

This always strikes me as any-benefit mentality thinking. I agree there is some small marginal benefit to this pattern, but the cost (in time, decreased readability and lines of code) is massive. The benefit of being able to change your getters and setters later in a public interface almost never actually shows up.

Most getters and setters aren’t even part of a public interface anyway - because either they’re private or they’re in application code. In both of these cases, you can delay replacing a public class field with public getters and setters until you actually need to. When it actually provides value, it’ll take all of 5 minutes to do the refactor. Intellij can probably do it instantly. And, Spoilers: this will almost never come up in practice. Public fields are almost always fine.
A native compiler also optimises the code. A native static linker also tries to omit unused library data and code. It's absolutely not the case that native devs don't care about code size (we do!)

I guess Javascript uses a slightly unusual executable format, text instead of binary. Otherwise, it seems like very much the same thing?
I actually have mixed feelings on this one... since I think Deno's approach has been generally cleaner, but also recognize the scale of what's in NPM.
I’m not aware of another systems language that pulls off nine nines of reliability. Having been paid to write Java, C#, and Elixir systems, I’ve found the BEAM to provide vastly better fault tolerance. My current project has requirements for zero downtime and zero data loss, actively replicates across 4 data centers across the US and handles the real-time medical data millions of hospital patients.
JSC is a multi-tier JIT with the last stage ultimately being LLVM, so if you want to be pedantic, Bun relies on LLVM’s optimizer which is written in C++.

The transpiling itself is written in Zig, which is the part that has the performance improvement. If Bun relied on JavaScript and JSC for the heavy lifting, it would be no faster than the other JS bundlers.

edit: no longer LLVM: https://webkit.org/blog/5852/introducing-the-b3-jit-compiler...
The cultural river is turbulent and swift.
super bonkers!
Anybody who is extremely on Twitter (Musk) or interested in American politics (Musk) can't help but be aware that invoking Soros is an anti-Semitic trope going back decades.
I need to make a montage of the thousands of hacker news commenters typing "The REAL danger of AI is ..." followed by some mundane issue.

I'm sorry to pick on you, but do people not get that the non-human intelligence has the potential to be such a powerful and dangerous thing that, yes, it is the real danger? If you think it's not going to be powerful, or not dangerous, please say why! Not that current models are not dangerous, but why the trend is toward something other than machine intelligence that can reason about the world better than humans can. Why is this trend of machines getting smarter and smarter going to suddenly stop?

Or if you agree that these machines are going to get smarter than us, how are we going to control them?
> They are in the unique position to enable local AI tools

Nothing special about Apple with regards to AI. M2 beats x86 in power efficiency, but not significantly better than other ARM processors.
Ask HN: Do you find GitHub less stable in the past 4 months?
OpenAI doens't want to be one of Windows/Mac/Linux, it wants what Microsoft was trying 20 years ago where it wants to strangle all OS not named Windows. Ironically OpenAI is now half owned by Microsoft.

It doesn't want to be one of the successful companies, it want to be the only one, like it is now, but forever.
I'm happy to answer questions that folks have around this product.
I understand the risks of inactive accounts, but as I have pointed out here before these binary policies do not address the all-too-common situation where someone is forgetful and/or incapacitated prior to their death. These people have more important things to think about than their email and their photos,and the transition from alive to dead (to be blunt) can easily take more than two years. By the time that the estate and the executor has control of the account it can easily be too late to save precious memories.
> Nah, rust still depends on libc at runtime which is a pain.

It does in general, though I don't really think this is a big pain or blocker in the general case, there are very version requirements around libc.

> Go doesn't have this problem afaik as it has its own stdlib and runtime.

That's also true, but it's not really a pure win. Choosing not to use a battletested libc has led to a variety of subtle and difficult to diagnose bugs over the years, e.g. https://marcan.st/2017/12/debugging-an-evil-go-runtime-bug/
I think the aspect you're missing is Erlang's total focus on 'green threads' (erlang processes - or just process) as the basic unit of computation. Just like Unix's "everything is a file" philosophy it's a mundane description that had wide-ranging benefits for building long-running services.

First, in the most basic situation, the VM will manage all of your parallelism. It will figure out how many physical CPUs and how much memory it has to work with and will maximize those resources. It will dynamically limit the resources consumed by a particular process such that it will remain responsive. Because erlang doesn't allow modifying values and uses message passing, memory corruption is extremely rare. This has pretty heavy performance and efficiency costs, but what you gain is extremely high flexibility in terms of scale.

To a first approximation, Erlang actually cares very little about how many machines an Erlang program is running. Once you embrace processes as the basic unit - which machine is running a process, as long as all machines can pass messages, matters very little. Also, again, all the VMs know what resources they have and can re-balance processes to best utilize those resources across many nodes. All without special configuration[1]. The very brave can even live-swap the code running inside a VM - existing processes spawned on the new code will execute and close as normal (no time limits, the VM has the old code still), while you swap your network interfaces over to your new code.

The process-centric design has other nice implications. Test can be run fully in parallel[2], which keeps a low-efficiency-per-thread VM very snappy in practice. Each process can fail fully interdependently as well, which means that cascading failures are quite rare. There are still lots of reasons not to live-console into production, but in a language that doesn't allow you to change memory values and also gives your shell full isolation, it's a lot more practical than in other languages.

It's worth saying that none of this is "magic" or from a special quirk of the language - any language that totally committed to message passing and allowing the VM to manage greenlet processes would get the same benefits. IMO these tradeoffs are very worthwhile for the kinds of things Erlang / Elixir specialize in (long running network-connected services) and I would encourage anyone who's been using Python for these kinds of things to consider this platform as an alternative.

[1] This is over-stating it quite a bit - you do need to care about multi-node issues and you do want to configure things if you're getting into weird resource bottlenecks...but it also will "just work" a lot of the time. Generally you should twiddle setting if you expect a weird workload in the cluster generally and if you have an occasional spike it will "mostly work."

[2] This isn't totally true in practice, you often have resources outside Erlang (databases, etc) that need to be shared between a large number of processes which limits parallelism.
> Add to that the fact that you're posting on a largely American forum where access to healthcare is largely predicated on insurance

Why do so many Americans think universal health care means there is no private insurance? In most countries, insurance is compulsory and tightly regulated. Some like the Netherlands and France have public insurance offered by the government. In other places like Germany, your options are all private, but underprivileged people have access to government subsidies for insurance (Americans do too, to be fair). Get sick in one of these places as an American, you will be handed a bill and it will still make your head spin. Most places in Europe work like this. Of course, even in places with nationalized healthcare like the UK, non-residents would still have to pay. What makes Germany and NL and most other European countries different from that system is if you're a resident without an insurance policy, you will also have to pay a hefty fine. You are basically auto-enrolled in an invisible "NHS" insurance system as a UK resident. Of course, most who can afford it in the UK still pay for private insurance. The public stuff blends being not quite good with generally poor availability.

Americans are actually pretty close to Germany with their healthcare. What makes the US system shitty can be boiled down to two main factors:

- Healthcare networks (and state incorporation laws) making insurance basically useless outside of a small collection of doctors and hospitals, and especially your state

- Very little regulation on insurance companies, pharmaceutical companies or healthcare providers in price-setting

The latter is especially bad. My experience with American health insurance has been that I pay more for much less. $300/month premiums and still even seeing a bill is outrageous. AI underwriters won't fix this, yeah, but they aren't going to make it any worse because the problem is in the legislative system.

> There's no court of appeal for insurance.

No, but you can of course always sue your insurance company for breach of contract if they're wrongfully withholding payment. AI doesn't change this, but AI can make this a viable option for small people by acting as a lawyer. Well, in an ideal world anyways. The bar association cartels have been very quick to raise their hackles and hiss at the prospect of AI lawyers. Not that they'll do anything to stop AI from replacing most duties of a paralegal of course. Can't have the average person wielding the power of virtually free, world class legal services.
Fair enough, but better than a human is supposed to be the point of all this. Who needs self driving cars if they're going to be mowing people down while they check their Instagram?
A strict interpretation by your car may mean that it yields to a person standing just off the curb is in the crosswalk with no intention of crossing. Your car won't go though because the law says they have the right of way.
Ah there's a fairly common perception game played at fairs in my home region: guess the height of the hanging ham.

A ham (technical, a prosciutto) is hanged on a rope and people have to guess how far it is from the ground.

The winner takes it home, of course.
I can totally vouch for the "the developers care, answer questions, and actually accept PRs" aspect. I had some time last summer and decided to spend it on Kate (KDE advanced text editor) and the experience was great! I had never approached KDE or Qt development before, and never even done actual C++ development (just some small course exercises). The devs were great at coaching on their IRC channel and in the GitLab issues.

The maintainer even made a blogspot at some point to explain my contributions: https://kate-editor.org/post/2022/2022-08-24-kate-new-featur...

Globally KDE is a fantastic experience, whether from a user's or a developer's perspective.
Is there a similar list of more generic or common mechanics? I've always been curious if a list that contained things like "tiles-based", "roguelike", "rhythm game" would yield interesting results if combined randomly.
It costs a lot of money to train foundation models, that is a big hurdle to open source models which can strangle further development.

Open source AI needs people with low stakes (Meta AI) who continue to open source foundation models for the community to tinker with