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

The original Orkut site was written in C# - it was very slow and couldn't handle the growth. Orkut was only a big success in countries like Brazil and India where internet connections were already so poor that nobody noticed how slow the site was.


> The original Orkut site was written in C# - it was very slow and couldn't handle the growth.

These are orthogonal facts presented as if they were related.


Not entirely orthogonal. Orkut's original C#/ASP.NET/SQL Server stack was an awkward fit for Google's predominantly Linux-based infrastructure, which made scaling and operating it more difficult. Almost all of Google's other web services were written in tight, optimized C++. David Jeske, Orkut's former technical architect, described problems with the .NET runtime, difficulties integrating with Google's infrastructure, and an eventual migration to Java and C++.

That doesn't mean C#'s execution speed was the primary bottleneck. In fact, Jeske's team reportedly made dramatic performance improvements while retaining .NET. But arguing that the choice of technology had no relationship to Orkut's scalability problems is just as misleading as blaming everything on C#.


The statement just mentions C#. Java is amazing and fast in capable hands, but so is C#. Of course you can have problems with a stack, but that's nothing to do with the stack in this case, but rather a skill problem associated with that stack.

If my current employer started having new software written in C instead of Java today, and while C has many problems, the problems we'd have would be all self-inflicted skill issues, not a direct problem with C.


And facebook was written in frikkin PHP. That means it was not C# that made it slow, probably just bad programming.


PHP did make it slow. They eventually wrote a tool to transpile PHP to C and then compile down to native.


Sure, PHP was obviously a very poor choice as an main language. Facebook still today suffers (i know people at facebook), and even pured in millions for HHVM and Hacklang.

If they had opted for C# they could probably have been able to run it as-is today.


[flagged]

Obviously. But a sane languge could/would just require better design and performance tuning. Not reinvent a new languge kind of change. At scale you need to design carefully no matter if its Java, C or Rust. But you mostly can keep the languge and not write you own.


Deactivating my LinkedIn account was one of the best things I did for my mental health. I have not missed it even once, and my career has never been better.


Yet another scramble to use up weekly quota before an Anthropic cliff. This isn't fun.


Israeli hegemonic ambition. Zionist funding of Trump's campaign. Corrupt profiteering from market manipulation. Distraction from the Epstein files. Gullibility of a large fraction of the US public. Trump's ego and stupidity. And when a nuclear superpower starts a war like this, there's not much anyone else can do to stop it. The result: a massive strategic blunder for the US, the true cost of which may not be fully understood for many years.


How well do models like these generalize to robot embodiments they weren't trained on?


Why cross-entropy follows a curve is fairly trivial to understand:

https://www.youtube.com/watch?v=GlYgs6v2YfU

In general, motion planning multi-axis systems is NP-Hard. Have a great day =3


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

Search: