skysight-inc/HackerNews huggingface dataset:
1. Get a lawyer. The advice they give you should outstrip anything you read here.

2. Prepare to cut your losses in a worst case scenario. The best time to contractually quantify ownership stake is before you enter into the engagement. By the end, you have neither contractual support for your expected ownership stake, nor the leverage to ink it into a legally binding document.

3. (my $0.02) Practically, the most you may get from this scenario is a very expensive learning experience. Whether or not you have the grounding to enter legal proceedings (or threaten that), the payoff compared to the mental and financial cost of litigating are likely not in your favor.

Sorry this had to happen to you. It happened to me, too. I learned a valuable lesson when it comes to doing this kind of work -- you need to get an airtight legally binding document before you start working, or else you'll be exploited. That your business "partner" never formally entered into a contract with you likely indicates the latter.
> using processor features that aren't exposed by the kernel or standard library).

As someone who doesn't do any low-level work, could you give an example of these kinds of features? I'd like to read into some of them :)
Wait, I just noticed your id. drfuchs as in David Fuchs? The inventor of the GF file format? I don't remember if we ever met in person back in the day but hi!
You didn't mention your role and I expect the experience to be somewhat difference depending where you end up in the hierarchy. Generally I'd say that the higher you are the more bullshit and bullshit work there is.

* In big corp there are a bunch of people who are actively just making a living and career out of shit talking and being in the right spot of the machinery doing very little actual work.

* There can be lots of redundant work and other inefficient waste. For example double/triple bug/task tracking systems, several different repositories with half assed mirrors etc.

* There are "gate keepers" who have been at the BigCorp for a hundred years and have managed to put themselves in a position where they get to act as the gate keeper of access to some resource. Examples are some "enterprise" level CVS tools like ClearCase where there's some "merge/release manager" who gets to do branches and merges and releases etc. These people will vehemently resist any change to make these processes more efficient. (see the point about efficiency)

* Some people exist in the organization just to make a career using whatever means possible including bullying, politics, (passive) aggression towards others (trying to sabotage their work, take credit for it), ass kissing, nepotism etc.
It's ok, from the figures it looks like we don't really need your respect. Continue ignoring the pain and fear that your fellow US citizens live in, and continue defending the actions of the stormtroopers who beat them to death in our streets.

If you don't want to help, just get out of the way.
i recently re-read the wisdom of crowds, ~15 years now since i first read it. still good, still relevant. there's even a section on how quickly SARS was identified in international collaboration despite no central, coordinating entity.

it's covertly a book about statistical reasoning, but with no dry statistical language, subversive in a way. we need more statistical reasoning in the world, particularly around risk assessment, to subdue fear and panic.

edit: as for fiction,

james clavell's asian saga[0] series is entertaining historical fiction, which i've read twice.

pat conroy's southern portraits, particularly the lords of discipline and the prince of tides, both wrenching, haunting, and beautiful.

also in the historical/cultural fiction realm: anna karenina, crime and punishment, a tale of two cities, les miserables.

[0] https://en.wikipedia.org/wiki/The_Asian_Saga
I'm afraid it's still that easy these days.
That was the first time I thought I may not need to visit a place in person ( not an expert; seeing it in person would be unlilely to yield a different reaction / insights ). Maybe virtual tourism could be a thing for sites like these.
I'd love to read some studies on this to be honest. My guess would be that a certain size its impossible to not have the kind of bullshit this thread is full of.

I'd wonder if it's a related to the age of the company though, or maybe the speed of growth. It's always felt to me like a company seems to hit a critical mass of, shall we say less than productive people, that then work together to hire more people like them and drive out people that want to make changes. Then it just snowballs.
Is support for NoSQL on roadmap?
> The bigger plugin makers will probably port their products, but it's going to cost the user; the smaller ones may simply give up macOS completely.

The writing has been on the wall though - Catalina with all its dropped frameworks & notarization already pushed some developers to give up on the Mac (or tell their customers to just stay on Mojave). Loads of Waves users were unhappy having to upgrade to v11 for Catalina support, and won't be happy paying yet again for Mac ARM support.

Come join us on the dark side. Plenty of us music people already switched from Mac to Windows. Even Linux audio seems to have come a long way, with Bitwig, Reaper, Renoise all supporting Linux now, and even plugin devs like u-he.
I still think you're missing the point. GCC indeed didn't invent "inline assembly as a string", no.

GCC invented "constraint metalanguage as the foundation for inline assembly generation", which is the model here that enables one compiler and one syntax to work the same way for basically every architecture over decades. Modelling the interior of the assembly code as a black box (which in this implementation means "string") is just a side effect of this important design choice.

Again, the stuff you're imagining isn't a general purpose assembly language model, it's an x86-specific hack that works only on the specific compilers and architectures for which it was targeted.
Once when I was frustrated with my current Job at a large corporation, an experienced friend told me the secret.

He said, they'd value "predictability over excellence".

Meaning, talk about your goals, give an estimation and arrive exactly on point. It doesn't matter if it's your personal project or projects/processes where you take the lead.

Being faster than estimated, or finding a better way and switching while your doing it will not be appreciated.

This really unlocked a lot of success and explained many glass walls i've been running into before.
I find myself re-listening to large portions of my audible library fairly often. I pick up so much more on additional read/listen-throughs.

I listen to or read Snow Crash at least once a year. I just enjoy most everything about it. Anathem required a couple listens, and a third listen was just for comfort food.

The Altered Carbon trilogy has depth and sublime world-building that I have now enjoyed at least a half dozen times.

I second mentions of Dirk Gently’s Holistic Detective Agency (and will mention The Long, Dark Tea Time of the Soul as well).

Ender’s Game is also comfort food for me.

Breaking from the speculative fiction reco’s above...
The Power of Vulnerability (Brené Brown) is more lecture series than audiobook, but as for non fiction I’ve recently given multiple listens to, that tops the list.

I borrowed “Landline” from the local library, read it twice and then bought it so I could continue to read it when I want to. I think I was in just the right age group and life situation for this novel to hit home for me. Your mileage may vary, but IMO read it without knowing anything about it in advance if you’re going to read it. That means don’t read the back cover etc.

(Blind borrowing of books from the library is fun and can be eye opening, try it sometime! Most places, you can borrow eBooks and even digital audiobooks without even leaving your home as long as you have a library card.)
You're not being unreasonable but that's not the issue. The issue is the leverage you have now. Your value to your partner ends with the sale. You are valuable to the new owner as the sole person who understands how the product works. Even if they only want the idea and the customers, recoding it will cost something and be cheaper/easier/faster with your participation, plus they'll need someone to support the current product for a while, or they'll shed those customers.

Convince your partner that the buyers will need you, and will only get you if you're happy with the terms of the sale. If you can enlist the buyers in this campaign, so much the better.
The Power Broker

The excellent series on Lyndon Johnson by the same author as The Power Broker

The Three Body Problem series
Would an OS like this mean really really tough DRM?
That also would have been true for BSD.

Linux probably also had good timing while the Unix wars were fought.
There's a bit of reading material on this I would recommend you look into. Here's a good place to start: https://plato.stanford.edu/entries/civil-disobedience/
The Campus Trilogy (Changing Places, Small World, Nice Work), by David Lodge.

DO IT!: Scenarios of the Revolution, by Jerry Rubin.

The Cuckoo's Egg: Tracking A Spy Through The Maze Of Computer Espionage, by Cliff Stoll.

The Hitchhiker's Guide to the Galaxy, by Douglas Adams.

Logicomix, by Apóstolos K. Doxiàdis and Christos Papadimitriou.

Other books that I strongly recommend can be found here (some of them are in French): https://pablo.rauzy.name/miscellaneous.html#books

Update: Pirates de tous les pays, by Marcus Rediker is a translation of Villains of All Nations: Atlantic Pirates in the Golden Age which you can thus read in English :). It really is an awesome read! After I finished it I immidiately ordered 5 more copies to give them to friends.
Yes, but low-level programming implies direct access to memory and instructions.

