skysight-inc/HackerNews huggingface dataset:
> Can you give a historic example of a human creating "truly novel ideas" that is not the product of mixing and matching existing ideas?

The invention of PCR comes to mind:

> During a symposium held for centenarian Albert Hofmann, Hofmann said Mullis had told him that LSD had "helped him develop the polymerase chain reaction that helps amplify specific DNA sequences".

https://en.m.wikipedia.org/wiki/Kary_Mullis
> ECS library that will do it in AoS way

TLAs aren't my forte. It's SoA of course.
I like Zed and appreciate that I can bring my own keys for the AI features. The only thing I don't like is that inline auto-completion seems to be strictly tied to GitHub copilot. Even if you supply Anthropic / OpenAI keys, that only supports the context and assistant features.
Isn't it the a distinction without a difference ? Apple isn't providing your real eye movements, but an 1 to 1 reproduction of what it tracks as your eye movements.

The exploit requires analysing the avatar's eyes, but as they're not the natural movements but replicated ones, there should be a lot less noise. And of course as you need to intentionally focus on specific UI targets, these movements are even less natural and fuzzy than if you were looking at your keyboard while typing.
SBT is awful. I've never used Gradle, but if SBT is saner then I'm worried. This blogpost is a bit old, but still on-target: https://www.lihaoyi.com/post/SowhatswrongwithSBT.html
https://archive.ph/HSp7S
"Wow you're really offended. Of course I was lying"
Look up the Sequre S99 soldering iron. Basically what you are looking for.
“Trust is built in drops and lost in buckets.”
Do you think you're like Apple: not allowing people to fix their phones, laptops ...?
Replace an o with a u
It isn't. However, there was no release note, it changed late in the beta cycle, and there's no plan to revert.

As of right now, if this isn't adjusted to solve going forward rather than disrupting current applications, I don't have the confidence to upgrade to iOS 18 in a way that I have been confident of earlier releases.
Sunk-tax fallacy.
The main difference from my point of view is the EWMA produces a measurement of the rate, whereas token bucket only produces the result of a comparison with the limit. If you don’t need the actual value of the rate then you can save a lot of time and space by using GCRA instead https://dotat.at/@/2024-08-30-gcra.html
It isn't the first questionable move, and it really shook a lot of people. Flipping back again a year later is the right move, but it doesn't instill confidence. It merely ceases the erosion of it.

Firing the CEO did help, though.
This is interesting, but what isn't mentioned is how long these devices can hold coherence (see https://en.wikipedia.org/wiki/Charge_qubit and https://en.wikipedia.org/wiki/Quantum_decoherence)

All existing QC approaches have two fundamental limitations: error rate and coherence time. You can decrease error rate through error correction, but that comes at the cost of adding gates and/or storage to replicate the QC state, but that causes a decrease in coherence time. I have not seen even a theoretical framework allowing both to be increased simultaneously.
And their last words were "Finally, we get to upgrade unity from this ancient version!"
Hacker Claims Data Breach on French IT Services Giant Capgemini
It sounds like cunty (adjective) or cuntie (diminutive). https://www.youtube.com/watch?v=Obagb7RQeYo
Atlas founder here. Happy to answer any questions people have about the tool!
Electronics run on magic smoke. Once you let the smoke out, they no longer work.
So in your hypothetical language with union types `X | Null -> Y` is a function that can actually return `Y | Null`? Why would you want to allow that as an implicit behavior? This would make for surprising and unclear error handling requirements.

One of the main points of encoding error information in the type system in the type system is that it forces you to account for it when you modify your code.

By "weakening" your assumptions on your function to allow it to produce Null values you have introduced a new requirement at all your call sites. Everywhere that you call this function now needs to handle the Null value. Its a GOOD thing that Haskell forces you to handle this via the type system.
Why buy this for $250 when you get the same thing from a pinecil v2 and use it with any 20v 100w PD USB-c power pack? I'm not seeing any differentiating features.
This is super exciting!

