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

Yeah its called the expectations, consistently bad is predictable

software that has "good" and "bad" parts in unpredictable


> software that has "good" and "bad" parts in unpredictable

Software that has only "bad" parts is also very unpredictable.

(Unless "bad" means something else than "bad", it's hard to keep up with the lingo)


that's why I write the first parts of my comment

your example is just bad code that unpredictable


And I disagree.

My assertion is that software that has only bad parts is way more unpredictable than software that has both good and bad.

For multiple reasons: because "bad" is not necessarily internally consistent. Because it's buggy.

Unless, again, "bad" here means "objectively good quality but I get to call it bad because it's not in the way I like to write code".


So we should all write bad code to keep it predictable? raising the quality of the codebase is unacceptable under this premise.

Possibly. Probably even.

High quality and consistent > Low quality and consistent > Variable quality and inconsistent. If you're going to be the cause of the regression into variable quality and inconsistent you'd better deliver on bringing it back up to high quality and consistent. That's a lot of work that most people aren't cut out for because it's usually not a technical change but a cultural change that's needed. How did a codebase get into the state of being below standards? How are you going to prevent that from happening again? You are unlikely to Pull Request your way out of that situation.


"So we should all write bad code to keep it predictable?"

its true and false at the same time, it depends

here I can bring example: you have maintaining production system that has been run for years

there is flaw in some parts of codebase that is probably ignored either because

1. bad implementation/hacky way

2. the system outgrow the implementation

so you try to "fix" it but suddenly other internal tools stops working, customer contact the support because it change the behaviour on their end, some CI randomly fails etc

software isn't exist in a vacuum, complex interaction sometimes prevent "good" code to exist because that just reality

I don't like it either but this is just what it is


Nvidia losses 200+ billions on recent weeks because Google TPU actually good and market realize that Nvidia have no "moat"

this is just panic buying to make stronger foothold


if we use your logic then every law written would be failure since at some point people would discover loophole/flaw that would get abused

the fix is we use more ambiguous words or just stronger government control

see how China "control" capitalist on this case if you want absolute government control


isn't it true though that laws that have frequently abused loopholes that effectively go against the spirit of the law are indeed failures? isn't that the entire purpose of having lawmakers who are constantly evaluating such things?

Yeah that is the point of having law maker

my point is making a law that a "future proof" is impossible, since guess what???? Human just cant account for every possible future scenario


You could see it as a failure to enforce the spirit of the law. Judges have the power to make it right and refuse the loopholes.

"Is there any sign telling Astral is actually making money via uv? How sustainable is it?"

maybe they would get acquihire like Bun ???? idk, somebody defo needs this


its nice way to say Indians

they probably would using AI to review the code also, like cmon this is MS we talking about

Yeah the only problem for me that Cloudflare is so dominant and Tech x monopoly is not a good combination

also they are becoming cloud service provider that can really threaten many big player because from bandwidth alone is real game changer


They really are quite spooky

wait, so its not affect apple users ????

Google just sent me a email today that Google would push forward


I just received an email from Google Play Developer today morning that they will not be activating the age verification APIs (they will throw an exception) because of the injunction, so there's nothing Apple specific about this.

> they will throw an exception

Reminds me of HTTP error code 451, Unavailable For Legal Reasons.

I can imagine some future programming language with a LegalRestrictionException.


generous of you to predict apple only make it 50% expensive

less than 30 bucks for entire year, insanely cheap

(I know that people must pay it on privacy) but still for maybe playing around with still worth it imo


Are you saying the reason they are offering it so cheap is because they are training on user data?

They say they dont train on your inputs. But their tos dosent prevent them from doing that.

My guess is they do train on slightly altered/obfuscated user data.


their model are cheap to run but not cheap $30 bucks a year

so yeah its both


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

Search: