LLMs can definitely write programming languages. I used Gemini CLI (once it came, AI Studio before that) with Gemini 2.5 Pro to create one with Rust and LLVM:
This was completely vibe coded - I never had to edit the code, though it was very interactive. The whole thing tool less than a month of some evenings and weekends.
(Note: it’s ugly on purpose, as I’m playing with ideas around languages that LLMs would naturally be effective using.)
I’ve also experimented with using rust to create a new programming language where I vibe coded (eg never wrote myself). My opinion is that it’s quite capable with disciplined management.
Stopped reading after the patently false “communist inspired universal basic income”. A casual knowledge of the topic would lead one to understand it’s a capitalist, Milton Friedman inspired, idea.
Hi all - I'm the head of engineering at GitHub. Please accept my sincere apology for this downtime. The cause was a bad deploy (a db migration that changed an index). We were able to revert in about 30 minutes. This is slower than we'd like, and we'll be doing a full RCA of this outage.
Thanks for taking the time to personally give a status update while things are on fire. I hope you and all the others who are dealing with this emergency will have an especially restful weekend.
I was just griping on Twitter yesterday about how many developers won't immediately revert an update that causes downtime, but will actually spend time trying to solve the problem while Rome burns.
Sometimes reverting is not reasonably possible--suppose you updated a database schema and clients immediately started filling it with new data that would have no home in any backup--you'd end up in another unanticipated state.
@keithba I have build a - private - GitHub action around https://github.com/sbdchd/squawk - for Postgres - that lints all our migrations files on each PR. The action extract raw SQL from the codebase and pass them into squawk.
It catches many exclusive locks migration or missing `index concurrently` that would otherwise have been release to production and causing downtime or degraded service. Maybe something you should start doing.
GitHub uses MySQL, not Postgres. They built the best-in-class online schema change tool gh-ost [1], and have a custom declarative schema change execution system built around Skeema [2], which contains a wealth of linters [3].
Even so, it's always possible for an engineer to submit a schema change which is detrimental to performance. For example, dropping an important index, or changing it such that some necessary column is no longer present. Linters simply cannot catch some classes of these problems, as they're application/workload-specific. Usually they must be caught in code review, but people make mistakes and could approve a bad change.
Disclosure: I'm the author of Skeema, but have not worked for or with GitHub in any capacity.
Most of the services are free. You don't have to use the test service if it is outside of your budget. For instance, you could push your successful builds directly to beta testers, if you'd like.
We've gone out of our way to make sure everything in the product is accessible via our REST API, and we also have a CLI you can install from npm.
Just curious, why is the testing so expensive? I've seen other products that provide this same testing service and they are all very expensive. Is it because of the hardware required, an ROI thing, a first to market thing, or something else?
We are investigating what it would take to support RN with Windows. I'm a huge RN fan (and we include CodePush inside of App Center.) If you have a moment, shoot me an email as I'd love to ask you more about your scenarios.
Hi - author of the blog post here and PM on the team!
We are very proud of what we've built here. Regardless of how you built your app (Swift, Java, React Native, Xamarin), we offer CI, releasing to your beta users and the app stores, Crash reporting, analytics, and even push messaging. Let us know your thoughts!
Why did Microsoft create this? Specifically, I'm not interested in the "because we love developers" story, I'm interested in the "this is strategic for Microsoft now and for the next decade because" story.
Why did they create it? It's $40 - $99 a month for premium usage and has the potential to make tying in with other MS products like azure, easier. Seems like plenty of reason to me.
The team is extremely passionate about creating developer productivity tools. App Center's creators include the founders of HockeyApp, Xamarin Test Cloud, and CodePush. This is something we were all iterating towards individually, and when we met up at Microsoft, we realized we now had the team and ability to make it happen.
Microsoft is very serious about creating amazing developer tool across any app, platform, and language for a variety of reasons. Making Azure the most productive place to power your app is part of it, of course. But, in the long run, the easier we make development, the more the world benefits.
Thanks, that makes a lot of sense to see this from the background of HockeyApp, Xamarin Test Cloud, and CodePush coming together. Ignore the non-answer guy, this is a totally sufficient answer in my opinion.
They don't yet support it and I don't think they will have strong Ionic integration as we haven't talked with them about it.
However, we recently rolled out Ionic Pro which is similar to App Center, but focused 100% on Ionic apps. Adoption so far has been strong despite only being out a few months, and we're investing a lot in the product. Hope you give it a try and we're excited to have some extra validation from App Center!
Interestingly, the new deeper HockeyApp integration recognized that my apps were built with Cordova, but then just shows a "Cordova support coming soon" page for Android and iOS. (The Windows Cordova app was recognized as UWP rather than Cordova. The Windows Electron app I have wasn't recognized at all, but that is unsurprising.)
Here's a scenario I'm dealing with that must be fairly common. A mobile app running against an Azure backend, where users can also access the app through a SPA on their desktop. I don't want my analytics data spread out over multiple analytics services, so can this analytics service support SPAs as well? Bonus points for being able to track the same user across mobile + SPA.
Right this second, we offer the ability to export your analytics to Azure Blob Storage, and Application Insights, where you can then join the App Center analytics with other data.
We are looking at what we can do to make the SPA + mobile workflow super easy, though. Stay tuned on this. In the meantime, feel free to reach out to me as I'd love to ask you some more questions.
Looking forward to hearing about this. On a similar note, why not collect errors from the backend and SPAs too... after all a stack trace is pretty much a stack trace wherever you are. I get that this isn't the market you're serving, but if you don't do this your user is likely to end up using two very similar error reporting services for the same project.
https://github.com/GoogleCloudPlatform/aether
This was completely vibe coded - I never had to edit the code, though it was very interactive. The whole thing tool less than a month of some evenings and weekends.
(Note: it’s ugly on purpose, as I’m playing with ideas around languages that LLMs would naturally be effective using.)