Hacker Newsnew | past | comments | ask | show | jobs | 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.


Facebook is actually a good counterexample to the claim that language choice doesn't matter. PHP's execution overhead was significant enough that Facebook developed HipHop, a PHP-to-C++ compiler, which reduced their average CPU consumption by around 50%. They subsequently developed HHVM and Hack to address further performance and maintainability issues.

That doesn't mean PHP prevented Facebook from scaling, just as C# didn't inherently prevent Orkut from scaling. But being able to scale an application and being able to scale it efficiently are different things. You can compensate for language and runtime inefficiencies with more hardware and better architecture, but that doesn't make those inefficiencies irrelevant.

C# would arguably have given Facebook a better starting point in terms of execution performance and static typing than PHP, but claiming they could have run the original application unchanged today is a bit of a stretch. Facebook's architecture, infrastructure and requirements have evolved enormously, regardless of language.


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.


From the original paper abstract:

“Claude review raises Codex drafts from 71.6% to 89.7%; Codex self review raises them to 84.5%. The reverse direction does not pay off: Codex reviewing Claude drafts drops the pass rate from 91.4% to 82.8%, and Claude self review leaves the 91.4% baseline unchanged.”

The highest pass rate was to use just Claude, at 91.4%. Claude reviewing Claude did not improve the pass rate.


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


Now if they could just extend the 50% weekly limit increase promotion which will otherwise expire on July 19th at 11:59PM Pacific, they might actually remain competitive.


They extended that until Aug 19th


Finally! Definitive, tangible, tactile proof that we're near the top of the bubble. /s


The triple whammy of (a) two layers of annoying timed usage windows, (b) constantly changing model availability windows, and (c) random unpredictable usage resets, is absolutely brutal for anyone who is trying to plan methodically and be efficient.

One minute I'm trying to use an entire week's worth of quota in less than 24 hours, then moments later I read the deadline has been punted and I have only 25% remaining to last me an entire week. This alone is enough for me to switch back to Codex once my current Claude sub ends.


Yeah I'm getting fed up with this dance. Especially when I'm trying to max out credits over a weekend.


Apparently, not even Anthropic, otherwise they could have done us all a favour by announcing it sooner.


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

Search: