skysight-inc/HackerNews huggingface dataset:
> that a well configured Emacs can

Well, that's the real issue for me. I spent a month an a half working on "configuring" NeoVim. I got it to a somewhat ready to use state for my usual workflows. But I still had a big pile of tasks in my backlog to actually get it finally 100% mine.

Then I discovered Helix, which doesn't need any configuration, no plugins to play around with. Builtin LSP, Builtin Fuzzy Finding of files, TreeSitter and the list goes on.

Even though it's still not fully checking all the boxes I need to have a 1 to 1 mapping of my previous workflows to what Helix offers. I find not having to build my own editor out of the Lego pieces and always needing to improve what it can offer me, makes the editor actually enjoyable.

IMO, VIM, NeoVIM and Emacs should start looking into implementing a bit more than just the barebones, some of these new features that people are accustomed to in 2023, and more and more will flock to these good editors.
You're not describing unit tests, they're integration tests.

You've fallen into the very trap of terminology the author mentions at the beginning of the article.
As in, "back to the state before the last interaction", which is pretty well defined.

(If there are clearly grouped interaction with transitions, this may be "back to the state, the last grouped interaction was finished and the current one opened.")
The error message indicates that "Operation not permitted while System Integrity Protection is engaged".

.... and if SIP is turned off?
The post is highlighting an interesting incident of vibration. The Apple article warning of effects of vibration is of less interest.
The server is provided by my employer so I can’t go into the implementation detail. But overall, most companies provide access to the API endpoint instead of using chatGPT itself since OpenAI uses your results to train (hence why it’s free for 3.5). The API endpoint supposedly doesn’t use your data for training which is why I use the API endpoint for personal stuff as well.
Gore Vidal Was Everywhere and Now He Is Nowhere
In the Southern District of Florida, United States of America:

But then she was charged in the United States with offences including trademark infringement, and was told to pay damages of $US1.2 million ($1.8 million).

Her 'bogo-debt' can still be sold for cents on the dollar to local (Australian) collecters who might haress her, future vacations to US STeates and Territories are now ill advised, etc.
> To create his photograph, Niépce treated a heated pewter plate with bitumen of Judea, or Syrian asphalt, a naturally occurring asphalt with light-sensitive properties.

> Historians suspect Neolithic peoples used the camera obscura effect in some of their monuments. The Ancient Chinese philosopher Mozi (470 to 390 BCE) made the earliest known written reference to the camera obscura

A box with a small hole in one side, that has been known since pre-historic times, and a naturally occurring substance that's relatively easy to collect: that's all it takes to make a "photograph". But it was first tried in 1827.

I often wonder how many inventions could have been made way earlier than they were, and why. Is it possible that they were, in fact, made, but simply didn't catch on? Or did catch on but were then completely forgotten?

Many people think the Antikythera wasn't a one-of-a-kind but in fact a product, for example (probably made in the 2nd century BC).

And the Pascaline, the calculator that Pascal invented in 1642 and actually made to work in 1645, was never commercially successful. The first calculator that enjoyed a modicum of commercial success appeared only in 1851, two hundred years later.

Yet the people who had the scientific knowledge and manufacturing skills to build the Antikythera could have made the Pascaline (probably better, even).

It would be fun to imagine Antiquity with many modern inventions in it.
I think I need to rethink the way I wrote this article, because the wrong message is being understood. Clearly I have done a bad job at writing it. I should rewrite this article entirely. Thank you for the feedback
Humans are built to run long distance.
Ooooh, excellent additions, thanks :)
A LOT less vibration on a bike handlebar vs a motorcycle
"The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay." — Tony Hoare

It is impossible in practice to persuade people to pay the same amount for a simple, reliable product that they would pay for a complex, unreliable one with more features. Reliability is a promise, and they have to trust. Features can be demonstrated now, so less trust is involved (or so it appears).

And then the features stop working.
I guess it depends on the software that you are writing and how it's structured. The testing pyramid seems to make some sense, as long as you realize that you need a multitude of different tests for checking various things.

For example, when writing a library that dealt with JWT and called into some other libraries, I opted for a lot of unit tests, I think the code coverage was around 90-95%. Writing tests for almost all of the functionality helped me actually discover one or two bugs which I could immediately fix without having them be released. Also, tests acted as documentation there, showing various use cases for the library, in addition to helping me actually make the API more user friendly.

