skysight-inc/HackerNews huggingface dataset:
This is good advice for contract workers, but is not applicable for the vast majority of "at will" W-2 employees in the US, where terms of employment can be amended ... at will.
I was using BitKeeper at the time and was just glad that there was (going to be) an alternative to all that drama! BitKeeper was a nice product but man did they misunderstand their customers.
Super cool! I would add a checkbox to toggle whether you want background removal, or make that an optional second step. In about half the cases I tried, the background was an important part of my image and without it only weird artifacts remained.
I’m on your side. I just think understanding the “enemy” is usually more beneficial than not.

[edit] to explain, I’m using this information to push the organization toward improvements that I can sell without mentioning remote work, but which, if adopted, will surely cause people here to notice a smaller difference between WFH days and in-office days. It may take a while, but this should reduce reluctance to allow long stretches of, or indefinite, remote work.
> The other side of the coin, the other option we shouldn't really rely on but we can, is entirely blocked by the way these vendors operate. Android has had its fragmentation issues because the vendors aren't using the stock Android, and aren't upstreaming the drivers and tweaks needed to actually run Android on their hardware. There is usually an economic incentive to not do so (if a custom ROM can be made for their phone, they won't get the ad and deal revenue from the garbage they've preloaded into the phone).

That's a really long-winded way to say "Violate GPL of Linux Kernel".

Compiled in closed source modules is explicitly against terms of GPL2, and yet billions of violating portable computers.

And people wonder why I pirate? Our rights are constantly shat on by the same interests that would imprison us for copying software or movies.
I plan to do multiple implementations of iNet too.

If you made an implementation,
I will make a list of implementations in the homepage ( https://inet.run ),
and add your implementation to the list :)

------

I do not know much about LLM yet,
but I like hypergraphs too :)

