skysight-inc/HackerNews huggingface dataset:
This is a good undocumented feature for choosing which emails to delete in Gmail:

>Gmail supports an undocumented “size” search operator that you can use to quickly find all the big emails in the mailbox whose size exceeds a particular threshold. The search syntax is:

>size:[size in bytes]

>To give a real example, a Gmail search query like size:5242880 will list all big emails who size is 5 MB or greater while size:10485760 will list email messages that are bigger than 10 MB.

>You may specify the size in MB as well which makes it a lot easier. For instance, size:5MB (or say size:5M) will find all Gmail messages that are 5 MB or greater in size.

https://www.labnol.org/internet/gmail-size-search/26669/
I won the first puzzle in 4 guesses, but had a tough time understanding the rules. I think some more clarification/simplification is in order. For example, it took me a minute to understand the colors represented gold/silver/bronze...
Transportation and freight cargo will likely remain, right? Heavy Machinery (excavators, loaders, etc) will likely not transition to electric. I agree that it looks like a diminishing demanded job, but we'll probably have ICE vehicles and machine still for a long time, right?
>Delayed CC is definitely an interesting idea!

You can set a video player to delay subs - it's absolutely awful. My spouse prefers having the subs in almost all cases - helps mumbling (talking through their asses as it being called) profoundly.
> GitHub issues, which is obviously the correct place to put things

Unless you care about project portability. In which case, GH issues are obviously the wrong, locked-in place to put things.

Not that there is an obvious solution to this problem. There are a few tools trying to fix this, but they're still a bit awkward. I wish Git added a somewhat-native/idiomatic way to deal with it.
Hopefully, but let's not forget about the power crisis that Texas had semi recently which may continue to give Texas a bad name in regards to infrastructure for a long time to come. I doubt that the residents affected forget that quickly.
I've been using the same (Synology) share for years with not a single corruption (that I know of). I've set TimeMachine to only run at night though when the laptop tends to sit on my desk where it has ethernet.
> UD is supposed to allow C to be implemented on different architectures

No, that's wrong. Implementation-Defined Behavior is supposed to allow C to be implemented on different architectures. In those cases, the implementation must define the behavior itself, and stick with it. UB, on the other hand, exists for compiler authors to optimize.

If you want to be mad at someone, be mad at the C standard for defining so much stuff as UB instead of implementation-defined behavior. Integer overflow should really be implementation-defined instead.
It may have been 2-4 seconds for your dev machine at work but 15-20 for a typical user.
What I learned from "The Goal" is that any business/system will always have a single bottleneck that dictates the max throughput of the whole business/system.

So as a manager it is your #1 objective to find that bottleneck and remove it. And the moment you remove it, the max throughput of the whole business/system improves until some other bottleneck is now limiting throughput. So you repeat finding and fixing that bottleneck etc.

There are of course different ways to fix the bottleneck. Kanban is a famous example of one. However even with Kanban the business will still have a bottleneck that limits throughput.
Kinda yes, in a more serious sense, there will be new roles for humans
to play with respect to moderating technologies;

"Bladerunners" might not be exactly what P.K Dick imagined, but maybe
not so far off.

If we take AI to be the science fiction vision we seem to wish for
then it will require managing, stewarding, planning, opposing,
judging, teaching, healing, hunting down and deactivating, sabotaging,
negotiating with....

Bricklayers became architects, surveyors and town planners as
complexity increased in the construction world. Cities evolved to have
traffic wardens and police... but the same has yet to really mature in
digital technology. We imagine all these benefits of "smart cities"
and "digital working" - many ideologies that have been around since
the 1970s. Yet software engineering is still in its infancy with
respect to civic function, ethics, rights and responsibilities,
remedies and rules.

We have a more or less laissez-faire free-for-all market economy that
produces isolated "goods". The failure of this default model can be
seen in the tombstones of the Google graveyard. And, while it was a
driver of innovation for some time, it isn't really working out in the
big "civic" sense, and we certainly cannot rely upon centralised mega
monopoly Big-Tech to do the right thing (except in a William Gibson
style techno-fascist dystopia).

