Hacker Newsnew | past | comments | ask | show | jobs | submit | malklera's commentslogin

> SBOM (Software Bill of Materials) – a machine-readable directory of all software components and dependencies used

This sounds like a really good idea all around, not only for open source.


I would have expected more people to want the position.

You see the complaints; people rarely praise a product; they just use it.

An IDE is a tool. What do you want to use the tool for? Put that as a priority and say no to everything else.

If the IDE is for you, look at the other editors and pick and choose each thing they do and decide how (or if) you want to do it. Are you happy with the result? That is a win. If somebody comes along with ideas/complaints, tell them no.


Really interesting read.

Weird libressl.org not being a secure website according to brave mobile, but on helium desktop it is secure.


I pity people that pay for a service and get ads anyway.

I do not know what is wrong with ads; only two or three times ever did I saw an ad and though "uh that is nice" and went to search for the product, mostly they all look like scams.

But since so much money moves through it, I suppose they work.


Everything mentioned applies to human programmers too, but we still get bugs and downtime in production.

Are LLMs more important so companies will pay to have these guardrails when they currently do not have them for their humans?


From the outside I see (do not write manually managed memory).

C/C++, you SHOULD do X to prevent certain bugs.

Rust, you MUST do X to prevent certain bugs.

Humans are lazy, error-prone, unskilled, etc. When I decide to get to a more low-level language, I will choose the language that forces me to good behavior.


Nice info.

Japan is either purposely chosen or an unfortunate choice for the example topic.

Does anybody want to guess what happened before the 2000 that Japan cancer rates were so high?


The only language companies understand is $$$; if you do not like their practice of ToS, do not use the app.

I have never read a ToS. I wonder how many of the services I use I would continue using if I did read them (probably most if not all).


The problem I see with all the rewrites is, long term, will the people that created the project stick around 5 or 10 years from now?

Will companies be more willing to donate time/money if they can actually monetize a product built on top of an MIT license?

I think right now the answer is "not enough"


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: