skysight-inc/HackerNews huggingface dataset:
If a sleeping low-latency task becomes runnable due to events (network, storage, timers) then ideally it would start running straight away, preempting a throughput-oriented task.
Well it talks about Uber varying pay (to make their market clear) in ways that some drivers they talked to find hard to predict and plan around.

And there's the section on Amazon varying delivery driver pay based on safety measurements that turned out to be buggy.
> Enterprise Database software is extremely sticky. So what I said in my original post, jack up the licensing the costs

Nope, that doesn't make any sense in my view. Let's say e.g. the cost of both MariaDB Enterprise and MaxScale is jacked up significantly. Then customers can easily switch back to MariaDB Community Server, and/or get paid support and products from Oracle MySQL, or Percona, or ProxySQL, or Pythian, or Vettabase, or Mydbops, or any number of other companies with significant experience in this exact space.

> and cut expenses

Prior to this sale, MariaDB plc already had major rounds of layoffs, discontinued several product lines, and spun off their cloud database. What do you suggest the new owner is going to cut, specifically?

> money paid is NOT going to the company

That is blatantly obvious, why do you keep repeating it? No one in this thread is saying the money goes to the company. That's not how acquisitions ever work!

> I'll point out the new CEO, while having engineering degrees, seems to be more a business type person.

Looks to me like a very similar profile to their two previous CEOs, except the outgoing one didn't have an engineering degree!
> Nobody in their right mind would choose to continue losing money.

In isolation, sure, but losing money in one area to make money (or some other form of currency such as fame) in another sounds a lot more reasonable. That's what a loss leader is.
I've heard people argue for this strategy a few times but I am not convinced. Most projects I work on have feature branches that get squashed into a single commit (erasing the history of the branch). If we even have the case described by the author we would just do the three steps (refactor, new api, update) as 3 commits.

One thing that has been a solid practice for me is to avoid long-lived branches. That seems to be what leads to this kind of multi-stage commit scenario. Someone wants to work for several days (or worse, weeks) on a feature and then drop the whole thing all at once. I strongly prefer to move things into main every day (or multiple times a day). One way to do this is to use feature flags to allow work-in-progress commits to land without causing problems. This also has the advantage (if systems are set up correctly) to enable on dev and staging environments for testing. It is also a hop-and-skip jump away from blue/green rollouts.

I don't want ways to make big commits easier to review. I want to force the team to commit small changes early and often. I understand not everyone agrees.
If you want to try your hand at violating Bell inequalities, there are widgets in [1] that allow you to input strategies (as javascript) for Alice and Bob. It continuously performs Monte Carlo sampling of the strategies and presents their success rate.

There's a classical-only widget, that goes through quite some contortions behind the scenes to prevent cheating via writing to global variables, and a quantum-allowed widget where that kind of cheating is possible due to the underlying implementation cheating in precisely that using-globals way in order to correctly simulate the quantum mechanics.

Anyways, I've had a few people tell me playing around with the widgets helped them understand the inequality.

[1]: https://algassert.com/quantum/2015/10/11/Bell-Tests-vs-No-Co...
Don't know about developing countries but in the US (Boston) I have encountered cabs with the rear door lock mechanism broken so that we couldn't get out until the driver unlocked the doors. Luckily I wasn't by myself but it was creepy.
Again, no non mobile OS prevents native applications from using the clipboard as it should be used. And none of them show any signs of changing that.
Which would be perfectly fine if you made this completely transparent and made the same information available to your applicants. Them not knowing the market rates (at least not even remotely as accurately) puts them at a significant disadvantage and you can't expect that most company won't exploit because it would be irrational to do that.
It isn't the interviewing.

I conducted around 500 interviews at my last company at all stages: initial screen, technical, architectural, etc. There were simply far more white men applying. (And this is in Atlanta where we have a highly bimodal racial distribution.)

It wasn't like we weren't bending over backwards to attract diverse candidates. I personally went to HBCUs on outreach programs, and there were dozens of annual Girls / Women Who Code programs and partnerships that other folks on my team participated in.

I was once even told I couldn't recommend someone for a role because they weren't diverse.

Look to undergraduate enrollment.
Inverter and batteries had long since been swapped out. I was about the fifth person to use the panel. I was staying with some original back-to-the-landers who had purchased the panel along with several others around the time it was made. They swore by Outback Power for their inverters, though I own and like an awful lot of Victron equipment now.
Makes sense – thanks for the explanation and for ripgrep.

Personally, I love this default and find it way more usable than grep in most cases. It’s a more important feature to me than the per-file search speed, since grep is often fast enough.
Which model did you get? IIRC their slide in units are actually made by Bosch, but the standalone ones with the physical dials are actually made by another company, and were generally considered worse.
Eugh pdfs. Even worse, the first one I tried was a scanned PDF, though they had at least run it through OCR.
Simple is good but another approach to simplicity would be more sensors (weight, thermal, steam, optical?) and a single "cook" button (or a menu/dial with few different cook options, defrost, warm, hot).

For casual use the UX is superior as it requires less micromanagement. Also lot more difficult to engineer well, though.
My question was genuine, not just rhetorical. I appreciate the additional context here, especially that Win32 is implemented as a long-lived NT personality. It's indeed a bummer that Microsoft didn't see it as expedient to maintain the others or continue to grow WSL1.

Windows Services for Unix was also longer-lived than I'd realized. Was that just before its time or did it have some other problem?
I've read - because if a user uploads content that gets you on a list that blocks your domain - you could technically switch user content domains for your hosting after purging the bad content. If it's hosted under your primary domain, your primary domain is still going to be on that blocked list.

Example I have is - I have a domain that allows users to upload images. Some people abuse that. If google delists that domain, I haven't lost SEO if the user content domain gets delisted.
My question wasn't about the day rate it was about the number of days, ie is it variable or fixed for each type of offense.
> the human body simply can't do productive work in that type of environment

investor appears

Investor: "But 10x'ers can"

/cape

investor disappears

Founders: "Whoa"
Man, I cofounded 3 companies (2 bootstraped & 1 VC backed) and I never expect employees to work 7 days a week.
From my cofounders I did expect that when there is really a deadline to hit (usually a big customer changing his specs on the whim, security bugs or infrastructure migration/upgrade)

However if "the founder" works less that his employees, you should start looking for a new job right away. This startup most probably won't gonna make it and to swap your limited time to work for them is a bad choice. Even if they pay you very well with investors' money it's best to be in a succeeding company and build the relationships that will give you chances to cofound/rise with the company growth.
The author already has a branch and its commits. What then would be the purpose of splitting the branch into three pull requests with one commit each?

- Each commit can be reviewed on its own

- Dependency tracking between commits? Yes...

- They don’t have AI built-in (a good thing)

- You can have an interdiff between commits unlike PRs

Commits are the bread and butter of Git. Just use commits.
We already kinda do this, old people get let out of prison if they're ill, etc.

I don't really think my example is terrible, I think it depends on what you think of as "equal". If the idea is to disincentivize an action, it needs to have a similar amount of pain to all people, presumably.
I think it's two types of defensiveness.

1. Shovel salesman insisting all "real" gold miners use their shovels

2. Those that have already acquired shovels not wanting their purchase to be mocked/have been made in vain.

Neither are grounded in reality. Why people believe their tiny applications require the same tech that Google invented to help manage their (massive) scale is beyond me.
> The 20-something founders who "grind" are not more successful.

Was there ever a consensus that 20-somethings who grind are more successful? I don't think so.

They simply do not have the requisite broad life skills that are required in business to succeed. They may have the energy, grit, a narrow set of skills and then stumble upon a goldmine product, but the combination of these factors results in what, a 1-2% successful exit rate?

As for the answer of "is it sustainable", it really depends how rich their parents are and how much they can fail upwards. Apparently, there are a lot of rich parents in the US.
I really think you've missed my point and I don't understand how.
A decision that could have been avoided entirely if any of the European or American automotive companies seriously focused on battery evs. They wasted decades.

As an American consumer, I'm pissed at our companies. I was I to building small evs in my teens, and back then the only good source for batteries was used power tool pack salvage.

They refused to let any bare cells enter the American market for years with exclusive deals. Guess who I could eventually buy them from though? Chinese suppliers.
Ah, right. The environment that's barely made a dent from the consumer/non-dev market in 20+ years of existence.
> essentially a suntan booth

Why would the booth need to emit UV light?
Circuitry (both digital and analog, including entire computers) can be built using hydraulics. Complex parts like logic gates, oscillators are present, but also "passive" things like accumulators, resistors, and valves -- it's all there.

They work in about the same way as electronic circuits do.

(But it's almost always less expensive to push electricity around than it is to push liquid around, and the parts are a lot smaller, so obviously electronic circuits are the usual winner.

Nonetheless, hydraulic circuits are still pretty common: See, for example, the valve body of an automatic transmission such as (mostly?) electronics-free 700R4.)
They should ring up Brazil......................
So what's been stopping African companies/government from exploiting their own natural resources for all of these years?

"Corporate greed" is a fun slogan, but means nothing in reality. In the few areas where the government is exploiting its own natural resources (instead of outsiders), the working and living conditions are not inherently better. If it worked that way, all of the middle east and large areas of Africa wouldn't be so destitute.
and the angular robot makeup reminds me of Stan Winston's work in HeartBeeps (1981).
I submit that most non-technical people have no clue what “squelch” means. It’s not a commonly used word outside of electronics. And it makes it sound like your radio’s output is being suppressed, which is inaccurate in this case. I think some more appropriate terms could be “party”, “group”, “topic”, “line”, or “room”.
I was probably one of the few who enjoyed Mason and still think the aggregator framework was great. We implemented a work-a-like in Java on Prime and it worked great there as well. It was effectively GraphQL before GraphQL, but local and remote, async, polymorphic, and extremely flexible. Not being in that world anymore I’m not sure if there is anything else quite like it, but there really should be.
> when one leading law firm announces salary increases and other law firms immediately match it

Because it's public so doesn't reduce the amount of bargaining power employes have and therefore distort the market. Which is the main problem here.
Worth noting that GDPR says all this crap is opt-in anyway, and everyone is just breaking the law. But the law isn't enforced :-(.
And realistically poor will always have more impact due to any fine. As they have almost always both in relative and absolute terms less disposable income. It is not like taking 9 million from someone on net earning 10 million will make them starve, but try to do same with someone making 20k and taking 18k from that...
nix-locate is actually a third-party command, shipped with nix-index: https://github.com/nix-community/nix-index

make sure to check out the pregenerated databases, they're very convenient
Had two Michelin stars.

Momofuku Ko closed recently. I went once around 2016, partly exactly because of his name and brand. It was ok but nothing memorable, I think he wasn’t even there.
I guess the closing probably aligns with his goals of maximizing a brand / money, and not actually cooking good food.
Sounds like the issue is they corrected the bug without documenting the breaking change and did it with minimal notice. Worse yet is that the API change will impact all software running on the host. So even if your distributed program works today, it will subtlety break when the user upgrades their host OS.
If your goal is security-oriented then the result will not be general purpose.
The law states all of this should be opt-in. Website operators just ignore it.
IMO this should have been included in their threat model. The only way to exclude yourself from insider threats is if insiders cannot possibly become threats.
@hansolo
From the peanut gallery of HN I’ve never understood Stacked Diffs. It looks like they reinvented commits as dependent PRs. Which are stacked on top of each other like commits are.
> DC-DC converters are not a "dead short across the input for part of the cycle" in normal operation - rather the voltage is across the inductor. If the switch stays on too long and the inductor reaches its saturation current, or one of the many other (cascading) failure modes, then can you end up with effectively a short across the input.

Right. Which is why under-designed AC-line powered power supplies can catch fire.
The failure mode of MOSFETS is usually to the "on" state, so the switch staying on is quite possible.
Can't agree.

I learned about BEGIN IMMEDIATE TRANSACTION.

And there's also busy_timeout.

The article also explains why/how/when things occur in detail which is valuable.
I am excited for the features announced. My current phone is the iPhone XS, which in September will be 6 years since its release.

Mind you, I try not to get excited for other releases when I made the decision to not yet upgrade my phone.
It's always useful to keep in mind the wide variety of HN users. For certain cohorts, the likes of Peter Thiel, Elon Musk and such are considered the pinnacle of their aspirations, and abusing workers is viewed as business smarts.
It's not a matter of opinion at all. You can disagree but you can disagree with the earth being a sphere also.

> People are building new software all the time. It all has bugs. It will always have bugs.

No. Most bugs these days are due to legacy decisions where security was not an issue. We are making advances in both chip and software security. Things are already vastly more secure than they were 20 years ago.

20 years from now, security will be a lot closer to being a solved problem.

> The only way to build secure software is to increase its cost by a factor of 100 or more (think medical and aviation software). No one is going to accept that.

What are you basing that cost on?

> Computer security is impossible at the prices we can afford.

No, it really isn't. There's a reason some organizations have never been hacked and likely never will be. Largely because they have competent people implementing security that very much exists.
If you're trying to speed run immortality, it's probably best to avoid solutions to longevity that rely on your descendants not turning you into an amusement park ride.

Lots of dead people are going to wake up in horror simulators. Or as Tamagotchi.
They also have kiosks and a web site.
> Is this TLD even worth a damn in 2024?

IMO: No. Table stakes nowadays are for all web sites to support mobile devices; the notion of having a separate web site for mobile users, let alone an entire TLD for those web sites, is obsolete.
I don't think this is a conspiracy at all, just a pretty standard case of an incumbent getting preferential treatment (why else do taxis get a reserved taxi stand, but Uber/Lyft don't?) and an "innovator" disrupting at any cost and externalizing the consequences (in this case congestion throughout the terminal and surrounding streets).

A more efficient stable state is clearly not being reached through market forces, but since there will never be agreement on whether that's due to too little (get rid of the medallions!) or too much market liberalization (ban the rideshares!!), and the only thing everybody can agree on is that a public transit solution is impossible, I don't see any way out.
Heh: https://en.m.wikipedia.org/wiki/Braeburn_Capital
just created shareable links, here's a graph of a CPI data article: https://www.graphme.dev/shared-graph/dba7ce6f-b24f-4573-a21f...
Extraordinary claims require a citation.

Edit: The parent appears to have committed the cardinal sin of believing CNN, which made this claim here[0], but cited a CDC report[1] does not support the assertion. I went looking for the underlying NCHS data, but couldn't find it.

[0]https://www.cnn.com/2023/12/21/health/nutritional-deficiency...
[1]https://www.cdc.gov/nchs/data/vsrr/vsrr031.pdf
I can't imagine how many days the author took to write such detailed article.

This is useful to anyone trying to scale SQLite web applications, even beyond Rails.

So thank you!
Hi. I'm techknowlogick, one of the two reviewers who have requested changes on this PR. A couple of clarifications:
1. I hadn't been able to continue my conversation with Kyle due to illness, and I am still dealing with it, but I am working on continuing that conversation.
2. The feedback that is holding up the PR is technical. Logging that amount of data has performance implications, and one of Gitea's main tenants is that it can run on reduced hardware. We know what impact it would have, as we are dealing with it from other tables. We don't have the ability to backport migrations to add indexes, etc.. (something that CommitGo has put a bounty on, though), so if it gets merged now and "well fix the filtering/etc.. later" means that if it gets merged then we have at least 6 months of bug reports around performance issues.
3. the code that is in the alternate distribution is different and doesn't include that PR. It is a few SQL inserts to log logins, package downloads, and git clones. 4. I am largely in favour of getting the PR merged, but if it means degraded performance and bug reports that we have to ask users to create DB indexes manually, that's something that I would hope could be avoided.

CommitGo, is the largest contributor to Gitea, and has contributed Actions in its entirety to the project. If the goal is to keep code away from the project for profit, that would be the one.

The priority of the company is to ensure the continued success of Gitea.
I concur.

I don't know why people are so happy to throw out the history. I find it's not uncommon that bugs are introduced during rebasing, and merging in from master. Sometimes this is due to incorrectly resolved conflicts, sometimes due to concurrent changes elsewhere in the codebase.

With --first-parent it isn't hard to have your cake (full history) and eat it too (linear mainline history).
The CIA is a symptom rather than the problem. The CIA simply reflects US foreign policy. This isn't a political issue either because you'd be hard-pressed to find a difference between Democratic and Republican administrations when it comes to foreign policy.

The so-called War on Terror and the invasions of Afghanistan and Iraq persisted through 4 presidents, 2 from each party. Both parties are neoliberals.

Abrahm Lincoln [1]:

> Labor is prior to, and independent of, capital. Capital is only the fruit of labor, and could never have existed if labor had not first existed.

sounds an awful lot like Karl Marx and the Labor Theory of Value [2]. So what happened? The two world wars massively increased US wealth, power and influence [3] and there was also the Red Scare, particularly after WW2 (although there were concerns about communists prior to that). The Red Scare (and Reagan in particular) destroyed the labor movement in the US. Now we people who champion tax cuts for Jeff Bezos. That's how successful the propaganda has been.

What's clear is the capitalists will side with fascists to destroy socialists and communists. Every time. Fascism is capitalism in crisis.

Why do I bring all this up? Because when you make a materialist analysis of historical events, you see the US acting in the interests of capital owners every time. So after WW2, with the red Scare, who was good at fighting communists? Nazis obviously. So is it any surprise that Nazis ended up in the command structure of NATO? Not in the slightest.

So there's no reforming the CIA in the current system. The entire system is corrupt. And the only antidote is class consciousness and class solidarity. Any polarization you see in modern politics is merely a tool to prevent class solidarity by workers. Racism was fanned in Reconstruction to avoid unity between freed slaves and poor white people. Race, religion, sexual orientation, gender identity, the middle class (as distinct from the "lower class"), whatever it is. There's always some manufactured culture war nonsense to keep people divided.

Until people realize they have more in common with their fellow worker than they do the guy who owns the warehouse they work in, nothing will change.

[1]:https://www.cooperative-individualism.org/lincoln-abraham_on...

[2]: https://en.wikipedia.org/wiki/Labor_theory_of_value

[3]: https://archive.is/QxfjL
I thought it was a pretty good list of common Rails-application-specific and sqlite3-specific knobs to turn, for newcomers to performance tuning. (Really just a guided tour though -- turn this knob to enable this particular tool for dealing with concurrency problems...)
>Huh, this tacit collusion being legal thing is mind boggling.

Not really ... If you're looking to hire workers in a particular region, how do you know what a competitive wage is? Well ... you look at what similar firms are paying their workers. How do you know what similar firms are paying their workers? You read surveys, industry reports, public statements, etc.

Nothing about any of that means you cannot offer a higher or lower salary for the same position.
> Is this company not actually making the market more efficient and transparent

No, not at all. Unless applicants/employees get full access to the same information.
Show HN: I made this simple retro blog/personal website with Firebase
I made this really simple retro blog which you can join with your google account to post, say hello!