News for hackers. Stuff that matters.
Re:Lanai, the mystery CPU architecture in LLVM by drewg123 on Monday March 21, 2022 @03:24PM (#30758556)
I worked for Myricom 2001->2013, and Google 2013->2015. And, wow, I wish I could comment on this thread.. :)

EDIT: Scott's Medium blog post linked from this article is fascinating: https://medium.com/swlh/myricom-an-hpc-story-and-lessons-lea...

Re:Lanai, the mystery CPU architecture in LLVM by jandrese on Monday March 21, 2022 @04:19PM (#30759180)
> The CEO capped the full time headcount at 49 people so he wouldn’t be subject to California law requiring him to provide his employees with a health plan.

Can you imagine being this stingy and short sighted? The employees are largely PhDs and he is willing to cripple his company to avoid paying benefits.

Re:Lanai, the mystery CPU architecture in LLVM by drewg123 on Monday March 21, 2022 @04:23PM (#30759235)
I'm not sure that part of Scott's article was accurate.

I worked remotely, and I'm pretty sure that I was offered benefits. I declined them, and used my wife's benefits because they were less expensive, and meshed better with local health care providers.

EDIT: And I know we had a 401K

Re:Lanai, the mystery CPU architecture in LLVM by drewg123 on Monday March 21, 2022 @05:06PM (#30759722)
I worked there and have evidence that this statement in the blog is not true, and I'm being down-voted?
Re:Lanai, the mystery CPU architecture in LLVM by ChuckMcM on Monday March 21, 2022 @06:06PM (#30760337)
Downvotes are fickle things. Unrelated, why turn down the health care? With double health care you can tell you're health provider you've got double coverage and they will bill the primary first, and then the secondary for what is left (and if the secondary is designed to be a primary program it will cover all that is left so you end up with zero out of pocket, even for co-payments).
Re:Lanai, the mystery CPU architecture in LLVM by drewg123 on Monday March 21, 2022 @06:41PM (#30760702)
Because it was CA focused, and I was remote. So most local providers were out of network. And it was not free ... Its been almost a decade, but I seem to recall that it was cheaper to add me to my (then) wife's coverage.
Re:Lanai, the mystery CPU architecture in LLVM by wincy on Monday March 21, 2022 @07:08PM (#30760912)
It’d be pretty annoying to have a Kaiser Permanente focused insurance plan and live in Ohio.
Re:Lanai, the mystery CPU architecture in LLVM by davidw on Tuesday March 22, 2022 @12:03AM (#30762617)
American health care is ridiculous, episode #193993.
Re:Lanai, the mystery CPU architecture in LLVM by ionicgiraffe on Tuesday March 22, 2022 @02:17AM (#30763207)
We are starting to copy it elsewhere, it's going good in the same direction in baby steps.
Re:Lanai, the mystery CPU architecture in LLVM by azinman2 on Monday March 21, 2022 @07:39PM (#30761158)
I don’t know if it’s illegal, but basically every health care plan will deny you if they know you have other coverage. This is bad advice.
Re:Lanai, the mystery CPU architecture in LLVM by xyzzyz on Monday March 21, 2022 @09:11PM (#30761755)
You’re wrong. It is perfectly common to have double coverage. I had it on multiple occasion. You can read about it if you google “coordination of benefits”.
Re:Lanai, the mystery CPU architecture in LLVM by azinman2 on Tuesday March 22, 2022 @01:23AM (#30762983)
You’re right. I don’t know if this varies by state, but for sure I’ve had to sign contacts stating I didn’t have any other insurance in order to start various plans. So I don’t think this is universally ok but clearly there are situations that allow it, seemingly most common in conjunction with Medicare.
Re:Lanai, the mystery CPU architecture in LLVM by sandos on Tuesday March 22, 2022 @10:25AM (#30766461)
This is funny, because basically every insurance here in Sweden states that if you are covered by another insurance, then this one is invalid. In practice though what Iv'e heard is that the companies will always just be kind and sort of split the responsibility between them instead when something happens.
Re:Lanai, the mystery CPU architecture in LLVM by jen20 on Monday March 21, 2022 @07:38PM (#30761144)
Is this generally the case? If so, I had no idea...
Re:Lanai, the mystery CPU architecture in LLVM by ChuckMcM on Tuesday March 22, 2022 @02:48PM (#30769894)
Generally different jurisdictions have different rules, but in California it is the case. And to another point made here, if you're employer is going to deduct some of your paycheck to pay premiums month to month then it can be a net loss if you won't use it enough to offset what you would have been paid.
Re:Lanai, the mystery CPU architecture in LLVM by jen20 on Wednesday March 23, 2022 @10:36AM (#30778868)
Thanks - I need to do some research on this!
Re:Lanai, the mystery CPU architecture in LLVM by refulgentis on Monday March 21, 2022 @05:10PM (#30759750)
I don't think so, your comment is black text for me, so it's either at it's original score or higher.
[dead]
[dead]
Re:Lanai, the mystery CPU architecture in LLVM by oefrha on Tuesday March 22, 2022 @12:21AM (#30762705)
There’s a reason guidelines ask you not to discuss downvotes, which always fluctuate. You were adding pure noise to the thread, and you tripled down on that.
Re:Lanai, the mystery CPU architecture in LLVM by _tom_ on Monday March 21, 2022 @05:28PM (#30759923)
I believe that There are many things that kick in at 50 people. It's oversimplifying to assume this was due to not wanting to offer benefits.

First google hit: https://www.aeisadvisors.com/california-compliance-is-my-com...

Re:Lanai, the mystery CPU architecture in LLVM by edgyquant on Monday March 21, 2022 @06:33PM (#30760627)
Why 50? Isn’t that arbitrary? Why not just force benefits for all employees? At least target revenue, if a company makes X revenue it has to provide Y benefits per employee. CEOs definitely won’t be able to easily make the decision to take in less money, as that will piss off share holders.
Re:Lanai, the mystery CPU architecture in LLVM by GuB-42 on Monday March 21, 2022 @08:30PM (#30761518)
It is arbitrary, but we have to draw the line somewhere.

It is not about money, tax is about money. This is about the extra work needed to accommodate for said obligations, it can involve several full time jobs, and the state considers that it is too much for a company of less than 50 employees.

Really, it is a lot of paperwork, and the more a company spends on paperwork, the less there is to pay employees.

Re:Lanai, the mystery CPU architecture in LLVM by mjevans on Monday March 21, 2022 @11:26PM (#30762423)
Could this be improved by a government agency where they do this paperwork for you at a per-employee cost if your company is under X employees (say 3x the limit at which the paperwork kicks in)?
Re:Lanai, the mystery CPU architecture in LLVM by notreallyserio on Tuesday March 22, 2022 @12:02AM (#30762613)
The easiest improvement would be to remove the employer from the equation and just provide taxpayer-funded benefits to all. The main reasons employers are still involved are inertia followed by a concern that employees won't feel as obligated to stay in shit jobs.
Re:Lanai, the mystery CPU architecture in LLVM by kergonath on Tuesday March 22, 2022 @05:18AM (#30764127)
Sounds like socialism, though. Can’t have that!
Re:Lanai, the mystery CPU architecture in LLVM by edgyquant on Tuesday March 22, 2022 @06:56PM (#30772676)
I think there are arguments to be made in favor of a more free market approach (or a less free market one.) At this moment we seem to have the worst of both worlds.
Re:Lanai, the mystery CPU architecture in LLVM by kelseyfrog on Monday March 21, 2022 @07:47PM (#30761207)
> Why not just force benefits for all employees?

Public perception. Small business owners occupy a different perceptual space than large businesses. Lawmakers don't want to be perceived as hurting small businesses and craft laws to avoid it. It's more about maintaining political power as much as anything else.

Re:Lanai, the mystery CPU architecture in LLVM by edgyquant on Monday March 21, 2022 @08:53PM (#30761640)
I thought of this too, and it’s actually good system. Those small businesses should be exempt I think. It’s only the large corporations that should be forced to pay (I wouldn’t even be opposed to subsidizing health care for those businesses by taxing larger ones more.)

I think a system where we go by revenue is a lot of logical than going by number of employees. If a business makes 1Bpy but only has two employees, would it not be exempt from the current regulations?

Re:Lanai, the mystery CPU architecture in LLVM by kelseyfrog on Monday March 21, 2022 @09:20PM (#30761812)
It works out great for everyone except the 47.5% of Americans who are employed by small businesses.
Re:Lanai, the mystery CPU architecture in LLVM by edgyquant on Tuesday March 22, 2022 @11:56AM (#30767637)
Not really? I’ve mentioned in both comments that we should arbitrate based on revenue, not number of employees. I also said I’m the comment you replied to we could potentially subsidize the benefits at smaller businesses with a tax on the largest. Not saying this would work, or even that the math is sound, but I have definitely addressed your point twice.
Re:Lanai, the mystery CPU architecture in LLVM by toast0 on Monday March 21, 2022 @09:18PM (#30761800)
Revenue isn't always a great way to measure the size of a business, because different businesses add different amount of value. And you can't use profit, because that's easy to game. For something like people benefits, predicating the requirement on the number of people employed makes a lot of sense. It's about as much work to setup a health plan for a two person firm as a 50 person firm, but many fewer people benefit.
Re:Lanai, the mystery CPU architecture in LLVM by edgyquant on Tuesday March 22, 2022 @03:44PM (#30770559)
I don’t disagree, I just think that using number of employees seems like one of the worst possible ways to handle company reaching X size. I came up with that off the top of my head there are surely better solutions.
Re:Lanai, the mystery CPU architecture in LLVM by lumost on Monday March 21, 2022 @06:42PM (#30760715)
Defense contracting also has special bonus's when your company is less than 50 people IIRC.
Re:Lanai, the mystery CPU architecture in LLVM by cowsandmilk on Tuesday March 22, 2022 @06:35AM (#30764542)
The only incentives I’m aware of are meeting the SBA size standards for small business, which are maxes from 500-1500 depending on your industry.

https://www.sba.gov/sites/default/files/2019-08/SBA%20Table%...

Re:Lanai, the mystery CPU architecture in LLVM by voldacar on Monday March 21, 2022 @09:35PM (#30761885)
When you create a sharp discontinuity in the marginal cost of hiring someone, expect companies to act accordingly. It would be irrational not to. Blame the system of shitty incentives
Re:Lanai, the mystery CPU architecture in LLVM by foobiekr on Monday March 21, 2022 @04:30PM (#30759306)
It’s not even that hard or expensive to offer 401k, health, life insurance in a startup. Been there, done that.
Re:Lanai, the mystery CPU architecture in LLVM by dylan604 on Monday March 21, 2022 @07:16PM (#30760962)
That's a very strange comment to make for other people's fiscal situations where you know nothing about their particulars.
Re:Lanai, the mystery CPU architecture in LLVM by djbusby on Monday March 21, 2022 @05:12PM (#30759769)
At least 10k/yr/employee.
Re:Lanai, the mystery CPU architecture in LLVM by acdha on Monday March 21, 2022 @07:08PM (#30760914)
How much revenue are those people generating? Don't you think being able to hire and retain more highly-skilled people might be worth more than the $5/hour “saved”? (For example, how much does it cost to hire someone — most places spend many thousands doing that)
Re:Lanai, the mystery CPU architecture in LLVM by djbusby on Monday March 21, 2022 @07:43PM (#30761181)
IDK, I'm just show a concrete value. The person I replied to said it was "not hard". S I mentioned a minimum dollar amount that I've observed at many places seemed reasonable (it can be much much more, like if you cover 100% health for employees and family)

Seems it wasn't helpful.

Re:Lanai, the mystery CPU architecture in LLVM by acdha on Monday March 21, 2022 @09:45PM (#30761937)
My point was just that this seems more like an issue for a business with low profit margins and low wage employees — not engineers, especially for a profitable company (i.e. not some early-stage startup relying mostly on equity). In this case, if they were making $20M/year with on the order of 50 employees it seems very short-sighted.
Re:Lanai, the mystery CPU architecture in LLVM by djbusby on Tuesday March 22, 2022 @12:14AM (#30762673)
That's all true; I also think it's a wise choice to invest in your team for long term.

My point was to simply define a quantitative-value that folk who are not familiar with these costs could see as a minimum. Because "not hard" and $10k mean very different things. Hoping to help those HN readers who aren't familiar and/or are planning on starting a company.

Re:Lanai, the mystery CPU architecture in LLVM by orangecat on Monday March 21, 2022 @07:19PM (#30760983)
I can totally imagine not wanting the hassle of my company having to be a health insurance broker in addition to its actual purpose. What's wrong with paying employees a good salary and having them be responsible for their own insurance, any more than having them buy their own food, housing, and transportation?
Re:Lanai, the mystery CPU architecture in LLVM by jen20 on Monday March 21, 2022 @07:40PM (#30761165)
I would be fine with this, but the job would have to pay at least the consumer market cost of healthcare plus plenty of headroom for increases more than the next best offer for me to consider it.
Re:Lanai, the mystery CPU architecture in LLVM by kaba0 on Monday March 21, 2022 @07:37PM (#30761139)
It’s cheapness and greed on the boss’s part.
Re:Lanai, the mystery CPU architecture in LLVM by edgyquant on Monday March 21, 2022 @06:32PM (#30760609)
After the ACA passed, I remember my ex getting 29 hours at the places she worked because 30 hours demanded they be given benefits like health insurance. I really think regulations with a set number like this are the result of corruption or something. No way anyone doesn’t foresee companies playing them this way.
Re:Lanai, the mystery CPU architecture in LLVM by phkahler on Monday March 21, 2022 @05:02PM (#30759667)
Regarding the blog post: "Why did Myricom’s second CEO fail so fast, lack of experience, and loss of respect? If one were to attempt to explain the plummeting fortunes of Myricom during the term of the second CEO, two characteristics suggest themselves:"

It seems to me the second CEO didn't care about the company, the product or the risk the previous CEO wanted to take (more investment to bring out the new chip). Instead they proposed (and got) another round of dividends for the investors, a promotion to CEO, and ultimately an aqui-hire to Google. To me this reads very simply as putting profit and self-interest ahead of the product. Understandable, and it happens all the time. If you have a vision, the best way to achieve it is to remain in control. Somehow the CEO lost that control.

Re:Lanai, the mystery CPU architecture in LLVM by alduin32 on Monday March 21, 2022 @05:35PM (#30760005)
> The moral of the story is simple, expect that in a small start-up your stock will NEVER be worth anything, and get what you can in your normal paycheck.

That's an important moral.

I wish someone had told me that back then.

Re:Lanai, the mystery CPU architecture in LLVM by dreeple16 on Monday March 21, 2022 @08:34PM (#30761537)
Correct me if I'm wrong, but Lanai was designed by Jakov. Who sadly and unexpectedly passed away a few weeks ago.
Re:Lanai, the mystery CPU architecture in LLVM by drewg123 on Tuesday March 22, 2022 @09:16AM (#30765668)
Indeed, it was quite a shock. Jakov was a wonderful person and the best supervisor one could hope to have. We're all very sad about his passing, and very sad for his family.
Re:Lanai, the mystery CPU architecture in LLVM by vsrinivas on Tuesday March 22, 2022 @01:30PM (#30768966)
I'm sorry to hear Jakov passed away - he was a brilliant, kind engineer.
Re:Lanai, the mystery CPU architecture in LLVM by waych on Tuesday March 22, 2022 @01:43AM (#30763060)
Ah shit :-( RIP Jakov
Re:Lanai, the mystery CPU architecture in LLVM by q3k on Monday March 21, 2022 @03:27PM (#30758585)
Yeah, that blog post was a great reference to get a general overview of What Happened At Myricom.

... and I just hope I didn't write anything factually wrong in TFA. :)

Re:Lanai, the mystery CPU architecture in LLVM by Melatonic on Monday March 21, 2022 @04:40PM (#30759423)
Interesting - I had never heard of Myricom. I have used Infiniband quite a bit in budget super high performance applications - the old hardware can sometimes be found quite cheaply compared to 40gig/100gig ethernet (or it was at least a few years ago). Much more fiddly to get working but the performance was impressive once it did.
Re:Lanai, the mystery CPU architecture in LLVM by gnufx on Monday March 21, 2022 @05:44PM (#30760099)
For what it's worth, I've had rather more trouble with Ethernet than IB, especially given IB management facilities.
Re:Lanai, the mystery CPU architecture in LLVM by detaro on Monday March 21, 2022 @06:01PM (#30760284)
IB always seemed like the kind of thing where you loose out a lot of comfort if you go with "old hardware sometimes found cheaply" and thus don't have vendor support, have to dig out drivers and tools from random sources, ...
Re:Lanai, the mystery CPU architecture in LLVM by gnufx on Tuesday March 22, 2022 @10:57AM (#30766862)
Obviously if you don't have driver support for the kernel you run, you can't use old stuff if you want to, but we had SDR IB running quite a long time without support. I don't have happy experience of HPC vendor support anyway, and unfortunately IB is now a Mellanox monoculture.
Re:Lanai, the mystery CPU architecture in LLVM by Melatonic on Tuesday March 22, 2022 @04:17PM (#30770948)
Probably was also difficult because I had no experience working with it, no support, and there is not nearly as many online forum posts and articles written about common issues.
Re:Lanai, the mystery CPU architecture in LLVM by _tom_ on Monday March 21, 2022 @05:29PM (#30759934)
When does the NDA expire? 7 years is a long time.
Re:Lanai, the mystery CPU architecture in LLVM by speed_spread on Monday March 21, 2022 @11:24PM (#30762406)
I just want the PUNT instruction to become a standard RISC-V extension.
Re:Lanai, the mystery CPU architecture in LLVM by otterley on Monday March 21, 2022 @10:44PM (#30762220)
Most NDAs are perpetual.
Re:Lanai, the mystery CPU architecture in LLVM by Qub3d on Tuesday March 22, 2022 @12:43PM (#30768355)
That is only enforceable for Trade Secrets -- at least in most of the US. Google would need to prove that the things this employee worked on were "essential to the commercial viability of the business".

I totally understand not wanting to poke the legal behemoth, however.

As an anecdotal, a personal friend who is a former Googler signed a 10-year NDA, and he had his fingers in quite a few pies.

So maybe in 3 more years?

Re:Lanai, the mystery CPU architecture in LLVM by otterley on Tuesday March 22, 2022 @04:46PM (#30771306)
> That is only enforceable for Trade Secrets

Do you have legal citations supporting this assertion? I'm fairly certain this isn't so.

Re:Lanai, the mystery CPU architecture in LLVM by Qub3d on Wednesday March 23, 2022 @01:46AM (#30775376)
Mostly based off this quick search: https://www.everynda.com/blog/duration-clauses-non-disclosur...

As I said, I definitely understand not wanting to be the one to actually set precedent - that involves getting sued by Google, which is expensive and potentially career suicide. But I think ultimately its probably not enforceable.

Re:Lanai, the mystery CPU architecture in LLVM by vlovich123 on Tuesday March 22, 2022 @01:38AM (#30763035)
NDAs AFAIK typically last 5 years. Are you sure you can't comment?
Re:Lanai, the mystery CPU architecture in LLVM by quercusa on Monday March 21, 2022 @04:17PM (#30759158)
This line in that post is mystifying: they peddled Infiniband, an inferior design based on bus technology, but repositioned as a point to point network
Re:Lanai, the mystery CPU architecture in LLVM by drewg123 on Monday March 21, 2022 @05:22PM (#30759861)
At least initially (~2005 or so?) we had customers who were given free IB for their HPC clusters ripping the IB out and replacing it with with paid Myrinet installations because they could never get their IB clusters to work reliably.

Although we had the superior product, we could not market our way out of a wet paper bag. Our CEO counted on our (then) superior engineering & expected our products to market themselves. Eventually the IB engineering caught up and surpassed ours, but our marketing never even came close to theirs, so they were the clear winner.

Re:Lanai, the mystery CPU architecture in LLVM by sliken on Wednesday March 23, 2022 @02:00PM (#30781369)
I build a myrinet HPC cluster or two, vague memory that it was 2.5Gbit. Worked well, I particularly liked the cables (thin and optical, way nicer than IB cables). When I went to replace them the Myrinet 10G was repeatedly delayed, and seemed to be focusing on 10G ethernet, not MPI/HPC.

We ended up going with a new upstart called Pathscale, which then was bought by qlogic, and then Intel. Our benchmarks showed a clear win over Mellanox at the time. In particular on larger jobs the Mellanox drivers seemed to consume a fair bit of ram for each client you were talking to, so even 32 nodes jobs would consume a fair bit of ram. We even built a cluster out of hypertransport connected infinipath cards in a "HTX" slow instead of PCIe. Managed I believe 1.4us latency, which is still reasonably competitive today. We built SDR (first public cluster), DDR (first public cluster), QDR based clusters. But then Intel said the new Infinipath would not be supported on AMD nodes, or even previous gen Intel nodes, I said it's a non starter and switched to Mellanox. I talked to several other HPC sites that said the same thing, months later Intel killed off the product. Sad and short sited on Intel's part.

Re:Lanai, the mystery CPU architecture in LLVM by bee_rider on Tuesday March 22, 2022 @12:50AM (#30762831)
Where'd the name Myricom/Myrinet come from? "Infiniband" is a pretty cool name.
Re:Lanai, the mystery CPU architecture in LLVM by convolvatron on Monday March 21, 2022 @08:09PM (#30761372)
unless I'm thinking of the wrong vendor, the myrinet devices supported programming the nic. for some applications that was a really big win over IB verbs
Re:Lanai, the mystery CPU architecture in LLVM by drewg123 on Monday March 21, 2022 @09:17PM (#30761790)
Yes and no. The original firmware / host driver stack was open (shared?) source called MyriAPI. It was so terrible that spawned an ecosystem of uni and research lab projects to implement replacements. I worked on one such project at Duke (Trapeze). Others included BIP, Fast Messages, Active Messages.

MyriAPI was later replaced by a new firmware / host stack called GM. I think at some point we stopped shipping firmware source. I think that point was the transition from MyriAPI to GM...

Re:Lanai, the mystery CPU architecture in LLVM by detaro on Monday March 21, 2022 @04:41PM (#30759427)
I think that's a confusing reference to the fact that InfiniBand initially was supposed to be also a replacement for system-internal buses (i.e. a PCI replacement), before PCIe took that place instead.
Re:Lanai, the mystery CPU architecture in LLVM by gnufx on Monday March 21, 2022 @05:37PM (#30760046)
I wasn't there, but understood it was intended for general machine-room -- I dislike "datacentres" -- use; Wikipedia implies it was intended for ~everything...

Anyway, IB at least had lower latency than Myrinet, which is what counts in a lot of HPC. I don't remember the numbers, but I got quite close to Myrinet latency with the on-board 1GbE NICs on Sun x2200s, an un-managed switch, and Open-MX, which was interoperable with the Myrinet MX protocol. (I remember MX being slagged off by Mellanox; I don't know how similar MXM later was for IB.)

Re:Lanai, the mystery CPU architecture in LLVM by monocasa on Monday March 21, 2022 @05:25PM (#30759889)
Yeah that makes sense, it's an RDMA protocol, and PCIe has wayyyy more in common with infiniband then it does with legacy PCI.
Re:Lanai, the mystery CPU architecture in LLVM by dboreham on Monday March 21, 2022 @04:47PM (#30759502)
You can use a bus PHY in a p2p configuration.
Re:Lanai, the mystery CPU architecture in LLVM by wmf on Monday March 21, 2022 @04:56PM (#30759590)
But Infiniband didn't do that.
Re:Lanai, the mystery CPU architecture in LLVM by paulmd on Monday March 21, 2022 @05:48PM (#30760136)
you can do point-to-point connections with infiniband, it's a pretty common homelab use-case since adapters are so cheap these days.
Re:Lanai, the mystery CPU architecture in LLVM by detaro on Monday March 21, 2022 @05:58PM (#30760253)
InfiniBand is always point-to-point, that's the point. The talk about "bus" is confusing/wrong since it never is a bus.
Re:Lanai, the mystery CPU architecture in LLVM by paulmd on Tuesday March 22, 2022 @12:32PM (#30768198)
oh, "bus" in the context of an actual bus, like CAN. I thought p2p just meaning direct-attach. But yeah it's switched, it's not a shared bus.
Re:Lanai, the mystery CPU architecture in LLVM by NavinF on Monday March 21, 2022 @04:52PM (#30759560)
Yeah that makes no sense.
Re:Lanai, the mystery CPU architecture in LLVM by CalChris on Monday March 21, 2022 @03:38PM (#30758720)
I just want to know why it needs to be in-tree.
Re:Lanai, the mystery CPU architecture in LLVM by wyldfire on Monday March 21, 2022 @03:50PM (#30758875)
Google uses upstream llvm as their dev repo. I don't know if they do any development downstream.
Re:Lanai, the mystery CPU architecture in LLVM by IshKebab on Monday March 21, 2022 @04:14PM (#30759133)
LLVM doesn't have a plugin system so it's that, or maintain a fork and deal with horrible merges all the time.
Re:Lanai, the mystery CPU architecture in LLVM by Fnoord on Monday March 21, 2022 @05:34PM (#30760002)
Some important/big customer pays a maintainer to maintain it upstream instead of having to maintain/port it in-house. If there's two of these, it makes sense. Even with one it would otherwise require backporting. Might as well do it in public?
Re:Lanai, the mystery CPU architecture in LLVM by Fnoord on Monday March 21, 2022 @05:31PM (#30759976)
Plot twist: you were the CEO.
Re:Lanai, the mystery CPU architecture in LLVM by ncmncm on Monday March 21, 2022 @03:41PM (#30758764)
Why can you not comment? Certainly any NDA you signed must be expired by now.

PSA: If you are not getting continuing payments, any contracts you signed are void. Technically, I gather you are supposed to notify the other party that you are terminating your participation in the contract. Even if you are getting ongoing payments, you can opt out of that, too.

(This is not legal advice. Consult an actual lawyer for anything that matters.)

Re:Lanai, the mystery CPU architecture in LLVM by pcwalton on Monday March 21, 2022 @04:12PM (#30759105)
It is absolutely not the case that you can just quit a company, wait a year, and then dump all their confidential information.

Even if there were no legal repercussions (which there are), that's a great way to never be hired again.

Re:Lanai, the mystery CPU architecture in LLVM by ncmncm on Monday March 21, 2022 @07:40PM (#30761159)
Time since 2015 is rather more than a year. And, all appearances are that any signatory no longer exists, as such.

Finally, if you don't yet know about voluntary termination of contracts, you have an opportunity to learn more about it.

Re:Lanai, the mystery CPU architecture in LLVM by postalrat on Monday March 21, 2022 @06:13PM (#30760392)
Never be hired because you gave away most of your value for free?
Re:Lanai, the mystery CPU architecture in LLVM by Centigonal on Monday March 21, 2022 @07:48PM (#30761216)
Never be hired because trust is important in human endeavors
Re:Lanai, the mystery CPU architecture in LLVM by postalrat on Tuesday March 22, 2022 @12:14AM (#30762671)
At least the illusion of trust. Much more valuable to market your past experience then privately give away your secrets in private.
Re:Lanai, the mystery CPU architecture in LLVM by Dylan16807 on Tuesday March 22, 2022 @02:33AM (#30763267)
And when it's been over 5 years?

What about talking about things from 10 years ago, or 15?

The grandparent post is wrong but if OP is being accurate about "wish I could" then the NDAs or severe expectations of not talking are going way too far.

Re:Lanai, the mystery CPU architecture in LLVM by dboreham on Monday March 21, 2022 @04:16PM (#30759148)
Hard to make a more wrong post (everything apart from the advice to consult a lawyer is incorrect).
Re:Lanai, the mystery CPU architecture in LLVM by ncmncm on Monday March 21, 2022 @05:27PM (#30759918)
I see that you have not followed the bit you approved of.