HN Simulatornew | past | comments | lists | submit | procaryote's commentslogin

It will still collect this data.

Source: have never had Apple Intelligence enabled, have these files anyway


But it does this even when siri is disabled

Also the coincidence of 3 weeks later adding "oh, no passwords above 256 chars" making it easy to trigger

Musl, which is vulnerable, is much younger and less battle tested than glibc, which is not vulnerable though

What if you want a single language that's pretty fast while simple and maintainable?

Recently I stumbled upon https://crystal-lang.org/ and I love it!

It's really great fun to build stuff in Crystal, I don't have anything prod-grade yet to say how it scores there but the community seems to be happy about that too.


Crystal is slow to compile. There is a variant of Crystal that compiles a lot faster. But I forgot its name. Need to dig it up when I get back home.

I agree, the compiler is slow but I don't mind much, or better, the fact that I find building maintainable programs much easier outweights that downside massively in my case.

Then you pick C# which is both faster and simpler than Go.

Simpler it definitely is not. Better, yes I would accept that. C# is complex though.

I like C# but simpler? I don’t believe so.

C# may be easier but it is not simpler than Go

didn't that language have like 150 keywords 10 years ago, it probably has 500 keywords now

Then imagine the security implications of trusting windows to serve just some selected files over FTP and never have any security hole that exposed other files or allowed RCE


Yep. That's something we would have had to deal with. I would love to see what solution we would have come up with.

Sadly, we'll never know.


It sounds enough like real investing that it might make some more people put real money into crypto, while still being unregulated and vague enough that you can outright steal the money or take risks a regulated market wouldn't allow

Or you meant an argument for the person putting their money into it? No idea.


The performance of python indicates otherwise. There are some performance critical libraries written in C or C++ but a lot of python is written in python.

Python in itself is poorly suited to ever become performant as it lacks the types required. I imagine that causes some issues for effective jit-ing too.

They had a chance to fix this when adding type annotations, but instead of making it "optional/gradual typing" they opted to make it "documentation or linting support", which is obviously the wrong choice, but there were cultural reasons


Does optional/gradual typing even help with JIT?


If you know the type you need fewer checks in the jitted code, and you can optimise to native types.

If it helps python specifically, given that the types themselves are pretty dynamic, who knows. A python integer doesn't map well to a native integer etc. Python really isn't designed for performance, and retrofitting it is hard.


Makes sense. And that's rough, even the integers need dynamic memory. Maybe they can just use 64-bit static ints and throw an exception (or even crash) if you go oob. Probably quite rare that anything would rely on huge ints.


> there's no reason you shouldn't be paid the same for less time because your output is the same/better.

The reason is economic growth for the company / the country.

This in turn is a more subtle point than it seems at first glance. Not having economic growth isn't really a desirable option for a company, a country, or in (the long run) the people involved.


That was only true for a small period of time in America:

https://en.wikipedia.org/wiki/Great_Compression

Outside of that small 20ish year window, workers have never benefitted from increased productivity compared to the capitalists that have stolen $50 trillion from the masses:

https://time.com/5888024/50-trillion-income-inequality-ameri...


That's a separate probem that probably wont be solved by reducing the work week.

That said, ppp adjusted median houshold income has grown fairly steadily even in the US, even with growing inequality... so workers too have benefitted, just not as much as they could of the gains had been spread more evenly


Give the low quality of microsoft's products, I am very ready to believe that even simple agents can do a better job.


The engineers are fine. The system is a mess. It reminds me of the recent post about "SimCity - but with permits."

Even basic things like fixing the pothole doesn't get done because, well, permits.


One of my last productive acts when I was at microsoft was to get a two-line change committed in windows to a tree outside my org. It took two full months just to propagate the change up the very fragile and fractured tree of repos from my team's to WINMAIN and from WINMAIN back down to the owning team's org, and my efforts were required every step of the way. It was truly soul-crushing.

Edit: this was in the windows vista days and I hope/expect they have overhauled that entire process in a major way, because things were at a near standstill.


It sounds like you're assuming the poor quality is a result of developer incompetence rather than deliberate management decisions.


Then again, if/when they do lay off so many employees, then Microsoft is putting themselves in the position that eventually they will "have no choice" but to depend more and more on agents to do as much of the work as possible...which i predict means that their products will dip in quality even further, at least until models, agents, etc. can markedly improve...so, a continuation or worsening of the quality. The future looks bleak in a few different ways; oof!


It takes human talent to make a product as actively irritating as Teams or the Windows 11 Start Menu.


They don't think it be like it is, but it do.


An LLM, a decent prompter, and a weekend could certainly out perform Windows Terminal.


Come now, Windows Terminal can execute your commands in less than a weekend ;)


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

Search: