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

Non trivial part was that GitHub had better UX than Hg-supporting forges.

People learnt git to use GitHub


I originally thought to write "Git winning might be as simple as linux and github using it.", before I decided to shorten it:) Yes, I think that was a significant factor.

For me it's about 2 days now? It was available pretty much the same moment it the blog post landed

There's apparently a bit of mess regarding intersection of what options you have enabled on your account (as in, workspace license) and country availability

Ha yes. I just spent 36 Australian dollars upgrading myself on our workspace account.... now I have a model called "Carbon", I still have "Hydrogen" but not "Neon".

Ever worked in a big company where internal nomenclature becomes an obstacle for external participation? This is that.

And this product launch is a failed activation for me


Capacity bottlenecks made them not include certain models in "promotional" accounts, i.e. ones that are currently on various promotional sales accounting.

There is a lot of those, one could say is that Google is trying to curb their previous overgenerosity


32bit addressing was supposed to be temporary stopgap with v4 being retired by 1990, for example

Nothing is more permanent than a temporary solution.

I read the other day that the 8086 and its ISA was a “temporary solution”. 50 years and counting on that one too.

The problem with "rewrite this in Rust" is more that Rust has laughable amount of Tier 1 platforms.

Now, rewrite in Ada, given that GNAT supports the same targets as rest of GCC...


Completely agreed but I’ll take any improvement at this point however small

There's gcc-rs too but at a slower pace than mainline/official Rust.

On security, both clang and gcc have security flags for this and Boehmgc (or even mimalloc) can be temporally used as a replacement to avoid nasty surprises.


BoringSSL is somewhat widely used because Google baked it into their projects (and partially by Microsoft, I believe they made a FIPS variant of it and used it in Go?)

LibreSSL had, IIRC, problem known as OpenBSD-itis. Or to put it bluntly, the developers didn't really care about any other platform. Plus I will admit that being the first and loud "we will fix openssl" they got linked with some loud PR that showed less understanding of code they mocked than OpenSSL developer who wrote it, and that's really impressive when you consider some of the mocked code fragments were results of developers never reading foundational documentation for a platform


> LibreSSL had, IIRC, problem known as OpenBSD-itis. Or to put it bluntly, the developers didn't really care about any other platform.

Well put. This is the crux of the issue.

If you ever try to use libreSSL you rub up against so much friction that most projects would hammer out early.


There's LibreSSL portable. It worked better in legacy machines I own, go figure.

During late 3.x timeframe Google has been explicitly adding Jujutsu support across the agent stack in Antigravity, but it's not fully exposed unlike Git yet

That's also true, the Antigravity harness may have been a contributing factor here. I use the internal Antigravity fork which uses JJ heavily because JJ is a core supported VCS interface for us.

Lots of JJ in public antigravity changelogs, it just seems not wired into UI well

That tracks. I've not used JJ in public Antigravity, only in the internal fork, and that's not JJ for git, but JJ for Piper, so I don't know how much commonality there is.

-Cyber variants of the models exist but you need to be in Fairwinds and that's AFAIK not easy thing.

The company I'm leaving due to change of projects I am 95% sure has access, but only from a part of the company that has extra security checks and blacked out windows :V


Interestingly, agy 1.5.13 (but seen that with 1.5.12 already) now works hard to coalesce multiple steps in tool calls, just like Opus does - i.e. building small bash one liners with separators

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

Search: