skysight-inc/HackerNews huggingface dataset:
If you are only looking at the plans, I’m paying $180 for just 4 lines. The rest is all fees and device payments that are all ending soon, at which point it will go down by $~80 a month. The “fees and taxes” section is royally killing me on my bill and makes up for the bulk of the bill, actually. That isn’t reflected on any advertised price.
It's not unique to a merge commit of course, but a point in favour of preserving history.
LLMs do not have general intelligence, but it does an awfully good job doing something human thought typically does -- synthesizing ideas. It's able to combine X and Y to produce Z.

LLMs cannot do first-principles reasoning well (unless it has seen the pattern before), but they excel at reasoning through analogy.

And guess what? Most humans reason analogically too. Analogical reasoning -- as opposed to first principles reasoning -- is actually more effective and useful in many situations, especially in ill-defined domains. Humans often think, "this situation looks like something that I've seen before, so I can apply my past knowledge but with a few tweaks."
I’m not advocating anything really just explaining the broken economics of political boundaries policing their own development.
I've read the Silmarillion several times, read through [0] and [1] each once, and I still mostly got tripped up on all the kings of Gondor who sound apparently a lot like antidepressants (I got 18/24).

[0] https://www.amazon.com/Introduction-Middle-Earth-Published-W...
[1] https://www.amazon.com/Languages-Tolkiens-Middle-Earth-Compl...
https://www.toyota-global.com/company/history_of_toyota/75ye...
I still remember when the auto industry said Catalytic converters were the only way and testified to Congress they weren't ready yet so they couldn't meet climate goals.
Toyota through a holistic approach was able to meet the emission standards without a Catalytic converter, but was still forced to adopt one even if it wasn't more efficient than their current design as it was a one size fits all solution.

Sort of like saying a gym membership is good for everyone since it increases life expectancy, and not taking into account blue collar workers might get the equivalent of a workout from just doing their job, and that going to the gym after 9 hours of physical labor might do more harm than good for those people
What's confusing about it? More Bs = more black (soft), more Hs = more hard.

The only thing slightly confusing is 'F', which is just a ½H.
Screen Accountability – Covenant Eyes
https://en.wikipedia.org/wiki/Debt-trap_diplomacy
Great article. Nice to have it interactive. How does it work? Do you have a terminal running somewhere or does it run in the browser?

One thing I noticed, and where I stopped continuing, is that the jump from Filtering Nested Arrays to Flattening Nested JSON Objects, is WAAAY too big. From a simple filter to triple nested filters with keywords that had no introduction in a simpler example, isn’t working for me
We do, it’s called a dump. One downside is they tend to produce a fair bit of methane, but they potentially sequester CO2 across geologic timescales. The other is most of the plastic was sourced from fossil fuels and releases CO2 as part of the manufacture process so it’s not a net gain.

Still better than burning it though.
Don't Do a Rebound Startup
This is also why 2D jump platformers like Megaman have triangular jump trajectories instead of parabolic trajectories. For snappy controls you leave the ground at the instant of the downpress and peak when you let go of the button. As the game can't know how high you intended to jump at the time the jump begins, the trajectory can't be parabolic. (At least, not on the way up.)

You could instead have the button downpress "charge up" energy and then begin the jump when the button press ends, which would allow for more realism, but also introduce a delay.
No one is planning to do that. Filling entry points with concrete, though, which is what the article is referring to, has been standard practice for a long time. And breaking up those large blobs of concrete has been a core activity of cataphiles for as long as it happened.

I was not a cataphile but, like lots of locals, I used to go down there almost every week-end in the mid-to-late 90s. The times of large decadent parties were already over by then. You could still meet a surprising number and variety of people but the "ambiance" was not as romantic as you might think from reading the article: the IGC was doing crackdowns and blocking entry points, the cataphiles were very hostile to other visitors, and the few "parties" that still happened at "La plage" or elsewhere where really a handful of people smoking weed.

The catacombs were a pretty cool playground to have, that's for sure, but let's not exaggerate its cultural importance.
Penciling cards? How about straight binary input through frontpanel switches?
It doesn't seem that complicated. It's as simple as "The camera is pretty good now, what if we marketed its quality by shooting our event with it and hyping it up that way?"

Likewise USB-C: "We can make more money if we have a special proprietary charger". It's never that complicated really, it's all in execution.
Conflicting requirements stemming from the psychological illusion of movement spontaniety.

People don't want the realistic, slow response. Normally people aren't aware of how early their body starts a movement, the conscious brain has the illusion of just having decided it but it's actually started much earlier.
> I was an obnoxious extrovert who had no privacy, shared everything online, and never thought before I spoke.

It’s almost like they’re describing me.

> Whereas true happiness comes from finding the quiet calm, the ‘home’ within you. Once you find this place, you’ll see that your friend list is narrowed down.

I think I need to meditate more!
Absolutely wild.
Can you explain how exactly you believe a government can exploit the PKI to MITM traffic to, say, google.com? Especially how they could do so in a way that wouldn't have been much easier if they (a) could force a browser to trust an insecure CA or (b) intercept my initial communication if they know I'm doing TOFU?
How have customers “voted with their wallets” when all of the major players released 5G to all their customers? It’s not like any actual choice was made by the customer.
> Your producer may try to get you to recreate that beautiful performance in the studio, but audio quality doesn’t matter as much when you compare the recording of a good performance to the recording of a much better performance.

Nobody is going to keep your iphone recorded song in their playlist.
The extra data type of unstructured/bytes is optional in that you don’t have to use it if you don’t need it. Just start with a table if that’s your use case.

In security, binary artifacts are common, e.g., to scan YARA rules on malware samples and produce a structured report (“table”). Turning packet traces into structured logs is another example. Typically you have to switch between a lot of tools for that, which makes the process complex.

(The “void” type is only for symmetry in that every operator has an input and output type. The presence of void makes an operator a source or sink. A “closed” pipeline invariant is one with source and sink, and only closed pipelines can execute in our mental model.)
Correct regarding memory - not true for memory because it's non-fungible unlike CPU shares

> You also cannot achieve a QoS class of Guaranteed without both CPU and Memory limits, so the pod might be evicted at some point.

Evicted due to node pressure - yes (but if all other pods also don't have limits it doesn't matter). For preemption QoS is not factored in the decision [0]

[0] - https://kubernetes.io/docs/concepts/scheduling-eviction/pod-...
OpenAI Consistency Decoder
You are not wrong on that level, i have been slowly writing a language in Rust anc all these point are deeply felt.

And yet... The Rust ecosystem win. Easily. For a simple reason.

Salsa. Oh and also clap. Lsp bindings. Ungrammar. Miette. Clap. Parsers. Etc

At every level the Rust packages are far better and allow to drastically reduce the cost of building this stuff.
Accurate! There's a whole thread in the Nexo FB group with people writing to the Governor and state legislators about the constant price increases at the pump. I love my car and am lucky to live near multiple stations and not have to drive often. One poster mentioned independently adapting the engine to be a hybrid plugin, and that would just make it the perfect vehicle.
Then you might be interested in my Go implementation of Forth [1]. No assembler required, but bootstrapped and with some rudimentary internal type checking.
The heap is just an `[]any` type array.

It runs in the browser via WebAssembly.

[1] https://github.com/s-macke/Forthly
Note that this paper is about the CLWW scheme of 2015. The Lewi-Wu Scheme of 2016 (Block Order Revealing Encryption) has entirely different security properties. Storage of the right ciphertexts (as they describe in the paper) is semantically secure.
Seems he is using something called biowasm aioli: https://github.com/biowasm/aioli

> Aioli is a library for running genomics command-line tools in the browser using WebAssembly. See Who uses biowasm for example use cases.

https://biowasm.com/cdn/v3/jq/1.6
Gains by what metric? Are you sure you didn't trade in better latency for worse overall throughput? Also, sure you didn't hit one of many CFS overaccounting bugs which we've seen a few? Have you compared performance without the limit at all?
China broke their word when it came to One Country Two Systems. I understand that Britain had a 99 year lease and felt like they had to hand back Hong Kong. But when military assets are deployed to protect Taiwan after China oversteps, those same ships should liberate Hong Kong and restore Hong Kong's prior status. China broke the terms of the handover, and it will sadly take another islands sovereignty being threatened before the world is willing to recognize what happened to Hong Kong, and do something about it
> constantly floating around throughout the day helping people out

I unironically love being distracted by other peoples problems. Usually the person giving me the work I'm really supposed to be doing gets annoyed at me for it, I'd love it to be my actual job.
In this example, the local variables are `string`, `pattern`, and `replacement`, and are implementation details; only the names `in`, `each`, and `with` are part of the public API. Renaming the local variables doesn't break anyone. Renaming the labels would break callers, just as changing the names of keyword arguments in other languages.
There's also a history in applying ECS in older things, it started taking off in early 2000's, it's been bread and butter (though not universal) for long now, also in some open source engines. See eg https://github.com/Adelost/entity-component-systems-study#re...
Agreed, it’s been so easy to onboard people onto Elixir we’ve just looked for raw talent knowing they’d be up on Elixir quickly.

As long as you have one experienced elixir engineer to guide the people learning I think it’s easy to move fast.
To extend, the answer is the BEAM itself. It ships with these tools built in.

From the whole zoo of system probing stuff or the downright amazing dynamic tracing.

Have a quick look at
https://www.erlang-in-anger.com/
I mean, isn't that the solution the government wanted? It was about bundling and interfering with other products the user had installed. An "arm's length" is all that they would have needed to do.
A good balance comes when both employees care about business decisions e.g. "is it worth spending 3 months of the teams time on X?" and vice versa non-engineers are aware of technical debt and why teams are trying to 'pay it down'. The ideal situation is when there is someone or a group of people who can take in all the information and make decent business decisions. After all - the codebase and it's maintainability is a part of the business (just like a well maintained oil rig vs. a bad maintained one impacts the business). It is just not as visible as managers can't walk around and eye up the code as easily as see cracks and rust in the building work.
This is pure gold. I wonder why there are so few modern equivalents to this sort of thing. All of the modern physics pedagogy that I've seen describes this experiment in idealized terms, and it turns out that this idealization is really a lie: the split beam is not two cleanly separated beams, it's smeared out because of the range of speeds of the thermalized atoms. I think we do students a serious disservice by sweeping details like this under the rug. Worse, the trustworthiness of the whole scientific enterprise is undermined when we simply describe idealized results and ask people to take it on faith that we're telling the truth, especially when it turns out that we're not.
I'm not sure, but wouldn't the absence of abs and airbags disqualify it from the EU market?
It’s a solved problem already. Various IK systems will tackle it properly and some games will have your feet IK follow the terrain and hands IK push up against surfaces.

However it’s a trade off of performance (the constant ray casting and IK solves aren’t free) but also responsiveness.

Many games opt for faster locomotion and responsiveness instead.

At the end of the day, it’s a technically solved issue and has been for years, but as with every single thing in game design, it’s a choice and trade off.
> Chronic injuries, on the other hand, are much less preventable and much more common among experienced lifters. I've worked through several, including a soft tissue injury in my hips and a nagging tendonitis in my left elbow.

Can you describe your hip injury a bit more?
Some specialized subreddits can be incredibly useful. /r/chatgpt due to its popularity is not one of those.

It's full of memes and people complaining its not as "good" as it was yesterday when it fails at completing their homework.

I would take anything said there with a big grain of salt, and stick to benchmarks.
Fascinating. Thank you (and siblings) for the correction.
Exactly. China to rescue after what west has done.
They were never moved around, but could be unloaded manually and read back from (floppy) disk at another memory location.
yaml2json | jq ...
I'm pretty sure that's how most remote controlled garage doors get closed.

Maybe some people in individual houses watch and wait for their door to be fully closed before driving away, but that doesn't seem to be the norm for collective housing (I've certainly never cared myself) or even for most individual garages around here.
Epic Games funded the development of Alan Wake 2 and the game is also an Epic Games Store exclusive (which I painfully found out wanting to buy the game but being on Linux), so I assume competing with Unreal would burn some bridges there
As with any secure system, it depends on your threat model but the early versions of OPE are woefully insecure. The attack you're describing sounds like the one on the Boldyreva scheme from 2009. While all OPE schemes leak some information, the more recent schemes are much more secure and often quite appropriate for many use cases (arguably at least).

ORE has different security properties, particularly Lewi-Wu 2016. There are also now hybrid schemes like the EncodeORE scheme of 2020 which is both more efficient and more secure than previous OPE and practical ORE schemes.
As a dev turned entrepreneur one thing I will do when selling projects is talk to clients about software as a depreciating asset. While there are some limitations to the comparison this framing makes sense to business people in general, especially well with finance or operations departments, and can work with internal stakeholders too.

The sources of the depreciation are tech debt and general turnover/churn in the method and process within an industry/vertical (like if you built a web app in 2002 based on ASP.NET, it's pretty tough for that to be a lively project today).

We know there are systems out there that have been running well and doing their job for 30 years, and there are systems that need to be replaced/rewritten from scratch every couple of years. Which one do you want to buy/fund/budget for?

If the customer or stakeholder only cares about a two year horizon you approach the project one way. If they say they want this thing to be firing on all cylinders 10 years from now then we approach it and price or budget for it differently. When you talk like this it doesn't sound too weird to introduce the idea that we should do an annual tune-up to a system that they don't want to have to replace until 2035. The tune-up is how you get 15 years of life out of your intellectual property instead of 10, this is how you sell time to pay down tech debt. The eventual rebuild is also part of the discussion (not if it will happen, because it will. But when it will happen is something we can influence, so the framing can be, would you rather do an expensive rebuild every 10 years, or do it in 15-20 because you paid for a regular maintenance along the way?).

Boom now in their head this software you're writing is like a car. Everyone understands cars. A car has a lifespan. If you didn't go to the mechanic and do your annual scheduled maintenance and the car breaks down, that's what you get for being cheap. Like I said big ops and finance departments actually really like the idea of a tuneup that prevents the car from breaking down. They're used to thinking about that with lots of physical assets anyway. A marketing department at a startup maybe not so much but their time horizon is usually short anyway.
So 7.5 years ago someone didn't understand the concept of a thin wrapper that forwards arguments to another executable. Big deal? Why is this here presented without comment?
The one thing I would like to have the ChatGPT thing do for me.

(and regexes)
Not the first idiot that falls for this website. If it were kids, I might forgive the ignorance and lack of common sense, but how are fully grown adults this naive and oblivious? It always boggles my mind.
Definitely thinking about adding back the Perfect Face feature, which got canned, now it's recompiled!

I can't wait for other improvements too!
I remain skeptical, but the EFF supports the bill, as does the ACLU. I hope that I'm surprised and it passes intact and actually accomplishes what it sets out to do.
I've heard of 'knocking' before as well, where they drop something that just makes a big bang on the roof a while before the main event.
> Memory is different because it is non-compressible - once you give memory you can't take it away without killing the process
I used to work in a company selling core banking systems and yes they are a mess. I never imagined they would still be running in 2023. I could write a book full of horror stories. What amazes me is how so many banks do ok despite a massive failure to delight customers or innovate. Banks are literally “a license to print money”.
I actually agree, this is the most questionable piece. I prefer (and have argued for in JS) Hack-style pipes, where the value "placement" always has to be specified.

That allows arbitrary expressions on the RHS of the pipe, so for example this would be valid Gleam:

pub fn main() {
io.println(
"Hello"
|> (_ <> " world")
)
}
You miss my point here. Im strongly against manadatory and forced contributions. If you don't see a purpose in financing something, force to do it brings inequalities and in long term create conflicts. I prefer reasonable choices that have sense for you or community.

Imagine businesses in private sector that would charge you for things that you don't ordered. Its nonsense, somehow tolerable if done by state.
It separates "names as public-facing API design decisions" from "names as developer conveniences for expressing intent and clarifying their code".

These are often very at odds. And if you don't want to repeat yourself twice with two identical names... you don't have to.

And unlike Smalltalk, in Swift at least, externally unnamed but internally named is easy (just make the external name _).
> At the end of the day, what certs you trust is a personal decision. It's not a democracy; there is no need for an entire country to agree on which certificates are trusted and mandate that by law. Pick the ones who you trust, and your choice need not affect my choice. (Most of us delegate to browser vendors, OS vendors, or our employer, of course, but that is a choice. Don't like Apple's set of root certs? Delete the ones you don't trust, or use Firefox, or use Chrome.)

This isn't entirely true. Let's disregard for a moment the spy agency's wet dream that this law introduces (likely fully intentionally). The more benign intent of this law is to prevent foreign entities from the EU (Mozilla, Google, Apple) from having the final say on whether two kinds of EU organizations (site operators and root CA operators) can successfully reach their clients.

Of course you in your capacity as a consumer don't care whether I trust the same root CAs as I do. But a site operator very much cares whether all of their target audience trusts their site, and by extension the root CA that they are paying, and would like for their government to guarantee this trust.

The theoretical problem that this law is theoretically intended to protect from is browser vendors imposing hostile requirements on certificates which cost EU companies money and/or access to clients. It's a form of protectionism, ultimately.

Of course, the law is clearly being influenced by EU members' security agencies as well, who would love to have the ability to issue fake certificates for any site on the internet. With this new law, they would only need to infiltrate/coerce/fool their local root CA and local auditors, and they'd get free reign over encryption everywhere in the EU at least.
The point is that it passes intact, or not at all.

> The GSRA is currently the only bill in Congress that could reauthorize the 702 statute that’s set to expire by the end of the year.

If this bill is defeated no other bill will be put to a vote before the deadline.

Ron Wyden knows that time is on his side. In a game of "who can hold their breath longer" the spooks will pass out first.
The rest is obscured by the milky way, for anyone wondering.
large state is too complicated and error prone. cut it down.

don't put big temp. buffers onto the stack, put them into your .data segment. (i.e. global).
> Teslas haven't been very reliable at all and have had to have their drive motors replaced

Any source for this? Electric motors are supposed to be more stable than ICE.
I run a few things on 128 core setups and I set CPU limits to much higher than request but still set them to make sure nothing runs ammok.

I would be curious to see this discussed but your article only states that people think you need limit to ensure CPU for all pods.
Do you mean 'moniker'?
Aside from being fired and going to jail, of course there is nothing to stop them. It is kind of an illogical argument.