Rust is not designed for memory safety only. If you only want that, there are other simpler options, like any functional, scripting or managed language. Instead, Rust is designed to bring as much memory safety as possible (but not more!) to the low-level and performance fields.
JOOQ from jvm world is exactly that, typesafe sql with dsl pretty much the same as good ol’ SQL
This type of agreement is best pursued as a non-technical, non-legal endeavor.

There’s a book “Never Split the Difference” by Chris Voss that will get you up to speed. His videos on YouTube are also potent.

Ideally, you want to avoid the “I brought this” style of language; what else is someone to do than think, “well I brought this, too!” It gets especially tense if the evidence is too damming, so the protection mechanisms kick over rather than the empathy and cooperation channels.

Good luck - you got this
1984 -- my all-time fav book. I've read it more than 10 times, because it's a beautiful dystopian love story that moves me like no other.
The problem is not whether its bad or not, but rather, having to learn a completely-different second syntax for one architecture.

Most Rust code is quite portable, targeting ARM, x86, MIPS, PPC, WASM, Sparc, s390x, riscv, ... That means, that for many snippets of inline assembly, you might encounter ~8 of them, one for each architecture, all using different syntaxes.

Intel syntax is quite similar to that of other popular architectures `op dst, args...`.

Adding another second syntax for x86 just doesn't add that much value IMO, and adds quite a bit of cost: now everybody dealing with x86 assembly needs to learn 2 syntaxes... and everybody dealing with portable code now needs to be at least able to read 2 syntaxes for x86... Without talking about the cost of implementing a second syntax in the compiler, etc.

If you prefer AT&T, you can always write a proc macro that translates it to Intel, and use that in your projects.

If I ever need to deal with such code, I'd just expand the macro to read the actual Intel syntax, modify that, and either fork the project, or submit a patch with a fix using Intel syntax.
Microsoft declined to extend its inline assembly syntax to support x64 or ARM-based processors.

If you want to use a single specific instruction or two, it's usually better to just use the compiler's intrinsics (Rust has already stabilized the x86 SSE and AVX intrinsics) than inline assembly. When you go to more complex assembly fragments, you tend to need more control over how the inline assembly fragment interacts with scheduling and the register allocator, and making that control work ergonomically is that much more challenging.
Because ultimately Rust wants to be a C++ replacement and you can't do that if you don't let people who know what they're doing opt into inline assembly and raw pointers.
A bunch of books: Leviathan Wakes by James S.A. Corey (as well as several of the sequels), American Gods by Neil Gaiman, The Windup Girl by Paolo Bacigalupi, The Magicians by Lev Grossman, Ancillary Justice by Ann Leckie, Harry Potter by J.K. Rowling, The Three-Body Problem by Liu Cixin, and a bunch of others.
The privacy policy sent me packing.
Actually, drama/soap opera is the part I am not a fan in scifi. I had pain watching Netflix's star trek and see the hero of the saga crying 10 minutes per episode... But I understand, it is here to target a broader audience.
In the case of Hazelcast Jet and similar products, loads of young garbage are unavoidable because it comes from the data streaming through the pipeline. A generational GC should in principle get a great head start in this kind of workload, and our benchmarks have confirmed it.
I used to read The Illuminatus! Trilogy [0] once every year or two, though that's slowed down; I feel like I've gotten something new out of it every time.

I'm now taking a second pass through Unsong [1], simply because I enjoyed the first read so much.

[0] https://en.wikipedia.org/wiki/The_Illuminatus!_Trilogy

[1] http://unsongbook.com/
The Salesforce Tower in SF is a great example of this. Big, tall, and bold with a pleasing curve.

But look more closely and it’s just utterly bland and boring. There is no detail. Just infinite repetition of the same window shape with a light shade.

And then an awkwardly inserted lobby that looks like you chopped out half of the bottom 3 floors and replaced them with a glass pane. Like an afterthought.
Cash in on the Keto Craze- KetoPower Boost Supplements
I've read all of discworld by Terry Pratchett at least three times. I'm almost finished with my second sequential reading. It's comfort food in book form for me.
These threads are posted a lot, but I still like reading the comments for new book recommendations if I see a match. Also, hopefully this can show people how great fiction is. I've seen comments that shun people for liking fiction compared to non.

For me:

Lonesome Dove

100 Years of Solitude

Catch-22

The Sellout (very relevant again)

East of Eden

Kafka on the Shore (and all the stories in Blind Willow, Sleeping Woman)
Rooftop – The Internet's Best Advice for Men
ROOFTOP is a free newsletter that curates the internet's best advice for men into a weekly email. Whether it's style, grooming, health, cooking, dating, wealth, productivity, or any other piece of advice you need to become better, we've got you covered.
To me, Art Deco stands out in modern skylines in part because it is distinctive. I don't think the glass covered skyscrapers that are sprouting up in every growing city are as ugly as their detractors say, but they do all look the same.

Of course, more distinctive architecture can also get repetitive (the referenced tiering in NY or Haussmann buildings in Paris), but at least they are distinctive to that place.
That rule is exactly where the the construction used becomes interesting: it's built in such a way so that if the turing machine halts, the player who set it up wins the game. If it doesn't, by the rule above, it's a draw. So it's fundamentally impossible to tell the result of an arbitrary setup (and in practice you could set it up such that it halts iff some unknown conjecture is true).

Regarding the oblivion ring loop, there's an example of it being used on MTGO, which doesn't end well (basically seems to crash the server and/or client): https://www.youtube.com/watch?v=AGXG5rNe_tI

And here's the paper on the latest turing machine construction in mtg: https://arxiv.org/abs/1904.09828
How Datarock is using PyTorch for more intelligent mining decision making
Thanks a lot for the clarification, Tirumarai! (Remote JOINs look awesome btw, congrats on the release :)
I really like that they removed some dependencies/software! :+1:

"In order to significantly reduce the footprint and simplify management of the Mender server, three major server dependencies have been removed."

I generally prefer deleting code.
The Dispossessed - Ursula K. Le Guin

Harry Potter - JK Rowling (re-read it all when the last book came out)
The Global AI Talent Tracker
Breadth is nice, but depth is too. I tend to gain more from a second read than from a first, and also I can consume content where I know what to expect while in a different mindset and state of being than what I require to crack open and explore something all new.

But sure, everyone is different and does things their own way. If it works for you, that’s great!

(Totally agree with putting down a book that isn’t working for you. You have no obligation, in most cases, to any book. It can be freeing to realize this if it’s not something that’s already obvious!)
The book I've reread the most is The Odyssey. For a long time, I've read it once every year.

Another book I've read many times is Eco's Foucault's Pendulum.

I've read Asimov's cycle of Foundation many times. Don't know how many, actually.

I've also read several times some philosophy classics, particularly Plato's Symposium, Phaedrus, Apology and Republic.

Then there are many books that I've read at least twice, almost all considered classics (from 1984 to LoTR, Great expectations to Tom Sawyer, Crime and punishment to Twenty thousand leagues under the sea, etc).
What is Rust's policy for signed/unsigned int overflow? I assume that it's not modulo or else the complier should have generated ADC for you.

I assume you've been using Compiler Explorer a lot?
Just take any operating systems course and try to implement your own.

Or try to program a micro-controler "hello world" that actuates an LED ?
My Favourite Ideas from One Year of Hunting Online
It's less "need" and "does the same thing but far more efficiently and can't rot because a machine makes sure it's correct".

I like letting my tools do stuff for me. If a tool can go look up what arguments this function expects, and their types, and tell me that, rather than my having to go check, and then also warn me if I typo one of them, then also take me straight to the definition of the function if I decide I want to read it, without my having to go hunt it down manually, all at zero cost (again, these things should be documented anyway), then why the hell not?

