skysight-inc/HackerNews huggingface dataset:
We use pull requests to spin out ephemeral environments and test the changes before merging to trunk.

All merges to main is deployed across environments so pull requests help us get faster feedback if something fails.

I think pull requests get a bad rep because it is thought as a review process. We see them as short lived branches. They actually improve code quality and unwanted commits even without manual review/approval.
So, I take it you're familiar with the history between those two then, and you're ignoring it for some reason? ;)
"Their horses are their livelihood. Now cars could take it away."

Change is the only constant, folks.
Can't really blame the user when every (software) license agreement they have to click on also has more than 50% all caps. It's a form of fatique.

Even as a technician i stopped caring about all caps and the license agreement. It boils down to two choices "You want to use this? Click yes and agree on things you don't understand" or not use it at all.
The capitalization reflects terms of art in the C++ 11 memory model. So, not my "true definition" but the one provided by the language used, in this case C++. This matters because Haiku is written in languages which use this model (or in some cases languages which don't specify any model but in practice conform to the C++ 11 model)

If you're Linus Torvalds you can insist compiler vendors adjust things as you prefer to some extent, thus the Linux memory model isn't quite the C++ 11 memory model despite the fact that GCC is used to compile Linux and GCC notionally confirms to C11 (and thus has the C++ 11 memory model), much of what Linux does is not conforming to the ISO document. Haiku can't expect the same benefit of the doubt.

The question of whether Haiku needs sequential consistency where it has it is vexed. Hyrum's law applies. The least scary approach might be to follow C++ and provide sequential consistency by default with an opt-out, then introduce use of the opt-out carefully.
I think it's important to take stock of what you have, and especially if you subscribe to the butterfly effect way of thinking, realize it would all be gone.

For example, I have a wife I couldn't imagine living without, and a child who fills my days with laughter. I've been married twice, so this isn't a case of not knowing what's out there, but appreciating what I have now. I have a nice enough house, my health, a vehicle, even a fun little dog.

So any vision of an alternate path would have to exclude all that. Maybe it would be better even. Maybe it would be far worse. I wouldn't trade what I have for a billion dollars, so that removes most of the financial incentives, I guess.
I’m not a publisher/journalist; I don’t have any posts. I’m a historian and archivist. And in those roles, I care about being able to retroactively access data that neither publishers nor relays considered to have value / be worth preserving at time of publication, but which instead was preserved due only to the “accident of history” of them publishing in a durable medium. Compare and contrast: digitized newspapers available on microfiche.
> Compilers already solve multiple NP-complete problems in the course of compilation after all, for example register allocation.

The NP-complete problem is optimal register allocation (through graph coloring). Register allocation in itself is not NP-complete. You can always use a suboptimal but fast algorithm because optimizations are optional. On the other hand, type checking is not optional, so having to solve a NP-complete problem for that would indeed be problematic.
anyone else wondering CHI is cardholder information
True enough. However, unlike a password, you can’t take a hash of it and thus reduce the consequence of exposure. It’s just another shared secret, albeit one that doesn’t rely on the fallibility of human creation.

The only good solution is WebAuthn and related technologies (phone passkeys for disaster recovery), so that server side needs nothing more than a public key.
Both of those probably coincide with the practices of fire and cooking, which meant our bodies could more easily process calories, better regulate temperature (humans aren't the fastest but they can run for hours because of temperature regulation), and need less of a digestive system.

Personally I think aesthetics and whatnot became a bigger factor in our development over time, that is, preferring partners with less hair so it was "bred out".
I didnt downvote you and agree with your general point, but consider that maybe downvotes came in due to your tone rather than your meaning. I actually normally would
downvote a comment written like yours was, just less so when I think it's making a still-important point (but you're less likely to convince anyone your point is important if you annoy them rather than try to enlighten them!)
The Watched Kettle Effect.
I think you forgot a “don’t” in your first sentence.

Agree btw, all these “basic functionality” cookie consent toggles are FUD by marketers who want to confuse you into giving up.
The product will degrade and customer service will worsen, but all RH's institutional/government customers will stick with them anyway because they have policies mandating the use of RH. This will cause RH to be more profitable, and their execs to get bigger bonuses.

It is possible (but certainly not guaranteed) that eventually, after years, some competitor to RH will arise and get enough of these customers to switch to make a real dent in RH's profitability, but by then the execs will be long-gone and cruising on their yachts.
1) When was the last time you fixed networking issues by turning on IPv6?

2) When was the last time you fixed networking issues by turning off IPv6?

For me, the answer to 1) remains "never", the answer to 2) is currently "Late winter"
You forgot the </sarcasm> tag. Or are you actually serious with your comment?

GCC supports various "flavors" of C, including fully standard compliant versions.

GNU extensions are all documented.
Sorry to hear you had this experience, I would say its worth giving another go maybe you can check out the IRC first to check the vibe before committing.
I understand pico is cheap, versatile and overall convenient.

But is there anything (besides time) stopping you from implementing this on top of e.g. linux gpio?
Interactive Mutation Browser
I saw it. Scary stuff. It is probably going to get a lot worse. For instance, here we have already had plenty of crimes involving crooks pretending to be police officers in phone calls, and they've already been quite successful in fooling elderly people to release their bank credentials, etc.
To be fair, some of them exist in PostgreSQL because it tries rather hard to conform to the SQL standard.
> Large organisations systemically overestimated the risks from bias, and underestimated the actual AI risks that society actually cares about.

The point of large organizations working on AI/LLMs/whatever is precisely to reduce labor costs by reducing the number of human workers and replacing them with AI. Why should they care about this in their development? (I'm not saying it's the right thing to do, just stating the facts about capitalism)

It is the rest of society that has the interest to fight those changes back.
a) Making artificial replikas and testing them out lets us learn something new and it is an interesting area for research

b) Artificial leaves can be "painted" on continuous surfaces anywhere. E.g. on the foots of beds, inside the walls, doorstep, perhaps even luggage…

c) Artificial leaves require less care and maintenance than bean plants.

Come to think of it I don't understand at all how would you use actual live bean plants to protect a home from bedbugs.
This is how I see the pull request example with credit cards and traveling.

You are on your way to a conference. You are at the airport and want to buy a coffee and a donut. You make a request... You've been waiting for almost an hour now. Nobody takes a look at and you still need multiple approvals, so you ping Barbara in charge of approvals to get the ball rolling, she says she will take a look after a meeting she is currently attending because she wants to be careful with what she approves. Oh, Tom, her colleague asks you why don't you eat salad and orange juice, it's cheaper and faster. You have a quick call with Tom to explain why you want a coffee and donut. Awesome, you convinced Tom to approve in just under 20 minutes. Barbara is back, but she doesn't respond... She is MIA, she went for breakfast... Your plane is leaving, so you skip breakfast. You arrive, by the time you land Barbara approved your breakfast, but now you are in a new country and circumstances changed, so you update your request. The earlier approvals are now invalid. You go through the whole charade again...

Pull requests assume you cannot trust your colleagues to make reasonable choices and you also don't trust your automated tests to catch anything insane (buying a 100k car for breakfast in the above example), so you have to gatekeep and slow down your team to make sure (?) that the code they commit is good.
Defaults matter. Making Google the default everywhere will cause people to stick with Google, for the most part.

Why is it legal for the monopolist to pay other companies to help it keep its monopoly? If Google couldn't pay Apple or Mozilla to make Google Search the default on their respective browsers, perhaps we'd see other, better defaults, and maybe people would continue using those defaults, eroding Google's market dominance.

> But "being the default choice with a trivial switch possible" is hardly an abuse of power.

The ease of switching isn't all that matters. I suspect if you polled a representative sample of people, they would tell you they believed that Google is the only option for web search. At best, some might admit they've heard of Bing, and then only because it's been the default for IE/Edge for years.
I always wondered whether bedbug == flea (which jumps). You squash flea and they are no more... I suspect its a different thing, as it appears bedbug swarms.
I sure have, I live here! Tried to pay for my croissant and juice in Penny Markt just this morning, i trid to test paying with my credit card and got the usual "Keine ausländische Karte!" :-)

And dont even try using a card in a restaurant or a bar, the terminal always, and i mean always just happens to be "broken" at this particular time.
Intel Let Google Cloud Hack Its New Secure Chips and Found 10 Bugs
Isn't China's https://en.wikipedia.org/wiki/South%E2%80%93North_Water_Tran... is the biggest?
PostgreSQL has been around for almost 27 years (and even longer, if you include the Ingress and Post-Ingress eras). And things, well things, they tend to accumulate, to quote Trent Reznor, heh.

On a related note, one could say that the C++ Core Guidelines[1] at least partially represent such a list. 55 matches for “don't use” and 247 for “avoid”, although not all of them are about language features, obviously.

[1]: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines
Generative AI can make some workers a lot more productive, according to study
b) Artificial leaves can be "painted" on continuous surfaces anywhere. E.g. on the foots of beds, inside the walls, doorstep, perhaps even luggage…

Mmmmhmmm.

It's basically like flypaper and they get stuck and die. Who would want products with the ability to kill bugs in a manner such that now they are permanently covered in dead bugs?
IPv6 is pretty great. You don’t run out of numbers locally, you don’t run out of numbers globally. Most software and OSs just support it these days… many embedded things still don’t.

I think the biggest pain point with IPv6 adoption is probably the large number of customers with a little netgear router that doesn’t know how to pass IPv6 through it. I also think local administrators that still purchase stuff that doesn’t support IPv6 are just shooting themselves in the foot. After all, the writing has been on the wall for over two decades.
A Cookbook of Self-Supervised Learning
Who interpretation carries significantly more merit that any of the commenters here.
Currently China is building a new project: https://en.wikipedia.org/wiki/South%E2%80%93North_Water_Tran... which I believe is larger.
> "Pull requests were invented to gatekeep access to open-source projects. In open source, it's very common that not everyone is given free access to changing the code, so contributors will issue a pull request so that a trusted person can then approve the change.

> "I think this is really bad way to organise a development team.

> "If you can't trust your team mates to make changes carefully, then your version control system is not going to fix that for you."

Man, I don't trust myself to be perfect. I trust myself to be careful but no amount of care makes me infallible. I make mistakes. And if we can catch my mistakes early by getting a second set of eyes on them, they're less painful for everyone to fix. When someone spends their valuable time catching my mistakes, they're doing me a favor.

Distrust might be part of the origin of pull requests, but that doesn't have to be the reason why your team uses pull requests. It can be about catching each others mistakes to learn, create a better product, and get better rewards. The tool is yours to use how you see fit--don't let ego prevent you from making it useful.
You're welcome & much good luck with your project!
I think one potential improvement for PHP is to make PHP templating usable again. This is something that could have a low cost of implementation but a big win.

Example on improvements

1) auto-escape output - one of the biggest reason not to use PHP for templating is that you need to manually escape your strings to avoid XSS, whereas a dedicated templating library can do this for you. This could be done with a either a special opening and closing tag or let you register a tag hook.

2) today you can use the alternative syntax for if, while, for, foreach, and switch

https://www.php.net/manual/en/control-structures.alternative...

This could be expanded for match expression, closures, and other block expressions.

3) custom HTML tag support, register a HTML tag like <my-form> and implement it thru an API, perhaps a class that implements an interface. And now you can do much better reusable components that can automatically close them selves instead of multiple calls.

e.g instead of

<?php open_form() ?>
<button type="submit">Buy</button>
<?php close_form() ?>

you can do

<my-form>
<button type="submit">Buy</button>
</my-form>

In the first example you need to always match one function call with another function call ( manual work), in the latter example you HTML just needs to be valid, which many editors can detect for you.

And it would be easy to share these custom components on github with composer.
Not so fast. The court affirmed the following-Epic can direct users to a website for alternate payment. But they left it ambiguous on whether Apple is entitled to compensaton at 30% of revenues. The courts (both district and appeals) seem to believe that Apple is entitled to some compensation under IP compensation theory.

So, if the Netherlands dating apps case ruling is any indication (Apple discounted the 30% to 27% for dating apps in Netherlands for using alt payment methods in that suit), Apple is likely to do something similar here in cases where their In-app-payments are not used.
Is this a genuine question? To ask this must mean you either don't realise all the tracking that is happening via your phone and web browsing unless you explicitly block it or you explicitly block every possible opportunity to be tracked and put continuous effort into staying anonymous. In the case of the latter, you know the answer because it would simply be not spending that time and effort, which isn't the top priority of most people, nor should it be.
Leaves need to be replaced regularly. You'd have to transport them to places where you can't grow them. I'm not even sure it would be a benefit for the environment.
This may be irrational but it's something that worries me about using postgres in production. Sure as a developer I love all the features, but the fact that the query planner can suddenly decide on a radically different (and incredibly inefficient) query plan makes it hard to trust. In some ways, a dumber query planner that needs coercing into the right query plan is more reassuring, in that you know it'll keep using that query plan unless explicitly told otherwise.
>Who would want products with the ability to kill bugs in a manner such that now they are permanently covered in dead bugs?

E.g. people who use flypaper.
A huge improvement over having alive bugs there.
Tolerating Malicious Majorities – Advances in Distributed Consensus
A possible reason is that it won't happen in git, simply because separate branches aren't sufficiently painful to motivate sharing that single hot mess HEAD. I used to work in a team where it felt like I was the only person who ever thought about these things and it was quite impressive how the switch from SVN to git completely flipped the path of (supposedly) least resistance: from separate branches only as a last ditch option for the most desperate situations to happy unbounded parallelism right until the (supposed) delivery day.
Exploit released for 9.8-severity PaperCut flaw already under attack
A pull request is when one maintainer asks another to merge branches.

If you’re interpreting this through the lens of a single main/master/trunk and multiple branches, then like both Farley and the author, you’re trying to interpret a foreign culture (distributed version control) through a parochial lens (single trunk-multiple branch).

The DVCS world is one of many sources of truth. For example, in the kernel community, Red Hat, Google, Debian, Android, etc. all have their own branches. Linus has a particularly popular branch. None of them are the main branch.
People who use flypaper are using a disposable product that gets thrown out.

That's fundamentally different from "your bed or luggage now works like flypaper."
it's one of the first things that a data scientist friend of mine asked.

Featurevisor SDK is stateless, in the sense that it evaluates features against given attributes and the content of the currently parsed datafile.

if we want to have native support of exclusions in the SDK, it has to become stateful on its own. either in memory, device level, or having a backend service that's aware of the session to go cross-device.

therefore, it currently does not support it. but I am open to exploring an API for it in future.

as a work around, what can be done for now is to track manually whenever a feature is activated (SDK has onActivation handler), and then pass that knowledge as an attribute when evaluating another feature. The second feature can then have a `not` operator in its segments to exclude itself in that case.

Links that can help:

Activation: https://featurevisor.com/docs/sdks/#activation

`not` operator: https://featurevisor.com/docs/segments/#not
Biogas Reactor from Human Waste
Was the startup successful? :)
No, it's not?

Bedbugpaper can be just as disposable.
I do know I don’t have to install an alt-store that is going to let its apps track my very soul if I need to install a popular app.

E.g. imagine Google rolling their own Play to install Chrome or Maps. Facebook for Whatsapp, Amazon for Kindle et Al, Netflix for its own… etc etc.

No the moment that happens it’s over
I hope the EU learned from this extreme and obvious malice and won't let them get away with something like this in the Digital Markets Act.
There's the hoary old cliche about "if I was given three hours to cut down a tree with an axe, I would spend the first hour sharpening the axe" but in many cases it's really true. You can look like a superhero just by pointing out some small feature that makes life easier.

One time I pointed out that, rather than reordering the tables to make loading work with foreign key constraints, we could pause trigger execution, load all the data, and then resume the triggers. pg_dump can even do it for you if you pick the options right (might be default), in addition to natively ordering the data correctly, but if you're messing around with large SQL files anyway, it's helpful..
What do you do if you need to check index ideas, or new table design?
In a perfectly competitive market products are basically the same and cost basically the same.

The fact that the Play Store is similar to the App Store doesn't mean it's not competitive
> why don't people usually work as hard for themselves as they do for these exploitative systems?

Choice.

They don't have a choice about getting up and going through the M-F slog. They have to so that they can afford to live.

For personal projects, people have choice and can weigh in all of the other things their lives need. Including recovery time from the M-F slog. Their contributions to personal projects are not coerced.
The Switch is not a substitute for an iPhone or Android phone, and I think this perhaps illustrates a problem with how we think about this issue.

Sure, if I have an iPhone or an Android phone, and I don't like the gaming landscape on either of those, I can get a Switch. But the Switch doesn't replace my phone. I can't toss the phone and now carry a Switch with me everywhere. (I also wouldn't want to carry a Switch everywhere; it's nowhere near as portable and doesn't fit in a pocket.)

So is it ok for a company to abuse their market position, if a consumer has the option to buy an additional device made by a competitor, and then have to lug around two devices, since the other device doesn't actually replace all the functionality of the original one? I would say no, it's not ok.
Can I ask why? I generally only see the “I switched from MySQL to PostgreSQL and loving it” comments in my info-bubble, so it'd be interesting to know what people who prefer to use MySQL feel is still lacking in PostgreSQL.
No *durable* (i.e. doesn't expire in a week and need to be refreshed) sideloading is the no.2 thing keeping me off iOS. The no.1 thing is that I find the entire user experience frustrating, inflexible, and frankly condescending. 3 would be that I can get 2-3 decent Android devices for the cost of an iPhone, so my phone-having-time per € works out about same-- plus I still get to upgrade every couple of years.

I get that people like their iPhones. My wife is one of them. I'm not. People are different. Choice is good. Some folks choose to cede control in favor of simplicity. Go off.
> in the UK rental apartments are not maintained and people are systematically evicted for asking repairs.

Really? That sounds insane. And totally illegal where I live (Germany). Got any source on that?
Only "oxen", "children", "brethren" ? What about "VAXen" ?
I cannot agree more with this, especially for organizations with incompetent management…
Check out this hotel: https://www.youtube.com/watch?v=J4aTcU6Fzoc
productivity will explode. check this one: https://chabotix.com/. a chatbot for your website, works with your documents, no coding required but just a simple text file upload. all powered with chatGPT.

i think all software players will be impacted dramatically. if anyone can produce product much faster, it will be even more challenging to stay afloat when you have only software products.
I think we have GH set up so we can make direct pushes to even main, we just agreed to do PRs because frankly I don’t even trust myself to do everything right and optimal. PRs are nice for reviews, but also for testing and discussion, sometimes just to share something you are not sure if it is the best. It’s just a way to present changes to people just trust (or don’t) and to have a place for discussion.

That’s how we treat PRs anyway. Occasionally I or a colleague indeed accepts their own PR (or use direct pushing) if it’s really minor (think a doc string) and need to get something out. So PRs are not just for envs without trust.