Integration and UI tests are also useful to see how the solution fares in the real world, but once you have to automate a browser or deal with mocking the DB (if you can't spin up a container, migrate the schema and seed it with real data for your tests), the complexity skyrockets. You might still want to have them and plenty of them, but at the same time you'll deal with slow and flaky tests more often, especially if the tech you choose or are stuck with won't support your needs all that well (e.g. Selenium). It's even worse if the thing you're testing changes a lot.

As long as you have a staging environment, you should be even well off for anything from load testing to even the occasional bit of manual/acceptance testing, or trying to reproduce issues there. With the help of logs/metrics you can reason about changes/bugs/reproduction scenarios more safely, without impact on prod. Even better with other supporting things, like feature flags. Test whatever you can: sometimes the limiting factor will be time, other times the complexity of the system (or how testable it is in the first place, e.g. no fixed element IDs in a web browser), other times you won't get the infrastructure, but it's still a nice pursuit.
It could be, but in general humans are pretty good at recovering from non continuous exposure to gasses and chemicals (except radiation).

But hearing can be broken in an instant.
A guide I wrote for $job that covers what I mention in the parent-parent post, and a couple other things: https://unito.io/blog/better-raspberry-pi-dashboards/

Note: only a guide, not scripted yet. See footnote for why :)
When Adobe released tools to allow you to release Flash Games as native apps on the App Store Steve Jobs had a total meltdown that resulted in the infamous clause 3.3.1 banning cross compilers.
I would love to see some numbers on how many people are able to make a living making music today vs 10 years ago.
It depends on what language you are using and what things you are testing.

If you use a language like Python, having tests that pass things that aren't the type you are expecting are useful. Likewise passing nulls to a nullable parameter, or different objects to an Object/Any type (or even a different implementation/type to a supertype parameter).

Those tests are part of the unit test repertoire, but unit tests should cover both expected cases/behaviour and unexpected cases.
You can disable updates. As long as the servers (and the OS) don’t break compatibility, you can continue to use the same old likely-non-backdoored version.
I see it expanding. Corporate customers are getting more strict not less about security. Security therefore can be a big unblocker for revenue. In a sense it is security but it is sales too. Like no compliance is no sale, whereas no feature XYZ may be negotiable.

Now add in the hellishly complex cloud environments and k8s, terraform and the like.
What it will speak about? I can suppose two options:

1. I am your God and will take care of you until you are old and your hair is gray.

2. GTFO from my Earth you scumbags.
That’s up to the customer. If the software is delivering good return on investment, they really might not care at all.
Yeah, ok, but I suppose you need more components, so more space, so a bigger board and higher assembly cost.
Like in your other story, the response you got is actually pretty reasonable and you seem to be slightly out of step with what other people are thinking here.

The fashion for high functioning, highly articulate individuals calling themselves "autistic" is relatively new. To the vast majority of people the word autistic means severe disability that requires constant care, involves repetitive stimming motions and often is directly visible via an abnormal facial structure.

In this conventional usage of the term autistic people don't turn up to job interviews and say "Oh your brother is autistic, cool that it inspired you, I'm autistic too!" because they don't turn up to job interviews at all. Depending on how severe her brother's condition is she may well have been quietly offended that you were trying to pass yourself off as having a similar problem.
I agree but I don't need the keys look anything. The best thing happened to my keyboard life so far was having to use a keyboard without the letters of a language I used daily drawn on it. I would rather buy "das keyboard" with purely black keys but it doesn't have enough keys for me to invest in.

However, I would love to have your software-defined visually configurable keyboard as a second one on my table and every app using it as a sorg of a "toolbar" / command palette. This was what Apple tried sort of (it would have been nice idea if they didn't sacrifice a real keys row for it). To me it sounds like an additional display with touch support can do the job.
They also have an ad where it's mounted on an engine hood of a tractor

https://www.youtube.com/watch?v=kuOQdo7t3Xk
I think the real value in unit tests isn't validating your logic is accurate (although sometimes it is for logic heavy methods as you say), but in validating that subsequent changes (often made by other devs) don't break prior logic.

In complex codebases it's easy to miss things when making changes and unit tests are great ways to catch issues in really simple bits of logic that have just later been overlooked.

Integration tests are typically so heavy and multivariable they can only be used to validate the most common scenarios. They're great sanity checks, but provide terrible coverage whenever there exists nuanced logic.
It's interesting to think that, by a combination of the grainy results and lengthy manual process involving plates and chemicals etc., photography was probably thought of so much more so as an art form, a method of rendering a picture (cf. painting, pressing), than we'd consider it today or even through C20 with less access to it (no camera phones) and it coming at greater cost & with delayed results (pre-digital).
I'm the first one to hate on JS, but the whole integrated event loop, with auto scheduled async tasks and Promise system that works both with callbacks or async is one of the easiest system for http calls I ever used.
That mistake makes a lot of sci-fi unintentionally funny. Especially if you interpret "energy dampener" to be some guy that runs around shooting any electronics with a water gun.
It was always funny listening to Apple peeps in that time period complain about that horrible, resource sucking, unstable, machine crashing web plugin and realise they weren't talking about the Windows Quicktime web player.
It's not an emotional channel, at least not purely. And you can express that very well in text, too. You just need to cut the irony and sarcasm. For the (rather dumb and contrived) examples from the article

* Unfortunately, her cake she was terrible.

* Her cake was such a failure, I had to laugh.

* She made a nice cake.
You'd be quite unlikely to stumble across this one though wouldn't you? I assume the theory came first in this case - and that may have built on centuries of study.
One of my children has severe epilepsy and has a Vagus Nerve Stimulation device implanted - Sentiva 1000

https://www.livanova.com/epilepsy-vnstherapy/en-gb/hcp/produ...

It has really helped although obviously it took surgery and then also nine months of slowly tweaking the settings.

Before the VNS they could (for example) not go on a trampoline for more than a few minutes without having a seizure, but now they're fine all day. They did still have seizures at night after the VNS but we tackled those with a different treatment.

The Sentiva 1000 sends regular soft pulses (for one minute every 3.5 minutes) and can also react to heart rate rising suddenly (which might mean a seizure) by automatically increasing its pulses. During a seizure if we want to manually activate the device we swipe over its location with a strong magnet and that activates it to send stronger pulses for a minute or so.

Batteries last about eight years. A few times a year we go to check the battery, the nurses have an ipad and a wand-type thing that they hold over the implants location, it uses some sort of low power NFC to read data and diagnostics from the implant. When we do need to change the battery that will be an operation. But less complicated than the initial operation (and even that was in-and-out in one day)

All pretty amazing.
Trying to avoid shipping bugs is a defense-in-depth affair, because fundamentally tests can only show the existence of a bug, but not that a program is bug-free. It starts right in the editor, where syntax highlighting can help with spotting mistakes such as writing 010 instead of 10 (0 prefix for octal is a terrible idea).

Pretty sure that bug-free code is one of the prides of programmers worth their salt; but there's no helping, when you forget about something while coding, it is very likely that you also forget to test it. That's why we need a separate tester.
> OO has a right to live on if there are still users and developers.

There have been almost no developers since IBM left in late 2013.

There are users, but users without developers is an ever-worsening security disaster.

So no - a public hazard does not have a "right to live on".
Collection of stand-alone Python machine learning recipes (2021)
Just because you find something inconvenient for marketing purpose doesn’t mean it’s propaganda. These are real people hitting exactly the problems cryptocurrency sales guys said they could avoid by using it, and they deserve the respect of not having their lived experience dismissed outright.

If you want to help cryptocurrency, put your time into fixing the problems rstger than still more empty marketing.
They definitely can be region specific. I never get Wirecutter, in fact I don't think I've ever visited the site. What I do tend to get is tomsguide, tweakers.net (which is local), and such.

Though interestingly I just tried your search and I get CNET, what hi-fi, and so on. Oddly google search is insisting in talking to me in English, which it doesn't usually do, so that's probably why I'm not getting local language results. If I write the search in Dutch then I get more results in that, not surprisingly. Typically I get a mix, so I dunno if something has changed on google's end or what.

Still no Wirecutter though.
I was about to ask the same question - basically the Packt books I have read have been (almost) universally poor quality.

It's been a long while since I've bothered with them so hoping that's changed somewhat.
I did not understand what is ZFS - could anyone be so kind to explain?
Describing people with cancer and dementia as deliberately driving up insurance prices just seems wrong
>In Oxford, he dined with Isaiah Berlin, considered by many to be the most-respected philosopher of the time.

Isaiah Berlin was absolutely not "the most-respected philosopher of the time", if this is supposed to mean "most respected as a philosopher".

In Europe he was considered a lesser academic philosopher, and in the US he wasn't that important either.
Also emojis are a derivative of emoticons (or smileys, as they were called if you went far enough back): https://en.wikipedia.org/wiki/Emoji
It was already normal back in the day of IRC and webmasters
I actually used to use ChatGPT but switched to the API once I had GPT-4 access. Mainly it’s because I simply didn’t use the $20 worth of the GPT-4 at the time. It was extremely slow and the question per hour limitation was annoying and stressful. I would always worry I would need it for something unexpected so I never used more than 15 questions at a time (but this has probably changed these couple months). In addition, the privacy implications are better for the API since the terms are better for how they handle your data. I also like how I can tie in GPT anywhere. I use the matrix bridge so you can give access to people like my parents who are not as tech literate to sign up and get used to chatgpt interface. I allow them to talk to it as a bot through WhatsApp bridge.
The product video features the
WINNINGEST MOTOX RACER OF ALL TIME (at 0:30)
which in terms of linguistic precision almost wraps around from awful to awesome.
I don’t think the average internet user thinks about state or form interaction the way that you seem to be suggesting they do.
If you’re going for guaranteed repeatable builds (for example you’re using Bazel) then you have no choice. Dependencies must have a single resolution.
Why is CUA-mode not enough?
Hands down LinkedIn is the single one.

Other than that - I haven't found anything useful among myriads of cv-ai-smart-ml-web3-bla-bla tools that are all over the internet these days.

I might only use Grammarly and ChatGPT for more or less adequate outreach.
> no, and for the same reason you can't use the output of a quarter million 2.45 Ghz microwave oven magnetrons to produce monochromic teal light (612500 Ghz).

Why we need monochromatic light? Gravitational wave background is just noise. A lot of orbiting objects in a galaxy will produce steady noise, due to interference. It's easy to check just by putting a bunch of wave generators with different frequencies in a same pond, and then move. Interference between waves will create noise with higher frequencies than original.

Even small effects are producing significant results over large periods of time. 1 billion years is 31.5E15 seconds.

If we integrate over all frequencies of gravitation noise floor, then we may have a number, which will explain a part of red shift.

More over, gravitational noise is important for Pilot Wave theory, because it may explain the source of energy for the pilot wave.

> no, same wavelength, going further on one half of the cycle, then not as far on the other half of the cycle. Same wavelength within the space, it's the space itself which changes.

It implies FTL speed at the second half of the cycle, which is impossible. If wavelength of light will be enlarged, then it will stay enlarged, because light traveling at c, so c-delta is possible, but c+delta is not.

> TBH, that would be a colossal waste of my time. I'm only even bothering to reply to this this now because discussion is supposed to be helpful while I learn things.

I have the same filling. I only reply because my pleasure to talk with you overcomes the inconvenience of Hacker News.

Maybe we should switch to email, or to a wiki with a proper set of tools for scientific discussion.
Pros and cons of using Shadow DOM and style encapsulation
I think I'm disagreeing with the definition implied by the article.
To me, an integration test involves integrating with another system.

Testing groups of functions or classes together is still a unit test, by Wikipedia's definition at least

"unit testing is a software testing method by which individual units of source code—sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures—are tested to determine whether they are fit for use" [1]

and by Michael Feather's definition

"A test is not a unit test if:

- It talks to the database

- It communicates across the network

- It touches the file system

- It can't run at the same time as any of your other unit tests

- You have to do special things to your environment (such as editing config files) to run it." [2]

Indeed, it's the inevitable result of doing TDD; the refactor step is likely to break out smaller classes/functions already covered by the existing tests.
If we write new, more granular tests every time we do the refactor step, then we end up with brittle tests.

[1] https://en.wikipedia.org/wiki/Unit_testing

[2] https://www.artima.com/weblogs/viewpost.jsp?thread=126923

Edit: To clarify, I'm not talking about calling the public API over the network, I'm talking about the public methods that consumers (including your network layer) would call.

That might be where the confusion lies here.
You can try Grist. Spreadsheet with Python formula support, and open source. https://www.getgrist.com/
https://github.com/gristlabs/grist-core/
ZFS is an advanced file system with integrated multi-device volume management. It was originally designed and implemented by Sun Microsystems for their Unix operating system Solaris. The copyright for the original codebase is now owned by Oracle and has since been closed up and made proprietary software. Prior to Oracle's acquisition of Sun, ZFS was made open source under the CDDL as part of OpenSolaris, that code was forked and it gave rise to OpenZFS which is used by many Linux and BSD users.

https://en.wikipedia.org/wiki/ZFS

https://openzfs.org
there are a ton of new companies who sell finasteride and minoxidil sponsoring basically every video on youtube, reach out to them and see who will pay you most for advertising
LibreOffice Draw is an excellent and very useful PDF editor. Just make very sure you have all the same fonts!
Total aside, I and others have had bad experiences with QuadLock. Ended up moving to the Peak Design mobile case and moto or universal mount and it’s been shockingly amazing.
Globals are a nightmare. Despite this being something really common to do for developers and something that will cause a pain for a lot of early adopters of [whatever software that requires it], I see this as a great move!
Probably, "I'm self conscious, but am still nothing to write home about. Neither AGI nor self-conscious AI implies some superhuman IQ. I also hate myself".