skysight-inc/HackerNews huggingface dataset:
Untrue. At least in the US you can either sign up for an annual plan that continues until you cancel it or you can extend the 3 year plan in annual increments.
Well, it is truly amazing what you can do with a cheap RTLsdr dongle and some time and energy. I used GNU Radio to build a receiver flowgraph that decodes and displays the signal from a nearby VOR aircraft navigation transmitter. It was cool to drive around it, and see the pointer update in real time.

The sensitivity of these things is on the order of a normal receiver, (0.1 microVolts) which surprised me, knowing the samples are 8 bits.
Hoogle cultures,and capturing runoff reduces your agricultural water needs.

https://permacultureapprentice.com/permaculture-water-manage...
> Enter Ghostty and Zed.

You're taking two desktop applications, written in Zig and Rust respectively, and extrapolating their lack of testing rigor as evidence that "there’s no correlation between software quality and tests"? Really?

Have you tried maintaining quality in enterprise software without tests? If you ever manage to do so, I'd be very interested to read about it.
I've faced that problem before: Someone claimed their autoscaling algorithm had to be working correctly, as he had written a proof and had a working simulator behaving perfectly. And yes, the code matched the algorithm as written, and the proof was correct... as long as latency was zero. Once I added lags to the right places in the simulator, we got the exact same problems than in production.
On the small I wholly agree, like how much energy do some teams or even companies still waste on style document types of disagreements? But other aspects, I do often care how the code "looks" or more precisely "does" something. Like, it shouldn't be needlessly wasteful of resources, but I don't want to pigeonhole myself as "the performance guy". It shouldn't be using under-educated idioms that increase the likelihood that someone's gotta come back to this later to fix something stupid like a null pointer exception. At the same time certain things that sometimes get derided as ivory tower complex (or just "clever") code constructions, I don't think should necessarily be avoided all the time, but should be tastefully balanced with an aim towards broader understanding and not showing off cleverness for the sake of cleverness. I've replaced so many hundreds of lines of code with some relatively simple tens of lines type theory constructions in plain old Java 8, just because a dev who stopped learning around Java 1.4/5 doesn't understand doesn't make them "complex" or "clever". I don't even particularly like static typing, but a tool is a tool.

But often I just don't care about even those details, and sometimes feel guilty about it. Carmack says to fill your products with give-a-damn, but I'm sorry, for so many things, a lot of the time I just don't/didn't. Work must be done anyway though, and not just by me. So practices that are broader, like enforcing tests, do help deliver a good enough product even under the guidance of devs and management and management's management etc. who seem to care even less than I do and don't even feel bad about it. It's particularly crazy when you talk to a customer who is gushing about something you know could have been even better with slightly different prioritization and tradeoffs; an important lesson is that many people are stoked merely that something exists.

It's sad when tests catch something that really should have been caught, if not during code authoring time by an author who actually cares a bit more than just doing the job however and going home, then by code review time, but in large companies you sometimes have to just accept things for long periods and at least with more tests we can be more likely to catch things at all. (Not to mention they're pretty valuable when the original author who best understood the code is long gone, they help you make minor tweaks without having to tradeoff new feature development time with time getting a deep enough understanding of that old code that still mostly works most of the time.)
if you were able to reboot the device, was it really ever bricked?
C++ Compile Health Watchdog
I can only speak for the UK market where land with permission to build upon is scarce. Land in desirable areas is always scarce and I would imagine that includes many US cities.

In the U.K. there are only a few housebuilders that operate at any scale, and they have the best links into gaining owrmission and buying land to develop.

‘Landbanking’ is the keyword for the phenomenon in the UK, but ultimately the housebuilders slow building when prices aren’t rising to maximise their return. It’s economically rational.

My view is that government should step in and build competing social developments to house those that can’t afford market rent. The first order effect — less homeless, greater security — is nice, the second order effect is even more powerful in my opinion.

Anchoring prices towards cost of production. The UK housing market is now, since we privatised social housing, another asset class and logically the operators of that asset only consider financial returns — not social ones.

As I understand it planning permission doesn’t exist in many parts of the US and so ‘building your own’ is feasible. The only problem is that mass transit into desirable cities also doesn’t exist and so urban sprawl and you have to commute even more insane distances to leverage that land that can be built upon.

This is the area where fundamentalist market thinkers miss the key role government can play because they’re that far down the ‘government is the problem’ rabbit hole they can’t imagine positive market intervention because the market itself is the holy arbiter of creation
you mean no, as in ... "Norway"? ...
It said gcc. I noted the default of llvm said to default with framepounter from 2011. Is this mainly a gcc issue?
I have and this is not the case. The issue is that it does not work very well for my use case.

I do agree that the tool is quite user friendly when you use it for the intended purpose: apps for the microcontrollers without many dependencies on external libraries.
There was an interesting discussion recently on (somewhat) opposite perspective https://antithesis.com/blog/is_something_bugging_you/ - how good testing systems makes everything way faster
I learned to code with hyper card and the examples give me a very warm fuzzy feeling
Actually such a large country would there be, other than general winter/summersense, Australia has a country wide time?
> So we'll be stuck fighting an unwinnable argument with a much larger community.

In what way would you be stuck? What functional problems does adding frame pointers introduce?
Sqlelf – Explore ELF objects through the power of SQL
Ask HN: How to handle cc disputes when customer fraudulently backdates request?
I was surprised to see that my startup recently lost a credit card dispute even though we submitted proof that the customer requested the cancelation after the renewal had already gone through. When I looked into the dispute history, I was able to see that he claimed to have requested cancelation several days before the renewal, when in fact his request came several days after renewal.

The true date of the request was evident in the email screenshot I submitted in my reply, so I'm not sure what else I could have done here. It wasn't a huge transaction, but I'm concerned to learn that if customers lie about when they requested cancelation, there appears to be nothing a merchant can do to win the dispute.

Does anyone have any advice?
So, AppleScript for the web?
Please include this information when you send the patch.
Is it hard to recruit younger devs? Also, I heard that the hard part of using Cobol is that almost every one uses a different "flavor" of Cobol, with different tool chains and most of the ecosystem is proprietary. Is that still true?
I don't know. When working in an unfamiliar codebase, tests are very helpful (even when some percentage of them will always be annoying). The problem is, the industry has focused on having lots of tests instead of having good code.
I agree a type system does wipe out 80% of the tests you need, but I still feel like the 20% is useful. You can just write tests that verify the output looks right without having to run every single line of code to make sure there are no typos or type issues.
Yes. People have had cfs or me since long before covid. I had it 25 yr ago. Its nothing new, but is fairly rare.
Repairing an EV battery is a risky operation, especially if you don't know whether it's damaged and about to short out as you pry it open. Working on such a thing anywhere near your home, or if you are in a wheelchair and can't run away in an emergency, is a terrible idea.

You are right in a way. ICE engines can be expensive to work on. But even the most dramatic repairs to ICE engines is presently cheaper than a typical EV battery. You could probably change the engine and transmission in a car for $10-15k, and that is very rarely necessary. Most repairs are minor for the life of the car, which could (up to the latest techno-trash designs) be easily 20 years or 300-500k miles. If auto makers wanted to, they could make ICE cars expected to last 30-50 years with routine maintenance and occasional replacement of worn-out parts. But they won't because it would put them out of business. Besides, people like new shiny things and being different.
Hydrogenaudio: ....and we are back
What happens when all white collars people flock to trade jobs (due to lack of other options)? plumbing will become a commodified job as well...
> Actually working with the people who do provide those patches?

Patches welcome means "Send me a patch and I can run git am", not "let me teach you".
> Apple Plus is amazing

It’s a pretty expensive service offering that you have to buy on top of a pretty expensive laptop.
Centiliter = 0.01L

Hectoliter = 100 L
Ok, we'll move the comments to https://news.ycombinator.com/item?id=39725445 and re-up that one. Thanks!
From an SQL background, this doesn't really surprise me at all. PostgreSQL is the closest anyone's ever got to being fully ANSI SQL compliant, with most of the proprietary vendors having rather paltry compliance numbers.
Remote is a clear competitive advantage for both attracting talent and reducing cost. Companies that can’t hack it will be left behind.
If you use a Jetbrains IDE you already use Java e.g. Webstorm and Pycharm.
Or you do not so conscious of time due to lack of tense. Still remember spending 1 hour on one economist line on the English implied sense of time and event sequence. All just used a few grammar not really exist in Hans language until forced into it in the last 100 year. Still not in its native form.

So is Japanese …
A friend of mine described lotteries as a tax on people who can’t do math.
>The datacenter we host with lost all network connectivity, including redundancies.

In the last 20 years we have nearly had a 100% uptime, once stung around 15 years ago when GoDaddy messed up their DNS servers, that was a 3-4 day outage from memory.

Then our previous datacenter, had 3 network connections, one was down for maintenance, a builder dug through one, leaving just one, and the datacenter cut through the working one thinking it was the damaged one, that was a 1 day outage also.

It happens, even to the best of them (a few days ago, Facebook lost their authentication servers).

Will work with the datacenter to understand why the redundancies failed over the next few days.

Days when even Triple Redundancy isn't enough.
Compare with one of my projects, [1]

It is a minimal, though modern-looking web chat.
The HTML, CSS and JS together is 5024 bytes.
The Rust backend source is 2801 bytes.
It does not pull in anything from anywhere.

[1] https://github.com/coolcoder613eb/minchat
A lot of people seem to be convinced widespread remote work means everyone making SF incomes and with SF career opportunities.

It's probably more like everyone making Pittsburgh incomes with 60% of SF opportunity.
We do this at Fastmail and, if I say so myself, our implementation is pretty damn good. We’ve had this for over a decade, so it was originally built for much lower powered devices.
> CoreAudio actually "just works" out of the box

If Apple is not messing up their USB subsystem like they did with Ventura, where people basically had to wait a whole major release until they got stable performance again with Sonoma.

Or if they don’t break iLok copy protection, like they just did with 14.4

And for professional hardware, you don’t have to install “all kinds of alternative drivers”. You just install the one official driver from the hardware vendor and that’s it.
It “wastes” a register when you’re not actively using them. On x86 that can make a big difference, though with the added registers of x86_64 it much less significant.
Multi-threading across multiple processors demo promises big performance gains
Also, they have some internalised sympathy for a good salesman and are forgiving. I think this tendency was alluded to several times in the series Mad Men where the lead character Draper who's an excellent salesman talked to other salesman.
How Microchips Work
If you can't read font-size: 14px, you got your resolution/scaling/screen size wrong. The default text size is similar to the standard text size of OS UI controls. If you can't read them, I'd suggest to reconfigure your setup: change resolution, change scaling, or configure the default zoom level.
I remember reading about how in the Soviet Union, there were places they were irrigating with brackish water and how they were now infertile. The obvious conclusion was that the Soviet economic system was busted to permanently destroy land for some temporary gain.
OK I missed that. Thanks. But it looks like Itanium was only tangential to this discussion, in that Knuth thinks multicore programming may be an even worse mistake than Itanium.
Seriously everything I read lately seems to have some hint towards to ecological disaster and climate change.

I get it, we’re proud of our technologically advanced society but man is it coming at a fucking huge cost for everything else, including things we rely on for food.

It’s hard to keep reading all this and saying, “oh well”. I mean it’s never going back to the way it was…
The American equivalent is the dust bowl. The ancient equivalent is the desertification of Mesopotamia. Etc. etc.

Humans are bad at long term thinking.
It's logical and it makes sense. I would argue, at first glance, that C's hello world (#include <stdio.h>, int argc, char ** argv, etc) would be more confusing to a total newbie. Java's even more so.
I reported security issues to Mintlify back when they used Discord for support. Gave recreation steps. Never got any feedback that looked to me like they were looking into it.

I reported similar issues to what's described in May 2023.
Centipede = 100 legs

Etymology is more complicated than "look up the prefix in the metric system tables", and OP is correct about the definition of centimillionaire.

https://www.merriam-webster.com/dictionary/centimillionaire
The original intent IIRC was the programs for the model 20 would be upwards compatible with the rest of the series, but that the higher level models would not be downward compatible with the 20. No idea if that ended up being achieved.
I dunno, in my career I’ve found that UI e2e tests were the ones that actually found bugs. All the unit tests that I’ve written ware mostly ceremony, to increase code coverage, etc, and were the first to need refactoring after some code change. A lot of refactoring.

The tests that stayed true were the UI tests that almost always pointed to real problems with real code.

It took a while to figure out how to write them though - trying to rely as little as possible on the internal ids / html / css and write them with what the user sees - e.g. instead of clicking on the button with “testid=login” we would “click on the button with the text login in it”. Identifying fields by the labels to them or tables by their column headers. It was inspired by rails’ capibara testing lib.

And making sure the tests were not flaky, fast to execute and isolated took some time.

But it was so worth the investment - it’s surprising how little those tests would change, as it allowed us to fearlessly refactor stuff without changing any tests. They felt a lot more like a friendly QA helping out rather than an annoyance you had to deal with after you’ve finished writing your code.

And writing them was actually fun, since you didn’t have to understand how the app worked, fiddle with brittle css identifiers etc, you just wrote the steps you thought the user should do and saved it into a file.

Being UI tests kinda meant they tested the whole system with the various micro services involved, databases and other infra. And I think this is where most problems in software arise, at the edges of systems when they try to interact with each other.

Static types, immutability automatic API schemas and validators usually make sure the code one writes executes reasonably well, its where the code one writes starts interacting with all the other systems where people usually can’t anticipate things. And thats where the integration / e2e / UI tests help the most I think.
Six ways mushrooms can save the world [video]
Types don't replace tests.

Tests don't replace types.

For either statement to be true, they would have to be entirely equivalent, at which point it would be a distinction without a difference to complain about.

And last I checked no type system automatically generates and minimizes failure cases.

And last I checked no test system can be used to formally prove anything about the behavior of code.
Libraries cannot buy used because they need the asset prepared for circulation. This includes a protective cover, barcoding, etc. They usually have a vendor do this preparation, and the assets (books, usually) are often not the same as what you would find in a store, they can be different sizes to fit in Automatic Materials Handling Systems, have more robust binding, etc.
But that would make SpaceX a legitimate military target.

And making higher orbits unusable may be beneficial for the US military wise but really bad for all other purposes and countries which would be catastrophic in the long run.
It caused a problem when building inline assembly heavy code that tried to use all the registers, frame pointer register included.
You can use pmtiles through mapserver via GDAL!
"Solid investment strategy" implies one could make money applying this idea consistently. There's a hundred new "next big thing" ideas every year - most of them amount to nothing.
> this kind of tinkering was fun and a good way to improve the machine I was using.

You know you’re alive when you log into iCloud from a hackintosh and then Apple notices, you get the ‘unauthorised hardware’ message (I can’t remember the exact phrasing) and your various iCloud services begin to cease functioning. It’s not often your OS is exciting.
Datasette was definitely a huge influence for this and I'm a big of @simonw and his work.

However, there's a couple of major differences:

- Datasette - to me - is a tool for devs - it takes a fair bit of tech know-how to understand how to load new data in datasette, install plugins and deploy an instance. I wanted Pretzel to have a "low-ceiling, high-floor" - meaning the tool should work well for non-technical folks but also shouldn't hinder technical folks and power users

- Datasette has a unique way to explore data based on "facets" where you can dig through data. It's a powerful way to explore but I personally don't think Datasette is the best tool for complex data transforms - its strengths lie in exploring datasets instead.

- For accessibility and speed, we wanted something browser local and fast - hence the focus on DuckDB and canvas rendered tables. Datasette requires setting up an instance and that's additional friction for non-tech folks and isn't particularly designed for large datasets (is my impression - I might be wrong)

- Lastly, we have ton of future plans - including in-browser python support via WASM (Pyodide), local LLM support, ability to connect databases etc.

I think there's space for both tools!
It's ironic that the article later on mentions nonchalantly that there's an IDE built as a VS Code extension.
Every passing day, I am more happy I am born as an Indian because I know it is possible to live a healthy life without having to resort to the consumption of protein at any cost.
Right, but I was asking about functional problems (being "stuck"), which sounded like a big issue for the choice.
Htmx 2! 8)
That’s true of 70-80% of tubular locks, but there are higher quality tubular locks that are designed with the standard tubular impressioning tool in mind, and on which it does not work.
Ah, so you can bullshit a bullshitter
You: logic

The English language: "allow me to introduce myself!"
I’m not sure what use case you’re coming from but it sounds like you’re saying something like: most end users don’t use a profiler or debugger so why should they pay the cost of debuggability? That’s fine I guess if you’re throwing software over a wall to users and taking no responsibility for their experience. But a lot of people who build software do take some responsibility for bugs and performance problems that their users experience. This stuff is invaluable for them. End users benefit (tremendously) from software being debuggable even if the users themselves never run a profiler or debugger that uses the frame pointers (because the developers are able to find and fix problems reported by other users or the developers themselves).
HyperTalk but yeah: https://hypercard.org/HyperTalk%20Reference%202.4.pdf
Hey, I left a comment in another thread about the differences:

https://news.ycombinator.com/item?id=39732135

Didn't know about OpenRefine - but one major difference is Pretzel is web-based meaning no installation necessary (important for work laptops, for eg). We're also going to be adding a ton of features to this - think Jupyter notebooks crossed with Metabase crossed with Datasette/Pretzel.
Permaculture maybe possible
Reimagining the Iconic BeOS BeBox [video]
These apps have sounded like an incredible cesspool for a long time, though I have been recently hearing they are even worse.

Honestly, I think the very concept is broken from the start. Neurotypical people do not need to use online dating or hookup apps. In fact, it robs much of the fun out of the experience. Meeting people in person, seeing how they interact with you, with friends, with others, how well they pick up on signals and how they make you feel and letting that pheromonal magic work is how our species has been doing these things from the start.

The normies should polish back up their social graces and head back to the bar and leave the online dating for the folks for whom it really is the best option. If we rob the apps of their mass market appeal, the profit model can collapse and online dating can go back to the niche it belongs in.
Thank you for that link; it's clarifying.

I think we're actually in agreement that the "library" part of a library is obsolete; it's just (as I understand) you and the sibling comments are using a neologistic definition of "library" that's unrelated to mine. Your link explains it as a place for social workers to care for clients. I'm fine with closing libraries and replacing them with that stuff—I'm not going to quibble on language, but that is not a library.

I should have considered this alternative definition before I wrote my comment, and how I phrased it. I see now exactly how it's been misinterpreted, and that people think I'm attacking unhoused people or something.