So I think many timeless jobs will adapt so that technologies can fit
into our society, as welcome, well-managed friends, rather than
allowing them to take-over our society. Maintaining that balance will
be a new frontier for human intellectual labour in teaching, legal,
planning and policing functions.
The logic worked for 29999 years, which is the whole point. It's like the German Tank Problem[0], but for lifespans.

[0]: https://en.wikipedia.org/wiki/German_tank_problem
Amongus in Rust. Destroy your codebase with AmongRust
I just published a crate that allows you to reveal all the imposters hiding in your sus code ( get it? source code. hehe! )

All you need is "cargo install amongrust" and you can use it in any projects you want. It is totally non-destructive and only adds code comments in your sus code.

crates.io: https://crates.io/crates/amongrust Github: https://github.com/0xhiro/amongrust

Give it a star if you like it uwu
> When you choose not to use Youtube, you are choosing to not be a part of a large part of society

YouTube isn't a large part of society. People use it to watch silly/educational videos far more than as a social platform.
Petrol stations will disappear, they'll get replaced by petrol delivery companies which will simply deliver petrol for your vintage vehicle, possibly with some sort of subscription.

I can see the petrol stations near the city centres becoming multi storey parking lots with electric chargers, and the ones on the outskirts becoming cafés with electric chargers. I'm fairly certain battery swapping won't become a thing, people take the piss when it comes to stuff that isn't theirs, just look at the city scooters debacle.
I remember the internal presentation that introduced the notion of DevOps to all the teams and the warm fuzzy feelings it gave us. The Venn diagrams and all. That was in 2016.

I also remember seeing "DevOps" quickly becoming just another role and silo and the everlasting disappointment of seeing yet another promising idea becoming the exact opposite of what it was supposed to be.

Happens way too often in "tech".
State of Control (documentary, 2022)
Have you tried these options for running glibc software on Alpine?

https://wiki.alpinelinux.org/wiki/Running_glibc_programs
Yeah. Look at the millions of words written on tweaking prompts.

And while SD is very impressive, it’s going to be a long time before it’s producing high res imagery, at least without ready access to lots of data center grade hardware)
There's a difference between people being able to make money based on them doing a good job, which is Adam Smith-style selfishness, and me wanting a Porsche, so taking one from someone, which is not.
Well, the _entire stock image industry_ has surely been disrupted. If you relied on stock imagery last year as your primary source of income, you may be out of work come next year.

https://www.shutterstock.com/press/20435
Can we all stop for a moment to appreciate this fantastic content?

Great writing, with well-picked and carefully crafted examples, with lots of good (and correct) advice. On a web page. That you can just read.

If you don't appreciate this, let's describe what this website is NOT: it is not an ad-ridden cesspool of misinformation with auto-generated text interspersed with ads. It does not smack you in the face with a SUBSCRIBE NOW popup. It does not drag you through the mud of misleading "customize my cookie preferences" dialogs. It has zero trackers. And the information is not posted on Facebook, Tumblr, Blogger, Medium, or any of the other black holes where content goes to be stamped with "SUBSCRIBE NOW LOGIN NOW" popups and eventually disappear and die.

Michał's writing is excellent (his "Guerrilla guide to CNC and resin casting" at https://lcamtuf.coredump.cx/gcnc/ is a classic already), but it's not just the writing that makes this content so great.

When reading this, I am reminded of the early days of the web and it makes me happy.
He is checking if the output is in a sane range. Not if the input values where. This may be correct for a trivial toy example but bite you in actual production code. Fun things like malloc(ab) vs calloc(a,b) where ab overflows in a well defined way and gives you valid pointer to an unexpectedly tiny buffer.
The "[...] executing that program with that input [...]" part maybe could be read as making it specific to a given UB triggering execution; but I'm no language lawyer :).
This is not a counter-point.

A "subject" might be any concrete thing- not merely valuable things in a worldly way. A candy wrapper, a stone, a broken cup, any thing.

It can also be an abstract thing as well.

What GP is saying- there must be a thing.
You misunderstood me. I was writing about demographics.
So, we're agreed then that farming as a profession remains?

I'm smack bang in the middle of a large agricultural region and while farm areas are larger than ever before they are multi million dollar (in annual cash flow) family businesses still.

They have massive sheds, small fleets of machinery, WAN's and storage, welding shops, silos .. and are still extended family businesses that are crying out for more boots on the ground.

The nature of farming has changed and will continue to change, but there will continue to be farmers; the robot that fixes the robots will get bogged and need repair itself.
But then again, UB doesn't mean the compiler author can't treat it as implementation-defined and do something reasonable.
Considering the engine is but one small part of the car, i doubt mechanics are going anywhere.
Does docker support true x86_64 emulation on arm64 hosts?
Using C++ as a scripting language, part 6
The way you'd assume they'd do it if they wanted relational values would be to never be able to edit prices, only create new ones.
Nowadays it looks like we are getting close to autonomous vehicles - but it was the same 20 years ago - I predicted then that drivers as a profession will disappear soon - and it still didn't happen.

Like many people have already noticed: we overestimate what can be accomplished in the short term and underestimate what can be accomplished in the long term.
Build stuff and post the updates on social media.
I am building a little apps for the past one year and tweet about them. Twitter now feels like my community. I love seeing what others are building, what their strategies are, how much they earn etc. I have some what grown to a phase where people give me feedback on my idea when I post them on Twitter.
There was no tracking or ad code except error reporting to bugsnag. Most of it was the firebase SDK. Which we did work towards removing, but which was a long term project because:

- Every single database read depended on it

- Many of them were subscriptions rather than simple reads, and so couldn’t be trivially replaced by an API call.

Don’t use firebase guys.
It doesn't have to be exact, no more than your input to Dall-E should be exact. Give the AI some understanding of intent of the project, some automatic metrics that will check AI's job quality and let it optimise against it. If AI doesn't generate what you wanted on the first run, correct it and let it learn. Basically what you would do with a junior developer.
Exactly, farming is a good example.
It was the dominant economy sector 100 years ago, and still is in many countries. Right now less than 2% of world population works on farming, if I am not mistaken.
But all the massive improvements, all the low hanging fruit it's gone - at least when you look at the next 50 years.
The more something is optimized, the harder is to optimize it harder.
Programming is as much encoding a domain and human communication as it is computation. If you can automate the first two, which is what you're claiming will happen, then all of human knowledge work could be automated. Call me skeptical.
Outdoors on a cloudy day can give excellent results too, especially if you use a camera where you can manually control the exposure.
Emulating it is a non trivial affair

The Playstation Classic can run fanmade Dreamcast emulators. I'd call that effectively trivial especially when it's a team with access to Sega's source code and intellectual property doing it.

Games were also relatively big so then you have the added cost of storage for those 40 or so games you would not include.

C'mon dude. A 64GB eMMC in bulk quantities costs less than three dollars a piece.
The recipe is to not accept click/touch after a while when you reshuffle a list.
That's really weird then. I'm often in Thailand and Google's never tried to change my interface language, though it does keep suggesting videos in Thai.
Make C Safe Again.

UBs in C language are the asleep plague just asking to get triggered into a głos bal disaster. Oops, too late.

There is another class of those there, described in some papers for CSmith. Milder but still quite bad.

Both got quietly not acted upon, when C++ got made.

Lets go back to Pascal/Modula/Oberon.
Of course! Thank you for the kind words!
Compose is a layer on top of the Docker client/API, so the container runtime provider shouldn't matter, I guess as long as there's a real dockerd under the hood, and modulo any bugs.
I wish I could use subtitles (especially on shows with a heavy accent...Peripheral was a pain sometimes) but I catch myself focussing on them too much and missing visual content. I tend to watch them even when I don't need them. It's quite annoying.
Almost all "jobs" will still exist, but will be different. "AI" and automation will make these jobs more efficient, but not replace them.

AI in the creative domain (art, music, writing, programming) will not replace the activity of crating and inventing. People still need to drive these tool, have a skill in controlling them, curate the output. Designers will still have a job to do.

People will still work in retail, maybe fewer on the checkout (thats already happening). People will still deliver parcel to your front door, the "last mile", just more efficiently with more automation in the rest of the process.

That not to say there wont me fewer people doing these jobs, in some cases dramatically fewer. But they will still all exist.

The question should be "what do our lives look like in 50 years time?". Are we still working 8 hour days 5 days a week? Do we still travel on "holiday" 1-2 times a year for a couple of weeks? This is where I think we will see the biggest change, the ways work slots into our lives, not the jobs that exist.
I'd be scared of scratching the glass of the scanner.
> It sounds like the source of much of it is just classic underestimation of the amount of work & complexity to implement something

Yeah, but this doesn't help, because the problem is that billing is perennially underestimated. Everyone thinks it looks easy, and offers "solutions" like those in this thread. And mostly they work, until one day you wake up and you no longer know how your bowl of spaghetti code works.
His point about how software on a high-end workstation barely changed over the course of 10 years is interesting. I feel like if you asked someone many decades ago whether hardware vs software would change more, they would likely say "software of course! it's easy to rewrite."

It's interesting to read a manpage on a slick, modern-seeming system like macOS and notice a date at the bottom which is literally last century.

I guess the key thing is the birth of self-sustaining "software ecosystems": even if the ecosystem is flawed, the benefit of being part of the ecosystem is really high, and choosing to be part of the ecosystem means adding to it, which makes the benefit of being part of it even greater. Unix is self-sustaining despite any flaws in the same way qwerty and the English language are self-sustaining despite any flaws. Unix is like a protocol for software projects to coordinate with each other and with human beings.

Ironically, if it wasn't for rapid development of hardware and broad penetration of computers throughout society, we might still be in a phase of rapid systems evolution, since the "ecosystems" wouldn't be as well-developed. Popularity increase -> lock-in.
For anyone interested, Rune's SOA is done entirely by DataDraw. The API for creating relations is passed almost verbatim to datadraw, which will generate a bunch of C code for interacting with the DD library. So Rune didn't really write any of this, it just bundled DD with a language runtime, and used a more permissive license despite DataDraw being LGPL... ! It was taking too long to set up Rune on an Ubuntu VM, so I just replicated Rune's version of the Benchmarks Game binary-tree benchmark using DataDraw directly.

DataDraw runs the depth=21 case (single threaded, -O3) in about 4.6 seconds on my M1. It has the built-in advantage of reusing the table allocations as the database is global and implicit, the indexes being u32 sized. The existing C++g++#7/MemoryPool and Rust#5/bumpalo versions (both array-of-structs) are discarding their allocations on every iteration. Running Rust#5/bumpalo with RAYON_NUM_THREADS=1 runs in about 2.7 seconds. So in addition to the implementation being someone else's and possibly misused LGPL, the claims re the binary tree benchmark are not really made out.

Nevertheless you can very closely approximate in Rust what DataDraw does, without macros or anything else, by creating a single global struct of `slab::Slab`s, inserting a dummy first element, converting the usize keys to NonZeroU32 and using this as your SOA. If you do that, then you get roughly the same perf except that DataDraw isn't doing bounds checks. So the Rust version can do it in about 5.5 seconds vs 4.6. Obviously this can't be parallelised as you're passing a single &mut SOA around or using a thread-local.

I also compared the perf for a `slotmap::SlotMap`. It was about 7 seconds, but it solves the ABA problem with the generational indices, so that may be worth it.

Finally I compared the perf for a global Slab<Node>, i.e. global AOS style, to avoid clouding the AOS results with bumpalo's insane performance. It ran quicker than the global SOA style, in 4.6 seconds, because the overhead of managing two arrays, their separate allocations and their bounds checks was too much for the memory access pattern to do anything, if there indeed was any advantage to it.
I'm in the fortunate position of knowing another language than english. While I'd much prefer watching with the original audio, sometimes I watch the dub because it's usually much clearer.
Set of general principles and practices in an organisation.
It's very easy to get an account here. In fact, I provided no email, and a password which I forgot. I literally can't log out. But point being is, registration is low effort.

This is good when there's no incentive to come here and troll. Communities like this one will stay sane as long as they're niche and unpopular. Once they become popular... well I think Elon sees with his own eyes what happens on Twitter.
Please mark (1936).
This us a rememberance piece for Ford Model T, which changed so much in America, and which all but disappeared by then.
We did actually test on older machines too, but the machine didn’t make a huge difference in this case, because it was network requests making it slow not JS execution.
MacOS contains tons of nice usability as a working environment, and even has great rolling package management with Homebrew, but the lack of native containers is the single biggest downside, basically preventing us from using containers more extensively at my work. The blocker for us is data work that needs a lot of memory locally, meaning it wouldn't work for us to allocate it to a VM for containers.
I've also wondered about the more speculative future of CAPTCHas - e.g. how to prove you are human when ML get better and better. Would be fun to add to the near future sci-fi I'm sometimes writing. I'd imagine CAPTCHAs could go towards social proofs ("Carl is asking you to verify he is human, are you sure?", doing things in the physical world ("Go out and make <this gesture> to the Google satellite") or being asked more and more difficult world reasoning questions, those that GPT (so far) struggle with.
> It seems unlikely given this exchange, as you seem to have decided to be as unhelpful as possible.

I'm not being unhelpful on purpose. They are just giving me answers that do not solve my problem. My problem is "Firefox requires overcommit to run for long periods of time ... because it has a memory leak". The solution to this problem is to figure out where the memory leak is coming from, and fix it, right? Not just to add more memory, even if it is only virtual memory.

> Guess what's going to create textures which might trigger such an issue? The browser's hardware acceleration. Guess what happens to browser's textures when the browser is killed? They're freed.

You just described a memory leak, yes, the exact issue that I am experiencing.

> Might be a bug in Firefox, might be a bug in the crash reporter, might be a bug in the driver, might be that chromium is not using hardware acceleration.

Well, I don't think the crash reporter or Chromium are at fault. And I know Chromium is using hardware acceleration because if I choose the d3d11 backend then Netflix goes black in screenshots due to DRM. So, if it is a graphics issue, it's something that Firefox does and Chromium does not. Which leaves Firefox bugs, or bugs in the driver that only Firefox triggers.

> But here you have a mozilla engineer specifically working on crashes, and instead of trying to work with them (possibly off-board) and with the data they have to diagnose the issue — because I'd assume when gsvelto talks about commit space contents that's what they see in the crash reports - you're just being a snarky asshole.

I'm sorry that I came off as a snarky asshole and that wasn't really my intention. I've been dealing with this issue for months, and as a result of that there is a lack of effort from me and that probably shows. I am sorry.

I would like to perform some more experiments to figure out what the issue is, but the problem is that when Firefox runs out of memory it also crashes half the other things on my system, which makes it dangerous.
You can install glibc+support libs on Alpine to run third-party software, but YMMV - I've had very mixed results.
Also fixing or at least iterating the corner cases and bugs that AIs generated. Someone needs to be there to tell AI to repeat what they did until solution generated is correct.
Depending on how your software is architected, there are other free clouds available: https://paul.totterman.name/posts/free-clouds/
Weapon smiths might be gone but weapons manufacturing is as big or even bigger than ever in history. So until humanity does a fundamental shift and stops all armed conflicts, it is as safe job as any.
We've got a few components written in C that I'm (partially) responsible for. It's mostly maintenance, but for reasons like this I run that code with -O0 in production, and add all those kinds of flags.

I'd be curious to know how much production code today that's written in C is that performance critical, i.e. depends on all those bonkers exploits of UB for optimizations. The Linux kernel seems to do fine without this.