[EDIT] I guess I just don't understand why people consider it burdensome. You probably ought to know your function's going to take a string. Is it that hard to type "string" in the signature? You're gonna have to figure out what it's supposed to return—when you do, write it down. It's a little more work for more complex structures but it still amounts to typing out things you already have to think through anyway, and the more complex the more important it'd be to record that somewhere, so may as well be machine-readable type information. In return, when you accidentally try to treat your string like a number you'll immediately know you've missed a step, you'll get comprehensive autocomplete on hashes and classes and such, jump-to-definition, instant typo-spotting, automatic refactoring, and so on, and you can hand it over to someone else and they'll get those same things, instantly. The payoff is 10x, at least.
Could anyone shed some light on what such a conversation with a lawyer might cost?

Talking to a lawyer before any contentious business conversation is always advised but what is the experience like?
Better not starting talking about niche in regards to Rust, unless adoption of a niche systems language isn't something to care about.

Productivity matters everywhere, systems languages that care about happy programmers have better chances of long term adoption.
If it is a static/general website with information and not much user interaction, I would say it should ideally work without JS.

If it is a web application that has tons of interactivity with a user, it would be of not much use without JS.
I calculated it myself in a CV course in university. The same effect was observed by others. I didn't read it somewhere. This shouldn't surprise anyone - white people have tremendously higher variance in color alone (skin, hair, and eyes).
I just started using Cryptomator for sensitive files on a self-hosted NextCloud (since i access it via internet). The photos thing was an issue so I just sync those unencrypted and use Cryptomator for non-media files - i suppose if I had a photo that I wouldn't want exposed i'd just move it individually over.
Cryptonomicon by Neal Stephenson, every three years or so.
Considering the amount of anxiety reading about this type of lifestyle induces in me, shows how much of a fear of unknown some of us live in perpetually.
Just be careful about wearing them in the wrong neighborhood
> If you prefer AT&T, you can always write a proc macro that translates it to Intel, and use that in your projects.

If you prefer AT&T (or you have a large body of existing AT&T code you don't want to have to translate all at once), use asm!("...", options(att_syntax)) and it'll Just Work.
> I know for a fact genetic diversity is highest among Africans.

This doesn't mean what you think it means. In particular, it does not imply wider phenotypic variance.
As someone who just worked on a project where I embedded lua, that's exactly what I was looking for. Why would I want to choose this over lua and what's the pro/con matrix?
Yeah, same experience. You can't change all of the things but you can change like 1 thing at a time that's really peeving you off, iff you have a good reason & can make a good argument & it's worth your time & effort.
I used inline assembly once when playing around with Rust on GPUs to get Cuda's implicit thread ID and grid ID: https://docs.nvidia.com/cuda/parallel-thread-execution/index...
The BeOS "reimplementation" is called Haiku. It is a pretty remarkably mature project, though unfortunately not what I'm looking for in a new OS personally.

The reason we don't see new OSs is pretty simple: there is entirely too much hardware you have to accommodate to be usable. There are klocs of actual kernel code in Linux, and Mlocs of driver code.
"All Lives Matter" is Racism 1.0 thinking.

But Racism 2.0 has been pushed out and – in some ways – it's a forced upgrade.

Racism 1.0 was widely understood: racists were bad people who made monkey chants on football terraces. It was "the nice people" vs "the mean people". If we "raised awareness", maybe one day it would be "stamped out".

Racism 2.0 is more complex.

It's structural and systemic, so for the first time a lot of of white progressives are discovering that we're part of the problem. Saying "I don't see colour" is suddenly the wrong thing to say. For a long time it was the correct thing to say and think.

People are having to re-learn stuff they thought they already knew and not everybody is thrilled.

Worse, Racism 2.0 is closed source. The code isn't really published anywhere, at least not in simple language. You have to kind of piece it together yourself from lists of "resources" thrown together by activists, some of whom have opaque agendas.

It's not as simple as it used to be, and it's not surprising that some people are confused.