skysight-inc/HackerNews huggingface dataset:
> All of them do. Including bash.

Are you sure? https://unix.stackexchange.com/questions/208615/is-cat-a-she... disagrees and neither https://manpages.ubuntu.com/manpages/jammy/man7/bash-builtin... nor https://zsh.sourceforge.io/Doc/Release/Shell-Builtin-Command... mention it
A good lawyer always tries, but with SBF as a client you need a miracle worker, not an attorney.
LINQ is just an interface, you need some sort of an implementation below it (be it the unmaintained LINQ-to-SQL that AFAIK nobody should be using anymore, or the latest EF rewrite).

It's also the first thing I recommend to anyone claiming that concatenating SQL strings together is a good use of your time in the 21st century. Makes writing things like complex HTML tables with configurable columns and tons of optional filters so much faster and more maintainable.
The construction of these houses is depicted in this documentary: https://youtu.be/5Q0FMxZBmO4
Good points! As someone who uses both ORM and raw SQL (I actually really like SQL as language) I sympathize with both sides of this debate. I prefer the readability of ORM in my models when developing, but closely monitor and optimize for N+1 and other inefficiencies, when needed. "When needed" is never cut-and-dry, but I try not to optimize too early. I actually tend to start new projects from the database and will scaffold with factories, seeders, and raw SQL queries to get a sense of the data model prior to coding.

ORM's such as Eloquent in Laravel also have some nice methods to resolve N+1 and perform lazy loading, but it's always tradeoff.
> Any testable definition of AGI that GPT-4 fails would also be failed by a significant chunk of the human population.

GPT cannot function in any environment on its own. Except in response to a direct instruction it cannot plan, it cannot take action, it cannot learn, it cannot adjust to changing circumstance. It cannot acquire or process energy, it has no intentionality, it has no purpose beyond generating new text. It's not intelligent in any sense, let alone generally. It's an incredibly capable tool.

Here's a testable definition of AGI - any combination of software and hardware that can function independently of human supervision and maintenance, in response to circumstance that have not been preprogrammed.

That's it. Zero trial learning and function. All adult organisms can do it, no AI can. Artificial general intelligence that's actually useful would need a bunch of additional functionality of course, there I'll agree with you.
The 737 NG has a lower crash rate than any Airbus on the list at 0.07. Hop on a 737 in the US and this is probably what you'll be on.
I always think it’s worth mentioning that All Quiet on the Western Front is a work of fiction, written by a guy who was on the front for about a month, at which time he was wounded and unable to return until a few weeks before the end of the war.

Junger is writing a memoir based on the four years he was in the war, much of it at the front.

I suspect Remarque gets more attention not because of greater literary merit, but because his sensibilities are easier for us to understand and better accord with that of our teachers. Junger is a much more alien read, and for that reason much more worthwhile.
Agentic uses of GPT can solve the context problem by breaking problems into steps and building prompts to solve those steps.

Can't do everything, but GPT+APIs can do a lot.
Calorie counting isn't very precise to start with, even if you're serious about it

https://www.insidescience.org/news/calories-count-only-when-...
Other than new stations that just haven't come online, I've never once pulled up to a location and failed to charge at a decent rate. Similar experiences with most people I've talked to actually at the stations I'm charging at.

I'm sure wherever these reviewers are doing their reviews, they're getting bad experiences. But personally I've never once had a problem. Maybe bad maintenance is more of a localized thing?
The UNO predates the Pi Pico by about 20 years. It was pretty small for everything it did back then. The headers are laid out in a standard format so that it can accept "shields", so now anything that wants to use those shields has to be this size.
Heh. I can't blame them for doing this, but not telling people what's happening (and why) was the big mistake.

People generally want their gadgets to be as lightweight as possible, cheap as possible, last as long as possible, and be reliable. There's tradeoffs in balancing those. eg: overbuilding the battery to make the device run longer in the face of degradation adds weight, size, and cost. Somebody has to make a call on where the balance should be.

