skysight-inc/HackerNews huggingface dataset:
Does it still require discrete graphics on Linux? It's been a very weird requirement from day one.
Clickable link: https://redact.dev
I feel the same way with the contact ability. Companies should have a human contact opportunity by law.
I edited over 100 podcast episodes with DaVinci Resolve 17. It's a really great tool not just for video editing but audio editing too.

Unfortunately Resolve 17 was never able to export mp4s for me without introducing both video and audio artifacts into the final video that didn't exist in the timeline when editing so I can't use it for editing video even though I want to. The issue might be hardware related but I'm not interesting in buying an entirely new computer for a chance that 1 application might work. I will give 18 a shot tho, I have a reproduceable video (a few minute 1080p screencast clip) that always produces the artifacts but it happens in every video I export with varying degrees of severeness (in all cases it makes the final video unusable). Their support didn't acknowledge the bug report I submit since I was using the free version of Resolve.

Everything else about the product was great tho, I would buy the pro version in a second if I knew it would export mp4s without artifacts on my machine but there's no way to trial the "pro" version as far as I know.
If it doesn't error in undefined keys you cannot help people figuring out when they introduced a typo in their config
Measurements You Should Make and Then Ignore (Plus One to Watch Intently)
> They can't fight or flight so their defense is toxins.

The very next sentence.

Animals can run away or fight, so they don't have the need to develop other deterrents. I guess aside from a very few exceptions like Amazonian frogs, which would also not be recommended to eat without very special processing. Probably best to keep off the menu altogether, just like most seeds, stems, and leaves for the reasons described in the parent comment.
Has Apple cracked the code with the M1 Air? It's light. It runs a 'heavy OS'. Three's no fans, and no noise.
Extracting isn't the hard part. I have yet to figure out how to append Whatsapp message from a previous backup which I have held for 8 years.

The iOS backup was corrupted and I had to start over again at the time. The Whatsapp file was extracted but I never got round to it. ( Along with important pictures inside the Whatsapp)

To this day I still blame on it on iOS backup problem. Which is still a thing in 2022.

I wonder why Facebook hasn't made an iOS to Android Whatsapp history transfer a priority. To most people outside of US, Whatsapp history transfer is the biggest lock in with the Smartphone ecosystem.
Meh, the older 12” MacBook (not pro, not air) was also fanless. I miss that 2 lbs design quite a bit.
If i hadn't bought Final Cut Pro and Motion back in 2011 - with a nice discount thanks to iTunes prepaid cards - DaVinci Resolve would be my first choice. I particular i've heard great things about their colour grading tools.
>people on HN should seriously question the competency of the average user here.

Intentionally miss my point, misrepresent my claim, insult me in the last sentence. Nice.
I'm not sure why one would use this "backgroundchecks" redirection link, which just appears to add ads to the top of the page. The actual site is https://justdeleteme.xyz/
This should work.

The automated ID verification might fail for a variety of reasons (frankly if they don’t originally have a copy I’m not sure what they’d be comparing it to) but the GDPR process should work if you fight long enough. You might need to prove that you owned the email or number though - email might be tricky but number is easier as you can submit a bill or do another subject access request to your provider which should still have records about it.

Good luck!
This is a naive question from someone who hasn't been involved in project management in almost a decade, but why can't feature development and refactoring be split across two different ownership groups?

The first group writes the initial version and all iterations (extra features) up to the point where the expected returns from quickly pushing out future iterations is less than the amount of required effort.

The second group then comes in and does a complete refactor, without changing the look or feel of anything that the customer actually wants. Meanwhile, the first group moves onto "the next big thing".
>Also a great place to work too.

100% man. I left two years ago due to some major life changes I didn't know how to handle, but still get nostalgic about the place to this day. It's not just the perks, but the culture too - both in terms of striving to improve as professionals and the laid-back, larrikin attitude towards just about everything else.

I run my own business now, but my long-term goal is to be able to create the same environment and provide the same opportunities that Blackmagic gave me.

>coffee daily

You're really underselling Bing there, mate. ;)
Ugh, more Japanese self-glorification.

News: such lone dedicated craftsmen and their acolytes have existed everywhere in the world.
Some struggle on without much appreciation, some are dead, and some were killed for 'progress'. Japan's craftsmen too are a dying breed after 150y of Meiji-Industrial revolution.

It's nice that they're trying to keep the crafts/traditions alive, but there's nothing unique about them. The old-world hangs on by a thin thread, waiting for its misery to end, while the plebs clap on and cheer.
Everywhere that a clippy lint is there to catch bugs, I wish it wasn't a clippy lint because it won't always get run and those bugs will get missed.

An example of a clippy lint that I like in clippy:

If you try to transmute() &[u8] into a &str clippy will point out that you should probably from_utf8_unchecked() -- this lint results in code that does the same thing but is clearer for maintainers about what we intended. If our reaction to the lint is "But it isn't UTF-8" then we just got an important red flag, but that's not why the lint is there.

On the other hand, clippy lints for truncating casts and I want those gone from the language so the warnings ought to at least live in the compiler not clippy. I would like to see a future Edition outlaw these casts entirely so that you need to write a truncating cast explicitly if that's what you needed.
I suppose that, over simplified, a startup in the US or UK can choose whatever to target in the whole world, whilst a startup in a poorer country might afford to target only poorer countries? (as its first step)
Can't read the whole thing cause it's paywalled, but this has existed for a while. Founding engineers usually get screwed in their base salary compared later hires for example.

Unless your company is especially aware of how market salaries work, you are most likely losing money by staying put more than 3 years at the same job.
Why mention Apple and then pull a 50% figure out of thin air? Apple market share for global smartphones is 23.4%. Tesla is 13.8% of global EVs. Not as dominant but still respectable.
Genuine question: are airborne diseases not spread by droplets?

I always assumed that it was the water droplets that carried viruses and bacteria, rather than them just floating freely in dry air.
Because other distros have different ideological reasons for packaging Firefox their way than Canonical. Fedora, for example, applies patches to Firefox before distributing their rpm.
Not necessarily. In my current role I am the implementer, and I may have to explain the current behavior of systems to managers. But they ultimately make the decision on what gets changed.

I present it as business impact / use cases, they decide what “policy” (non-tech) changes they want to make, and I decide how to technically best implement that considering the existing design and new changes.
Are you talking about devices like the Maschine+ for example? Those are just DAWs in a more portable format. Works just like their Maschine software, but on a smaller screen and more hardware controls.

Elektron makes hardware that is very different than a DAW-but-portable.
That’s how ethics goes. It’s fine to give someone something if you don’t know what it’s going to do. Makes it kinda difficult to disprove/ confirm a common belief that something is bad for your health.
> the fuck are you on about?

wow, tough guy here :) I recommend you seek the truth over emotional highs. If you're not willing to do the work then be quiet - not for me but for your own good. FYI I wrote a two theses on the topic and read through tons of available material and defended both in front of a panel of people who served as ambassadors and are highly credible politologists, international lawyers, geopoliticists and I have zero investment in either side being right.
- "au fur et à mesure"

- graduellement

- progressivement

- petit à petit

--------

side note: for some reason I find the use french words, terms, and expressions in English (and there are a lot, in a strict technical sense almost every french word is a valid English word) somewhat annoying because they usually diverge with time in ways that are important enough to change meaning but not enough for the sense to be inferred just from local context alone. given how prevalent anglicisms are in french this make for more confusing and verbose conversations.

--------

Ex: "mise en place" just mean setup, so image two french software engineers talking about software "setup", one that has in his mind the meaning/philosophy meant here and the other using the more generic meaning.
I like fans. If you have decent fans things are cool and quiet. I wish my phone had active cooling.
Anything working with (downloading) massive datasets would 'work' slower, but as fast as possible (provided the supplier can keep up too) is better?

