skysight-inc/HackerNews huggingface dataset:
This is a bad excuse.

0.002% of our customers need security against sophisticated hackers who have the capability to hijack a repair service and replace it with a spying custom made iphone screen replacement.

Let’s make screen repairs 5-7x more expensive for 100% of our customers !

That will get the hackers !

Yea, right....
If you’re that paranoid about your security, go to an authorized apple repair centre which doesn’t bother repairing the parts and just charges you to replace the entire circuitry.

No one’s stopping you.
Leave the rest of us, alone from this.
Document Foundation starts charging €8.99 for 'free' LibreOffice
> It is, but that's if you don't mind the less fortunate folks starving. Not starving, but ending up as homeless drug addicts.

There are homeless drug addicts and alcoholics everywhere.

> And the large number of working poor.

Yep, the working poor are better off in Europe, esp. in places like Denmark or Norway. They can actually have somewhat non-shitty life, even when working minimum wage jobs.
I agree that debugging bad macros is annoying, especially proc-macros but that’s not comparable since by their very nature proc macros are no more powerful than hand written code. They cannot create new semantics, at best they can add new syntax sugar for things that already exist in the language.
> I am an amateur developer

Nowadays I mostly work with Java, Node.js (JavaScript/TypeScript) and Rust.
I have been programming professionally for about 15 years, and I have been paid for work in C++, C#, Python, PHP in the past, not to mention a gazillion languages that I used on my side projects.

> I find it difficult to switch between the grammar of the languages

I have similar issues that you describe (wasting a few minutes, in my case, because of some syntax error) if I start off from an empty file or if a few days have passed from the last time that I used a certain tech.
If I am continuing work on an on-going project I first do smaller tasks in existing codebase to get "into it", If I am starting a new project I sometimes copy an old one to get started and I edit it (delete most of the code, modify the config etc.)

Also, a lot is gained if you make yourself aware that you just switched to a different tech.

Obviously (is it?) I use an IDE and that helps _a lot_.
A bit off topic, but I recently discovered that when I want to rasterize my images to bitmap, the webp format does a much better job around the edges near transparent edges. The png export is terrible.
"when in reality there are a lot of talented people in India and from India."

There are skilled people from India, but rarely in India I'd assume. The market for software engineers in India is not great to put it politely so the talented people will obviously go where the money and benefits are which is US, Europe etc. And yes I'm sure there are exceptions, but probably not too many or do you know anyone actually buying software engineer services from India and paying western salaries?
Forgery requires some kind of deception/fraud. Painting an imitation of the Mona Lisa isn’t forgery. Trying to sell it as if it is the original is.
The problem is that there is a lot of code and libraries using older patterns. And modern C++ is sufficiently different from the older C++ to constitute effectively a new language while still being unsafe. Moreover, in an attempt to address the efficiency the language has added views and ranges that provides more ways to corrupt memory. So why rewrite libraries in modern C++ when you can port them to Rust or Go and gain memory safety?
I was one of two people in the Unimation research department. I worked on problems like developing those car welding robots you see everywhere.

The Unimate was hydraulic. It had a normal working weight at full length of about 400 pounds. It was VERY fast. You REALLY don't want to be anywhere within its reach.
If the US government goes to war with crypto, it’s not going to be a long fight. The exodus of corporate capital from the ecosystem will be a fatal blow to crypto prices and projects.

Rule number one is don’t fight the IRS.
Apple USDJPY rate is going to jump from 120 to 160, that's huge jump but it's just applying real forex. Rate difference to real forex is same as last rate change in 2019 (about +11.2%, maybe for 10% consumption tax and exchange fee/margin).
> A system will produce what it can produce, regardless of whether you set a goal.

This is just fundamentally not true for human beings. Certainly not for all of them; I know personally I need a bit of time pressure to perform my best.
Undefined Behavior deserves a better reputation (2021)
USB-C to DC barrel jacks with USB PD voltage selection [video]
Ah, i must not have compiled it with libreadline-dev... And I didn't know about rlwrap!
Is Node.js THE most influential server tech of last decade?
The answer today is to use a GhostCell
So here I thought the free market always finds the lowest price based on supply and demand and costs had very little to do with it.
Learn how to integrate the best ORM in Ruby ecosystem with Hanami (and any Ruby) application!

Hanami 2.0 comes without the persistence layer nor views preconfigured. It is useful then to know how to set up the best ORM available in the Ruby ecosystem.

While this episode showcases the Hanami integration, you can apply these tips to any application you'll ever write.
You seem to be quite well versed in the persona of Mark Russinovich.

Does he still develop the sysinternals tools? Does he program any more or has he settled into the life of an xTO? Rust, C++, what is he using? Did he port all his tools to Rust?