What nobody really talks about in the context of device longevity is wear levels in the onboard flash. A battery replacement or three doesn't extend that clock. It's pretty good but it doesn't last forever. This is more of an issue on devices with smaller amounts of flash storage with a lot more storage churn.
ItCppCon23 C++ and Game Development: The Good, the Bad, and the Ugly [video]
Might be interesting in context of discussions about replacing C++. It has opinionated takes on gamedev use of C++.
At a certain point we should just admit that Chinese bootleggers make better honey than the bees.

After all, it has the correct amount of water and sugar, the correct sugar composition, the correct pollen, and it all has to be cheaper than real bees otherwise they wouldn't bother.
> How does "we'll just immediately terminate all business dealings with you forever" not sound like a retaliatory restriction on the recipients' exercise of their rights?

A enterprise has the right to refuse customers if the reason isn't discrimination of race, color, religion, sex, sexual orientation, gender identity or nationality.

"I violated a contract I made with them" isn't one of those.
Would those incidents be frequent enough to make anything but a de minimus impact?
I recently encountered the phrase "peanut butter term," although not in the context of "wokeness" specifically, to refer to a label that will stick to and spread all over just about anything. I think its a useful companion or alternative to "umbrella term."
well if you're using an interpreted language without any sort of build step then I suppose that's all you can do, but if your backend is written in a compiled language with compile-time execution functionality, then it seems useful to do stuff like this then, instead of at run-time, likely multiple times per request—that's a lot of unnecessarily repeated string-building, without any benefit for doing so!
What are you missing specifically that New Relic has?

We are a full grafana prometheus shop and the New Relic/Datadog price tag is insanity compared to the utilization we get out of the free tooling.

Once you get over the learning curve of promQL or whatever you're looking for it's not bad at all.
do people here have so much free time on their hands ?
>LINQ has almost always been an anti-pattern

You mean "LINQ" as an input for ORM? or LINQ in general?

either way this is crazy claim.

There's shitton of projects where queries aren't complex and LINQ will make your life saner instead of this stringly typed hell called SQL.

Just check what ORM is generating for your queries and if it is a mess then write it manually and you're good to go.

This way you get both benefits: sane type system and performance.
I’m confused by your line of questioning. Why do you think I can’t be satisfied?

I don’t have a problem with this Google poll. I think it is valuable.

What would satisfy my desires is exactly what I stated in my original comment: something more objective, like defect rates of Rust code bases compared to non-Rust ones. Metrics like these have their owns problems, but would be a nice supplement to the opinion-based poll.

Neither the objective metrics, nor the opinion poll can provide a complete picture, and neither is a substitute for the other. Both would be awesome.
Part of its lifespan depends on what kind of tuning it has, with some commercial engines being detuned for longevity instead of power output, and if it has extra optional features like additional oil or transmission cooling, or bypass oil filters, and other extras. Consumer vehicles however are often built and designed with lower lifespan expectations and a higher performance profile.

But ive had numerous 90s+ low trim consumer vehicles breaking 300k miles easily and I know some semi-trucks do have 1 million+ miles on the original motor because of such features. And so while I don't have much experience with commercial delivery vehicles, I don't see any big problems with saying they could go a million miles themselves, although due to the nature of delivery driving and driver turnover I would also expect 400-500K miles to be when a rebuilt should be considered unless it was all done by one driver who doesn't drive like mad and they had skilled mechanics maintaining them. And if they didn't care about ruining the engine at some point I would expect 6-700K atleast if it was a well built commercial engine with commercial features.
How about this? Taking a dense obtusely written ML algorithm with a ton of mathematical notation, plug it into GPT4, and get torch code? Cuz I do that often.
> AMD might be facing a tough battle

The Ryzen 7940HS, which is a pretty good value, is on TSMC 4nm, rumored to already cost close to $20k/wafer.

Even if they double the transistor count, a single SKU should theoretically be cheaper to produce, since you're reducing the footprint by 4. Of course, this is assuming yields don't fall too badly on 2nm (which they probably will, 2nm feels like alien technology at this point).
On one hand that seems like transparent ass-covering to me, but on the other companies should be free to engage in transparent ass-covering. These are for-profit institutions, their duty is to their shareholders, not social causes they barely pay lipservice to. When it was in their interest to vocally support drag shows, they did, and now that it isn't in their interest, they aren't.

That's the reality of these companies, and also why no one should look to them for moral guidance.
Now that Tesla chargers can talk the same CCS protocol and Teslas these days can speak CCS, newer adapters can just be dumb adapters either way.
To be fair, a lot of those tools have that one weird caveat you need to know, and are also strongly dependent on your dialect.

For example there's an aggregate function in DB/2, LISTAGG, that joins strings... the caveat being that if they get too long, the query blows up. It's in OracleSQL too, which has a syntax where you can tell it to truncate the string.

SELECT, INSERT, UPDATE, DELETE work more or less the same whether you're on MariaDB, Postgres, DB/2, OracleSQL, etc.
Actually was thinking on this, I suspect you're right that this is another potential stressor that should be considered.

Not so much diseases from animals brought by humans, but rather diseases/parasites from related animals who just mosied onto and sometimes over Beringia of their own accord.

E.g., wooly mammoths on the Eurasian steppes and American mastodons spent a lot of time developing in isolation, they could've had their own diseases they'd evolved to resist, then Beringia arises from the seas, and 100 years later, a mastodon catches the Mammmoth-flu or something.

From what little I understand, some of the N. American megafauna have been shown to have limited genetic diversity due to small founder populations, which we know can increase the vulnerability of a population to a novel disease.

I'm wondering how you'd be able to prove or disprove this though, maybe coprolites? Googling this briefly turned up this amazing website with the even more amazing tagline "#1 for fossilized #2"...

https://poozeum.com/

Brb doing a PhD in paleoepizootiology.
Closest modern day equivalent is probably a DIY Tiny Home.

Here's one for $66k (steel frame only): https://www.homedepot.com/p/Bungalow-Raised-Deck-loft-2-Bedr...

Other companies out there bundle additional components (more than just the frame). A quick google search turns up DIY kits that includes insulation, floors, walls, etc.

Edit: This was actually on HN a couple weeks ago https://news.ycombinator.com/item?id=36209328
The key is to develop a monitoring framework. pick the tool/s you want, enrich and standardise what can be done with them (dashboards, alerting, etc) then make the path to using them easy
From Sections 3 and 4 of the VQGAN paper[1] upon this work is built: "To generate images in the megapixel regime, we ... have to work patch-wise and crop images to restrict the length of [the quantized encoding vector] s to a maximally feasible size during training. To sample images, we then use the transformer in a sliding-window manner as illustrated in Fig.3." ... "The sliding window approach introduced in Sec.3.2 enables image synthesis beyond a resolution of 256×256pixels."

From the Paella paper[2]:
"Our proposal builds on the two-stage paradigm introduced by Esser et al. and
consists of a Vector-quantized Generative Adversarial Network (VQGAN) for projecting the high dimensional images into a lower-dimensional latent space... [w]e use a pretrained
VQGAN with an f=4 compression and a base resolution of 256×256×3, mapping the image to a latent resolution of 64×64indices." After training, in describing their token predictor architecture: "Our architecture consists of a U-Net-style encoder-decoder structure based on residual blocks,employing convolutional[sic] and attention in both, the encoder and decoder pathways."

U-Net, of course, is a convolutional neural network architecture. [3]. The "down" and "up" encoder/decoder blocks in the Paella code are batch-normed CNN layers. [4]

[1] https://arxiv.org/pdf/2012.09841.pdf
[2] https://arxiv.org/pdf/2211.07292.pdf
[3] https://arxiv.org/abs/1505.04597
[4] https://github.com/dome272/Paella/blob/main/src/modules.py#L...
I lived across from one (nowhere near as nice as that one though), and you definitely can't tell.
yeah, I heard that electric and modern vehicles don't need software or good engineers anymore.... Ford is going old school.
How does one become always aware in advance of having incomplete or misleading information on every subject that comes up in a conversation? I think some politeness and courtesy should be granted in those situations. Especially if you allow for the fact that it is you who could be having incomplete or biased information as well?
Prior discussion: https://news.ycombinator.com/item?id=18265533

This often comes up as a "look how much cheaper housing used to be" discussion. Keep in mind things like gfci outlets, fire code, insulation requirements, electrical/plumbing inspectors, permits, etc weren't an issue back then.
Not for these chips. The Vivado licensing is kinda complex these days because it's basically segregated by the chip series rather than actual software features. But it can basically be summed up as "Free for low/mid-range devices with all features, free for people using Alveo accelerators and specific UltraScale SKUs, and pay us money for anything else."
"It would be tough to offer the same kind of kit in this day and age given the difference in building material back then compared to now."

I see a lot of houses going up around here using metal studs...
I live in one of these. Still standing since 1908, and honestly the quality of the wood used in the construction is the secret, I’ve been trying to find tight grained fir that I can make some plugs to patch some holes drilled for wiring in the original wood floor, and I can’t even come close. Luckily mine was made by a craftsman who obviously took pride in his work.
Few might remember that Alpine was originally based on Gentoo. You can still find some old references (like mkinitcpio hooks for fbsplash).
Unless you're on Java. Just need three columns out of twenty? That's too bad. The JPA spec mandates you pull all the columns in that table.

But fundamentally on any programming language, all popular ORMs treat the database like it's MySQL 5.7—the bare minimum in modern functionality. It's like owning an Audi but being told you have to drive it like a 1971 Chevy Vega—a lowest common denominator.
Emacs. Runs as a server, stays alive when clients drop. Window management on keyboard. Tramp mode is great. But I'm sure you've heard this already :)
Overall, I think the article is pretty good. ORMs fall under the same category as garbage collection or try/catch exceptions: it is a tool. Tools solve a lot of common cases, but that doesn't relieve the developer from understanding what is actually happening under the hood.

* Garbage collection solves pointer problems, but the developer has to know what is being allocated and when to prevent churning memory.
* Try/catch exceptions solves breaking the tie between where exceptions can occur and where exceptions can be handled, but the developer still has to determine if all of the exceptions are being handled.
* An ORM solves relating objects to data persistence, but the developer still has to know what relations weren't covered in the original query after the objects are used.

> Active Record struggles with this, and that’s why we refactored our billing
> subscription query. Whenever we got results we didn’t expect, we’d have to
> inspect the rendered SQL query, rerun it, and then translate the SQL error
> into Active Record changes. This back-and-forth process undermined the
> original purpose of using Active Record, which was to avoid interfacing
> directly with the SQL database.

This is where I disagree. ActiveRecord was meant to map objects you have to your relational database, hence Object Relational Mapper. It is not a reporting interface. But it is reasonable to get around this. One way is to get a lot more specific in building the query with `arel`. Alternatively, open the raw connection and execute SQL with `ActiveRecord::Base.connection.execute`.

The disconnect here is believing that ActiveRecord solves billing/reporting SQL statements. It does not. It solves mapping objects. If your access pattern doesn't match (reports, N+1, GraphQL) then you have to understand the tool well enough to create your own mapping solution (custom SQL, preloading/scoping, data loader).

I remember when Java was considered really, really slow. The guy used a code example to prove a point. I rewrote the code to stop relying on the GC allocating/freeing data structures over and over and sped the program up by 400% on that alone.
it's strange that "liked using" isn't the goal in general
In the long run your body adapts, physically and hormonaly. Your stomachs shrinks, your ghrelin/insulin get back to normal levels, &c.

It's very hard to over eat in a single meal unless you eat absolute junk food. It's relatively easy to over eat even on healthy food if you eat 3 meals per day + snacks here an there
It has nothing to do with overheating. It is battery ageing. The internal resistance of a battery increases as it ages, leading to brownouts when peak current happens.