(I learned about it from Wolfram Physics's docs.)
Protip: if you remove the "hidden" class name from the div containing the key word "Recents", you can see recent emojis made by others (which is both fun and disturbing)
Agreed, I was like, oh cool I get to learn about query engines with basic SQL with postgres or MySQL.
apparently "compostable" plastic are only compostable in industrial composters. If they're on the ground they still stick around for years.
I guarantee zig is 100x more production ready than 99% of the 4 million nested dependencies included in the average js project
Can you show a source for your iCloud backup CSAM scanning claim? These days iCloud supports E2EE so they have no ability to scan once you enable it.

Signal does not support any cloud backups and WhatsApp uses iCloud so this seems like a flawed comparison.
While the article elucidates well on the intricacies and challenges of async Rust, I feel it's crucial to note that one of Rust's core philosophies is ensuring memory safety without sacrificing performance.

The async patterns in Rust, especially with regards to data safety assurances for the compiler, are emblematic of this philosophy. Though there are complexities, the value proposition is a safer concurrency model that requires developers to think deeply about their data and execution flow. I do concur that Rust might not be the go-to for every massively concurrent userspace application, but for systems where robustness and safety are paramount, the trade-offs are justifiable. It's also worth noting that as the ecosystem evolves, we'll likely see more abstractions and libraries that ease these pain points.

Still, diving into the intricacies as this article does, gives developers a better foundational understanding, which in itself is invaluable.
> The worst of them before the pandemic were the ones that showed up at 11:30 ate free lunch and was out by 1:30.

So this is what they were doing with in office work and you think remote work is the issue?
This is like the piano version of hacker typer.

https://hackertyper.com/
I've come to feel that regulating a platform like Twitter as a public utility could be a well intentioned but unfathomably evil act.

Tweeting is the ultimate example of an activity that's designed to be engaging but is otherwise awful. I think it may be the very nature of popularity-driven ultra-short-form content that it encourages online mobs, cancel culture, dunks and hot takes.

If there's even a chance this is true then it would be criminal to calcify this medium in its currently known form as a permanent pillar of our public square - which regulating it as a public utility would do. We could be inflicting suffering on future generations that might have escaped it.

No. It's better to hope that we discover better ways of communicating, and tweeting becomes irrelevant and dies.
Azure Cosmos DB design patterns – Part 1: Attribute array
EME-free builds are available if you know where to look: https://ftp.mozilla.org/pub/firefox/releases/117.0/
Most of the rant, apart from the old man yells at function colors, is about lifetimes of arguments of async functions. And it's presenting a special case as some kind of pervasive limitation.

Async functions don't have to always own their arguments. Just the outermost future that is getting spawned on another thread has to. The rest of the async program can borrow arguments as usual. You don't need to spawn() every task — there are other primitives for running multiple futures, with borrowed data, on the same thread.

In fact, this ability for a future to borrow from itself is the reason why Rust has native await instead of using callbacks. Futures can be "self-referential" in Rust, and nothing else is allowed to.
Then you know what will happen. They will relentlessly spy on their users.

This is a for-profit company. It will always do what is more profitable, even if they don't do it right away.
It is clear in a non group conversation, since the contact will show up in a blue color in the “to” field.

In an MMS, it could be unclear, but only if you choose to put an email address in the “to” field. If you know it is an MMS, and you only use phone numbers, then it will not be an email.
Library developers can afford to deal with complexity much more than users of libraries. Offloading such work on highly skilled people developing the basic infrastructure is surely the right approach.
You can literally solve the housing cost issue if every company guaranteed remote. Live and work anywhere, housing solved.
Thanks a lot! Very helpful to apply for a new job.
Yeah, John Carmack should have been shot when he was breaking and entering his school to steal computers. Think of all his infamous deeds that could have been prevented.
That's more a feature of the messed up way US ties health insurance to employment, isn't it? Very few layoffs venture close to criminal territory, more part of how business works.
Or personal experience - to quote “And that's about four more sentences of extra clarification that none of your comments have even deserved”.

Personally? I’ve never had that level of vitriol unless I’m well and thoroughly in need of a vacation. Or in need of a new life entirely.

Since, you know, if you actually were congruent with that you’d never need to actually reply with that or even your prior responses.

But thanks for clarifying.
It's YouTuber clowns marshalling their fanbase of teenage kids who quite literally do not have fully developed brains yet. Very embarrassing indeed.
It’s not the targeting, it’s the largely surreptitious compilation of the dossier about people that is so vile.

If someone showed up at your house with a folder about a loved one, turns out they had been following them around town, tracking their movements, taking pictures, reading their emails, etc. I don’t think you’d be two thrilled, but hey they’re only going to use that info to target ads…pinky swear…
Some employees also already lived in a city with one of the "hub" offices, but were told that their particular team would be in a different hub, so they'd have to move anyway. They sent engineering to Chicago and product and design to LA/SF - a deliberately terrible organizational decision that was probably calculated to force the highest possible number of potential union members to quit.
I think that's the right take. If you're are legitimately good, and you press on long enough, (and admittedly you have some luck), you'll often win eventually.
Do you live in California? This is textbook whataboutism. Wtf does this bill have to do with homelessness?
this is what Go got right like 10 years ago
i don't see that many people with more than one contribution that have the caliber of linux. so to me it looks like that when the first big contribution is wildly successful, then they will stick working on that and not start other projects.

possibly one of the reasons why git could be successful is that linus quickly handed over development to someone else.

of the top of my head i can only think of a few people that created multiple wildly successful projects. donald knuth with his books and with TeX (and i am not sure if the books are considered wildly successful). richard stallman with emacs and gcc (and the GNU licenses), anders hejlsberg with turbo pascal, c# and maybe typescript.

if you look at everyone else, they usually have only one wildly successful project that they are known for.

here is a list of programmers: https://en.wikipedia.org/wiki/List_of_programmers
most there only have one project that is widely known. if they have multiple projects then most of those are smaller.
Apple is using the data first-party only and isn't reselling or otherwise making it available for third parties to use. Explain how it's not benign, other than "tracking bad". How does it harm consumers, or put customers at risk?
Hoare Was Right.

(But if you're only firing up a few tasks, why not just use threads? To get a nice wrapper around an I/O event loop?)
The power of spark is truthfully that it's really good at running sort + aggregate type queries on columnar stored data. Once you start needing to do complicated joins it becomes more about how you structure everything.
A common use case for maximized browser window - tab-bar on the left- or right-side of the browser, and websites set to zoom to more than 125+ % to read it comfortably ... With higher resolution and bigger screen monitors everything seems to be getting tinier and tinier on screen. :)
The status updates on this incident were very frustrating: https://www.issquareup.com/incidents/06zffytdqjdz

There is a global outage, stopping hundreds of millions of dollars of credit card transactions from processing, and all the detail they share is:

- "We are continuing to work on a fix for a disruption"

- "At this time, we do not have a solution for the disruption, though we have all the right people working to get it resolved"

- "Very sorry for the inconvenience today."

- "Thank you for your patience!"
I got laid off while working to fix a nasty bug that kept crashing our servers. I never finished or checked in that code, and the corpus of discovery leading to the solution was all ephemeral on my machine, so when I wiped said machine, it went up in smoke.

I wasn't deliberately sabotaging anything, and had I been given more notice than a morning video meeting with the office manager before my access was cut, I'd have probably checked in at least my WIP with a good commit message. But I wasn't, so I didn't
You know, the more I read about these things, the more I realize we are literally getting close to "spells" technology.

This is literally an entire paper about constructing a specific incantation to create an effect. Neither the author nor the LLM maker can completely deconstruct and trace every steps of the process from the input to the output. They only know how to chant a litany, add a request, chant another litany, then look at the output and hope they didn't summon Satan.
The east-west infrastructure really isn't there, and I guess that says a lot. Incentivized to get goods to and from the coasts, the national governments don't have the financial motivation to develop cross-continent highways. An interesting documentary about driving equipment into rural Congo, https://www.youtube.com/watch?v=vN_6jfIoYE4
I somewhat agree with the author, sometimes with async rust I need to figure out how to tell the compiler that yes I want to recursively call this async function. This can be a huge pain, especially because it’s not always clear what went wrong.

Other times however rust stops me from writing buggy code and where I didn’t quite understand what I was doing. In some sense it can help you understand what your software better (when the problem isn’t an implementation detail).

I get the authors frustration, I often have the same feelings. Sometimes you just want to tell rust to get out of your way.

As an aside, I think there is room for a language similar to golang with sum types and modules and be a joy.
Modern XEPs have brought XMPP to today. ActivityPub is fairly new too.
Chinese Communists, i.e. "Red Chinese". The people in control of the mainland after the nationalists got kicked out to Taiwan.
> (And we wouldn’t feel comfortable giving them access to our internal Slack anyhow.)

I can't wait till people start using LLM chat bots with RAG to exfiltrate private Slack conversations.
I think banking on SymEngineX ("SEX") for the Sympy 2.0 release would be interesting branding.

I'm also cheering for Sympy, I think it's longevity now still predicts success in the future.
> 96% of US users opted out of IDFA sharing

If it's so clear that users don't want to be tracked online, why don't we just ban it altogether? It would solve a lot of problems.
As with anything Android, it comes down to market share and variance. I doubt there’s an exclusivity agreement.

Samsung has really great products. How many people are buying that instead of an iPad? So many of my Android using friends will have an iPad.

Google let Android on tablets languish for years and the result is they’re such a small part of the marketplace that very few app developers can justify the return on investment.

And then even from those few Android tablets, how many have a good pen outside of Samsung?

It’s a niche of a niche of a niche to target
> But then rust also has channels. When you read about it, it talks about "messages", which to me means little objects. Like a few bytes little.

As a wise programmer once said, "Do not communicate by sharing memory; instead, share memory by communicating"
Bonus: ちち covers both titty and daddy. Food for thought. And babies too, I guess.
Async is also spread through so many crates that your program will have to be async in its entirety, or at least depend on the tokio crate for a lot of things. Want a web server? Async + tokio or gtfo. Want an sql connector? You better write your own, unless you want async. Each with a different solution to the various problems async brings -- and dont even get me started on async closures and such shit, thats where hell pokes through the earth and does unholy things your compiler.

I enjoy Rust, and I love how the compiler helps me solve problems. However, the ecosystem is "async or gtfo", or "just write it yourself if you dont want async lmao", and that's not good enough.
I can't go for golf, but I can read HN whole day easily in the office.
Is it normal the the report would not be public? I'm not often an FAA report enjoyer, but I would quite like to read this one!
Sprout24 CPU
Waiting asynchronously on multiple channels/signals. Heterogenous select is really nice.
Async Everything is a bad language.

Async/await was a terrible idea for fixing JavaScript's lack of proper blocked threading that is currently being bolted onto every language. It splits every language and every library-ecosystem in half and will cause pains for many years to come.

Everyone who worked with multi-threading outside of JavaScript knows that using actors/communicating sequential processes is the best way to do multi-threading.

I recently found an explanation for that in Joe Armstrong's thesis. He argues that the only way to understand multi-threaded programs is writing strictly sequential code for every thread and not muddling all the code for all the threads in one place:

"The structure of the program should exactly follow the structure of the problem. Each real world concurrent activity should be mapped onto exactly one concurrent process in our programming language. If there is a 1:1 mapping of the problem onto the program we say that the program is isomorphic to the problem.

It is extremely important that the mapping is exactly 1:1. The reason for this is that it minimizes the conceptual gap between the problem and the solution. If this mapping is not 1:1 the program will quickly degenerate, and become difficult to understand. This degeneration is often observed when non-CO languages ["non concurrency-oriented", looking at you JavaScript!] are used to solve concurrent problems. Often the only way to get the program to work is to force several independent activities to be controlled by the same language thread or process. This leads to a inevitable loss of clarity, and makes the programs subject to complex and irreproducible interference errors." [0]

[0] https://erlang.org/download/armstrong_thesis_2003.pdf

There is also a good rant against async/await by Ron Pressler who implemented project loom in java: https://www.youtube.com/watch?v=oNnITaBseYQ
Is electric propulsion even viable for passenger jets?
1B in cash but not profitable: https://twitter.com/typesfast/status/1700108412024127569
They're not lightweight and easy enough to use.

I have Docker on my Mac. I run things in it if I have to, but it's pretty resource heavy and I have to look at my notes every time I want to run "docker run".

Plus Docker isn't actually a fully secure sandbox!

There's Firecracker, which I believe is secure (AWS built it for Lambda after all) but good luck figuring out how to run that on a Mac.

I want something that's tiny, fast, ridiculously easy to use and that I can run dozens if not hundreds of instances.

WebAssembly is almost that thing.
There isn't a Threads account. You upgrade your Instagram account to work with Threads.

It isn't a different platform, specifically because they didn't want to build up yet another social graph from scratch. Your graph in the Instagram app is your graph in the Threads app. This is somewhat akin to how Messenger isn't a different platform from the rest of Facebook.

There may be a future 'downgrade' function, but removing those orphaned threads posts amounts to a partial deletion of your Instagram account. The text that Meta is investigating this is actually in the slide show, but I don't know if they have said anything about what level of commitment they have given, or timeframe they are shooting for.
Yeah it's a stupidly good deal from the looks of it. It's very cool of them to resist the industry trend of trying to squeeze recurring revenue out of every product!
They have "transparent methods for verification".

"Developing and adopting scientifically rigorous and transparent methods for monitoring, reporting, and verification is essential for permanent carbon removal."

See: https://www.heirloomcarbon.com/news/heirloom-joins-carbon-re...
The Seamless Bay Area vision is very SF-centric.

Even though SF is the cultural capital of the region, the majority of the population and economy resides in Santa Clara County (San Jose, Apple, FB, Google, Stanford, SLAC), Contra Costa County (Cheveron, Toyota, ATT), Alameda County (UC Berkeley, LLNL, LBL, Port of Oakland), and San Mateo County (South San Francisco, the entire biotech industry).

All those counties are working with the State Govt to build a unified mass transit system connecting Sacramento, Modesto, East Bay, and South Bay into a single public transit region [0][1][2], especially because most of the labor class lives in the Sacramento region and the Modesto/San Joaquin Valley region.

Furthermore, the City and County of San Francisco often jeopardizes Bay Area unity by threatening to withhold funding to Caltrain or BART due to SF Supervisors internal conflicts. Given the (relative) lack of major private employers in San Francisco after the 2008 economic crisis, all the other counties prefer to make their own deals together and independent of SF. This is why Livermore pulled out of the BART Extension project which caused the entire system to teeter financially because Half a Billion dollars were reallocated to a separate project.

And honestly, even though I have lived in SF for a massive portion of my life, it could die and no one would care less in the Bay Area. San Jose has always been the primary engine for the Bay Area, especially after the Port of SF, the SF Financial Industry, and most non-tech companies left by 2010.

[0] - https://www.sjrrc.com/valley-rail/

[1] - https://www.valleylinkrail.com/

[2] - https://www.caltrain.com/projects/electrification
I've seen one wasm VM for Rust that offered what looked like transparent M:N, which should solve (in that case) most async difficulties. We'll see how that evolves.
> When you learn Rust at a company you have the full support of the others on your team, who already know Rust.

Not guaranteed. Maybe it was that one guy who decided to introduce Rust to the codebase, then quit.

But I agree, generally, learning anything is easier when you have someone to ask.
> So no one (especially not TSMC) will risk oversupply by building too many fabs.

Everyone and their dog is investing like crazy. Intel and TSMC are both setting up fabs in Silicon Saxony (although the question remains on how productive these will be, given the issues with the far-right in Saxony), TSMC is also expanding capacity in Arizona, and Samsung is building one in Texas.

There will be no oversupply, not for the next few years. Demand from automotive, hyperscalers, AI and pent-up consumer demand is ludicrous.
One of the things that seems to have been kept very quiet about hydrogen is its ability to self-ignite when leaking from high pressure into air. The jury is out on the exact mechanism but most seem to think it creates a wavefront that has high enough energy content to auto ignite.

This seems to be why automotive hydrogen refueling is relatively slow. At very high pressures there is no reason why refueling should take longer than gasoline refueling.

They made the nozzle so small (less than a millimeter) because if a valve fails open and the hydrogen vents to air, it will limit the length of the invisible flame that probabilistically results to a meter or two.

The temperature limit of the tank is one reason to rate-limit as well, but I don’t think it explains the whole picture.
I’m far more excited about what this may unlock for the iPad than the iPhone. I might actually be able to use it to the capabilities of its hardware.
> The first step in building a query engine is to choose a type system to represent the different types of data that the query engine will be processing.

This. Out of nowhere. Why would this be the first step? There's no explanation... Why cannot be this the tenth or the hundredth step?
> I remember when he made a splash by designing the office so that every developer had a window and a door.

I can't believe it's been 20 years since I read this post[0], but I remember how clever it was that each office had a only a single window, but had sight lines to other windows also, making it look like each one was a corner office.

[0] https://www.joelonsoftware.com/2003/09/24/bionic-office/
I recommend buying the Animators Survival Kit and working through the exercises within. It’s what many animators use as their intro to animation and will teach you most of what you need to know of the mechanics.

From there, it’s just a matter of acting and experience
How to buy a well-made shoe