I've written before about how I think the more FBP-style concurrency of Go and the message passing one in Erlang complement each other as much as streaming DNA processing inside the cell and fire and forget cell to cell signaling between cells do in biology:

https://livesys.se/posts/flowbased-vs-erlang-message-passing...

The FBP/CSP-style in Go being more suited for high performance streaming operations inside apps and compute nodes (or cells), while the message passing mechanism shines over more unreliable channels such as over the network (or between cells).

Ergo seems like it might allow both of these mechanisms to be implemented in the same language, which should be a big deal.
251 words you can spell with a calculator
Before the invention of lead-free solder you would hear heavy metal.
Personal: More than a decade ago, I got my first job abroad. I moved, started the job, and it stank. I never quit that fast. But I was in a foreign country, with no job, not a lot of money, and didn't even speak the local language.

Anyway, in the next weeks (which became months...) started to apply to all kinds of jobs, I'm sure more than a 100. I haven't even received a single screening call. I was depressed like hell, and running out of my meager savings too.

Suddenly I got an email: "We wanted to reach you to invite you for an interview, but the phone number in your CV is incorrect". First I though that they don't know how to use the phone, or something, until I checked the CV I was sending everywhere - my phone number was indeed wrong. I facepalmed so hard, and was ashamed of myself so much, it's unbelievable. Now I just laugh hysterically whenever it comes to my mind.
society often over powers good ideas.. if the zeitgeist is about kube, companies will accept its cost not really knowing the lost benefits anyway..

I guess we'll have to wait to reinstate these features later on
https://www.audubon.org/news/how-birds-survived-asteroid-imp...

... though it doesn't get into the air quality directly.
Thanks for asking :)

The original essay was pretty long, so I'm releasing it in chapters here:

[0] https://taylor.town/oh

Chapter 1: "Proplifting, Plant Piracy, and Dumpster Chocolates"

[1] https://taylor.town/oh-theft
If we're talking wide-open unregulated markets, that's pretty obvious. It just comes from experience.

https://en.wikipedia.org/wiki/Triangle_Shirtwaist_Factory_fi...

https://en.wikipedia.org/wiki/Bhopal_disaster

https://www.theguardian.com/environment/2011/jan/06/bp-oil-s...

etc etc
Show HN: I made a free resume card generator
The ideal situation for this sort of code is to basically treat it as marshalling code, which is often ugly by its nature, and have the "payload" processing be significantly larger than this, so it gets lost as just a bit of "cost of doing business" but is not the bulk of the code base.

Writing safe NIFs has a certain intrinsic amount of complication. Farming off some intensive work to what is actually a Go node (or any other kind of node, this isn't specific to Go) is somewhat safer, and while there is the caveat of getting the data into your non-BEAM process up front, once the data is there you're quite free.

Then again, I think the better answer is just to make some sort of normal server call rather than trying to wrap the service code into the BEAM cluster. There's not actually a lot of compelling reasons to be "in" the cluster like that. If anything it's the wrong direction, you want to reduce your dependency on the BEAM cluster as your message bus.

(Non-BEAM nodes have no need to copy using tail recursion to process the next state. That's a detail of BEAM, not an absolute requirement. Pattern matching out of the mailbox is a requirement... a degenerate network service that is pure request/response might be able to coincidentally ignore it but it would be necessary in general.)
But it's just a soldering iron and a weird usb c power bank. Of course one can spend 300$ on it and justify it, but is this actually better than the alternatives?

The ts100 and variants of it have been around for a long time, can be adjusted on device and powered by regular usb pd power banks.
Cutting with a lubricant and grit is super effective. Silicon dioxide, that is sand, is everywhere.
IronSource & WETA acquisitions may have been expensive mistakes
I hear the term “magic smoke” (or “magic blue smoke”) mainly from people who are messing around with electricity and who put it through an electronic component in volumes or directions that burn the component out.

The resultant puff of smoke brings the component’s behavior from the logical world to the physical one—tangible evidence of an unfortunate finality-of-outcome, an intricate IC become just a lump of charred sand again.

Likewise Unity could have done a whole lot of things with their licensing framework while users still had trust in their behavior. But now that they’ve blown out the figurative trust “chip,” they’re gonna have to find a way to get a new one before they get much out of tinkering further with their licensing circuit.
How Telegram Became a Playground for Criminals, Extremists and Terrorists
It doesn't work like that. This is a business, not a family member or old buddy. Their move last year underscored the immense risk that business have when dealing with them. Your game is a single CEO change away from bankruptcy when you give them so much power.
Then stick to commenting on posts about such software instead of trying to mislead people about software you know nothing about.
On the flip side wouldn't that make replacement tips much more expensive? On my old Hakko station I've replaced the tips several times but the element and sensor seems to be going strong.
Bionicle – my actual part in its origins (2015)
Most significantly: goroutines are not addressable. This means that, from application code, you cannot send messages directly to a goroutine [1], you cannot link two goroutines, you cannot terminate a goroutine from another goroutine, you cannot directly watch a goroutine's exit [2], and there's nothing akin to the process dictionary (there are no "goroutine-local variables").

[1]: you usually use channels instead

[2]: you usually use sync.WaitGroup (or similar, e.g. errgroup.Group) instead
Branching Paths – Japanese Indie Games Documentary [video]
Mastercard acquires Recorded Future for $2.65B
TLDR: When electronics burn out, they often release "magic smoke" that is believed to be the source of their power (since they almost always fail to work afterwards).

https://en.wikipedia.org/wiki/Magic_smoke
> but Android has been an annoying gap

If I were to guess - the issue is that many phone basebands appear (at least) as a serial device, and we all know from late 90s/early 00s dialer scams how bad that can go if some hardware manufacturer forgets to label the serial port in a way that can be detected as "never fucking ever expose this to apps"...
This is a very strange way to think. You could apply it to anything that could not exist in the past that people happily pay for today. "Medical care was much more affordable in middle ages!"
I do have a TS100 which I use either with a battery pack or a wall charger.
For storing it, I am using a metal casing that is used for a single cigar. There's also room for a tiny metal cleaning brush which protects the tip during storage. Given that all of this is metal and that the soldering iron doesn't have that much thermal capacity, I can pack it up while the tip is still hot and the casing will only get mildly warm, but not to the point where it'd cause damage.
https://www.nytimes.com/2024/09/07/technology/telegram-crime...
I think every major idea was truly novel at some point. Even an idea like "I will write down the things that happened, so when I am dead, other will know what has happened from my writings" was novel at some point.

Which means that an LLM can probably technically come up with novel ideas, since novel ideas aren't some special category of things, it's just that LLMs are not very good at it.
Nope, that's just currying and/or partial application.
A different kind of durability than what people mean by "durable workflows", though. Durable workflows require durable storage of their current state; supervisors give you durable computation services. Supervisors don't even guarantee "durable computation"; if a process crashes halfway through processing a request, it's not like the request will be automatically retried or something. (That isn't even a good idea, there's a very good chance the reason why that request crashed one process will crash others.)
How are they getting the data you claim is shared with them?
Thanks! It cost more but I think the outcome was worth it.

We really pushed the envelope on every aspect of the hardware to max out the joules we could push into the material. The trick is being really responsive to the load so that you don't overshoot the target temperature too much.

With the Power Station plugged into the wall and a full charge on the batteries, you can get about 104 Watts into the iron.
That seems less like an argument against public officials having enhanced scrutiny, and more an argument why they should have no scrutiny at all — because that’s the only defense against such a fanciful attack. That’s the logic that brought us the abomination of qualified immunity.
September 12, 2024 at 12:41 p.m. EDT: NYPD commissioner resigns amid federal corruption probe - https://wapo.st/3TrnijL
dunno. my first ever soldering project was a handwired keyboard. i was popcorning when i finished. it was my first time using a mechanical switch keyboard too. not bad... 2° project, right after finishing the keyboard was soldering a PMW3360 sensor to someone's board from Github. it was a freaking blast on my 40W, 40 BRL (~ 8 USD) solder

i still have it & i'm selling handwired keyboards at a very cheap price (made with it), trying to set a non-profit that sells fair priced handwired keyboards with Vial & aims to teach the basics of electronics for teens... i can't see myself supplying anything more expensive than cheap solders, nor i can see what joy i would get from an expensive solder tool

my wiring for reference -> https://happort.org/keyboard_example.png
Urban heat and within-city residential sorting
> No-one knows if Hitler bumped into Trotsky, or Tito met Stalin. But works like Dr Freud Will See You Now, Mr Hitler - a 2007 radio play by Laurence Marks and Maurice Gran - are lively imaginings of such encounters.

Now I want to check this out!
I would say it’s entirely irrelevant to being nice. Unity demanding that every garbage tier game flaunt that it was made with Unity seemed like it was a net negative for unity itself.
That is a minor thing that really annoys me. Modern games all look like NASCAR when they start.
Back in the 80's a friend of mine had a system for launching model rockets built out of power cords - a extension cord with multiple outlets for distribution, and power cords with microclips on one end to hook to the rockets. And of course he had to find out "what happens if I plug this in". (If I remember right the microclips were fused together, but they may have just melted, it's been a while.)
Google depends on it for firmware updates and repairs on the Pixel lineup.
https://pixelrepair.withgoogle.com
I was just stating what the difference is to a closed market environment like Second Life. Whether it's good or bad is another matter. In my view experimentation is good. I would assume that nobody can control your in-game assets arbitrarily unless you grant them permission via some contract.
Reminds me of the old subtlepatterns dot com
Because the final product will require tons of details to have been thought through, which can quickly become bike-shedding derailments. How many times have you had to say “this is just example styling—we can tweak it later”? The hand drawn sketch conveys that implicitly.
I do think that only having one CVE in six years is a pretty decent record, especially since that vulnerability probably didn't grant arbitrary code execution in practice.

Rust is an important part of how Firecracker pulls this off, but it's not the only part. Another important part is that it's a much smaller codebase than QEMU, so there are fewer places for bugs to hide. (This, in turn, is possible in part because Firecracker deliberately doesn't implement any features that aren't necessary for its core use case of server-side workload isolation, whereas QEMU aims to be usable for anything that you might want to use a VM for.)
This is excellent advice that unfortunately seems to get lost in a lot of Haskell teachings. I learned Haskell in school but until I had to use it professionally I would have never been able to wrap my head around effect systems. I still think that part of Haskell is unfortunate as it can get in the way of getting things done if you're not an expert, but being able to separate pure functions from effectful ones is a massive advantage.
Looks neat. I might have thought web features were cool ten years ago but no longer want any more devices with wifi and possibility of telemetry in my house. Not to mention having to bring up a browser to configure instead of pushing a physical button. No desire for limited Tesla-like design.

Is that the case, or did I misunderstand?
What does he have to do with the current discussion?
Unless you're in life support or some other critical engineering path, always start by aiming for good enough, not best.

If you're moving quickly, some of your decisions will be wrong, but that's ok. By the time it comes to revisit a decision, you will have more information and be able to make a better decision. Don't regret making the wrong decision, consider it a prototype. It's nice if you don't make a lot of wrong decisions, but if you're not making any wrong decisions, you're probably spending too much time deciding.

You're balancing the cost of making a more informed decision vs the (cost of changing your decision later, including potential cleanup costs * the probability of having decided wrong).

If you're working in a team, having consensus towards using the decision is more important than having the right decision or even having consensus about it being the right decision. With the right team, you can say something like 'I know everybody doesn't like this decision, but let's work together on it for the next 2 weeks and we'll change it if we need to.' That's usually better than trying to find consensus on a decision for the next 2 weeks. If nothing else, your team will have 2 weeks of experience with using the decision to inform a future discussion... and in the meantime, it might be good enough and you can work on something else.
It looks interesting. I know some people will start comparing it to workstation ones, but I personally always look for portability. A few times I would be in the field with my drones and I need something small, battery-powered, and good enough for a quick job. So maybe people with similar use cases will find it useful. The only thing that I would say would have been good to have is a phone app and connection over Bluetooth to adjust the settings.
Incidentally, there is a variant of the canonical Bell experiment called the Greenberger-Horne-Zeilinger (GHZ) experiment that doesn't require multiple trials to collect statistics. The GHZ experiment uses three photons in an entangled state rather than two and can produce a result that is incompatible with classical mechanics in just a single observation.

https://en.wikipedia.org/wiki/GHZ_experiment
Strongly agree.

Back in high school, I put together a program called DreamPool that would just literally pick out a few nouns from a gigantic dictionary file and bubble them up in a little graphic of a well, and then I would sit quietly and spin those concepts around attempting to connect them together.

LLMs are like a version of this on steroids and the potential as a tool for augmentation is huge.
> I don't understand the hate. They did a very bad decision and had major backlash. Fast-forward one year: they rectified it completely, they greatly improved the free terms compared to what was before, they replaced the CEO and other involved executives.

But nothing prevent them from doing the same again if their indicators say it would be profitable. Developers just don't want to take the risk anymore.
The difference between novelty and hallucination is feasibility. With integrated critique and feasibility checks you can eventually map the hallucination space into novelty.
> but people who got burned by the change already got burned, and they want to avoid it in the future.

They likely have also put effort into moving to other frameworks, and if those are working out well enough for them there is no point making the effort to go back even with this change reverted.

Same for new projects that went directly elsewhere: unless Unity offers significant benefits (and the project controllers feel that Unity can be trusted not to repeat the rug-pull later) the effort of changing stack are likely not worth it.
Would you mind explaining what you mean by stateless?
Anduril launches 'autonomous cruise missiles' designed to operate at scale
I've often wondered if it having a reputation as being hard is accurate. Not necessarily because of syntax etc. but because of you don't already have a grounding in programming/engineering/comp sci. it can be difficult to fit the insights Haskell provides into any meaningful framework.
That was my experience anyway, came to it too early and didn't understand the significance.
Show HN: QuickPoint. Make presentations, web pages etc. with a YAML like syntax
Show HN: QuickPoint. Make presentations, web pages etc. with a YAML like syntax.

I started this project during lockdown. Remember that?? It developed from an idea I had for exchanging value in URLs. The idea being that if , for example, you had a subscription to the NYT and if they linked from their article to an article in the WSJ the WSJ would a receive a small payment from your subscription. The idea seemed much too abstract for any stakeholders in publishing organizations so i thought I'd better build my own publishing platform. I didn't think it would take this long but here it is (after two kids) in a usable form. You can use if for anything and publish your anything to the web. Down the line you can charge for your creations.

The language is YAML like and any good names for it are welcome.
The viewer is a React component that you can drop into any webpage with a one-liner, the aim is to open source that.
It's probably full of bugs so do let me know.

It's a fun thing and works great on mobile. I imagine harried developers who need to give presentations might find it useful in it's current form.
Maybe. I've lived with horses long enough to know that some of them are just assholes.
Like I have said, you have to take the measurement every day at the same time and in the same order with respect to eating, drinking and dumps.

And yes, you can measure that accurately.

I had been obese for many years and I had many failed attempts to lose weight. This has changed only after I bought accurate digital scales and I have started to measure carefully, every day at the same time and in the same conditions.

During a day, your weight will vary a lot, perhaps by more than two pounds between the maximum and the minimum. Nevertheless, if you take care to measure at the same point every day, the accuracy is good enough, the uncertainty is less than 1/10 of a pound, if you are careful.

When I was losing weight, I could see very clearly the effect of eating one spoon more or one spoon less per day of certain foods, so I was eventually able to lose one third of my initial body weight, in about ten months.