skysight-inc/HackerNews huggingface dataset:
We used to place an INT3 vectored exception handler on function entry points and do everything interesting inside the exception handler. This made the execution stack basically invisible to every debugger since it doesn't debug exception handlers. You can enable/disable interrupts and tracing and whatever you need to do inside the exception handler to guarantee that nobody can see what you are doing and/or verify that no other program has registered another exception handler before doing anything interesting.

If you need to hook functions in third party software, this trick can be used to hook the function without modifying any of the functions code. All you need to do is modify some pointer used by the function to zero, and it will raise an exception as soon as something like p-> is executed on that pointer, then your exception handler can execute whatever code you need (i.e. write over stack, write to memory, exfiltrate handles) and on exit all you need to do is restore the correct register containing the pointer and wind back the execution counter by the size of the de-reference instruction.

Please don't use this knowledge to hurt people ...
Pricing Out Your Legacy: Thoughts on WordPress’ 100 Year Plan
38%.

And 38% is not "a third way to 100%". I'm sure you know what diminishing return is.
dumb. I admit the mistake.
China had their own mile. “The journey of a thousand miles begins with a single step” was actually only around 300 English miles long.
Mind sending a link to the film you purchased? I have a large hot window I’ve been thinking of doing this to
We only need to look to nature to find the immortal jellyfish.

Much of medical science is "artificial" extension of life. Natural would be you dying of Smallpox at a young age. Instead you've artificially extended your life with a vaccine.

https://en.m.wikipedia.org/wiki/Turritopsis_dohrnii
Maybe they can do the North American Camel that went extinct 12,000 years ago next. Lots of great candidates, both recent and prehistoric.
Oh shut up. Don't be a dick.
The strengths are that it's simple, hard to game, and doesn't harm ordinary people because the average person gets a refund of 100% of the money. (It's also somewhat progressive because people with more money tend to emit more carbon and so pay more tax, but only get the same refund.)

The main "weakness" is that it imposes significant costs on existing fossil fuel operations. Oil and coal companies would lose billions of dollars in value because they would both have to pay the tax and experience a surge in new competition from alternatives that can now underprice them. I don't regard this as a problem -- the writing has been on the wall for a long time now and if you've invested in these industries you could have predicted this was coming -- but it is an inconvenience because it causes those industries to lobby against it aggressively, which makes it harder to enact. (But the same will be true of anything with near-term effectiveness, because the whole point is to put them out of business.)
my mistake. 40% of the way there, point still stands.
Encryption with "exceptions" is not end-to-end. Full stop.

Thanks for highlighting this fact.

Also, I'd never trust any FB/Meta products with my information or privacy, especially Whatsapp.
Huh that's pretty smart if true.
You need at least two completely independent teams who don't see each other's code so you'll have a rough idea how much developer bias is responsible for the signal. Right now they are all copying code from each other, a single error in these and all the climate models are effected. Replication here should mean different scientists writing different code arriving at the same estimates.

It needs to be open source, and it needs to be way more organized, no physical constants which aren't constant or which have bad precision or which have different values in different parts of the code.

Actual error modeling built in or at least a way to measure and quantify the accuracy.

Some models only use CO2 input for radiation and not for many other parameters that depend on CO2. Because the code is a mess and constants that shouldn't be constants are all over the place. And getting "constants" right is even more important than having high resolution to the simulation.

Getting real physical data to replace all the ad hoc constants is extremely important. And validating the correctness of the cloud modeling with real world data is also important.

And you can't write huge spaghetti code, it needs to be readable and comprehensible to someone other than original programmer so that people can validate the assumptions.
Simply put, people aren’t rational and the vanguard of climate shaming live in cold climates.
Regarding the greenhouse-gas emissions of air conditioners, it's more than just the induced demand for power generation (which in Egypt still depends heavily on fossil fuels [1]).

I was a little bit surprised by that callout in the story, so I went looking for info on the refrigerants themselves. If you're old enough to remember the worries about the ozone hole over Antarctica, you might remember that we agreed to phase out CFCs as a refrigerant. They were replaced by HCFCs which are less dangerous to atmospheric ozone (yay) but have a very high impact as a greenhouse gas per unit mass (boo) [2].

Ultimately the HCFCs will be replaced with ammonia, propane, and other alternatives which have a lower greenhouse gas effect, on the same order of magnitude as CO2 [3].

[1] https://www.iea.org/countries/egypt

[2] https://unfccc.int/process/transparency-and-reporting/greenh...

[3] https://climate.ec.europa.eu/eu-action/fluorinated-greenhous...
But is it with monoculture?

Seen some HN comments about that recently.
True, but if it's open source, TS is probably a lot more practical for maintenance or contributions vs smaller pool of Haskell devs.
And everyone measures TVs in inches, somewhat bizarrely.
I lived in Seattle for three years, never had AC. It’s weird to see it on the same list as Houston. Are you sure you’re not confusing it with somewhere else? Or has the climate in Seattle really changed that dramatically since I lived there 7 years ago?
The more a society develops the lower its birth rate. Most of the developed world is well below replacement rate, and the rest of the world will be there soon too.
Generally speaking the surface receives about 1kw/m2. I’d love to see a spectral graph that shows how that kilowatt is distributed. How much visible light can you sneak for a very low amount of that energy?
Yeah, but it's Jane Street. They've got the money and talent to do it right and they've got a very strong dev culture that esteems correctness.

And they're in a market where a tiny competitive edge can reap large rewards.

They're rather the exception that proves the rule.

I'm sure all their competitors do the same for the same reasons. But for companies that view software primarily as a cost centre, I can see it going horribly wrong.
Yes?

The WHOLE POINT of native apps is that they are better at integrating with the system. Like access storage, gps, camera, accelerometer/gyroscope, etc.

Besides that the only benefit of a native app is basically that the UI/UX will be closer to what the user is accustomed to.
I don't believe in writer's block. Yes, there are days when you don't want to write, or you can't think of what to write. Still, if your job is to write, you sit down and write. Maybe you write crap. Maybe you can find a nugget in that later. Steven King (not a writer I like very much) writes every day. It's said that George Lucas (who hates writing) locked himself in an office with legal pads and a pencil for eight hours a day, every day for months, until he finished the first draft of A New Hope.

You're right, there really are no rules, except for the one that says WRITE. Everyone's process is different. There are many techniques, many suggestions, many methods. But none of them work unless you write.
Carbon emissions produce externalized costs or they don’t. If they do, it’s the proper role of government to internalize them while ameliorating any inequitable transition costs.

Everything else is green theater.
Ah, back when people believed things they saw on the Internet.
I thought we wanted billionaires to be immortal!
We are always "close" to a breakthrough. This is exactly what happens with every advancement in science and technology.
Not true. They are well past 1%. That's not looking at reality. You can lower it below 38% but 1% is pure fantasy.
The assumed burden is higher because you are trying to let the young to the shoulder the burden of the old. In Japan(or any other country tbh) the return of the tax values to the young is vastly smaller than the old. Immigration is not gonna solve this problem, that's just delaying the ponzi scheme or push the burden to the other country anyway.

What if we tip the scale to young more and treat them fairer? What if we start moving some of the services to the young instead of the old?
Endeca was killed by Oracle.

I recently completed an Endeca to Algolia migration. I spent quite a bit of time auditing the Endeca implementation, from the XML files to the Windows desktop application. It was pretty good for its era.
So the toolbar on iOS has 5 buttons

Go back | go forward | share | bookmarks | see all windows

Do you think there should be a separate button just for “Add to Home Screen”?

Or could you just put the standardish share icon on your page and below it say “click here and choose add to Home Screen to…”?

Is that really that much harder than to tell someone to go to the app store?

Most people know how to scroll.
> 48% if half way to 100% … It's halfway their to taking your job and your underwhelmed.

You’re implying 100% reliability is actually attainable. If that were the case, wouldn’t that mean the halting problem would have been solved by AI? I’m not an expert but I’ve heard that’s like one of those fundamental laws of information theory that really can’t be broken.

> It's typical. It's like an indie band is only popular when not many people know about it. Once everybody starts talking about it all the time it loses it's popularity.

I think applying the sociology of hipster band fans to LLMs is a mistake and I’m not sure how the vogueness of the technology correlates with the correctness of the actual models. Sometimes an early technology seems docile or useless at first but eventually reaches ubiquity and in retrospect the utility is obvious. But sometimes (more often than not) standard adoption curves don’t make sense to apply to a new technology because it isn’t useful enough to go through an adoption cycle. I think there’s a temptation to apply the analogy of something like the early internet or smartphone to LLMs but those are networked products. LLMs don’t really improve with the various applications built on top of them if the LLM is itself fundamentally broken or faulty to the point that it is unsafe to use in practice. Furthermore given the massive amount of premature hype due to the AI zeitgeist, you can safely assume enough user hours have been spent messing with LLMs to get a verdict on their utility. Unlike the feeble technology that takes a longtime to reach a scale to know its utility, we don’t have to wait 10 years for 100m people to try LLMs, it happened in a week. My only point being, I think we should be apprehensive about trying to draw analogies of other adoption cycles that structurally are very very different to this one.

Obviously, I, like probably everyone else on this website would love LLMs to be reliable to a high degree. Just this morning I had such a good use for an LLM that I was seriously considering building (and admittedly still am pondering) but the second I started to think through the LLM faultiness, I had to consider the complexity of the safe guards and weigh if it was really better to use GPT or just write a nasty regex script and constrain the problem. I’m leaning heavily towards the latter but I’d much prefer a silver bullet if it really killed vampires. Until then (if that day ever comes), it’s lead bullets for me.
Yes, and that would constitute "being a nuisance" but not "malicious vandalism".
The particular one I bought is this one: https://dropovercl.s3.amazonaws.com/21fa0b29-7858-4233-b895-...

It doesn't seem to be a real brand, Bauhaus sells it and its made in Taiwan. I'm sure there are similar or better films out there.
Well then we are part of the way their still right?

It works but only edge cases are a problem. Next step is to fix the edge cases.
Font's aren't quite just a collection of images. Though they almost are which makes it hard to see the boundaries.

But a computer font (as opposed to the typeface it represents) is a specialized program, ie it has logic as well as data. Specifically, kerning tables and the conditions under which to use ligatures would be lost by the approach you're proposing. But I'm not a typographer or font expert and I suspect other things also. Anyway that doesn't make it completely untenable, just not a complete & automatic process.

It is similar in concept to how recipes are handled by intellectual property law. A list of ingredients isn't protected, nor is a specific result. But a list plus instructions is. You can copy a recipe by applying a different set of instructions to the same list of ingredients, resulting in an identical dish. In this the type characters are the ingredients, but you still need to provide a set of instructions to combine them into a font. You can provide ones that create an identical result, but you can't simply copy them from the original font.
I believe the original comment wasn't written to say that he doesn't know how iPSCs can be useful (obviously they are very useful), but he doesn't know how this breakthrough/paper makes much of a difference.

He's getting at the fact that we've known how to induce pleuropotency for quite some time (I did some reach in this in orthopaedics in 2010), which is what the article title is misleading us to believe.
I'd go further and say the sweet spot is probably writing a simple function that fits in the model's context window, in a language you don't know. Even here it screws up, but you can go back and forth and get somewhere. I can only imagine the mess one would make using it to build an actual application of any size. The analogy that comes to mind is using google translate to try and write an essay.
https://mazzo.li/posts/fast-pipes.html#splicing :

> In general when we write to a socket, or a file, or in our case a pipe, we’re first writing to a buffer somewhere in the kernel, and then let the kernel do its work. In the case of pipes, the pipe is a series of buffers in the kernel. All this copying is undesirable if we’re in the business of performance.

> Luckily, Linux includes system calls to speed things up when we want to move data to and from pipes, without copying. Specifically:

> - splice moves data from a pipe to a file descriptor, and vice-versa.

> - vmsplice moves data from user memory into a pipe.

> Crucially, both operations work without copying anything.

But then to scale to more than one node, everything has to be copied from the pipe buffer to the network socket buffer; unless splice()'ing from a pipe to a socket is Zero-copy like sendfile() (which doesn't work with pipes IIRC).

"SOCKMAP - TCP splicing of the future" (2019)
https://blog.cloudflare.com/sockmap-tcp-splicing-of-the-futu...
Funny how proponents have to talk about sports or actors' unions to sell developer unionization because we aren't sports players or screen actors. Try talking about what actual engineering unions do instead, like the SPEEA.

(Frankly, I can't think of any unions of engineering professions aside from the SPEEA in the US and I couldn't find any in a casual Google search. Anyone know of any? And if there aren't any, well, people might want to think really hard about why.)
If only your sig was fredflintstone!
Evidently, Hasura is migrating to Rust. That's pretty fast and seems to have a lot of developers.

https://discourse.haskell.org/t/hasura-migrating-to-rust/662...
The problem with tape drives for backups is that they only just outpace the sizes of hard drives over the years and are multiples of hard drive prices.

Most of us have used tape drives in the past for backups only to find that hard drives work better, are more reliable overall, can be accessed randomly, and are cheaper.

Imagine using a 2Gig DAT tape for backups these days, as I did do way back in the past. Or a 60MB QIC cartridge, as I did do a few years earlier than that DAT tape drive.
More discussion a few days ago: https://news.ycombinator.com/item?id=37261001
I infer long term engineering leaders, just from how coherent their dev culture seems to be.

They're big on FP and OCaml and do a lot of open source work around OCaml, and have done for years.

Speaks to consistent leadership.
> When companies create this microservices bog and then, when any problem comes up, they say, “distributed systems are hard” it reminds me of when my toddler throws food on the floor then says, “look, big mess”

https://x.com/telmudic/status/1684479894406025216
Yeah, I think it would be neat to change time to be defined as 1 chrono = how long it takes for light to go 1e9 meters. 1 kilochrono is 55 minutes. Useful enough for space travel type situations where you can’t rely on solar days for units.
I’d describe overly generous as being being unsustainable/bankrupting the very communities they serve. (Or for a qualitative example take police officers in Suffolk county NY earning $200k-$700k/yr in addition to generous pension and health benefits (worth millions on top of that))

You raise a reasonable point that I admittedly don’t have a satisfactory response for, regarding an alternative negotiating framework, but it seems to me the pendulum has swung way too far in one direction, and their is no effective check on capture by public sector unions.
Well, I really appreciate it. I'm planning to apply it in two ways specifically: Increasing my daily average step count by only 2% per week, and decreasing my daily average calories by only 1% per week. Both numbers are high enough that I think I should be able to round to whole numbers pretty well. Using the rule of 72 for some quick math, I think that means I can double my step count in 36 weeks. (I haven't figured out quite how the math works for the calories if I'm counting down, not up, but I'll get it!)

I have a strong tendency to err on the "either I jump all the way to my goal or I've failed" side and burn myself out, so I'm actually going to try to use my will power to refrain from walking more steps, or eat a couple more calories. I'm hoping it'll help drive home that I succeed in the long run when the short-term change is small.

Thanks for writing it!
> So you never have to wait for a vehicle and all of your routes are direct with no stops? I doubt that.

If I am riding the metro at peak hours then I wait a minute or two.

If off-peak then I leave the house at the appropriate time so as not to have to wait.

There are stops, but they are predictable and short. Nothing at all like the experience of being in a car.

> You been on US public transit?

Yes, and in my experience, my insurance company does not raise my rates if someone damages a metro car.

> You pay for public transit while you're not using it.

In the same way that I pay for car infrastructure when I'm not using it, except that I pay a lot more for car infrastructure I don't use than people who don't ride the metro pay for that.
I realise you're reasoning from a general architectural standpoint, but if you rent, basement apartments are a nice hack. I rent one and it stays perfectly cool even on 30 degree days just because there's much less wall to get heated by the sun. There are definitely tradeoffs though; more bugs and spiders, and flooding might be an issue depending on location.

As for the architecture, one ancient trick is to paint houses white.
The argument is that it’s unnecessary, or less necessary,
if we reconsider how we build our buildings.
What about genetic diversity? Is there enough quality DNA to establish a hardy herd?
With regards to the hiQ case (IANAL, but I followed this case closely): the 9th circuit asserted that the CFAA (Computer Fraud & Abuse Act), which is a _criminal_ statute, does not apply to scraping websites. On the other hand, if you create a user account and scrape while logged in, that is a matter of contract/civil law, and the website can sue you to stop breaching the terms of service (plus maybe damages).

The takeaway for those of us in the trenches who feel we have as much a right as Google or Bing to crawl websites, is that we are not subject to arrest and imprisonment, just tort law. The ruling has apparently caused the major social networks to switch from criminalizing web scraping to putting most content behind a login and threatening to sue small companies out of existence.
Oh man, Flitetest. About 10 years ago I got really into building those planes. Never bought any kits, just used their free plans to cut my own foam boards. I did buy some components from them; usually a bulkhead or landing gear setup.

My favorite one was the F-22 replica (https://store.flitetest.com/ft-22-mkr2/). With the right motor and prop—and by abusing the discharge rate on the battery—I think I got that jet screaming at ~60mph. Not sure what the precise speed was, but it was definitely in the “should I be buying insurance for this?” territory.

The Bloody Wonder was my favorite for aerobatics. It was easy to build, fairly tough, and easy to fly but still twitchy when you wanted it to be.
Because that perception is wrong. Based on poor judgement (often Youtube clickbait and low information Reddit), based on simply a lack of knowledge regarding CPU architecture.

I would not upgrade yet from this 11900K because it's the best homogeneous core design that Intel released for desktops. It includes AVX512, and is the only consumer CPU from Intel to have it. Intel engineers have stated that they are dedicated to furthering AVX512, and that it's removal is temporary. All of the errata from Skylake was finally fixed in Rocket Lake, which went on for generations until Rocket Lake.

Some people were so deadset against 11th gen that they recommended 10th gen because there were 10-core CPUs. Yet the ringbus design it inherited from Skylake was very strung out by that point with unresolvable issues like the well-known L0 parity error. There's many other reasons but I doubt you're interested in rehashing Rocket Lake as it sounds like you feel you have enough information to make up your mind.

And I certainly wouldn't use AMD due to even more bugs than Skylake and poor latency. They're improving, but it's not my choice.
> I cannot imagine trying to develop this way. But if people like it, whatever blows your hair back.

I agree; who am I to comment on how you write the code, as long as it gets written, right? That said, I've already had a "this is really odd code you committed last week, what's up with that?" and the reply was "oh, dunno, that's just what ChatGPT gave me". Meh. Actually writing things yourself does increase your understanding, so it's not the same, not really. It's when they told you to take notes at school: I didn't believe my teachers it'll help retain knowledge on account of being a stubborn little idiot, but they were right!

For people who have already done this programming thing for a while I guess it'll work out, but my main worry is the effect it will have on more junior people who will "grow up" on ChatGPT. "Figuring it out" yourself has a lot of value.

Just because the code is free of syntax errors doesn't mean it's free of bugs. Shell scripting is a classic case where it's hard to make something work but also buggy. You need to actually understand the code and reason about it. Trail-and-error programming rarely leads to good code.

I also fear we'll end up with hard to read overly verbose/repetitive code, "because ChatGPT/copilot will just generate it".