Given that his reputation is in other areas I don’t immediately see what makes his proclamation noteworthy. As someone that read his book and used his tools I’m more puzzled by his statement than motivated to spring into action :-)
> If you make no reasonable attempt at vetting your supply chain and harm comes to users as a result, then IMO you should be liable for negligence just like a restaurant serving food with poisonous ingredients.

You trying to kill FOSS for end users here?

> If you can not afford to review 2000 dependencies then you can not afford 2000 dependencies.

Occasional security issues can just be the cost of doing business. And that's OK as long as your company isn't doing something critical like running the banking system. Needing to restore your shopping site from backup isn't the end of the world.

There's also the separate and even rarer problem of possible malicious non-internet dependant code in dependencies which would be relevant if running an xray machine or a nuclear power plant (e.g. things disconnected from the internet) but Ive never heard of a malicious non-internet dependant (so not something that tries to connect to a remote server) code in a dependency.
> You're not describing a "creative" situation where you are building something new.

That's true. But the article is not titled "Why deadlines are pointless for creative processes." It's arguing that deadlines are pointless. Always. That's oversimplifying at best, click-baiting at worst.

I'd argue that even in a creative process, if you add enough of a safety margin on top of a conservative estimate, then a deadline can be expected to be met with reasonable confidence. This is absolutely necessary for doing business. "We release when it's ready" is a workable strategy when there are no obligations, but claiming that this always works in all other contexts is just not honestly considering other contexts.
In our case, there's a marketing campaign planned, customers invited to a conference where the new version will be announced, and so on. There are people depending on the release date they've been given.
"Hilariously awful" template metaprogramming is a thing of the past. It has been years since it seemed needed, or since I read any. New, more intuitive features have displaced it.

With concepts in C++20, you get to choose whether templates are duck-typed.
Absolutely. The SOA record is important too, to cover queries not taking the happy path.

However, once I comform that everything is working alright, I crank up TTL to one day to reap some performance gains. For sites with low visits, and likely to not have the DNS query cached, the query latency can add up, and sometimes goes as high as 100ms if the recursive resolver has to take several round-trips to resolve the whole domain chain at EDNS level.
Not sure what's your point. Yes, deadlines are arbitrary just as most things are. That most things are doesn't change a thing about correct estimates being practically impossible and deadlines harmful.
breaking Eroom's law.
in the last 50 years the costs and timeline of drug development (clinical trials) were in increase. A phenomenon first published in nature and described as Moore's law reverse.
As of today it costs ar. $800Mio and it takes 12 years to bring a cancer therapeutic to the market.

I spent 8 years as a cancer scientist in drug discovery space, till I realised it doesn't make much sense to keep searching for more potential targets, if they will end up on a shelf for lack of clinical trials budget.

I am trying to solve this issue by platforming the infrastructure. Bringing web2.0 to clinical drug development.
I think it's unclear how much computational resources the uncompression steps take.

At the moment it's fairly fast, but RAM hungry. But this article makes it clear that quantizing the representation works well (at least for the VAE). It's possible quantized models could also do decent jobs.
The system would work if we simply provided low-cost schooling (taxpayer funded). It would keep folks from winding up with a predatory company who may or may not train you well, merely enough. You don't need to make the requirements easier - just lower the barrier to entry in a different way.

Not to mention that having enough well-rested folks with a CDL means that everyone is a little more secure, and we are more likely to have enough people to drive busses and transport goods in emergencies. (Yes, I know it'll take more than lowering the schooling costs to fix all this, but it is a start)
A pension invests the money into stocks, bonds, etc. It doesn’t just pay out more than you put in using incoming cash.

Owning land is not a ponzi because you actually own something. It would be ponzi if someone told you that you were invested in land but they had actually just pocketed your cash and used other investors’ buy-ins to pay you.
It is very rare that we actually work on something truly novel, and it’s even rarer that the majority of the task/project is novel. It’s really not that hard to identify something “reasonable” for most tasks, once you’ve broken it down. The pieces that are actually novel — you make an estimate to produce an estimate (how much work do you need to do before you get a handle over it?)

Of course, the further you go out, the more your error margins (and the less others naturally rely on your estimate, and the more likely you say something generic like coming soon in 2025)

But this notion that it’s all creativity born of the ether, as if you’re sitting around waiting for eureka to suddenly strike is complete bullshit.

There is the issue that external resources will latch onto your vague estimates like it’s the word of god, and try to hold you accountable to unreasonable degree, but that has nothing to do with your planning. Usual solution there is to figure out what feels reasonable, and then double it again for your boss — and double it again for the client (which you’ll probably lose a bit to negotiation). There’s also the issue that a single heisenbug can take stupid amounts of time to resolve… but that’s why you doubled up — you keep buffer for that kind of thing.

The vast majority of any project is just plumbing — creative or not.
Anyone knows the minimum requirements of the game?
1. would be better as a function, so you have:

- a nice explanatory name to it

- if the functionality changes then it is more probable that the name would change

- the code is hidden away if you don't care about the why (maybe you are looking for something else)
That's a really professional looking website. Rare for Linux distros. 10/10
A lot of the time what happens is the human side doesn't need to keep up.

They'll say "This actuator fails if driven past it's limit in hot weather after a rainstorm, and we have data showing that people can overdrive it accidentally in this condition".

Then they'll replace all affected actuators even if it costs millions .

Or they'll add a software patch to keep you from overdriving it.

What they don't do is say "It's probably fine, people just need to be more careful". If someone made a mistake once, someone else can make it again. Systems have to be built for the people who will actually use them, not theoretical elite users.

On occasion the technical fix has it's own dangers that need to be evaluated and you can't find any substitute for operators doing the right thing(See Gare de Lyon for the perfect example of multiple human errors by different people interacting with complex safety systems).

But only some careful analysis will tell you what's more dangerous.
"Every time a player makes a deposit, a Management Fee is subtracted from the overall game balance. This is how we finance and promote the game!" https://blog.ponzifarm.com/blog/game-rules/#management-fee
>The only fair model here is the one where 100% of apple's income comes from hardware sales alone. That is the only situation where you don't set up the user to be exploited by erecting these walls around what they can and cannot run on their own hardware.

And that is what we call the slippery slope.

Apple has created a successful product,
therefore developers want to make money from it,
therefore apple cannot charge a fee for access,
therefore apple cannot charge for developer tools,
therefore apple cannot charge for hardware (lest it makes the developers market smaller than it could be if phones were free)
Is there an explanation of why they abandoned it ? It seemed very cool at that time...
Body shops?

I guess you don't mean www.thebodyshop.com ???
> And in all my years of experience, I still am no closer to understanding how to fix that.

Does it need fixing? This may be a case of the cure being worse than the disease (the velocity loss outweighing the security risk).
Sure, threads exist, but they also make things more complicated. Simple batching can make a single thread go a lot further, was my point.
Stable Diffusion Models and Image Generation
Customers are stealing shopping baskets instead of buying bags in New Jersey
I was gonna ask why it was abandoned but then I read through the caveats, and well… yikes!
I’ve said it before and will say it again: as long as there are no painful legal consequences, including jail time, for the responsible managers and C-suite, such behavior will not stop.
Mark is not the subject. He is speaking of Rust and memory safety. I agree with him in general, that if a project requires C/c++ kind of capabilities then better to use Rust. But, if one doesn’t require Rust then I think one must avoid it by all means, because it’s such an investment into such a huge learning curve and such deep levels of complexity and mental burden.
I'm surprised the failure to deposit pension deductions isn't treated as a more serious failure. Knowing nothing about UK law... is that not some sort of crime?
The illegal part about them is usually the fraud aspect. You tell your investors one thing but then do something else.

One may argue that that's part of the definition of a ponzi scheme, i.e., if you are open about it then it's not technically a ponzi scheme sincs it's lacking that particular necessary characteristic.

(With that definition, ponzifarm is not a ponzi scheme.)
I'm a type of person that can't live without deadline. If my mom doesn't say "today" in her order, I'd forget to do it.
I can imagine some uses for this. Imagine having to archive a massive dataset where it’s unlikely any individual image will be retrieved and where perfect accuracy isn’t required.

Could cut down storage costs a lot.
> Estimation, planning, and progress tracking are difficult skills that must be learned, but they’re not impossible.

Judging by the constant stream of overdue and overbudget projects in more traditional businesses like construction, which are significantly stricter in terms of regulation, planning and have been around forever compared to software engineering, I'm not convinced accurate deadlines are possible.
There is NaSC as well: https://parnold-x.github.io/nasc/
https://www.phoronix.com/review/python-311-benchmarks/4
I think this is a silly idea. There are still loads of questions surrounding Rust. Especially about it's practicality... There are articles denigrating the likes of the trait and async systems on HN almost every day. And even ignoring that argument, any language is viable, so long as it can be used to build what you want to build.
This.

And when it isn't, everyone suffers. When it is low-cost to free, you get folks that want to be doctors and qualify. When it costs more than a nominal fee, you take those folks and sort them by whoever can afford it, which may not be the best candidates. It also makes it more of an "elite" profession since poor folks are priced out of it.

By free, I do mean low-cost to free for the student and funded by taxpayers. Educated people benefit society at large, and especially so when folks are doing public service of different sorts (like doctors).
> Half of the time I want to press right-click or even left-click on the
> touch pad it actually registers as middle-click

Are you sure that's not a hardware issue? This doesn't happen in other OSes on the same hardware?
Taiwan is closer to China (~180km) than Tasmania is to Australia (~240km)
I’d make the opposite argument. Losing ETH will allow US devs and companies to work on actual technologies which are useful for society broadly.
Apache Shenyu Project Graduates
Apache Shenyu API gateway graduates from incubation to top level project
With an USB C stick, you could have a knock algorithm that involves plugging it in with a particular orientation pattern as well.
What’s H2?
Yes, I think it's clear that he's guilt from the games I've seen, the low mistake rates etc., and it surprises me that Ragan disagrees.

Unfortunately I can't spend the time actually having a look at Ragan's analysis.
My googling doesn't show any quote that resembles that, can you give a source?
> Why would small developers work to prop up a giant who already has so much power imbalance

Because the alternative to fighting that power is wielding it. Coalitions are temporary alignments of interests. They're a hallmark of democracies. Their mechanics are highly selective against dogmatists; generally a good thing. Unfortunately when it comes to communities with a high concentration of purists, this knack for pragmatism can backfire by driving disillusionment.

Put another way: do you see small developers benefiting more by allying with big developers against Apple?
I suspect you also have detailed specifications and requirements to allow estimation and planning. Outside of hardware-based environments, this is often missing and engineers that push for it are dropped because they are not 'autonomous' enough.
I’ve worked at a $100 million revenue online company that didn’t make any profit. OP says money is tight after covid, so seems like it the business is connected to a (physical) market that was affected by the pandemic. He says there is an extensive roadmap by a management team that are not familiar with the technical details, so it seems like the technology is not the core business.

It’s not difficult getting to a high revenue fueled by aggressive and expensive acquisition using money from investors who gets dazzled by growth numbers, but if your customer lifetime value is low and you’re not a pure SAAS business which means margins won’t automatically improve with scale, turning that company profitable can prove very difficult.
I sell both my software as OSS, and as commercial software with a delivery through a corporate appstore. Companies are happy to pay.
Fortran is still in use so im not worried that i use c++
I agree, knowing all details of the language/framework you're using is the key to amazing productivity. In IT terms you could compare it with the performance gains you're getting from holding data in cache instead of querying them on demand over the network.

However it isn't always possible. Nowadays a typical dev team uses 10 different frameworks or more, and after a couple of years some of them will have changed.
Mission critical is almost meaningless when applied to the entire software industry. It’s whatever each company wrote their core software in. For twitter Ruby was mission critical, for Facebook it was PHP.

Security critical is also rather meaningless, because the idea that a specific language must be used to write secure software is something that the Rust community is claiming but is otherwise unproven and not particularly popular as an opinion. In fact I’ve seen many counters that nearly any GC language offers the same security guarantees as Rust.

Finally, there’s the mighty inconvenient fact that a large amount of safety-critical software (a well-defined term and domain!) is written in C and C++ with a track record of multiple decades while Rust is completely unproven.
If you are building a software (or anything else for that matter) for a specific event that has a starting date carved in stone then you can't avoid deadlines.

Take some sporting event for example. Let's say F1 competition. You must have racing car ready by the start of the season. Having it ready two weeks latter is not an option.
They're still far more complicated than a layman might guess after years of hearing that simple is always better.

I'm guessing things like fly by wire would be automatically assumed to be unsafe by a lot of people.

When cars get features that are anything like what goes into planes, people tend to get upset and say "I'm not an idiot, you should make cars expensive and complicated just because some drivers can't stop crashing without a computer".
> The way it was done before was to use the "virtual" prefix keyword for virtual functions across the entire class hierarchy. Merely a discipline which was enforced religiously via coding guidelines

No, that did not enforce safety or solved the refactoring problem I told you. It seems you do not want to listen that override fullfills the case where you assert that you are overriding (and it will be a compile error). You have a misunderstanding and a wrong mental model for how virtual worked. It did not enforce anything, just declared a virtual function, no matter it was new or an override. virtual can introduce a new virtual function by accident.

Example:

class MyClass {
public:
virtual void f(int) {}
};

class MyDerived : public MyClass {
public:
virtual void f(int) {}
};

Refactor:

class MyClass {
public:
// NOTE: signature changed to double
virtual void f(double) = 0;
};

class MyDerived : public MyClass {
public:
// FORGOT TO REFACTOR!!! STILL COMPILES!!!
virtual void f(int) {}

//void f(int) override {} // COMPILE TIME ERROR!
};

> You are making inflammatory statements without understanding what has been written; it is not appreciated

No, I was not. I was just showing you do not know how the mechanism works with facts.

Above you have an example of why what you say does not work. I would recommend to talk more concretely and not to make too broad statements about tools you seem to not know in detail but it is up to you, I would not stop you. Just a friendly recommendation ;)
the paternalistic moralism has nothing to do with safety, but absolutely more with creating the hype and keeping it proprietary ofc
Depending on the contract, missed deadlines usually have penalties. There is a reason for deadlines, especially for complicated projects. The reason being other people have to plan their time to make use of their available resources profitably.