Add in a requirement/desire for it being real-time (or equivalently (you'd get further and further behind) continual) and it could be necessary if large (per second) enough.
Mutt is the only client that is fully featured and not broken: https://lwn.net/Articles/837960/

Nothing else comes close.

Discussion on HN: https://news.ycombinator.com/item?id=25222166
In Japans case because of Fukashima; whatever your views on Nuclear you can't really blame Japan for being spooked by that.
> This is a possibility that I thought about at some point myself, as I am sure many others in the field have too. I eventually came to the conclusion that it doesn’t work. So I am somewhat skeptical that their proposal actually solves the problem. But maybe I was wrong and they are right. Gerard ‘t Hooft by the way also thinks the information comes out in gravitons, though in a different way then Hsu and Calmet. So this is not an outlandish idea.

"So this is not an uncommon idea." FTFY
If you're on a Mac, Spark:

https://sparkmailapp.com/
I have the opposite problem... I find perl's data structures so ridiculously easy to write that I can quickly build up arrays of hashes of arrays of (ad infinitum) while in the "flow". Throw in the ability to actually get references to things, and control de-referencing of things, and I've never felt perl has stopped me (for better or worse!) from doing anything with data structures.
Ha yes the loveable and wise Bing. I almost mentioned her. Very much the mother of a whole company of odd-sock wearing PhDs.
And I'm still struggling to see any difference.

> I’m still struggling to see the relevance though, trying to get me to buy things is very different from trying to get me to use a feature you profit from (in my opinion).
S/he wrote:

> Give a pause to though

That's very different from what you wrote:

> repress your thoughts

(I suspect you have to me extremely odd ideas about what meditation is, and why try it. I wonder if you'd actually like it)
Evidently, at least two people care.
I know I need to look for a new job. My last raise was much smaller than the people who left and I can tell I'm emotionally done with the technology I'm working with.

I really hate job hunting though and the company I'm at now is particularly friendly to its employees and has a mission that I'm personally aligned with which is pretty rare (not to mention I have an amazing boss, if it weren't for her I might have left.)
The chips run too hot under normal workloads to not have a fan. Not having a fan would reduce performance and make it not worth the additional cost for the ‘faster’ chip.

My opinion is intel/amd are not incentivised to make silent / fanless designs as they are hard to market as they are not going to be the fastest. Apple are incentivised as a silent cool running computer is something people will buy.
Calorie density? Teeth may have been 'designed' for low-caloric-density foods. The art of civilization is increasing that density, so we have time to do other things (civilized things)
I'm lovin' Caddy! Below is a typical reverse proxy + www redirect + static file serving. It's so much more readable and simple than Apache/Nginx that I can't imagine switching back.

www.example.com {
redir https://example.com{uri}
}

example.com {

# tell Caddy where your favicon files are
@favicon {
path /favicon.ico
# + other favicon files...
# ...
# ...
}

# serve your static files
route /static/* {
root * /var/cache/example.com
header Cache-Control max-age=31536000 # 1 year
file_server
}

# serve your favicon files from your favicon route
route @favicon {
root * /var/cache/example.com/favicons
file_server
}

encode zstd gzip

# reverse proxy to your app
reverse_proxy 127.0.0.1:8080

# do some logging
log {
format json
output file /var/log/caddy/example.com/access.log {
roll_size 100MiB
roll_keep 10
roll_keep_for 2160h # 90 days
}
}
}
My iPhone 7 supports sync over WiFi. I've never benchmarked it, but I'd expect the speed to be better than USB 2.
$ perl -E 'my $f=[[{X=>{Y=>["FOO"]}}]]; say $f->[0][0]{X}{Y}[0];my $g=$f->[0][0]{X}{Y}; say $g->[0]'
FOO
FOO

Seems pretty trivial.
> It is like Ansible or Terraform for a semi-idempotent distro

"Like" does a lot of work here. Those systems go one way: what if we applied this concept to managing existing systems. Nix goes the other: what if we built a system around this concept. I think that's a nice elevator pitch, but misses a lot otherwise.
During my high school, I had a bunch of (amateur) projects involving video editing. As a broke student in a poor country who didn't want to just torrent Premiere and call it a day, I started exploring several FOSS video editors:

- OpenShot: simple interface, but crashes quite a lot

- Kdenlive: clunky and crashes way too much

- Shotcut: good for quick edit and the most stable out of the three

The biggest problem I had as a novice is the lack of tutorials/documentation. I then tried some freeware options (including HitFilm Express which I also found to be good) before finally settled with Resolve. When it comes to features and stability, especially in SFX and color grading, Resolve is far more superior and also has more resources to learn from. Of course, that means it is heavier and more complex, but it satisfies my needs so well that I don't mind roasting my CPU. It remains one my favorite piece of software and has only improved since then.
Why is "commercially applicable" more mundane than "not commercially applicable"? If anything, I'm excited by something I might be able to use more than something I won't.
Magnus Carlsen famously went into a Lichess Bullet Shield online tournament very late, and clicked 100% on "berserk" mode which means his 1 minute time was cut in half to 30 seconds, and still managed to win 88% of the games and climb to #3 at the end. The first batch of games were of course very very easy for him but in the middle of the video and forward there was more of a challenge, especially at the 30 second time control it's amazing to watch. The bottleneck is probably his mouseclicks, not the brain :)

https://www.youtube.com/watch?v=NTEj4moaay0
I suspect that Mozilla looks at the telemetry and very few people use containers. I'd guess because users don't understand what they're good for. Perhaps you, an enthusiastic user, could do a little writeup somewhere (here?) on why they are the cat's meow.
I'm sure there's >10Gbits of 'gis/satellite data' available every second if you want it?

Or what if you want a bunch of historical data for some sort of analysis, and you'd like to start that now, not next week when it finishes downloading? If it's historical (i.e. sitting there available to download) then faster is always better right? If your connection is the bottleneck then all else equal why wouldn't you want it?

(I imagine 10Gbps is about the point currently where it's not necessarily going to help going faster on your end, unless you you have multiple (concurrent) sources, or know that even at that you're still still the bottleneck.)
I’m curious why you say Unity will have no choice but to go open source?
Definitly. I've been replacing some of my more janky & complex bash scripts with ruby and it becomes a lot cleaner imo. Also, I recently 'discovered' Pathname, it takes away a lot of the pain of dealing with files and directories in ruby and allows for pretty clean code imo.
If people on the right are diverse and not "blended together", how would be possible for me to guess your political indentity?

Sure, you could be a Monarchist, Conservative Christian, Reagan Conservative, Centrist, Classical Liberal, AnCap, libertarian, etc.

But all the secrecy points to things it would be rude to guess: nazi, strasserite, pedofile, burgundist, etc..
Corroding the willingness and ability to think and communicate clearly. Why bother? Not only will nothing change, it won't even be respected.
Survivor of a cult does not necessarily mean that someone joined a cult themselves. Kids escaping environment they were born in may be survivors of a cult. People with spouses who joined a cult may be survivors. Environments may change, leaving a mainstream church in a specific area may mean leaving a cult. Etc. Don't look down on them unless you know all the details.
OpenSea is not providing any tool for businesses to sell and be compliant with tax authorities. You sell to anons, don’t collect vat etc
From some quick searches, it sounds like modern jet engines are up to ~40% energy efficient, measuring kerosene ==> thrust. I'll guess that production-aircraft-grade hydrogen fuel cells won't get past 85% efficient (hydrogen ==> electricity). Then you have the inefficiencies of the electric motor, and the propeller. Maybe 60% total efficiency could be achieved? (So 1.5x the current-generation commercial jet engine efficiency.)

My point: Your "much more efficient" looks correct, as language to use among informed engineers. But risky to use around managers, customers, etc. - who'll quickly develop fantasies of around-the-world jumbo jet flights, powered by the hydrogen tank in their carry-on duffel bag.
> By contrast, just California alone produced 173500 metric tonnes of just bell peppers. California alone produced almost 1000000 metric tonnes of sugarbeets.

California exports a lot of stuff. Canada may simply be trying to feed itself, so the 'extra' volume may not be considered a major consideration.

> […] the scale doesn't really come close to what is happening in the US southwest.

How useful is scale if it can't be sustained?
The concern with SEO is that the goal is to drive traffic to a site without meaningfully improving the content. Doesn't the same argument apply here? If the video doesn't change, and it's just the title and thumbnail changing in an effort to get more clicks, how is that materially different from SEO?
Sounds more like ownership annotation than generations.

Generations basically takes advantage of the fact that recently allocated memory is much more likely to be deallocated sooner - ie. it's run time/age based.

What you're describing with arena is more like ownership where siblings can't outlive ancestors - ie. deallocate when parent/root (arena container) is deallocated.
> For messaging purposes, it is absolutely identical to JSON in this regard. Once you have many existing implementations out in the wild that need to interact with each other, you'll need namespaces or their NIH analogue. And JSONs with namespaces will be just as bloated as XML.

It's definitely not identical. There's one major difference, that rarely seems to get mentioned but seems to be responsible for most of the pain:

JSON maps directly to language-native data structures, but XML does not.

The reason for this is that XML distinguishes between child nodes and attributes, but in the basic data structures that most languages have, there's no way to represent this in a conflict-free manner without doing something like `{ attributes: { ... }, children: [ ... ] }`, which is an awkward structure to query.

The result is that when you're working with XML, you almost always end up with a "data API" that's designed specifically for XML (eg. classes representing nodes with getters for attributes and children), whereas with JSON you're generally working with simple nested lists and structs.

This introduces relatively much complexity in what's a "hot path" in terms of development effort - every single time you want to interact with the deserialized data (which is all the time!), you have to deal with an XML-specific data structure instead of treating it as "just another source-agnostic pile of structs/objects".

The result is tightly coupled code that requires the reader to be familiar with the specific XML API/representation being used, instead of it 1:1 mapping from the serialized data to a language-native data structure. That's not good!

While it is true that you are likely to implement a namespace-like mechanism in JSON as well, for open protocols, the difference is that the format itself does not specially define namespaces - which means that the 1:1 mapping always remains true, and it's the protocol developer's choice to eg. reserve a `children` property to contain child nodes, with the understanding that that property then cannot be used for other things anymore.

XML deserializers cannot do this; it's entirely possible for XML to exist that looks like `<tag children="yes"><subtag/></tag>`, and therefore there is no possible 1:1 mapping that a deserializer can use that's guaranteed not to make certain data inaccessible. And since child nodes are not represented as an attribute in XML's data model, you cannot expect protocol designers to avoid a specific attribute either.

Bottom line: I suspect that this seemingly small design difference has far-reaching second-order effects in how deserializers are implemented, and that that is responsible for most of the pain that people experience in working with XML.
First, I want to ask you to write up a 101/how-to for this diet (and include one for pescatarians like me). Cuz this is great.

Second, my friends and I (years and tears ago) got really into Price and the (recipe /cook) book based on his work, Nourishing Traditions. I recommend this work to anyone into the above. Was this book a part of you coming to these conclusions?
The Galaxy platform for accessible, reproducible and collab biomedical analyses
Funnily enough until they said their country was such, I assumed they were American saying 'global' South to distinguish from meaning a South American country.

'Southern hemisphere' is fine though I think? And I assume that's what was meant.
There is another reason, there were way more brands of android phones in the past. I'm looking to buy a new phone, a flagship and my choices are basically Samsung, oneplus and xiaomi, each with its own issues. Samsung s22 in Europe reviews show that its a failure. Oneplus software took the wrong direction the last few models and xiaomi is just xiaomi with ads all over the place.
Strictly speaking all x86 MOVs would have to decompile to some level of atomic load/stores, because of the ordering guarantees on x86.

That's an example of "lost in translation" as we don't know if the original source required ordering or not. x86 cannot express the weakest memory model supported by C.