The throttling feature still exists in iOS. All that’s changed is that you will be made aware that it’s happening and you can switch it off if you prefer a brownout when your battery is degraded.

Other manufacturers are happy to let your handset reboot, it could lead to another sale for them. Some would call that planned obsolescence.
What matters is Boeing MAX vs everything else. It needs a few years more of testing at least until we can trust that it's safe.
Martin Fowler's Patterns of Enterprise Application Architecture has a section called "Data Source Architectural Patterns" with some data access patterns. It doesn't explicitly call out "ORMs" but they tend to combine multiple patterns. It also has a section on "Query Objects" which cover some of the method -> SQL magic ORMs do. It also lists pros and cons of these patterns

As with many things, ORMs come with pros and cons. Imo they can be especially productive for simple CRUD applications and prototyping but may quickly increase complexity with object or data models that use more complex query patterns.

https://martinfowler.com/eaaCatalog/
Fair, I appreciate the answer. I guess I’ve just seen enough purchases where it’s just for the payday that I’m a bit cynical. Thanks again for taking the time to read and answer, wishing you the best
There is a counterpart: https://www.zhornsoftware.co.uk/caffeine/
Since so many people are asking what "emulation" is, I'm going to respond to the parent comment instead:

"Emulation" refers to emulation of chip designs. When a chip has billions of transistors that are all connected to each other to perform higher level functions, you need to test out designs in order to make sure those higher level functions actually do what you expect them to. Most modern chip designs (at least the digital portions of them) are designed using what's called a Hardware Description Language or "HDL" such as System Verilog or VHDL. It's somewhat similar to traditional programming, except threads are nonexistent, so it's essentially an unholy bastardization of a markup language and a programming language. But I digress... These functions are then synthesized into their low level building blocks such as buses, gates, and registers, and are placed and laid out on a chip.

Going back to the part about billions of transistors; as you might imagine, testing of such designs must be rigorous and thorough. Only problem is that it's really, really computationally intensive. There are 2 ways of doing it: Simulation (CPU Based) and Emulation (FPGA Based) Simulation is slower, but yields more data like waveforms and whatnot (though you can get waveforms with emulation, but there are more limits.) Also, simulation takes less time to compile, since there's no place and route step.

I should also point out that there are 4 key simulation levels: Simulation Model (usually compiled C code) RTL Simulation (Functional level simulation) Gate level Simulation (simulating the individual gates) and physical simulation (where the transistors and trace routing are all accounted for.) Each level being roughly an order of magnitude more computationally intensive than the previous. Most time and engineering effort is spent on RTL level simulation, which is what can, and is often emulated on an FPGA, and why this product is so relevant to hardware designers.
Tuber farmers who can't do anything but eat the day's harvest get by on much simpler culture than grain farmers. Landlords with granaries? Tubers can't be stored, so the idiot building palaces is wasting time. Kings and armies marching to claim faraway fertile lands? Rich city ruling over neglected grain basket region? They can't eat anything from faraway land. Festivals, astrology? Those won't help for perennial crops. Accounting? Not helpful for food.
Are you trolling? Using 737 NG would be like using Airbus NEO variants, which ALL were excluded from the list in the single aisle category for having a 0.00 crash rate…
There's a youtube video on the page that autoplays, and youtube is on the magic list that can autoplay without interaction
Thank you. It was arguably never useful beyond an intuition pump. It's a test of credulity, of susceptibility to pareidolia, not reasoning ability.
The 737 has also been around a lot longer. The 737NG has a rate of 0.07 compared to the A32x's 0.09. The A330 is 0.19 while the 777 is 0.18. But even this is kind of misleading. All but three of the fatalities (total fatalities, not accidents) due to the 777 come down to intentional acts that would have destroyed any aircraft.
Cool dataset! Though I would hesitate to draw conclusions from it as a passenger, since the # of events is so low. Someone would need to do the statistics to see if the B737 and A320 series have enough flights to be significant.