skysight-inc/HackerNews huggingface dataset:
A glycol/water mix is almost always chosen primarily because of the anticorrosion purposes and freezing point alteration.

If you have a racing car you run pure water with a bit of 'wetter' (a surfactant) in the cooling system as it gives you the highest thermal capacity / cm^3 ratio. If you want to increase the boiling point (to run a smaller heat exchanger) that's most trivially achieved through pressurisation.
What if they connect the amount paid to the years of experience? For example, you pay less to view a student's profile and more for a top professional.
Im still sitting out the Mx Air. But the MacBook Air M3 may end up being too expensive, so I may sit that one out as well.
I have seen so many React code bases that are the polar opposite to "clean, manageable code" that I would strongly disagree with this premise.

That's not to say React is to blame, per se, but good code is the result of good developer practices rather than some framework.
The key replay attacks only work on very very certain very very very old vehicles.

Seriously the myth that key fobs are sooo insecure, they aren't.
> You don't have to be a gun nerd to know that a gun that comes standard with an attached bayonet is materially different from a rifle designed with deer hunting in mind.

I'll bite - what are these relevant material differences?

You seem to think that "designed" is important but is that a material difference by itself? If so, how does that work? Is that true for anything else? (There's a lot of cross-over between other outdoor equipment, such as vehicle drive systems, clothing, and shelter, so ....)

If it's that the intent results in other differences, what are they?

It's not the ammunition. It's not how the gun functions. (Yes, the SKS is supposed to be more tolerant of rough handling than most guns, but the AR-15 is less tolerant.) Surely it's not appearance....

Yes, people tend to shoot back, but what material difference in gun design/function is a consequence of that?

You contrasted deer hunting with shooting people, but how are they appreciably different at the same distance? (The obvious difference, that the military prefers wounds to deaths, works against your conclusion.)

.223, which is what the AR-15 shoots, isn't legal for deer hunting in some jurisdictions because it isn't powerful enough. 7.62x39, which is what the SKS shoots, usually is legal for deer, because it is roughly equivalent to the ancient 30-30. However, typical deer rifles are significantly more powerful. (Of course, people do hunt things other than deer.)

You seem to think that a bayonet is important, but are bayonetings a problem? If not, what material difference does a bayonet make? Does that difference persist after the bayonet is removed? If so, how? (I ask because the first thing that most people do with an SKS is to remove the bayonet.)
This is a very fun thing to do, unfortunately where I work (France), the HR team send out weekly/monthly emails with somes HR updates, and at the end the list of everyone who is hired (this includes conctractors), and everyone who leaves (resigned or fired), so it would not add any information to run LDAP searches and dumps/diffs.

It's always kinda stressful to open this email and find out if one colleague you liked has decided to leave, but most times, this colleague informed you before the email arrives.
> has a test suite with 100% branch coverage

Is actually even more than that, has 100% MC/DC coverage [1], which is something that is not easily achievable for most projects.

[1] https://www.sqlite.org/testing.html#:~:text=In%20this%20way%....
I don't know what to ask you in a public forum, but it's nice to see your name pop up!
Because I didn't know what resize bar is, and the link doesn't talk about what it is.

https://www.intel.com/content/www/us/en/support/articles/000...

# Description

What is resizable bar? How do I enable it for my system?

# Resolution

Resizable BAR (Base Address Register) is a PCIe capability. This is a mechanism that allows the PCIe device, such as a discrete graphics card, to negotiate the BAR size to optimize system resources. Enabling this functionality can result in a performance improvement.
> For a company that has a declining marketshare like Mozilla it's really way too high IMO.

Everyone talks a lot about market share but I never saw the breakdown of the market in terms of what is actually reporting the user agent. For example, both Chrome and Edge provide embeddable webviews used by applications to put together their GUIs, while Firefox doesn't. Other competitors such as Microsoft also pushes Edge very aggressively in a way that to me seems ethically questionable. Chrome leverages Google's control over some apps and features to be pretty much the only browser that is able to render some pages.

To me, Firefox is undoubtedly the best browser out there, and the only reason I see people use any other browser is inertia and not having control over their OS to change defaults. So what's the argument on market share?
When someone says "build their own chip" they do not in general mean to extract their own silicon ingots from sand, or to build their own fab. They mean to "tape out" their own SoC design and send it to a fab owner such as TSMC, Samsung, Intel for the physical manufacturing step.

Apple does not own a fab. Arm does not own a fab. Qualcomm does not own a fab. I believe IBM does not own any modern fab (some built in early 2000s, yes).
Because people like you intentionally misinterpret and misrepresent what actually happens in Europe.
In 1991 "artificial" probably meant something like "pre-recorded and re-cut". Which is basically AI voice generation, but at scale.

>Do you think this is an unreasonable interpretation? Or should Congress be required to list exactly what technologies are prohibited in this context and update that list every time something new comes around?

Not OP but this is the right question to ask. My answer is yes, congress is quite literally required to update statute to reflect modern technology (ensuring it conforms to the founding principles of course).
You just described every single sit-down interview between a reporter and a politician.
Really not ironic at all unless you think the leading authority snails or planets needs to be a snail or planet...
What if they make some basic info visible? E.g. role, company, and university. Similar to those headlines.
The example with IEF doesn’t make sense. Whether you declare a function private or public doesn’t impact its usability as a gadget. And as I understand it reading up on IEF, the problem with removeDatabase is when it’s exposed as a remotely callable API without any auth check which is a very different problem. Am I misunderstanding what the author is saying?

I think the main problem with the article referenced in the submission is that percentages of vulnerabilities change based on the problem domain. The main threat for web facing services isn’t memory safety but that’s because most web facing services already use memory safe languages like JS, Java/JVM, Python, Ruby, or Go. It’s weird to pick Rust for its memory safety for web services. The reason to pick Rust is because you get C/C++ like performance without the memory safety issues. If you don’t need the perf, all the other languages are better choices because you’ll probably move quicker.

It’s interesting that 20% are still memory vulnerabilities. Assuming this is all the same class of attacks on web services, that means 20% of applications do care about perf and have exploitable memory safety issues. Or the methodology is shoddy and they’re comparing different classes of software. Regardless, the premise of the first article is flawed and rife with statistical analysis problems that paint a misleading picture while the response isn’t infusing me with a lot of confidence on the merits and comes off as unnecessarily fanboish trying to stretch for a reason of “but no rust still makes sense”. 70% of vulnerabilities in Chrome are memory safety. This holds for similar classes of software written in c/C++ (eg Windows). There’s a reason all major c/c++ codebases have started getting grass roots and organizational support to transition away as quickly as possible.
Lot of focus on mpg here. I couldn’t even tell you what the mpg on any of my 3 bikes is. It’s so unimportant to most riders.

Most interesting to me is the Ninja 7 smoking a zx10r, for a few hundred feet off the line, granted. Picture of exciting shit to come perhaps.
The plots for Chicago and Washington DC are also wrong. They both have lots of diagonal streets.
The key to spice trade is TINA - There is no alternative - in financial terms. The largest form of investment in Middle Ages had been farmland with average ROI of c.a. 7-8 percent but no guarantee (wars, diseases, crop failure). The ROI of spice trade was 200-300 percent over similar period.

So if you wanted double you capital it was either spice trade or investing in land for 20 years.

And the cost? It is like asking Citadel about their servers costs....
I can't think of any other magazines that are likely to host articles such as ' “The Universe Wants Us to Take Her Clothes Off” With Grimes ' sorry
I like the quote, but except this bit which is terrible, and undermines it all:

> Yet it is admirable to profess because it was once admirable to live.

Living is still admirable. Professing without living is just so many words.
A quote from discord: "apparently alpha-zero has been replicated in open source as leela-zero, and then leela-zero got a bunch of improvements so it's far ahead of alpha-zero. but leela-zero was barely mentioned at all in the paper; it was only dismissed in the introduction and not compared in the benchmarks. in the stockfish discord they are saying that leela zero can already do everything in this paper including using the transformer architecture."
> If Firefox is destined for a market share of 2%, may as well get there quickly. A few years of decline vs a few months makes little difference in the long term.

How does that play into your decision to use Firefox or any other browser? I'm a Firefox user and I care nothing about market share. I get annoyed if I stumble upon a page managed by incompetent devteams and thus only runs on Chrome, but that's a quick in-and-out.

Why do you care about share? Why do you feel it's relevant, specially if people are pushed to use Chrome or Edge through unethical means?
> leads me to believe that such cars had negligently insecure encryption

While accurate, the standard may not be as rigorous as you'd like to imagine; there was a time not long ago when a wire coat hanger was enough to unlock a car.
go out on the side of mountain and dont think of work and let your mind wander freely.
But a museum doesn’t ask you to “buy” an exhibit… The misleading aspect of digital “ownership “ is in the use of the word buy.
There's probably nothing wrong with Crunchyroll if you're into the content it provides. The article is about Sony removing the digital copies that buyers of Funimation DVDs/Blurays purchased together with their physical media - and the article argues that some may have discarded the physical media because they have (had) convenient access to the digital copies (hint: don't do that!). But yeah, this is another instance where people who forked out their hard-earned money for legal copies of media are screwed and might be tempted to think "why didn't I simply download a pirated copy?".
I have the most respect for this country
Do you have a source on Mistral API, etc. being based on TensoRT-LLM? And what are the main distinguishing features?

What I like about vLLM is the following:

- It exposes AsyncLLMEngine, which can be easily wrapped in any API you'd like.

- It has a logit processor API making it simple to integrate custom sampling logic.

- It has decent support for interference of quantized models.
Remember that when the Apple Watch came out, it had a feature that let you send doodles to other people? No one quite knew what the watch was going to be for at the beginning either.

(Counter point: At least it could also function as a watch)
Yeah, right, I reckon we understand one another. As they say 'it takes one to know one'. ;-)
For me, it's the stories of "how IT jobs suck" but it's not that IT jobs suck it is due to where you live.

Also the misunderstandings of how things work here.

OP said "Layoffs in the WFH era are weird"

Yes they are, but people here don't suddenly go offline quite as weird is what I was trying to get at.
Good idea. Though I think the fact that they trusted the departing person, and the departing person delivered -- if it plays out that way -- is much more positive message than effectively implying that the company didn't trust the person.

The company letting a manager relay a message, with any censoring, is certainly better than the person having no way to get their contact info to people, and they might also say something nice for morale.
I guess that the solution to this problem can be automated. The DB or an extension to the DB or application code can run the query without hints sometimes and compare the result with the version with hints. If the hinted version is still faster, good. If it is slower, it's time to tell the DBA. Or switch to the unhinted query automatically if it's faster for a large enough number of times.
Yes please. That's the peer review of my dreams. What an extraordinarily valuable resource that would be.
Also think how much GDP AGI and ASI can create.
Fortinet Avverte di una Grave Faglia nel FortiOS SSL VPN e l'Urgenza di un Aggiornamento

Fortinet ha recentemente rivelato una vulnerabilità critica nel suo sistema FortiOS SSL VPN, identificata come CVE-2024-21762, con un punteggio CVSS di 9.6, indicando il grave rischio che essa presenta. Questa faglia di sicurezza consente l'esecuzione di codice e comandi arbitrari, ponendo a rischio la sicurezza dei dati e dei sistemi aziendali.

Secondo quanto dichiarato dall'azienda, questa vulnerabilità è molto probabilmente sfruttata attivamente nel mondo reale, mettendo a repentaglio numerose organizzazioni. Sebbene non siano stati forniti dettagli specifici sui metodi di sfruttamento e sugli attori coinvolti, è chiaro che l'aggiornamento dei sistemi è cruciale per mitigare i rischi.

Le versioni interessate dalla vulnerabilità includono FortiOS 7.4, 7.2, 7.0, 6.4, 6.2 e 6.0. Fortunatamente, FortiOS 7.6 non è affetto da questa falla. Si consiglia vivamente agli utenti di queste versioni di aggiornare immediatamente alla versione corretta per proteggere i propri sistemi da possibili attacchi.

Questa notizia arriva in concomitanza con il rilascio di patch per altre vulnerabilità, come CVE-2024-23108 e CVE-2024-23109, che colpiscono il supervisore FortiSIEM, evidenziando l'importanza di una costante vigilanza e aggiornamenti nella gestione della sicurezza informatica.

Inoltre, l'incidente recentemente divulgato riguardante l'infiltrazione della rete informatica delle forze armate dei Paesi Bassi da parte di attori sponsorizzati dallo stato cinese tramite dispositivi Fortinet FortiGate sottolinea l'urgente necessità di proteggere le infrastrutture critiche da potenziali minacce cibernetiche.

È evidente che il panorama della sicurezza informatica è in continua evoluzione, con attori minacciosi sempre più sofisticati e determinati. Pertanto, è fondamentale per le organizzazioni rimanere vigili, adottando le migliori pratiche di sicurezza e assicurandosi di implementare tempestivamente gli aggiornamenti di sicurezza forniti dai fornitori.

In conclusione, la sicurezza informatica è una sfida in costante evoluzione, e solo attraverso una stretta collaborazione tra le aziende e i fornitori di soluzioni di sicurezza possiamo proteggere efficacemente i nostri dati e i nostri sistemi da minacce sempre più avanzate e diffuse.
I’m also pretty sure that syncthing won’t help you with local full device backups and restores right? Isn’t the only way to do that to turn on developer options and use adb or another program that interacts with adb to backup? Google doesn’t even intend the user to do that judging by the way it’s hidden behind developer options, their only full device backup solution is cloud based.

So the question here is “how does Grandma sync content and make full device backups without the cloud?”

It sounds like Google’s option is to implement it yourself. You’ve got to go out and find the right software for your needs and none of it is made by Google.

For full device backups you have to be well-informed enough to enable Android debugging (which, again, is a developer feature and is labeled as such), or to get a third party program like syncthing/rsync. You have to build your sync stack on your own without Google’s help.

That DIY situation fine for a lot of people and it is true that it’s more powerful and open than what Apple gives you. But Apple is selling you a solution that is much more friendly to the average person and represents a complete solution without relying on third party software.

I can tell a 70 year old who refuses to use the cloud how to plug their iPhone into a Mac or PC and take a regular backup without needing to put their data on a cloud. On the Mac you don’t even have to install software, and on the PC the software comes from Apple directly. I don’t have to explain how to tap the build number seven times to enable developer options.
Yes - if it’s anything like the iPhone, the features of the second generation will be pretty much finalised by now, and they will be well into planning the third generation.
> A man moves from East Germany to Siberia, where he knows his letters will be censored. He establishes a code with his friends: anything written in blue ink is honest and true; anything written in red ink is false and only there to get the truth past the censors. A month goes by and the man’s friends receive a letter written in blue ink: “Everything is wonderful here. Stores are full of good food. Movie theaters show good films from the West. Apartments are large and luxurious. The only thing you cannot buy is red ink." [1]

[1] https://www.guernicamag.com/tomas-hachard-the-red-ink/
Fortunately in Europe what the said boss did is illegal and this can end with a criminal prosecution.
Query planner improvements are always welcome, it's a very important part of the DB. Though of course most of the time you notice it is when it's not doing what you want ;-).

One part of this I found rather frustrating is the JIT in newer Postgres versions. The heuristics on when to use appear not robust at all to me. I've seen this for a rather typical ORM-generated query that is pretty straightforward, but pulls in a lot of other tables via joins. It runs in a few milliseconds without the JIT, but the JIT spent 1-1.5 seconds doing its thing on top of that and makes it incredibly slow for tiny amounts of data.

I know now to just disable the JIT, but this feature can give a pretty terrible impression to users that don't know enough yet to figure out why it's slow. I like Postgres a lot, but enabling the JIT just seems far too dangerous as a default setting to me.
> There has been plenty of attempts at copy protection on CDs. Some more successful than others.

Yes, but they're fundamentally incompatible with the CD standard.

I'm not denying that digital downloads for music were the first big use of DRM. But in that case, it was perhaps even more futile than in other applications.
No, there’s lots of technical reasons why. Not least of which is that c/c++ has be try very loose aliasing rules as well as the lack of a concept of move/drop (language nerds can chime in with all the other reasons). Even c++ would struggle even though committed members are aware c++ is dying and are trying to bridge the gap somehow.

If you changed the language to support a Rust-like borrow checker, you’d lose back compat which defeats the purpose of stick with C semantics in the first place. There’s the related problem that the borrow checker isn’t automatic. There are places it does good inference, but any structure that has ownership needs to have that owner ship explicitly defined (and often in functions too). That is hard to do when you have to deal with a lot of legacy code that doesn’t have it - while that part can be solved through annotations, things inexpressible in the Rust borrow checker are perfectly legal C so you’d somehow also have to change that code. Additionally the Rust borrow checker can still fail spectacularly on very reasonable code. That’s being addressed in Polonius if that project ever lands, but even then it’s just a step function improvement to solve specific what should be valid code - it doesn’t fix all issues with the borrow checker.

