| ▲ | ksec 6 days ago |
| I am hoping we have even more surprises in Rails World in two weeks time. And may be a glimpse of ZJIT? It is not just Ruby and Rails has gotten faster, CPU performance and core count has been getting cheaper. One thing I forgot to post last time in the GitHub CEO step down thread. I am hoping Microsoft won't force GitHub to move away from Ruby Rails. I remember there were some noise early on during the acquisition M$ wanted to get rid of it. |
|
| ▲ | FinnLobsien 6 days ago | parent | next [-] |
| Re: GitHub. IF they do a rewrite, that should buy us at least 5 years, based on my experience with large-scale rewrites lol |
| |
| ▲ | givemeethekeys 5 days ago | parent [-] | | Even with AI? | | |
| ▲ | throwawayoldie 5 days ago | parent [-] | | In that case, it'll only take 8 years. | | |
| ▲ | mrits 5 days ago | parent [-] | | We need a new 80/20 rule. I propose a 90/0. You get 90% done quickly and the other 0% over the next few years . | | |
| ▲ | mdaniel 5 days ago | parent [-] | | We actually already have one of those, and it still fits just for a different reason: > The first 90% is easy/fast/cheap, it's the second 90% that's hard/slow/expensive Since most of the generative approaches treat code as disposable, then the second (and subsequent) 90% approaches just throw it away and start over. It's like all the awesome parts about a rewrite, with all the awesome parts about "it was rewritten because no one understood it" | | |
| ▲ | throwawayoldie 5 days ago | parent | next [-] | | I always heard it as "The first 90% of the work takes the first 90% of the time, the remaining 10% of the work takes the other 90% of the time." But yeah. | |
| ▲ | mrits 4 days ago | parent | prev [-] | | Ha! I've never heard of that one |
|
|
|
|
|
|
| ▲ | tekknolagi 5 days ago | parent | prev | next [-] |
| Re: ZJIT: all development is happening in the open in the zjit folder of the ruby/ruby repo. You can follow along! |
|
| ▲ | stackskipton 5 days ago | parent | prev [-] |
| Having been on Microsoft acquisition before, generally they encourage .Net usage for greenfield if possible but it’s pretty gentle encouragement. I’ve heard they are getting pretty pushy against C++. |
| |
| ▲ | voidfunc 5 days ago | parent [-] | | Really depends on the org you're in and what ecosystems you need to work with. Almost everything we write is Go based at Microsoft in my org. |
|