C++ is exploring gradual safeness to provide for optionally strengthening the safety but it’s unclear that approach actually makes sense other than as a balwark to c++ dieing completely (ie the switching cost would be weighed against the cost of fortifying the safety of the code and relying on a poor estimate of the risks involved since there’s too many unknowns)

TLDR: structural, cultural, and back compat issues will prevent anything like the borrow checker.
I still to this day feel like I'm being snitched on, even if I own the hardware directly.

Probably some MS server =|
> You need to know at least one level abstraction below your current one to use the tool effectively.

I'm not sure that's true in general.

For example, for some tools there's no single 'one level abstraction below'. Let's take regular expressions as a simple example. You can use them effectively, no matter whether your regular expression matcher uses NFAs or Brzozowski derivatives under the hood as the 'one level [of] abstraction below'.

(Just be careful, if your regular expression matcher uses backtracking, you might get pathological behaviour. Though memoisation makes that less likely to hit by accident in practice.)
Would fossil fit this bill?

Somewhat git-compatible, based on sqlite3.
Things each have pros and cons for various groups. Inflation and deflation can both be bad, in the same way that being cold and being hot can both be lethal to you.
Story I heard about the Phalanx is that it detected and fired on a kite. Split it in two with a short burst. Then two more bursts as it cut the two pieces in half. An engineer commented on the radar tracking it's own bullets and that the 8th bullet has it's aim improved by the tracking of the first bullet.
safe Rust isn't just the borrow checker, it's also:

- no uninitialized memory
- clone vs copy semantics as part of the type system
- Send, Sync, "fearless concurrency"
- no unchecked indexing
- type safety (you can't just cast things like in C)

I do think these are clear complements to a borrow checker, since it's all in the interest of preventing undefined behavior. Yet, there are even more nice modern features of Rust that C lacks:

- hygienic macros
- namespaces
- pattern matching
- modern build/package system
Surprisingly enough, as toxic as Amazon is, after I got Amazoned and made my choice to “leave Amazon and get a nice severance” instead of “try to work through the PIP and still get fired and only get a third of the severance amount”, they let me stay for a week to finish up a customer project. I worked in Professional Services.

I told them that I really wanted to finish the work for a customer (large state organization) because I liked the customer. They let me stay for a week.

Of course that was bullshit, I took the time to have back channel communications with the customer to see if they would hire me as an independent consultant after I left and to start interviewing.

I’m sure they would have. But I gor a full time offer less than two weeks later.
It's possible to implement some down-vote feature, if you see a profile that doesn't match expectations. A user with many down-votes can be banned and alll payments will be returned.
Or, if it fails, it might set AR/VR back significantly.
I'm just repeating something I heard on the Alex Jones show to be honest. It's a conspiracy theory after all - insert your protagonist of choice.